asking for help!!!have to rebot my server everyday!!!!

What software do you run? Apache, nginx, mysql, etc. Running a lot of stuff will do that, and some software is known to use the hard disk a lot. Databases such is MySQL are notorious for doing that, so you have to be careful how you configure it and keep the software running to a minimum.

Do you have a lot of cron jobs that run.

If you have a lot of visitors and/or a lot of sites using a database (such as Wordpress), that could cause your site to access the hard disk more, so if you can't fine-tune it enough to prevent having to reboot, you may need to spread the load over two or three Linodes.

Firstly check you have followed the documentation for fine tuning apache2 and mysql:

~~[http://library.linode.com/troubleshooting/memory-networking" target="_blank">](http://library.linode.com/troubleshooti … networking">http://library.linode.com/troubleshooting/memory-networking](

Secondly, if this is as regular as clockwork - then something in cron will be the cause (logrotate on very large log files can cause thrashing).

Check your log files - if you have set anything to 'debug' and are no - longer debugging, switch it off.

Check the space you have available in your root… even Linux needs to breathe.

Sometimes these problems are hard to track - so monitor your node using:

iotop - disk usage per process

iftop - network usage per process (possibly not needed for your problem but useful to have handy)

top - general CPU and mem usage monitoring

top

total used free shared buffers cached

Mem: 497 485 12 0 19 113

-/+ buffers/cache: 352 145

Swap: 511 31 480

here is my member use

5.3 0.9 27388 53356 /usr/sbin/httpd

5.3 0.9 27340 52872 /usr/sbin/httpd

5.2 0.9 26892 51876 /usr/sbin/httpd

5.1 1.1 26328 51836 /usr/sbin/httpd

5.1 1.1 26312 51836 /usr/sbin/httpd

5.0 1.0 25780 51316 /usr/sbin/httpd

4.9 1.0 25224 50772 /usr/sbin/httpd

4.7 1.2 24400 49260 /usr/sbin/httpd

4.7 1.1 24088 49548 /usr/sbin/httpd

4.7 1.1 24016 49548 /usr/sbin/httpd

4.7 0.6 24040 49548 /usr/sbin/httpd

4.6 1.1 23796 49260 /usr/sbin/httpd

4.6 1.0 23756 49260 /usr/sbin/httpd

4.6 0.6 23744 49216 /usr/sbin/httpd

4.5 0.5 23404 48856 /usr/sbin/httpd

2.8 0.0 14424 28040 /usr/local/lxlabs/ext/php/php ../sbin/kloxo.php master

1.5 0.6 7864 241584 /usr/libexec/mysqld –basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --socket=/var/lib/mysql/mysql.sock

1.3 0.0 6776 33208 /usr/sbin/httpd

0.8 0.0 4548 4552 ntpd -u ntp:ntp -p /var/run/ntpd.pid -g

0.6 0.0 3268 10112 sshd: root@pts/0

0.5 0.0 2980 25948 /usr/bin/python -tt /usr/sbin/yum-updatesd

0.2 0.0 1440 4684 -bash

0.2 0.0 1084 58528 /usr/sbin/named -u named -t /var/named/chroot

0.2 0.0 1084 4684 sh ../sbin/kloxo-wrapper.sh

0.1 0.0 976 7124 /usr/libexec/courier-authlib/authdaemond

0.1 0.0 948 4680 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --socket=/var/lib/mysql/mysql.sock --log-error=/var/log/mysqld.log --pid-file=/var/run/mysqld/mysqld.pid --user=mysql

0.1 0.0 928 2704 /usr/libexec/gam_server

0.1 0.0 916 5728 /usr/local/lxlabs/ext/lxlighttpd/sbin/kloxo.httpd -f /usr/local/lxlabs/kloxo/file/lighttpd.conf

0.1 0.0 848 2600 /bin/sh /usr/local/lib/ipsec/_plutoload --wait no --post

0.1 0.0 828 23280 automount

0.1 0.0 764 2896 dbus-daemon --system

0.1 0.0 736 2884 xinetd -stayalive -pidfile /var/run/xinetd.pid

0.1 0.0 704 7260 /usr/sbin/sshd

0.1 0.0 704 4352 ps -eo pmem,pcpu,rss,vsize,args

0.1 0.0 624 29512 sort -k 1 -r

0.1 0.0 600 3232 /usr/local/libexec/ipsec/pluto --nofork --secretsfile /etc/ipsec.secrets --ipsecdir /etc/ipsec.d --use-netkey --uniqueids --nattraversal --virtualprivate %v4:10.0.0.0/8,%v4:192.168.0.0/16,%v4:172.16.0.0/12

0.1 0.0 592 5384 crond

0.1 0.0 544 2208 init [3]

First, when you need to post output, post it as code. You can do that by clicking the Code button right before you paste then clicking it again after you paste. That will put [ code ] and [ /code ] (without the spaces) before and after. That will format your post so it's easier to read what you're posting.

Second, I notice a lot of httpd processes running. That looks like something apache would do – when you get a lot of people accessing your site, apache will spawn extra processes to handle the load. With each process trying to access the site all at once, that will cause more disk thrashing.

I also see a few things I'm not familiar with: gam_server and some stuff related to klaxo and pluto. If you don't need those, it might be good to turn those off.

Another thing is mysql. Most stuff uses mysql, which tends to be a resource hog (most are). Try to see if you can minimize what is using mysql.