antirelayd question

ymfm

Active Member
Feb 21, 2003
38
0
156
Brazil
Hi.
Antirelayd is taking all the CPU usage.
Server load goes up and down all the day.

PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
17472 root 25 0 1496 1496 1196 S 72.6 0.1 12:58 0 antirelayd

Sometimes is goes to 99% permanently running.
I restarted exim, but the antirelayd goes again to 80-90% of CPU usage.

CPU states: cpu user nice system irq softirq iowait idle
total 98.0% 0.0% 1.9% 0.0% 0.0% 0.0% 0.0%


13:57:02 up 12 days, 14 min, 1 user, load average: 2.89, 3.82, 5.45
189 processes: 169 sleeping, 8 running, 5 zombie, 7 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 74.4% 0.0% 3.1% 0.1% 0.0% 3.9% 18.1%
Mem: 1030088k av, 1017008k used, 13080k free, 0k shrd, 136060k buff
766644k actv, 142536k in_d, 17308k in_c
Swap: 2040244k av, 106248k used, 1933996k free 556320k cached

Any help?
Thanks
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,437
31
473
Go on, have a guess
That's odd. Have you tried re-installing exim to see if that fixes it? If so, I'd logs a support request with cPanel and have them look at it:

/scripts/updatenow
/scripts/exim4

One final thought, none of your partitions are full, esp. /tmp?
 

ymfm

Active Member
Feb 21, 2003
38
0
156
Brazil
I'm running /scripts/upcp --force before the exim installation.
The problem is that up2date is running for 100 minutes.

What should I do? Kill pid and start again?
Or I must wait?

Thanks,
 

deieno

Well-Known Member
Nov 16, 2003
69
0
156
Floripa - Brazil
Hello there,
I know this post is Old, but is the only one I found something about my problem and maybe some of you can help me. For days I'm trying to fix this issue but anything I do resolve the problem.

The antirelayd is the top process and always eat between 10 and 80% from cpu. Exim and cPanel has been updated and nothing fix.. If you have some tips in how can I optmize this service I would thank you.

Here is the top screen:

29790 root 16 0 3780 1680 1288 S 27.0 0.2 0:17.72 antirelayd
30430 mailnull 17 0 8816 3464 2472 S 2.0 0.3 0:00.06 exim
30442 mailnull 15 0 8968 3668 2536 S 2.0 0.4 0:00.06 exim
15753 nobody 20 4 47936 34m 5132 S 1.7 3.4 0:05.74 httpd
30433 mailnull 16 0 8824 3452 2452 S 1.7 0.3 0:00.05 exim
30454 aquarela 23 8 10548 9116 4512 S 1.7 0.9 0:00.05 cppop
30453 alecrim 23 8 10544 9120 4508 S 1.0 0.9 0:00.03 cppop
30455 grife 24 8 10544 9100 4512 S 1.0 0.9 0:00.03 cppop
474 root 15 0 0 0 0 D 0.3 0.0 3:15.17 kjournald
3217 mysql 22 6 81308 58m 3012 S 0.3 5.8 4:46.26 mysqld
21131 root 23 8 10528 9060 4516 S 0.3 0.9 0:29.58 cppop
15729 nobody 19 4 47772 34m 5216 S 0.3 3.4 0:05.18 httpd
15732 nobody 19 4 47744 33m 5084 S 0.3 3.3 0:04.65 httpd
15927 nobody 19 4 46496 32m 5116 S 0.3 3.2 0:04.10 httpd
26053 root 15 0 2348 604 476 D 0.3 0.1 0:01.87 syslogd
30379 thermoid 23 8 10548 9172 4512 S 0.3 0.9 0:00.19 cppop
1 root 16 0 2240 484 404 S 0.0 0.0 0:02.90 init
2 root RT 0 0 0 0 S 0.0 0.0 0:00.58 migration/0
3 root 34 19 0 0 0 S 0.0 0.0 0:00.24 ksoftirqd/0
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,437
31
473
Go on, have a guess
That's most likely unrelated to this thread. Whenever I've seen what you describe it's because you've been running /scripts/fixrelayd

Have a check of /etc/syslog.conf and make sure there are no duplicate lines. If there are any, remove all but one and then restart syslog:

service syslog restart
 

deieno

Well-Known Member
Nov 16, 2003
69
0
156
Floripa - Brazil
Thanks a log :) :) :)
there were a lot:

local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog
local0.notice;local0.debug;mail.*;mail.none;mail.info;local0.info /var/log/maillog


I removed and server get better :)

Any ideia why this happened?
Thank you so much!!!
 

deieno

Well-Known Member
Nov 16, 2003
69
0
156
Floripa - Brazil
Sorry... You have already answer: "Whenever I've seen what you describe it's because you've been running /scripts/fixrelayd"

Was exactly what I did... all time the /etc/relayhosts and /etc/relayhostsusers are empty making trouble to customers.

So, all times I run /scripts/fixrelayd I have to clean syslog.conf ?

Thanks
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,437
31
473
Go on, have a guess
Yes, if you use that script.

Alternatively, just run the following to have the same effect:

service syslog restart
service exim restart