|
From: Mike <li...@mi...> - 2006-06-08 16:42:13
|
> > I couldn't find anything in the archives, though I may have > used the wrong > > terms. > > > > We have been running webmin and usermin for a couple years > without any > > problems until just recently. This week I've received > calls about usermin > > being down, and the only way I've been able to start it up > again is to > > restart the server. > > > > Does usermin or webmin have a log file, or can I turn on > logging for them? > > > > I did turn on the e-mail notification for services changing > states, and that > > works, I received an e-mail earlier about usermin being down. > > > > For restart usermin I've tried: > > Clicking start from the webmin service monitor, also from > the usermin > > configuration page. > > /etc/init.d/usermin restart (and start) > > /etc/usermin/start > > And /usr/libexec/usermin/miniserv.pl > /etc/usermin/miniserv.conf (what > > /etc/usermin/start does) > > > > None of them result in usermin running, nor do they report > errors (except > > the ones that try to stop usermin, they error because it > isn't running to be > > stopped) > > > > Thanks, > > Mike > > > > > > I have occasionally seen usermin consume all available > memory, and then > crash after selected users try to read their mailboxes with > usermin. The > miniserv.error file (I have it in /var/usermin) showed "out > of memory", > and the miniserv.log showed a user trying to read mail. > > My problem is that I cannot repeat this problem on demand, > so I havn't > been able to determine the root cause. Does your logfiles > show anything > similar? No such errors in there on mine, but thanks for pointing me to the error log location. I see: Failed to bind to "port#" : Address already in use at /usr/libexec/usermin/miniserv.pl line 338 I must have also missed that miniserv.pl was still running in my "ps aux" because this morning it was listed 5 times (once for every time I tried to restart it) After killing those processes I was able to start usermin again. The last entry in the error log before the failed to bind messages was that it was Restarting. Looking in the miniserv.log file I saw that a user was trying to change their theme at that same time. I'm guessing that is what crashed it, so I have removed the 'theme' option now. Everything is back operational now. Thanks for everyones assistance. -Mike |