Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: ramos on March 03, 2007, 09:38:02 PM
-
PLEASE HELP!
I have a 7.0 upgraded to 7.1 and 2 days ago I upgraded to 7.1.1 since then I get 100% processor load. With top I get runsv wan getting 99,9% of processor. When running pstree I get runsv---multilog. Tail /var/log/wan/current shows:
/var/service/wan/run.static : line 5 : exec : pause : not found
arping : recvform : Network is down
Can anyone help me?
-
As a workaround for this problem I created a file called "pause" in /usr/local/bin with the following content:
#!/usr/bin/perl
use POSIX;
pause();
Make sure the file is runnable:
#chmod 755 pause
-
Thank you for the quick answer but it doesn't work! Did I missed something?
I have the exact same message in tail /var/log/wan/current and processor is still loaded at 99,9%.
I tried even to upgrade the e-smith-base from smetest and it didn't work. It fixes the wan pause problem but there is another crashed process.
Thank you!
-
Here is the solution. I had the same problem after the upgrade. Charlie worked out a solution in a couple of hours and it has been pushed into the next upgrade.
http://bugs.contribs.org/show_bug.cgi?id=2580
-
And as a important note any problems always always report to the bug tracker. Thanks!
-
I finally nail it down! Thank you all for helping me!
My solution:
Apply Charlie replacement for run.static then top to see pid for runsv; kill pid; do sv restart wan and you're back in bussines. It works until server reboots. Then you have to restart the wan.
Have fun :roll: !
-
This is fixed in 7.1.2 which will be arriving soon.
-
I just fixed it by:
yum --enablerepo=smeupdates-testing update e-smith-base
then
ps ax | grep "runsv wan"
kill nnnn (where nnn is the pid for the runsv wan)
then
sv restart wan
This works on a running server without a reboot.
If you can re-boot, then just do :
signal-event post-upgrade; signal-event reboot
after the yum command.
-
kill nnnn (where nnn is the pid for the runsv wan)
I can see no reason why that would be necessary. Just updating the package should be all that is required.
Please post technical followup via the Bug Tracker. Thanks.