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.
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.