Server crashing every night.

Since about 3 nights ago my server has been crashing. It seems this happend after a client who had a large site deleted his files as he moved his hosting elsewhere. This might be linked I dont know.

The problem is this all services stop cant see sites or access email.

I think the issue is to do with repquota

When I can access shell this is what I see with top.

 1645 root      19   0  4836  656  568 R 99.9  0.0 311:26.55 repquota
19903 root      16   0  2080 1132  780 R  1.0  0.1   0:00.10 top

ps -aux shows lots of this

iworx    16045  0.0  0.0  2164  952 ?        Ss   08:12   0:00 /bin/bash -c cd /home/interworx/cron ; ./iworx.pex --fifteenly
root     16046  0.0  0.9 25700 19724 ?       S    08:12   0:00 /home/interworx/bin/php -c /home/interworx/etc iworx.php --fifteenly
iworx    16059  0.0  0.6 25296 12992 ?       S    08:12   0:00 /home/interworx/bin/iworx-db --defaults-file=/home/interworx/etc/my.cnf --basedir=/home/interw
root     16085  0.0  0.0  5740 1052 ?        S    08:12   0:00 sh -c /home/interworx/cron/storage.pex --chunksize=200  --chunk=1  >/dev/null  2>&1
root     16086  0.0  0.8 27428 18212 ?       S    08:12   0:00 /home/interworx/bin/php -c /home/interworx/etc storage.php --chunksize=200 --chunk=1
iworx    16093  0.0  0.6 25296 12992 ?       S    08:12   0:00 /home/interworx/bin/iworx-db --defaults-file=/home/interworx/etc/my.cnf --basedir=/home/interw
root     16094  0.0  0.0  4192  612 ?        D    08:12   0:00 /usr/sbin/repquota -g /home
spamd    16477  1.5  1.6 38668 34036 ?       S    08:14   0:20 spamd child
root     18350  0.0  0.0  5208 1324 ?        S    08:27   0:00 crond
iworx    18351  0.0  0.0  2164  952 ?        Ss   08:27   0:00 /bin/bash -c cd /home/interworx/cron ; ./iworx.pex --fifteenly
root     18353  0.0  0.9 26052 19724 ?       S    08:27   0:00 /home/interworx/bin/php -c /home/interworx/etc iworx.php --fifteenly
iworx    18364  0.0  0.6 25296 12992 ?       S    08:27   0:00 /home/interworx/bin/iworx-db --defaults-file=/home/interworx/etc/my.cnf --basedir=/home/interw
root     18393  0.0  0.0  4460 1052 ?        S    08:27   0:00 sh -c /home/interworx/cron/storage.pex --chunksize=200  --chunk=1  >/dev/null  2>&1
root     18394  0.0  0.8 27440 18216 ?       S    08:27   0:00 /home/interworx/bin/php -c /home/interworx/etc storage.php --chunksize=200 --chunk=1
iworx    18403  0.0  0.6 25296 12992 ?       S    08:27   0:00 /home/interworx/bin/iworx-db --defaults-file=/home/interworx/etc/my.cnf --basedir=/home/interw
root     18404  0.0  0.0  5352  612 ?        D    08:27   0:00 /usr/sbin/repquota -g /home

I have a ticket open but as yet no reply im just getting worried now as I dont want to request that the box be rebooted again tomorrow morning. As this seems to be the only way to get it back as it does not accept any commands if I am lucky to get to a shell.

Anyone had or this issue or can maybe give me some advise?

I’ve never heard of an issue like this but i’ve ran into issues myself with sites that are larger then our /tmp directory. Since this does appear to be a server related issue (not so much InterWorx) it’s hard to say if you’ll get answers from IWorx support.

If you can provide more information about your server you can probably find your solution here.

send me a link to a copy of your ‘dmesg’ and /var/log/messages file, and an output of ‘df -m’, or post em here if you feel comfortable.