mariadb-10.0-server: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

[miken32 (Michael Newton)]

When I start the server, I get these entries in the system log:

Jul  4 10:54:39 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.1-server): The Debug key is no longer respected. Please remove it.
Jul  4 10:54:39 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.1-server): This service is defined to be constantly running and is inherently inefficient.
Jul  4 10:54:41 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.0-server): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jul  4 10:54:51 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.0-server): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

No log files are created in /opt/local/var/log/mariadb-10.1/, and launchd says it is constantly trying to restart the server, but it seems to be working just fine. I can connect to the database without problems.

[ryandesign (Ryan Carsten Schmidt)]

Replying to miken32@…:

When I start the server, I get these entries in the system log:

Jul  4 10:54:39 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.1-server): The Debug key is no longer respected. Please remove it.

This will occur for all MacPorts ports using the built-in launchd plist creation mechanism on recent versions of OS X. This is filed as #49990.

Jul  4 10:54:39 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.1-server): This service is defined to be constantly running and is inherently inefficient.

This will occur for all MacPorts ports using the built-in launchd plist creation mechanism on recent versions of OS X. We don't have a separate ticket for this and fixing this may have to be done on a case by case basis so it's not straightforward.

Jul  4 10:54:41 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.0-server): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jul  4 10:54:51 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.0-server): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

No log files are created in /opt/local/var/log/mariadb-10.1/, and launchd says it is constantly trying to restart the server, but it seems to be working just fine. I can connect to the database without problems.

Note that the first two lines were about mariadb-10.1-server, while the second two lines were about mariadb-10.0-server. So any errors would be logged in /opt/local/var/log/mariadb-10.0/. Which server do you want to use? You should sudo port unload the one you don't want to use.

[miken32 (Michael Newton)]

Replying to ryandesign@…:

Replying to miken32@…:

Jul  4 10:54:41 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.0-server): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Jul  4 10:54:51 MacBook-Pro com.apple.xpc.launchd[1] (org.macports.mariadb-10.0-server): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Note that the first two lines were about mariadb-10.1-server, while the second two lines were about mariadb-10.0-server. So any errors would be logged in /opt/local/var/log/mariadb-10.0/. Which server do you want to use? You should sudo port unload the one you don't want to use.

Hmm, I hadn't noticed that. I upgraded from mysql-5.7-server to mariadb-10.0-server to mariadb-10.1-server. There were some issues with the upgrades, will try restarting and I expect it should clear it out. Should the unload be made part of the uninstall command, if it's not already? The 10.0 server has been uninstalled for a couple of weeks now.

[miken32 (Michael Newton)]

Yes, confirming that a restart did the trick. Also that there is zero logging by default, so my.cnf needed to be edited to enable logging for the server. Sorry I hadn't noticed the 10.1/10.0 in the syslog entries!