kernel warnings about webmaild

ameen

Member
Apr 27, 2002
19
0
301
dmesg is reporting these kernel warnings about wemaild:

application bug: webmaild(17508) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(17806) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: php(18008) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: php(18590) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: php(20235) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(20663) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: whostmgrd(20881) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(21413) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(24914) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(28027) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: php(28350) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(29240) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(30349) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(31696) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(710) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: php(909) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(6966) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(8178) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webmaild(10401) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.

cPanel.net Support Ticket Number:
 

wwwhosts

Well-Known Member
Apr 25, 2003
59
0
156
NZ
same here

this happened after the client had setup backup incorrectly, then upgraded to WHM 8.4.0 cPanel 8.4.0-R83 then had a hdd timeout.
what a mess :confused: but this is now the only error

Sep 30 18:04:52 emma kernel: application bug: php(5221) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:06:37 emma kernel: application bug: webmaild(5325) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:08:20 emma kernel: application bug: whostmgrd(5502) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:11:07 emma kernel: application bug: php(5815) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:12:56 emma kernel: application bug: whostmgrd(6012) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:14:21 emma kernel: application bug: whostmgrd(6176) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:20:29 emma kernel: application bug: webmaild(4277) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:25:36 emma kernel: application bug: whostmgrd(4769) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:28:26 emma kernel: application bug: whostmgrd(5118) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:30:41 emma kernel: application bug: cpaneld(5289) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:31:59 emma kernel: application bug: whostmgrd(5441) has SIGCHLD set to SIG_IGN but calls wait().
Sep 30 18:36:16 emma kernel: application bug: cpaneld(5814) has SIGCHLD set to SIG_IGN but calls wait().

cPanel.net Support Ticket Number:
 

Danks

Active Member
Oct 10, 2001
26
1
303
I get these errors as well, it seems to only happen on redhat 9 servers.

application bug: whostmgrd(27717) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: whostmgrd(30838) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.

cPanel.net Support Ticket Number:
 

Striker

Member
Aug 5, 2003
6
0
151
Was anything found out about this? They only happen occasionally...

My server is RedHat 9 with WHM 8.5.1

Code:
application bug: whostmgrd(4771) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: cpaneld(14249) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: whostmgrd(4446) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: whostmgrd(29890) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: whostmgrd(29955) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
 

Striker

Member
Aug 5, 2003
6
0
151
This is probably a minor problem and is low on their FIXME list since it poses no real threat, the kernel just puts a workaround in place.

That's no excuse not to fix it though, in the future, I suspect this might break things badly...
 

Website Rob

Well-Known Member
Mar 23, 2002
1,504
1
318
Alberta, Canada
cPanel Access Level
Root Administrator
I think you are a brave person, Bailey. ;)

Wasn't aware WHM had been certified for RH Enterpise and think you could be doing 'a lot of troubleshooting' over the next little while.

I'm curious as to which kernel version you use?
 

nat

Well-Known Member
Jan 16, 2003
210
0
166
Originally posted by Striker
That's no excuse not to fix it though, in the future, I suspect this might break things badly...
My server RedHat Enterprise 3 server locks up right after this error in logs:

Feb 16 04:45:03 server kernel: application bug: whostmgrd(26244) has SIGCHLD set to SIG_IGN but calls wait().
Feb 16 04:45:03 server kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
 
Last edited:

valdur

Registered
Feb 16, 2004
1
0
151
I have the same problem.
kernel: application bug: whostmgrd(8723) has SIGCHLD set to SIG_IGN but calls wait().
kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.

It is causing me problems, because an apache child seems to die soon after that and as a result of this a desktop computer is locked off of the web server for about 5 minutes. Trying with an other browser won't help. (error_log: [notice] child pid 21725 exit signal Segmentation fault (11)).
This happens randomly and the user does not have to use wemaild, cpanel or whostmgrd himself.

OS: RedHat 9
Cpanel: cPanel 8.8.0-R73

Valdur
 

nat

Well-Known Member
Jan 16, 2003
210
0
166
This is what cpanel sent to me:

--

This is not something to worry about as found in the cPanel CHANGELOG.

this is really annoying since we are going to be forced to call
wait in some circumstances even when SIGCHLD is set to IGNORE
because of broken kernels. The tradeoff is the error message which
doesn't affect anything but makes people go crazy when they see it.
However its better that we don't create zombie processes, so for
compatibility between diffrent linux versions it might just be
best to live with this warning message as it doesn't do anything
but make people ask questions.

--



Well its funny how the server just keeps on stopping to work after getting that error. It's nothing to worry about.-Whatever. Why not just fix it?