MySQL Invalid Status

Problems with the Mac OS X version of XAMPP, questions, comments, and anything related.

MySQL Invalid Status

Postby gegeMartinelli » 15. January 2017 11:42

Hello,

I'm facing with a strange problem.

I'm running XAMPP 5.6.23.0 under Sierra, I have created plists to start MySQL and Apache automatically. This works fine (Applications work).
However to make the MySQL Plist working I had to do : chmod 600 my.cnf

The MySQL plist is as follows :

Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>EnableTransactions</key>
<true/>
<key>Label</key>
<string>apachefriends.xampp.mysql.start</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/XAMPP/xamppfiles/xampp</string>
<string>startmysql</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>WorkingDirectory</key>
<string>/Applications/XAMPP/xamppfiles</string>
<key>KeepAlive</key>
<false/>
<key>AbandonProcessGroup</key>
<true/>
</dict>
</plist>


If I start the control panel, the MySQL status goes to "Checking" then "Stopped" but the Apache status is "Running". This is wrong because MySQL works.

From the control panel, If I stop all, obviously all server status go to "Stopped". However, MySQL remains active (because my applications which connect to any data base still works).

Now, If I'm trying to restart MySQL from the control panel, status goes to "Starting" and after a while (about 20 seconds) returns to "Stopped". At this time, I checked the err log file, and noticed a loop for messages written into this file (see bellow). That I do not understand.

So I tried to push further my investigations.

I removed the PList from /Library/LaunchDaemons, and just tried to start MySQl from the control panel. This time everything went OK. It seems to me there is a sort of incompatibility with Plist and the Control-panel procedures.



Any idea ? Thanks a lot in advance

Gégé

macbook-pro-de-gerard.home.err

2017-01-15 10:53:59 1843 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/macbook-pro-de-gerard.home.pid ended
2017-01-15 11:02:39 1183 mysqld_safe Starting mysqld daemon with databases from /Applications/XAMPP/xamppfiles/var/mysql
2017-01-15 11:02:39 140736210990016 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2017-01-15 11:02:39 140736210990016 [Note] /Applications/XAMPP/xamppfiles/sbin/mysqld (mysqld 10.1.13-MariaDB) starting as process 1325 ...
2017-01-15 11:02:39 140736210990016 [Warning] Setting lower_case_table_names=2 because file system for /Applications/XAMPP/xamppfiles/var/mysql/ is case insensitive
2017-01-15 11:02:39 140736210990016 [ERROR] mysqld: Can't lock aria control file '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control' for exclusive use, error: 35. Will retry for 30 seconds
2017-01-15 11:03:10 140736210990016 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/Applications/XAMPP/xamppfiles/var/mysql/aria_log_control'
2017-01-15 11:03:10 140736210990016 [ERROR] Plugin 'Aria' init function returned error.
2017-01-15 11:03:10 140736210990016 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: The InnoDB memory heap is disabled
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Memory barrier is not used
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Using SSE crc32 instructions
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Completed initialization of buffer pool
2017-01-15 11:03:10 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:10 140736210990016 [Note] InnoDB: Retrying to lock the first data file
2017-01-15 11:03:11 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:11 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:12 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:12 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:13 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:13 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:14 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:14 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:15 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:15 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:16 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:16 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:17 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:17 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:18 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:18 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:19 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:19 140736210990016 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-01-15 11:03:20 140736210990016 [ERROR] InnoDB: Unable to lock /Applications/XAMPP/xamppfiles/var/mysql/ibdata1, error: 35
2017-01-15 11:03:20


it loops forever.... but if I exit from control panel (stop) the loops terminates and the following messages are added to the error log.


InnoDB: Error number 35 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2017-01-15 11:28:11 140735724544960 [ERROR] InnoDB: Can't open '/Applications/XAMPP/xamppfiles/var/mysql/ibdata1'
2017-01-15 11:28:11 140735724544960 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-01-15 11:28:11 140735724544960 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-15 11:28:11 140735724544960 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-15 11:28:11 140735724544960 [Note] Plugin 'FEEDBACK' is disabled.
2017-01-15 11:28:11 140735724544960 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-01-15 11:28:11 140735724544960 [ERROR] Aborting

2017-01-15 11:28:11 883 mysqld_safe mysqld from pid file /Applications/XAMPP/xamppfiles/var/mysql/macbook-pro-de-gerard.home.pid ended
gegeMartinelli
 
