cxswatch starting... Seems to be stuck on. Produces load.

Community forum to discuss cxs.
If you believe that there is a problem with your cxs installation and want support then, as a paid product, you should use the helpdesk after having consulted the documentation.
Post Reply
jols
Junior Member
Posts: 111
Joined: 08 May 2007, 04:43

cxswatch starting... Seems to be stuck on. Produces load.

Post by jols »

15226 root 18 0 40652 34m 1412 D 14.4 0.6 0:13.98 cxswatch starting...

I see the "cxswatch starting... " process continuously running on a few of our servers. On one inparticular it seems to produce a significant load:

We do need this daemon to run.

Here are the results of:

ps -ef | grep cxs

root 15226 1 6 04:22 ? 00:00:26 cxswatch starting...
root 15228 15226 0 04:22 ? 00:00:00 cxswatch - sleeping
root 15229 15226 0 04:22 ? 00:00:00 cxswatch - sleeping
root 15230 15226 0 04:22 ? 00:00:00 cxswatch - sleeping
root 22401 12004 0 04:29 pts/6 00:00:00 grep cxs
root 22990 22982 0 04:00 ? 00:00:00 [cxs] <defunct>
root 28766 1 0 04:05 ? 00:00:00 /usr/sbin/pure-uploadscript -B -r /etc/cxs/cxsftp.sh


Any advice or recommendations?

Thanks much.
jols
Junior Member
Posts: 111
Joined: 08 May 2007, 04:43

Re: cxswatch starting... Seems to be stuck on. Produces loa

Post by jols »

Here's what I've got in the configure cxs section:

/usr/sbin/cxs --Wstart --allusers --www --smtp -Q /home/quarantine --qoptions Mv --mail root --Wmaxchild 3 --Wloglevel 0 --Wsleep 3 --filemax 0

I take it that the "cxswatch starting..." may run for a while, during a scan of all the accounts?
jols
Junior Member
Posts: 111
Joined: 08 May 2007, 04:43

Re: cxswatch starting... Seems to be stuck on. Produces loa

Post by jols »

Okay, finally, "cxswatch starting..." went away and the load is returning to normal. Probably a false alarm on my part.
jols
Junior Member
Posts: 111
Joined: 08 May 2007, 04:43

Re: cxswatch starting... Seems to be stuck on. Produces loa

Post by jols »

Okay bingo, looks like I need to somehow keep csx from scanning error_log files, as this is what is apparently taking up the load.

Any recommendation about how to edit the configuration file to do this?

Thanks much.
Post Reply