Anyone else having antirelayd issues after last night's updates?

Prism329

Member
Dec 5, 2003
14
0
151
Getting a bunch of these into my reports box...

"antirelayd failed @ Thu Jun 28 01:16:01 2007. A restart was attempted automagicly."

When I do a ps -aux, I see a ton of instances of antirelayd running.

root 18687 0.0 0.1 11208 1156 ? S 00:42 0:00 antirelayd
root 18692 0.0 3.9 68164 40428 ? S 00:42 0:00 spamd child
root 18693 0.0 3.7 67516 38564 ? S 00:42 0:00 spamd child
root 18797 0.0 1.5 68956 16372 ? S 00:43 0:00 cpsrvd - waiting for connections
root 18809 0.0 2.7 38180 28080 ? Sl 00:43 0:00 ./samp01b-r2
root 18963 0.0 2.7 38024 27856 ? Sl 00:44 0:00 ./samp01b-race
root 19011 0.0 2.7 38020 27908 ? Sl 00:45 0:00 ./samp01b-bike
root 19523 0.0 0.1 58592 1164 ? S 00:50 0:00 antirelayd
root 20056 0.0 0.1 58592 1164 ? S 00:59 0:00 antirelayd
root 20396 0.0 0.8 19656 8748 ? Sl Jun27 0:00 ./samp02-madoshi
root 20717 0.0 0.1 58596 1168 ? S 01:07 0:00 antirelayd
root 21146 0.0 0.1 58596 1168 ? S 01:16 0:00 antirelayd

As far as I knew, antirelayd only required one process to run... suggestions/advice welcome.
 

keithc

Member
Jun 5, 2007
14
0
151
Same thing here

Hi,

Just wanted to add that I'm seeing the same thing on my end. I have about 130 antirelayd processes running on one of our boxes.

Thanks,

Keith
 

Prism329

Member
Dec 5, 2003
14
0
151
Another quick update... whatever this is is causing my box to launch an outbound process peaking at 80 Mbps. I restart antirelayd, and it drops back down to normal traffic.

Again, that only started with the last automatic Edge update.
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
This was a leftover from the issue with chkservd in an earlier build. The following should fix it:

killall -9 antirelayd
service chkservd restart
 

Bailey

Well-Known Member
Aug 12, 2001
120
1
318
Wisconsin
I can confirm this was a bug in chkservd released in the 6/27/07 upcp (released to Edge and Current branches). It was supposed to be fixed in subsequent builds of cPanel.

I had started a thread about it on 6/27 here in the forums, but Nick deleted it. Sorry, I tried. :( Obviously we users can't do much to identify and resolve these issues quickly if cPanel won't allow documented problem reports to remain untouched on the board.

:D Bailey