try rm /var/log/uvm/*.crash
then run the test
then wait 24 hours then run the test again
i doubt your "hard locks" have anything to do with this.
Printable View
Followed the steps above and now I get 19 again. I will wait 24 hours and try again.
Is there a log that will show what was happening right before the server locked up? How can I access it if there is?
I ran the delete command again and I got "No such file or directory." When I run the 'cat command' I get 19. If I look in that directory there is a file named console.log.crash.1
never mind... didn't read the warning... my own screwup... bah..
I got 29 here.
I'll try the patch...
EDIT: seemed to fix it! Counts still 29.
Just patched here this morning.. all seems ok now.
Did this make it into general circulation now? I'm seeing behavior on my partner's UT that indicates I forgot to apply this patch. I just applied it to be sure, but I was wondering if this is part of UT's automatic upgrades?
I did ran the patch because the test came up with 116. Previously system would stop forwarding packets after a while. It is still doing that, but after applying the patch I cannot move mouse or do anything with a keyboard. Any ideas?