Re: alarm handler bug on OWS 7.22?

On 13 Oct 1998, ProzessDV wrote: > Here is a part of the ONCONFIG file: > > # Diagnostics > > MSGPATH /informix/etc/online.log # System message log file path > CONSOLE /dev/console # System console message path > ALARMPROGRAM db_alarm_prog # Alarm program path> > The event handler db_alarm_prog is a binary. There is an entry in the variable > path, but I also tried to give the full pathname and the same error ocurred. I > think there is not much I can do wrong in my configuration. I can also show > some entries in online.log: Use a full path it is far more reliable. This way if someone is playing with a new path and happens to bounce the engine everything still works. > This didn't work: > > 13:04:14 Process exited with return code 1: /bin/sh /bin/sh -c db_alarm_prog 2> 23 "Logical Log 333 Complete." "Logical Log 333 Complete." It did not fail but online thinks it did because db_alarm_prog returned a non-zero return code. The alarm program MUST return zero (0) unless it ran into errors that should be logged to the online message log. > This worked: > > 14:26:03 invoke_alarm(): /bin/sh -c 'db_alarm_prog 5 6 "Internal Subsystem> failure: 'MT'" "Attempting to bring listener thread down" ' > > Art S. Kagel, kagel@bloomberg.net