SEO

I am presently running DB2 V8.1.6 on Red Hat Enterprise Linux 3 ES.

Every second, the following messages appear in my /var/log/messages file:

Jul 10 09:04:45 kernel: application bug: db2fm(21697) has SIGCHLD set to
SIG_IGN but calls wait().
Jul 10 09:04:45 kernel: (see the NOTES section of 'man 2 wait').
Workaround activated.

Jul 10 09:05:46 kernel: application bug: db2fm(21724) has SIGCHLD set to
SIG_IGN but calls wait().
Jul 10 09:05:46 kernel: (see the NOTES section of 'man 2 wait').
Workaround activated.

I assume the error message is correct: that db2fm is calling the wait
function even though it is set to ignore the death of a child signal.
Apparently, the wait() function depends on the death of child signal to be
enabled.

This did not happen in DB2 V6.1.5 or whatever I was running before.
Probably because it did not start db2fm if it even had one. Now there is
one in my /etc/inittab

fmc:2345:respawn:/opt/IBM/db2/V8.1/bin/db2fmcd #DB2 Fault Monitor Coordinator

Since each of these error messages has a different pid, I assume that each
one dies within a second and a new one is started.

What is going on and how do I fix it?

--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 14:30:00 up 11 days, 3:26, 3 users, load average: 4.23, 4.22, 4.18

It seems to be the fault monitor which has these problems not
the fault monitor coordinator.
So you could disable the fault monitor for your instances by
executing the following command as instance owner:

db2fm -f off

The individual settings for the fault monitor could be found in
the following file:

<INSTHOME>/sqllib/fm.<hostname>.reg

You might also completely remove the fault monitor coordinator from
your /etc/inittab file.

It's interesting to see how much confidence IBM has in their DB2 product
that
they are introducing such silly things.

HTH.

Best regards

Eric
--
IT-Consulting Herber

Mobile: +49 177 2276895

***********************************************

Download the IFMX Database-Monitor for free at:

http://www.herber-consulting.de/BusyBee

***********************************************



"Jean-David Beyer" <jdbeyer@exit109.com> schrieb im Newsbeitrag
news:10f8asclkeb6t96@corp.supernews.com...
> I am presently running DB2 V8.1.6 on Red Hat Enterprise Linux 3 ES.
>
> Every second, the following messages appear in my /var/log/messages file:
>
> Jul 10 09:04:45 kernel: application bug: db2fm(21697) has SIGCHLD set to
> SIG_IGN but calls wait().
> Jul 10 09:04:45 kernel: (see the NOTES section of 'man 2 wait').
> Workaround activated.
>
> Jul 10 09:05:46 kernel: application bug: db2fm(21724) has SIGCHLD set to
> SIG_IGN but calls wait().
> Jul 10 09:05:46 kernel: (see the NOTES section of 'man 2 wait').
> Workaround activated.
>
> I assume the error message is correct: that db2fm is calling the wait
> function even though it is set to ignore the death of a child signal.
> Apparently, the wait() function depends on the death of child signal to be
> enabled.
>
> This did not happen in DB2 V6.1.5 or whatever I was running before.
> Probably because it did not start db2fm if it even had one. Now there is
> one in my /etc/inittab
>
> fmc:2345:respawn:/opt/IBM/db2/V8.1/bin/db2fmcd #DB2 Fault Monitor
Coordinator
>
> Since each of these error messages has a different pid, I assume that each
> one dies within a second and a new one is started.
>
> What is going on and how do I fix it?
>
> --
> .~. Jean-David Beyer Registered Linux User 85642.
> /V\ Registered Machine 241939.
> /( )\ Shrewsbury, New Jersey http://counter.li.org
> ^^-^^ 14:30:00 up 11 days, 3:26, 3 users, load average: 4.23, 4.22, 4.18
>