I'm extremely happy with e-smith in general, I've managed to tweak it and twist it in a way that I like, mainly by installing several new rpms and such. However, lately it's been giving me a lot of headache.
Mainly from the fact that it crashes every 4-5 days or so. At one point my uptime was close to 180 days, but now I am lucky if I see a week.
Now before anyone says it's hardware related, I assure you 100% it isn't. I've swapped components several times, new nic(s), new videocard(s),new motherboard(s),new cpu(s), and even new memory.
I run a website that's fairly well visited off my server. I get about 3000 hits a day. I also run a distributed.net proxy program. My site relies heavily on php and mysql.
http://www.hardwareflux.comI need to find out why e-smith is crashing on me so much.
Can anyone suggest where to even start?
I'll explain the crash.......I have my terminal set up on TTY2 where I log in as a user and run the distributed.net proxy program. I issue a setterm -blank 0 command so the screen doesn't blank, and that's about it, I let the screen just stay there and watch the proxy output from time to time, while I work on my main machine. It works flawlessly, and I do mean really well, for about 4-5 days, and then boom, just freezes, without any error message or what not. Just a solid lock. Have to do a hard reboot for the system to reboot. It does through the horrid fsck process and takes a good 5 minutes to boot.
Same thing happens after 4-5 days again..
Plz help me, I'm going nuts!
4 Replies
804 Views