Then kill all of them, repeat the first command in this post and kill them again.
Then start webmin again and now your webmin + virtualmin should work again.
As Tony said, you shouldn’t have to do that. I dunno exactly what’s going on there, the writelogs.pl process is not even run under the same process as Webmin–the two are wholly separate. It just seems related, but really isn’t.
I’ll ask Jamie to chime in here with thoughts on debugging the problem.
Those writelogs.pl processes are run from Apache, not from the main Webmin server process … and will be running all the time. If you need to restart Webmin, the best command to run is just :
/etc/webmin/restart
As for what causes this hang in the first place, it is hard to say … I haven’t seen it on any of my test systems. Do you do the upgrade from the command line (with yum install), or via some other method?
Also, the upgrade process can take a few minutes to complete … how long was it hung for?
Nope. Different problems. I don’t know that we ever figured out what was happening on Koen’s box. But I’ve got my debian system booting up now to reproduce your problem.
"Also, the upgrade process can take a few minutes to complete … how long was it hung for? "
Update to newest version of virtualmin said: completed.
I updated it throught webmin itself, not the command line.
After the “completed” text webmin seems to get in a loop.
It doesn’t load anything anymore.
I then shutdown webmin and usermin.
Start up again => same problem, loops
Kill +/- 800 manually writelogs.pl processes (they immediately start again) , start webmin/usermin => works again.
The writelogs.pl processes are not at all related to Webmin’s process. They are spawned by Apache, and of course they’ll come back (or your Apache would have to die because it would have nowhere to write logs to). If you have +/- 800 domains, then you’ll have as many writelogs.pl processes. You can disable the writelogs.pl processes if you want to, by setting Apache to write directly rather than via a process. This is in the Server Configuration:Website Options for each of your domains. But, again this has no relation to Webmin.
So, we still don’t know what’s happening with your Webmin restarts and why they’re failing (a bunch of writelogs.pl won’t have any impact, unless some limit on your server is being hit–I’m not sure if 800 would hit any limits…maybe if the total process count over 1024, but I doubt any modern system has a process limit of 1024).
What happens if you just restart Webmin manually from the command line: