I'm running the 6.5.1 .deb.
Seems like slimserver_safe gets confused once in a while -- perhaps
slimserver crashes and it tries to restart -- and never gives up. My
logs get filled with this -- repeats ever second:
2006-12-26 07:17:22.6161 ERROR: There is already another copy of the SlimServer
running on this machine. (Address already in use)
2006-12-26 07:17:22.6230 MySQLHelper: stopServer() Running shutdown.
2006-12-26 07:17:28.7028 MySQLHelper: createConfig() Creating config from file:
[/usr/share/slimserver/MySQL/my.tt] -> [/var/cache/slimserver/my.cnf].
2006-12-26 07:17:28.8478 MySQLHelper: startServer() About to start MySQL with
command: [/usr/sbin/mysqld --defaults-file=/var/cache/slimserver/my.cnf]
2006-12-26 07:17:30.5556 ERROR: There is already another copy of the SlimServer
running on this machine. (Address already in use)
[...]
Perhaps stopping is not working when attempting to rotate the logs
then it gets confused trying to restart. And indeed just now I had
two slimserver processes running (had to kill -9 them to get them to
die).
For yesterday it did this for quite a while:
$ zgrep -c 'already another' slimserver.log.1.gz
11592
I need to look at this more, but I'm wondering if it would not be
better to not use slimserver_safe. Can I point slimserver to an
existing (empty) database and have it use that?
--
Bill Moseley
[EMAIL PROTECTED]
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
