application bug: webcached on /va/log/messages

[Edwin Ruiz_2]

Hi:

I am getting this messages on /var/log/messages.My server is one HP Blade server BL40P running Red Hat A.S. 3.0 and OAS 10g. Can u help me?

thanks


application bug: webcached(7675) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webcached(7675) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webcached(7546) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webcached(7546) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webcached(7546) has SIGCHLD
set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
application bug: webcached(7546) has SIGCHLD set to SIG_IGN but calls wait().
(see the NOTES section of 'man 2 wait'). Workaround activated.
[root@salato-apl17 log]# application bug: webcached

[Steven E. Protter · Accepted solution]

Sounds like webcahe isn't happy about something.

Messages are not necessarily a problem. If you take the following survey:

1) Is the application fully functional?

2) Is the entire application working on one server or are multiple servers involved?

3) Are there any messages in the httpd logs or the webcache log?

If the answer to 1 is yes, please consider doing nothing.

If the answer to 2 yes yes, consider uninstalling webcache because you don't need it on a single server installation.

If the answer to 3 is no, once again consider doing nothing.

We have substantial expereince with this application.

SEP

[Edwin Ruiz_2]

Thanks Steven:

i will replay ur questions:
1. Aplicatin are working fine
2. We have tow servers with OAS , one server with midtier, other running infra
3. where can i see webcachelogs?

[Olivier Drouin]

It is not "webcached" that is complaining, it is the system.


$ man 2 wait

ECHILD if the process specified in pid does not exist or is not a child of the calling process. (This can happen for oneâ s own child if the action for SIGCHLD is set to SIG_IGN.

See also the LINUX NOTES section about threads.)




$ man signal

According to POSIX (3.3.1.3) it is unspecified what happens when
SIGCHLD is set to SIG_IGN. Here the BSD and SYSV behaviours differ,
causing BSD software that sets the action for SIGCHLD to SIG_IGN to
fail on Linu