cpanellogd spawning 100's of times?

[Kiwi]

With the latest release, has anyone noticed cpanellogd run 100's of processes at once? They're sleeping processes, not zombies.

[Kiwi]

That's how the processes look:

root 24079 0.1 1.1 7188 5408 pts/0 SN 14:47 0:00 cpanellogd - upda
root 24125 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24126 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24127 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24128 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24129 0.2 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24169 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24170 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24171 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24172 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24173 0.2 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24242 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24243 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24244 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24245 0.0 1.1 7188 5408 pts/0 SN 14:48 0:00 cpanellogd - upda
root 24254 0.3 1.1 7184 5408 pts/0 SN 14:48 0:00 cpanellogd - upda

[cpanelnick]

Originally posted by Kiwi
That's how the processes look:

ps uxawwwww | grep cpanellogd

[Kiwi]

root@server [~]# ps uxawwwww | grep cpanellogd
root 16801 14.0 0.8 5416 4120 pts/0 SN 15:14 0:02 cpanellogd - updating logs
root 16994 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 16995 1.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 16999 1.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17001 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17002 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17004 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17005 0.0 0.8 5416 4124 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17006 5.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17023 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17025 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17026 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17027 1.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17028 4.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17036 1.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17039 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17040 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17041 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17042 5.0 0.8 5452 4160 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17051 0.0 0.8 5452 4160 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17052 0.0 0.8 5452 4160 pts/0 RN 15:14 0:00 cpanellogd - updating logs

Its happening on all machines running CPanel 6.2.0 or later. Once there are 100's of processes, they almost can't be killed and the machine has to be restarted.

[cpanelnick]

Originally posted by Kiwi

root@server [~]# ps uxawwwww | grep cpanellogd
root 16801 14.0 0.8 5416 4120 pts/0 SN 15:14 0:02 cpanellogd - updating logs
root 16994 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 16995 1.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 16999 1.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17001 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17002 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17004 0.0 0.8 5416 4120 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17005 0.0 0.8 5416 4124 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17006 5.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17023 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17025 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17026 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17027 1.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17028 4.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17036 1.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17039 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17040 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17041 0.0 0.8 5436 4144 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17042 5.0 0.8 5452 4160 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17051 0.0 0.8 5452 4160 pts/0 SN 15:14 0:00 cpanellogd - updating logs
root 17052 0.0 0.8 5452 4160 pts/0 RN 15:14 0:00 cpanellogd - updating logs

Its happening on all machines running CPanel 6.2.0 or later. Once there are 100's of processes, they almost can't be killed and the machine has to be restarted.

what ticket number did you have on this ?

EDGE 29 will display more information about that cpanellogd is doing. hopefully this will help track this down.

[Kiwi]

bug report #10466. its happening on 40+ machines, redhat 7.2/7.3, on single and dual systems.

[cpanelnick]

Is anybody else having this problem ?

[carlgm]

Hey Kiwi,

Which version of CPANEL you using?

[Kiwi]

Tried all versions starting above Cpanel-6.2.0-RELEASE_12 and its happening on all of them, across Redhat 7.2 and 7.3, including different kernels and machines with and without custom software installed.

[carlgm]

Hello,

When did this start happening?

[sewebhosting]

same thing happening here its crashing my machine load is so high, i have to pull plug

[vishal]

Hello,

I am on Redhat 7.3 and WHM 6.2.0,Cpanel 6.4.0-S3.

This all started happeing when i upgraded to WHM 6.2.0. The server load goes High and yesterday ftp and cpop failed and today Apache was down (I know this is only due to CPU load which had gone up to 100% OMG )

Help this might be the new issue as the mail() function and exim are still fighting on my machine. I did everything means everything but no use.

Now what's up with this a New Issue and a New NEWS on WHM NEWS with a NEW upgrade and even with a NEW problem.

When will this NEW ??? Stop.

Regards,

[Website Rob]

The following may or may not help and is offered as it has helped for me.

Last year I had read here about Edge releases being better than the other two types. After having used that type for 6 or so months now, I have noticed that I do not have a lot of problems posted by others. Not to say that using it has solved everything (how Linux and WHM/Cpanel are installed and setup makes a big difference as well), but does seem to be the best of the three types available.

Whenever I am having problems or after changes/upgrades, there are two things I find helpful:

1. httpd.conf test

# /usr/local/apache/bin/httpd -t
Syntax OK << this is all you want to see

Amazing how easy it easy to screwup this file and the above command will state exactly where, there is a problem.

2. checking for defunct processes

# ps -xla
look for any process stating: <defunct>

I noticed for example, "/scripts/upcp" went zombie on me on the last Cpanel update and I had to kill the process -- Zombies are not a good thing for all kinds of reasons. Although a Server reboot or Apache restart should clear out these type things, always good to eyeball it first.

HTH

[vishal]

Hello Rob,

Thank you for such a good info . i'll definately follow what u have given.

But what should be done with exim + php + mail() function.

What i did already .

I am on the latest stable tree
WHM 6.2.0
Cpanel 6.4.0-S3
RedHat 7.3

I have tried everything for solving this problem but Failed.

1. The "twek settings didn't work for me"

2. The suexec "enable" "disable" didn't work.

3. I have tried everyscript regarding the mail problem. even /scripts/newexim didn't help.

4. /scripts/fixvaliases -- No help!!!

Should i try PHPSuexec. Only that remains now!!!

What do u say ?

Hope u have found any solutuion for it.

Regards,

[Website Rob]

vishal, I would do the three things I mentioned above - and in the same order. If you want to skip switching to Edge Releases, at least do the other two.

One other thing I should mention as well, in Update Preferences I have set "everything" to Manual Updates Only! This prevents unwanted surprizes as I only update when I have researched problems others are having from updates and I have the time to correct/troubleshoot any problems an update may cause the Server.


Not sure what your reference to "exim + php + mail() function" is, but never run a Server without 'suexec' always being enabled. I would leave phpsuexec for now and focus on other problems first.

It's a shame that Nick never provided some details in his other post as I would like to know just what:

EDGE 29 will display more information about that cpanellogd is doing. hopefully this will help track this down.

really means and where one can view this 'more information'???