Posts: 13
Joined: 23. May 2013 15:34
Operating System: Windows Vista

Re: MySQL Invalid Status

Postby Nobbie » 15. January 2017 12:03

I dont have any Apple hardware/software and i dont know plist at all, but for me it looks as if plist runs Xampp with insufficient rights and/or as an insufficient UserID.
Nobbie
 
Posts: 9800
Joined: 09. March 2008 13:04

Re: MySQL Invalid Status

Postby gegeMartinelli » 15. January 2017 12:22

Thanks Nobbie for the reply.
I do not understand your remark because when using the Plist, MySQL starts pretty well.

My problem is only with the Control Panel (manager-osx) which provides me with an wrong status and worst, it creates a loop wen trying to restart the server.

Of course, I do not have the same problem under Windows because one may install MySQL and Apache services to start server automatically.
gegeMartinelli
 
Posts: 13
Joined: 23. May 2013 15:34
Operating System: Windows Vista

Re: MySQL Invalid Status

Postby Nobbie » 15. January 2017 12:46

gegeMartinelli wrote:I do not understand your remark because when using the Plist, MySQL starts pretty well.


Then simply use Plist only, i thought, that is the problem. Seems i got it wrong.

gegeMartinelli wrote:Of course, I do not have the same problem under Windows because one may install MySQL and Apache services to start server automatically.


I dont use WIndows either, i am working on Linux since many years. But I know that also on Windows are many known problems with process and user rights (i.e. all services are started by "SYSTEM" user) especially when HTML/PHP files and/or Databases are moved onto Network Drives etc. - in that case users very often struggle with similar problems as you currently do.
Nobbie
 
Posts: 9800
Joined: 09. March 2008 13:04

Re: MySQL Invalid Status

Postby gegeMartinelli » 15. January 2017 15:53

Nobbie wrote:
Then simply use Plist only, i thought, that is the problem. Seems i got it wrong.


Yes that I'm doing, I reported my problem, because it could be useful if XAMPP developers read this forum, and try to fix.
gegeMartinelli
 
Posts: 13
Joined: 23. May 2013 15:34
Operating System: Windows Vista

Re: MySQL Invalid Status

Postby Nobbie » 15. January 2017 22:09

gegeMartinelli wrote:because it could be useful if XAMPP developers read this forum, and try to fix.


This wont happen ever, as there are no "Xampp developers". Xampp is a distribution (only), BItnami only builds the packages and add some configuration files. There is no development, all the tools have their own development. Therefore, there is no "Xampp developer", as Xampp is not a software product. It is a distribution. Not more.
Nobbie
 
Posts: 9800
Joined: 09. March 2008 13:04

Re: MySQL Invalid Status

Postby gegeMartinelli » 16. January 2017 10:48

I used the word "developers" to be short. In fact I know that they are just integrators and XAMPP is just a package. But in the other hand, they also have developed a few lines of code (a few procedures, the control panel window, and so forth). This is exactly the point. If they have time, perhaps they may look at the problem I got and understand where it comes from.

Anyway thanks a lot for all advices you gave to me. Have a nice day.

Gégé
gegeMartinelli
 
Posts: 13
Joined: 23. May 2013 15:34
Operating System: Windows Vista

Re: MySQL Invalid Status

Postby Nobbie » 16. January 2017 11:56

gegeMartinelli wrote:But in the other hand, they also have developed a few lines of code (a few procedures, the control panel window, and so forth). This is exactly the point. If they have time, perhaps they may look at the problem I got and understand where it comes from.


Not at all, even the control panel has been developed by a forum member and given to Bitnami. Bitnami only develops the installatation procedure, but i am pretty sure that this does NOT affect your problem in any way. You even may use a ZIP Package instead of an installer and simply "install" Xampp by unpacking the ZIP Archive.
Nobbie
 
Posts: 9800
Joined: 09. March 2008 13:04

Re: MySQL Invalid Status

Postby gegeMartinelli » 17. January 2017 11:02

I've just find in the following Web Page something similar to my problem. I'm going to see if changing the id will fixes it.

http://stackoverflow.com/questions/2126 ... anager-osx

and I'll give the feedback after.
gegeMartinelli
 
Posts: 13
Joined: 23. May 2013 15:34
Operating System: Windows Vista


Return to XAMPP for Mac OS X

Who is online

Users browsing this forum: No registered users and 7 guests