Online log: Process exited with return code 255 ✓ Answered: green (solid confidence) — Asker confirms 'The bug in the log backup script is fixed' after following Marcus Haarmann's wrapper-script/onmode -l diagnostic approach.

Advisory only.

HI, ALL, IDS11.50 FC8, RHEL 6 After did a level 0 backup in RHEL5 and restored it in RHEL 6 , All seems working OK. But my automatic logical log backup job caused a extra line in online log file ( see below). Any idea? Thanks, Frank 19:49:50 On-Line Mode 19:49:51 SCHAPI: Started dbScheduler thread. 19:49:51 Booting Language <spl> from module <> 19:49:51 Loading Module <SPLNULL> 19:49:51 SCHAPI: Started 2 dbWorker threads. 19:50:15 Logical Log 88372 Complete, timestamp: 0xd50ade2c. 19:50:16 Logical Log 88372 - Backup Started 19:50:16 Logical Log 88372 - Backup Completed 19:50:16 Process exited with return code 255: /bin/sh /bin/sh -c /dbbackup/logbackup/EventAlarm.pl 2 23 "" "Logical Log 88372 Complete, timestamp: 0xd50ade2c." "" --047d7bd7689415ee3f04f0bd91a1

Original post: HI, ALL, IDS11.50 FC8, RHEL 6 After did a level 0 backup in RHEL5 and restored it in RHEL 6 , All seems working OK. But my automatic logical log backup job caused a extra line in online log file ( see below). Any idea? Thanks, Frank 19:49:50 On-Line Mode 19:49:51 SCHAPI: Started dbScheduler thread. 19:49:51 Booting Language <spl> from module <> 19:49:51 Loading Module <SPLNULL> 19:49:51 SCHAPI: Started 2 dbWorker threads. 19:50:15 Logical Log 88372 Complete, timestamp: 0xd50ade2c. 19:50:16 Logical Log 88372 - Backup Started 19:50:16 Logical Log 88372 - Backup Completed 19:50:16 Process exited with return code 255: /bin/sh /bin/sh -c /dbbackup/logbackup/EventAlarm.pl 2 23 "" "Logical Log 88372 Complete, timestamp: 0xd50ade2c." "" Response: Well, you are going to have to look at what /dbbackup/logbackup/EventAlarm.pl does. The message would indicate that, that perl script (since it's .pl?) exited with a status of -1 (at least I believe the 255 is -1 but since it's reported as a unsigned 1 byte int you see 255 rather then -1). So while it appears the log did get backed up something else that the script does would appear to be causing it to think it's exiting with some sort of failed status. Jacques Renaut IBM Informix Advanced Support APD Team

Hi, seems to me your perl script does throw an error when invoked by the alarmscript mechanism. I would suspect either perl is not installed or at least not installed correctly (maybe you have missing modules). As a check, register a new script like invoke_alarm.sh in onconfig as alarmprogram which then calls the original perl script and gathers the output of stdout/stderr in a file. That way, you can see the messages. Something like: #!/bin/sh /dbbackup/logbackup/EventAlarm.pl $* 2>&1 >> /tmp/alarm.out Call onmode -l to fire a logical log full alarm event for testing. Hope this helps, Marcus Haarmann ----- Ursprüngliche Mail ----- Von: "FRANK" <yunyaoqu@gmail.com> An: ids@iiug.org Gesendet: Freitag, 24. Januar 2014 21:54:44 Betreff: Online log: Process exited with return code 255 [32342] HI, ALL, IDS11.50 FC8, RHEL 6 After did a level 0 backup in RHEL5 and restored it in RHEL 6 , All seems working OK. But my automatic logical log backup job caused a extra line in online log file ( see below). Any idea? Thanks, Frank 19:49:50 On-Line Mode 19:49:51 SCHAPI: Started dbScheduler thread. 19:49:51 Booting Language <spl> from module <> 19:49:51 Loading Module <SPLNULL> 19:49:51 SCHAPI: Started 2 dbWorker threads. 19:50:15 Logical Log 88372 Complete, timestamp: 0xd50ade2c. 19:50:16 Logical Log 88372 - Backup Started 19:50:16 Logical Log 88372 - Backup Completed 19:50:16 Process exited with return code 255: /bin/sh /bin/sh -c /dbbackup/logbackup/EventAlarm.pl 2 23 "" "Logical Log 88372 Complete, timestamp: 0xd50ade2c." "" --047d7bd7689415ee3f04f0bd91a1 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Thank you All! The bug in the log backup script is fixed. Frank On Mon, Jan 27, 2014 at 2:44 AM, Marcus Haarmann <marcus.haarmann@midoco.de>wrote: > Hi, > > seems to me your perl script does throw an error when invoked by the > alarmscript mechanism. > I would suspect either perl is not installed or at least not installed > correctly (maybe you have missing > modules). > As a check, register a new script like invoke_alarm.sh in onconfig as > alarmprogram which then > calls the original perl script and gathers the output of stdout/stderr in a > file. That way, > you can see the messages. > Something like: > #!/bin/sh > /dbbackup/logbackup/EventAlarm.pl $* 2>&1 >> /tmp/alarm.out > > Call onmode -l to fire a logical log full alarm event for testing. > > Hope this helps, > > Marcus Haarmann > > ----- Ursprüngliche Mail ----- > > Von: "FRANK" <yunyaoqu@gmail.com> > An: ids@iiug.org > Gesendet: Freitag, 24. Januar 2014 21:54:44 > Betreff: Online log: Process exited with return code 255 [32342] > > HI, ALL, > > IDS11.50 FC8, RHEL 6 > > After did a level 0 backup in RHEL5 and restored it in RHEL 6 , > All seems working OK. But my automatic logical log backup job caused a > extra line in online log file ( see below). > > Any idea? > > Thanks, > Frank > > 19:49:50 On-Line Mode > 19:49:51 SCHAPI: Started dbScheduler thread. > 19:49:51 Booting Language <spl> from module <> > 19:49:51 Loading Module <SPLNULL> > 19:49:51 SCHAPI: Started 2 dbWorker threads. > 19:50:15 Logical Log 88372 Complete, timestamp: 0xd50ade2c. > 19:50:16 Logical Log 88372 - Backup Started > 19:50:16 Logical Log 88372 - Backup Completed > 19:50:16 Process exited with return code 255: /bin/sh /bin/sh -c > /dbbackup/logbackup/EventAlarm.pl 2 23 "" "Logical Log 88372 Complete, > timestamp: 0xd50ade2c." "" > > --047d7bd7689415ee3f04f0bd91a1 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7b86eae66fba3004f0f9f1dd