Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Michael on March 14, 2001, 02:26:03 AM
-
Has anyone else experienced this?
I'm running e-smith 4.1.1 on a Pentium MMX 200 w/ 64 meg ram. Over time e-smith gets slower and slower. It effects everything from email to web access. It gets to the point where even trying to load the web management screens takes 10 minutes each. After I reboot, e-smith is snappy and responsive again for a while but then slows down.
I have the disk optimization option turned off since it is not recommended for older pcs.
I used this same machine with only 32 meg of ram on e-smith 4.0 and had no problems like this appear. I skipped 4.1 so I don't know if it does it on that version.
Any ideas?
Michael
-
Michael wrote:
>
> Has anyone else experienced this?
>
> I'm running e-smith 4.1.1 on a Pentium MMX 200 w/ 64 meg
> ram. Over time e-smith gets slower and slower. It effects
> everything from email to web access. It gets to the point
> where even trying to load the web management screens takes 10
> minutes each. After I reboot, e-smith is snappy and
> responsive again for a while but then slows down.
>
Have you checked /var/log/messages for any errors?
Darrell
-
No errors listed in the /var/log/messages file, but I recently rebooted and e-smith is working well at the moment.
-
Assuming my /var/logs/messages is huge. Is it safe to just check what errors were reported and then delete them or do I need to restart some service after that?
regards,
aniston.
-
aniston wrote:
> Assuming my /var/logs/messages is huge. Is it safe to just
> check what errors were reported and then delete them or do I
> need to restart some service after that?
If you delete the files, but do nothing else, the files will still be huge, and still growing, just not visible. The file does not disappear from the disk until the last program which has the file open closes it. This disk space is then deallocated.
If /var/log/messages is huge, you should find out why. If you need to do something about it,
/usr/sbin/logrotate -f /etc/logrotate.d/syslog
will rotate the syslog log files.
man logrotate
will give you more information about the logrotate program.
Regards
Charlie
-
Just to share some info:
Michael:
I have a Pentium 150mhz 64mb Ram and WD8gb HDD as e-smith box and, as It's not in really production stage yet, I enabled disk optimization without any troubles, e-smith works just great here!
I don't know really which pc should be considered older,
Maybe something in the bios setup could tell you if your hdd controller accepts optimization or not.
Aniston:
Normal size of my var/log/messages file is about 1mb each (rotating weekly)
Alejandro
Charlie Brady wrote:
>
> aniston wrote:
>
> > Assuming my /var/logs/messages is huge. Is it safe to just
> > check what errors were reported and then delete them or do I
> > need to restart some service after that?
>
> If you delete the files, but do nothing else, the files will
> still be huge, and still growing, just not visible. The file
> does not disappear from the disk until the last program which
> has the file open closes it. This disk space is then
> deallocated.
>
> If /var/log/messages is huge, you should find out why. If you
> need to do something about it,
>
> /usr/sbin/logrotate -f /etc/logrotate.d/syslog
>
> will rotate the syslog log files.
>
> man logrotate
>
> will give you more information about the logrotate program.
>
> Regards
>
> Charlie
-
I get that also on a machine here
Cyrix 686 120
60Mg RAM
20gig Hard Drive
I turned off the Disk Optimization and it took longer, but it still happpens. Over time it just slows to a crawl until it gets to a point where it is unusable. A reboot clears this right up.
Eric
-
I get that also on a machine here
Cyrix 686 120
60Mg RAM
20gig Hard Drive
I turned off the Disk Optimization and it took longer, but it still happpens. Over time it just slows to a crawl until it gets to a point where it is unusable. A reboot clears this right up.
Eric
-
Perhaps it would be interesting to do a
ps -aux
If there is a bug or a loop of a program, and it reproduces a process infinitely, this could be a cause and show you where to go.
e.g. I had an error in a perl script. Apache httpd reproduced its process without an end and the memory was getting filled with httpd processes until 100%.
try out "top" too. It will show you how much percent of CPU and RAM is used. So you get an idea about what is slowing down your computer.
The optimization is for UDMA, isn't it? Only the newest motherboards support UDMA-100. Some 1-year-old motherboards support UDMA-33 and perhaps UDMA-66. If you have a UDMA-capable motherboard you should have a special UDMA-IDE-cable betwenn IDE-Interface and Harddisc for >UDMA33.
Stephan