Dataskq is acting wierd

[redunix]

Hello,

looks like dataskq is going strange.

[root@server data]# pwd
/usr/local/directadmin/data
[root@server data]# ls
admin sessions skins task.queue10 task.queue.tmp templates tickets users
[root@server data]#

[root@server data]# cat task.queue.tmp
action=cache&type=popquota
[root@server data]# cat task.queue10
action=tally&value=all 0 anaconda-ks.cfg gg install.log install.log.syslog packages anaconda-ks.cfg gg install.log install.log.syslog packages anaconda-ks.cfg gg install.log install.log.syslog packages root /usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats_updateall.pl now -awstatsprog=/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl
[root@server data]#

Where is this coming from? there are like 10-20 processes of dataskq.

[redunix]

I still have the same problem. Can anyone help me out?

[ben29]

to finish the queue
you should do:


/usr/local/directadmin/dataskq d2000

[redunix]

It does this everyday. Around 13:30. It also starts like 10 dataskq processes and the load on the server god up to 40-50. I delete the task.queue files from /usr/local/directadmin/data/ and then killal -9 dataskq to get the load back to normal.

[nobaloney]

You'll have to find out what cronjobs or other settings are putting ten dataskq process onto the server. Are you, or one or more of your clients, running backups at 13:30?

Jeff

[redunix]

Today it made 3 task.queue files:

[root@server data]# ls
admin sessions skins task.queue task.queue10 task.queue.tmp templates tickets users


[root@server data]# cat task.queue*
action=cache&type=popquota
action=tally&value=all 0 * * * root /usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats_updateall.pl now -awstatsprog=/usr/local/directadmin/plugins/awstats/hooks/cgi-bin/awstats.pl
action=cache&type=popquota

top - 14:31:58 up 8 days, 1:28, 1 user, load average: 26.13, 25.59, 24.94
Tasks: 188 total, 4 running, 184 sleeping, 0 stopped, 0 zombie
Cpu(s): 17.1%us, 22.0%sy, 0.0%ni, 28.1%id, 29.8%wa, 0.0%hi, 3.0%si, 0.0%st
Mem: 4054908k total, 3141680k used, 913228k free, 45536k buffers
Swap: 0k total, 0k used, 0k free, 323416k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
517 root 20 0 150m 28m 1444 S 32 0.7 71:03.74 lfd - sleeping
16773 root 20 0 78408 69m 1608 D 5 1.8 2:12.46 /usr/local/directadmin/dataskq
14684 root 20 0 78408 69m 1608 D 3 1.8 4:06.81 /usr/local/directadmin/dataskq
15698 root 20 0 78408 69m 1608 R 3 1.8 3:15.01 /usr/local/directadmin/dataskq
12187 root 20 0 78408 69m 1608 D 2 1.8 7:18.41 /usr/local/directadmin/dataskq
13140 root 20 0 78408 69m 1608 D 2 1.8 6:06.20 /usr/local/directadmin/dataskq
22382 root 20 0 45800 38m 1608 D 2 1.0 0:18.86 /usr/local/directadmin/dataskq
7469 root 20 0 78408 69m 1608 D 2 1.8 13:02.72 /usr/local/directadmin/dataskq
8738 root 20 0 78408 69m 1608 D 2 1.8 7:19.14 /usr/local/directadmin/dataskq
10040 root 20 0 78408 69m 1608 D 2 1.8 9:42.74 /usr/local/directadmin/dataskq
13941 root 20 0 78408 69m 1608 D 2 1.8 5:06.99 /usr/local/directadmin/dataskq
5649 root 20 0 78568 70m 1616 R 2 1.8 11:12.15 /usr/local/directadmin/dataskq
6666 root 20 0 78444 69m 1608 D 2 1.8 15:21.98 /usr/local/directadmin/dataskq
17925 root 20 0 78408 69m 1608 D 2 1.8 1:39.05 /usr/local/directadmin/dataskq
2619 root 20 0 78568 70m 1616 D 1 1.8 16:30.89 /usr/local/directadmin/dataskq
3598 root 20 0 78568 70m 1616 D 1 1.8 14:32.69 /usr/local/directadmin/dataskq
4920 root 20 0 241m 145m 968 D 1 3.7 2:48.89 rsync --daemon
11178 root 20 0 78408 69m 1608 D 1 1.8 8:29.23 /usr/local/directadmin/dataskq
31764 root 20 0 78444 69m 1616 D 1 1.8 45:25.80 /usr/local/directadmin/dataskq
32535 root 20 0 78448 69m 1616 D 1 1.8 34:38.11 /usr/local/directadmin/dataskq
875 root 20 0 78444 69m 1616 D 1 1.8 24:20.18 /usr/local/directadmin/dataskq
23466 root 20 0 8840 2000 1624 D 1 0.0 0:00.99 /usr/local/directadmin/dataskq
496 root 15 -5 0 0 0 S 0 0.0 11:47.77 [md0_raid1]
21117 root 20 0 45800 38m 1608 D 0 1.0 0:45.61 /usr/local/directadmin/dataskq
23173 apache 20 0 126m 63m 1532 S 0 1.6 0:00.20 /usr/sbin/httpd -k start -DSSL
23530 root 20 0 14732 1184 836 R 0 0.0 0:00.05 top d1c


if a user would start a backup with cron i should see this back in the task.queue files right???

[nobaloney]

There shold only be one task.queue file. It runs lines from the top, removing them as it runs them (I'm not sure if before or after), then it removes the entire file when there's nothing more in it.

Perhaps you need to contact DirectAdmin Support (http://www.directadmin.com/support.html) or hire someone to look into your server.

Jeff