Process exited with return code 0
Frank's IDS 12.10.FC4 on Red Hat Linux started writing "Process exited with return code 0: /bin/sh -c .../alarmprogram.sh 2 23 ..." to the online log after each logical log switch, following an instance bounce; identical instances showed nothing. Replies noted this isn't an error (severity 2, alarm class 23 = log full/switch), suggested checking whether ALRM_ALL_EVENTS had been changed in the onconfig, verifying LTAPEDEV/ALARMPROGRAM, confirming ksh exists (the script uses #!/bin/ksh), and rerunning the command with sh -x to trace it. Frank suspected a changed bash/sh link, but no confirmed resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Folks,
IDS12.10 FC4, Redhead Linux.
I believed I saw this error before and can not recall its answer or
explanation.
/usr/informix/etc/alarmprogram.sh is the original script( no touched). It
was quite before, just started to complain two days ago after the instance
bounce .
Other instances have the same configuration, and DO NOT have this error.
LTAPEDEV /dev/nullALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
Any comments?
Thanks
Frank
14:17:12 Maximum server connections 237
14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns blocked
9, Plog used 19338, Llog used 96819
14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
/usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
0x2596520e." "" 23001
14:17:21 CDR Spool transaction queue completed
14:22:13 Checkpoint Completed: duration was 0 seconds.
14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
0x25a712d1 Interval: 466446
--001a1147b218ce8885051c0497ba
Best way to debug this is to run the command line that's in the log but
adding -x so you can see why it failed:
/bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647
Complete, timestamp: 0x2596520e." "Logical Log 218647 Complete,
timestamp: 0x2596520e."
"" 23001
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Wed, Jul 29, 2015 at 9:42 AM, FRANK <yunyaoqu@gmail.com> wrote:
> Folks,
>
> IDS12.10 FC4, Redhead Linux.
>
> I believed I saw this error before and can not recall its answer or
> explanation.
> /usr/informix/etc/alarmprogram.sh is the original script( no touched). It
> was quite before, just started to complain two days ago after the instance
> bounce .
>
> Other instances have the same configuration, and DO NOT have this error.
>
> LTAPEDEV /dev/null> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
>
> Any comments?
>
> Thanks
> Frank
>
> 14:17:12 Maximum server connections 237
> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns blocked
> 9, Plog used 19338, Llog used 96819
> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> 0x2596520e." "" 23001
> 14:17:21 CDR Spool transaction queue completed
> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> 0x25a712d1 Interval: 466446
>
> --001a1147b218ce8885051c0497ba
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a1134bae0f7f043051c04f46f
Frank,
I do not see an error. The alarmprogram.sh script is provided by default
in the $INFORMIXDIR/etc directory
It receives 6 parameters and depending on the alarm, a different action
is executed.
In your case you are getting the following 6 parameters:
*2
23
Logical Log 218647 Complete, timestamp: 0x2596520e.
Logical Log 218647 Complete, timestamp: 0x2596520e.
<empty string>
23001 *
==> meaning that the severity code is 2 (Information) and the class of
the alarm is 23 which means that the logical log *218647 *was either
full or a switch to a different log took place before the log was
actually full (onmode -l for example).
This is not an error, this is normal behavior. You will get this
everytime a log is full.
Are you sure that this script is in its initial state and was not
modified at all ?
Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
*select * from sysmaster:sysconfig or syscfgtab*
Cordialement, Regards,
Khaled Bentebal
ConsultiX
Tél: 33 (0) 1 39 12 18 00
Fax: 33 (0) 1 39 12 18 18
Mobile: 33 (0) 6 07 78 41 97
Email: khaled.bentebal@consult-ix.fr
Site Web: www.consult-ix.fr
Le 29/07/15 16:42, FRANK a écrit :
> Folks,
>
> IDS12.10 FC4, Redhead Linux.
>
> I believed I saw this error before and can not recall its answer or
> explanation.
> /usr/informix/etc/alarmprogram.sh is the original script( no touched). It
> was quite before, just started to complain two days ago after the instance
> bounce .
>
> Other instances have the same configuration, and DO NOT have this error.
>
> LTAPEDEV /dev/null> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
>
> Any comments?
>
> Thanks
> Frank
>
> 14:17:12 Maximum server connections 237
> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns blocked
> 9, Plog used 19338, Llog used 96819
> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> 0x2596520e." "" 23001
> 14:17:21 CDR Spool transaction queue completed
> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> 0x25a712d1 Interval: 466446
>
> --001a1147b218ce8885051c0497ba
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Hello, Frank.
I think you probably changed the default value of ALRM_ALL_EVENTS in your
onconfig.
Check it out.
Best regards.
Alexandre Marini
IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10
IBM Information Management Informix Technical Professional
IBM Certified Developer - Informix Genero
BRIUG website administrator
Informix independent consultant
> To: ids@iiug.org
> From: khaled.bentebal@consult-ix.fr
> Subject: Re: Process exited with return code 0 [35538]
> Date: Wed, 29 Jul 2015 11:47:56 -0400
>
> Frank,
>
> I do not see an error. The alarmprogram.sh script is provided by default
> in the $INFORMIXDIR/etc directory
>
> It receives 6 parameters and depending on the alarm, a different action
> is executed.
>
> In your case you are getting the following 6 parameters:
> *2
> 23
> Logical Log 218647 Complete, timestamp: 0x2596520e.
> Logical Log 218647 Complete, timestamp: 0x2596520e.
> <empty string>
> 23001 *
>
> ==> meaning that the severity code is 2 (Information) and the class of
> the alarm is 23 which means that the logical log *218647 *was either
> full or a switch to a different log took place before the log was
> actually full (onmode -l for example).
>
> This is not an error, this is normal behavior. You will get this
> everytime a log is full.
>
> Are you sure that this script is in its initial state and was not
> modified at all ?
>
> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> *select * from sysmaster:sysconfig or syscfgtab*
>
> Cordialement, Regards,
>
> Khaled Bentebal
> ConsultiX
> Tél: 33 (0) 1 39 12 18 00
> Fax: 33 (0) 1 39 12 18 18
> Mobile: 33 (0) 6 07 78 41 97
> Email: khaled.bentebal@consult-ix.fr
> Site Web: www.consult-ix.fr
>
> Le 29/07/15 16:42, FRANK a écrit :
> > Folks,
> >
> > IDS12.10 FC4, Redhead Linux.
> >
> > I believed I saw this error before and can not recall its answer or
> > explanation.
> > /usr/informix/etc/alarmprogram.sh is the original script( no touched). It
> > was quite before, just started to complain two days ago after the instance
> > bounce .
> >
> > Other instances have the same configuration, and DO NOT have this error.
> >
> > LTAPEDEV /dev/null> > ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> >
> > Any comments?
> >
> > Thanks
> > Frank
> >
> > 14:17:12 Maximum server connections 237
> > 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns blocked
> > 9, Plog used 19338, Llog used 96819
> > 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > 0x2596520e." "" 23001
> > 14:17:21 CDR Spool transaction queue completed
> > 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> > 0x25a712d1 Interval: 466446
> >
> > --001a1147b218ce8885051c0497ba
> >
> >
> >
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Hi, Khaled,
Yes, the script is the original IBM script, NO modification at all .
--It had been working fine from the beginning ( upgrade time) no such info
in online log;
--Other instances have the exact same configuration and alarm script, NO
such issue.
I am hoping, probably another reboot could resolve it mysteriously ...
Thanks
Frank
On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
khaled.bentebal@consult-ix.fr> wrote:
> Frank,
>
> I do not see an error. The alarmprogram.sh script is provided by default
> in the $INFORMIXDIR/etc directory
>
> It receives 6 parameters and depending on the alarm, a different action
> is executed.
>
> In your case you are getting the following 6 parameters:
> *2
> 23
> Logical Log 218647 Complete, timestamp: 0x2596520e.
> Logical Log 218647 Complete, timestamp: 0x2596520e.
> <empty string>
> 23001 *
>
> ==> meaning that the severity code is 2 (Information) and the class of
> the alarm is 23 which means that the logical log *218647 *was either
> full or a switch to a different log took place before the log was
> actually full (onmode -l for example).
>
> This is not an error, this is normal behavior. You will get this
> everytime a log is full.
>
> Are you sure that this script is in its initial state and was not
> modified at all ?
>
> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> *select * from sysmaster:sysconfig or syscfgtab*
>
> Cordialement, Regards,
>
> Khaled Bentebal
> ConsultiX
> Tél: 33 (0) 1 39 12 18 00
> Fax: 33 (0) 1 39 12 18 18
> Mobile: 33 (0) 6 07 78 41 97
> Email: khaled.bentebal@consult-ix.fr
> Site Web: www.consult-ix.fr
>
> Le 29/07/15 16:42, FRANK a écrit :
> > Folks,
> >
> > IDS12.10 FC4, Redhead Linux.
> >
> > I believed I saw this error before and can not recall its answer or
> > explanation.
> > /usr/informix/etc/alarmprogram.sh is the original script( no touched). It
> > was quite before, just started to complain two days ago after the
> instance
> > bounce .
> >
> > Other instances have the same configuration, and DO NOT have this error.
> >
> > LTAPEDEV /dev/null> > ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> >
> > Any comments?
> >
> > Thanks
> > Frank
> >
> > 14:17:12 Maximum server connections 237
> > 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns
> blocked
> > 9, Plog used 19338, Llog used 96819
> > 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > 0x2596520e." "" 23001
> > 14:17:21 CDR Spool transaction queue completed
> > 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> > 0x25a712d1 Interval: 466446
> >
> > --001a1147b218ce8885051c0497ba
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11466196f84862051c0bd4fb
Folks,
I believe the issue should be caused by a secretly changed "bash" shell
version,
[informix@leslie ~]$ ll /bin/sh
lrwxrwxrwx 1 root root 4 Nov 21 2014 /bin/sh -> bash
Will keep you updated.
Thanks
Frank
On Wed, Jul 29, 2015 at 7:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> Hi, Khaled,
>
> Yes, the script is the original IBM script, NO modification at all .
>
> --It had been working fine from the beginning ( upgrade time) no such info
> in online log;
> --Other instances have the exact same configuration and alarm script, NO
> such issue.
>
> I am hoping, probably another reboot could resolve it mysteriously ...
>
> Thanks
> Frank
>
> On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> khaled.bentebal@consult-ix.fr> wrote:
>
> > Frank,
> >
> > I do not see an error. The alarmprogram.sh script is provided by default
> > in the $INFORMIXDIR/etc directory
> >
> > It receives 6 parameters and depending on the alarm, a different action
> > is executed.
> >
> > In your case you are getting the following 6 parameters:
> > *2
> > 23
> > Logical Log 218647 Complete, timestamp: 0x2596520e.
> > Logical Log 218647 Complete, timestamp: 0x2596520e.
> > <empty string>
> > 23001 *
> >
> > ==> meaning that the severity code is 2 (Information) and the class of
> > the alarm is 23 which means that the logical log *218647 *was either
> > full or a switch to a different log took place before the log was
> > actually full (onmode -l for example).
> >
> > This is not an error, this is normal behavior. You will get this
> > everytime a log is full.
> >
> > Are you sure that this script is in its initial state and was not
> > modified at all ?
> >
> > Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > *select * from sysmaster:sysconfig or syscfgtab*
> >
> > Cordialement, Regards,
> >
> > Khaled Bentebal
> > ConsultiX
> > Tél: 33 (0) 1 39 12 18 00
> > Fax: 33 (0) 1 39 12 18 18
> > Mobile: 33 (0) 6 07 78 41 97
> > Email: khaled.bentebal@consult-ix.fr
> > Site Web: www.consult-ix.fr
> >
> > Le 29/07/15 16:42, FRANK a écrit :
> > > Folks,
> > >
> > > IDS12.10 FC4, Redhead Linux.
> > >
> > > I believed I saw this error before and can not recall its answer or
> > > explanation.
> > > /usr/informix/etc/alarmprogram.sh is the original script( no touched).
> It
> > > was quite before, just started to complain two days ago after the
> > instance
> > > bounce .
> > >
> > > Other instances have the same configuration, and DO NOT have this
> error.
> > >
> > > LTAPEDEV /dev/null> > > ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > >
> > > Any comments?
> > >
> > > Thanks
> > > Frank
> > >
> > > 14:17:12 Maximum server connections 237
> > > 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns
> > blocked
> > > 9, Plog used 19338, Llog used 96819
> > > 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > 0x2596520e." "" 23001
> > > 14:17:21 CDR Spool transaction queue completed
> > > 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > > 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> > > 0x25a712d1 Interval: 466446
> > >
> > > --001a1147b218ce8885051c0497ba
> > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --001a11466196f84862051c0bd4fb
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a113a34268c598b051c18eaa5
Is ksh installed on this server? alarmprogram.sh uses ksh by default. Ive seen
those types of messages on linux if ksh is not installed locally.
Brad Patterson
> On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
>
> Hi, Khaled,
>
> Yes, the script is the original IBM script, NO modification at all .
>
> --It had been working fine from the beginning ( upgrade time) no such info
> in online log;
> --Other instances have the exact same configuration and alarm script, NO
> such issue.
>
> I am hoping, probably another reboot could resolve it mysteriously ...
>
> Thanks
> Frank
>
> On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> khaled.bentebal@consult-ix.fr> wrote:
>
>> Frank,
>>
>> I do not see an error. The alarmprogram.sh script is provided by default
>> in the $INFORMIXDIR/etc directory
>>
>> It receives 6 parameters and depending on the alarm, a different action
>> is executed.
>>
>> In your case you are getting the following 6 parameters:
>> *2
>> 23
>> Logical Log 218647 Complete, timestamp: 0x2596520e.
>> Logical Log 218647 Complete, timestamp: 0x2596520e.
>> <empty string>
>> 23001 *
>>
>> ==> meaning that the severity code is 2 (Information) and the class of
>> the alarm is 23 which means that the logical log *218647 *was either
>> full or a switch to a different log took place before the log was
>> actually full (onmode -l for example).
>>
>> This is not an error, this is normal behavior. You will get this
>> everytime a log is full.
>>
>> Are you sure that this script is in its initial state and was not
>> modified at all ?
>>
>> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
>> *select * from sysmaster:sysconfig or syscfgtab*
>>
>> Cordialement, Regards,
>>
>> Khaled Bentebal
>> ConsultiX
>> Tél: 33 (0) 1 39 12 18 00
>> Fax: 33 (0) 1 39 12 18 18
>> Mobile: 33 (0) 6 07 78 41 97
>> Email: khaled.bentebal@consult-ix.fr
>> Site Web: www.consult-ix.fr
>>
>> Le 29/07/15 16:42, FRANK a écrit :
>>> Folks,
>>>
>>> IDS12.10 FC4, Redhead Linux.
>>>
>>> I believed I saw this error before and can not recall its answer or
>>> explanation.
>>> /usr/informix/etc/alarmprogram.sh is the original script( no touched). It
>>> was quite before, just started to complain two days ago after the
>> instance
>>> bounce .
>>>
>>> Other instances have the same configuration, and DO NOT have this error.
>>>
>>> LTAPEDEV /dev/null>>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
>>>
>>> Any comments?
>>>
>>> Thanks
>>> Frank
>>>
>>> 14:17:12 Maximum server connections 237
>>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns
>> blocked
>>> 9, Plog used 19338, Llog used 96819
>>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
>>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
>>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
>>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
>>> 0x2596520e." "" 23001
>>> 14:17:21 CDR Spool transaction queue completed
>>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
>>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
>>> 0x25a712d1 Interval: 466446
>>>
>>> --001a1147b218ce8885051c0497ba
>>>
>>>
>>>
>>
>>
>
*******************************************************************************
>>> Forum Note: Use "Reply" to post a response in the discussion forum.
>>>
>>>
>>
>>
>>
>>
>
*******************************************************************************
>> Forum Note: Use "Reply" to post a response in the discussion forum.
>>
>>
>
> --001a11466196f84862051c0bd4fb
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Yes, ksh is there.
use ksh ?
it showed : /bin/sh /bin/sh -c......, see below log output.
14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
/usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
0x2596520e." "" 23001
Thanks
Frank
On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <informix@bpatterson.com>
wrote:
> Is ksh installed on this server? alarmprogram.sh uses ksh by default. Ive
> seen
> those types of messages on linux if ksh is not installed locally.
>
> Brad Patterson
>
> > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> >
> > Hi, Khaled,
> >
> > Yes, the script is the original IBM script, NO modification at all .
> >
> > --It had been working fine from the beginning ( upgrade time) no such
> info
> > in online log;
> > --Other instances have the exact same configuration and alarm script, NO
> > such issue.
> >
> > I am hoping, probably another reboot could resolve it mysteriously ...
> >
> > Thanks
> > Frank
> >
> > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > khaled.bentebal@consult-ix.fr> wrote:
> >
> >> Frank,
> >>
> >> I do not see an error. The alarmprogram.sh script is provided by default
> >> in the $INFORMIXDIR/etc directory
> >>
> >> It receives 6 parameters and depending on the alarm, a different action
> >> is executed.
> >>
> >> In your case you are getting the following 6 parameters:
> >> *2
> >> 23
> >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> >> <empty string>
> >> 23001 *
> >>
> >> ==> meaning that the severity code is 2 (Information) and the class of
> >> the alarm is 23 which means that the logical log *218647 *was either
> >> full or a switch to a different log took place before the log was
> >> actually full (onmode -l for example).
> >>
> >> This is not an error, this is normal behavior. You will get this
> >> everytime a log is full.
> >>
> >> Are you sure that this script is in its initial state and was not
> >> modified at all ?
> >>
> >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> >> *select * from sysmaster:sysconfig or syscfgtab*
> >>
> >> Cordialement, Regards,
> >>
> >> Khaled Bentebal
> >> ConsultiX
> >> Tél: 33 (0) 1 39 12 18 00
> >> Fax: 33 (0) 1 39 12 18 18
> >> Mobile: 33 (0) 6 07 78 41 97
> >> Email: khaled.bentebal@consult-ix.fr
> >> Site Web: www.consult-ix.fr
> >>
> >> Le 29/07/15 16:42, FRANK a écrit :
> >>> Folks,
> >>>
> >>> IDS12.10 FC4, Redhead Linux.
> >>>
> >>> I believed I saw this error before and can not recall its answer or
> >>> explanation.
> >>> /usr/informix/etc/alarmprogram.sh is the original script( no touched).
> It
> >>> was quite before, just started to complain two days ago after the
> >> instance
> >>> bounce .
> >>>
> >>> Other instances have the same configuration, and DO NOT have this
> error.
> >>>
> >>> LTAPEDEV /dev/null> >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> >>>
> >>> Any comments?
> >>>
> >>> Thanks
> >>> Frank
> >>>
> >>> 14:17:12 Maximum server connections 237
> >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns
> >> blocked
> >>> 9, Plog used 19338, Llog used 96819
> >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> >>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> >>> 0x2596520e." "" 23001
> >>> 14:17:21 CDR Spool transaction queue completed
> >>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> >>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> >>> 0x25a712d1 Interval: 466446
> >>>
> >>> --001a1147b218ce8885051c0497ba
> >>>
> >>>
> >>>
> >>
> >>
> >
>
>
*******************************************************************************
> >>> Forum Note: Use "Reply" to post a response in the discussion forum.
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
>
>
*******************************************************************************
> >> Forum Note: Use "Reply" to post a response in the discussion forum.
> >>
> >>
> >
> > --001a11466196f84862051c0bd4fb
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a1135b4d2cfbaef051c19ac8e
Yes, but the script itself is KSH:
[infx1210@tardis etc]$ head $INFORMIXDIR/etc/alarmprogram.sh
#!/bin/ksh
#
****************************************************************************
#
# Licensed Materials - Property of IBM
#
# "Restricted Materials of IBM"
#
# IBM Informix Dynamic Server
# Copyright IBM Corporation 1996, 2011
#
[infx1210@tardis etc]$
Have you already tried the test that Art asked?
/bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log
218647 Complete,
timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
0x2596520e." "" 23001
Keen regards.
On Thu, 30 Jul 2015 at 16:52 FRANK <yunyaoqu@gmail.com> wrote:
> Yes, ksh is there.
>
> use ksh ?
>
> it showed : /bin/sh /bin/sh -c......, see below log output.
>
> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> 0x2596520e." "" 23001
>
> Thanks
> Frank
>
> On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <informix@bpatterson.com>
> wrote:
>
> > Is ksh installed on this server? alarmprogram.sh uses ksh by default. Ive
> > seen
> > those types of messages on linux if ksh is not installed locally.
> >
> > Brad Patterson
> >
> > > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> > >
> > > Hi, Khaled,
> > >
> > > Yes, the script is the original IBM script, NO modification at all .
> > >
> > > --It had been working fine from the beginning ( upgrade time) no such
> > info
> > > in online log;
> > > --Other instances have the exact same configuration and alarm script,
> NO
> > > such issue.
> > >
> > > I am hoping, probably another reboot could resolve it mysteriously ...
> > >
> > > Thanks
> > > Frank
> > >
> > > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > > khaled.bentebal@consult-ix.fr> wrote:
> > >
> > >> Frank,
> > >>
> > >> I do not see an error. The alarmprogram.sh script is provided by
> default
> > >> in the $INFORMIXDIR/etc directory
> > >>
> > >> It receives 6 parameters and depending on the alarm, a different
> action
> > >> is executed.
> > >>
> > >> In your case you are getting the following 6 parameters:
> > >> *2
> > >> 23
> > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > >> <empty string>
> > >> 23001 *
> > >>
> > >> ==> meaning that the severity code is 2 (Information) and the class of
> > >> the alarm is 23 which means that the logical log *218647 *was either
> > >> full or a switch to a different log took place before the log was
> > >> actually full (onmode -l for example).
> > >>
> > >> This is not an error, this is normal behavior. You will get this
> > >> everytime a log is full.
> > >>
> > >> Are you sure that this script is in its initial state and was not
> > >> modified at all ?
> > >>
> > >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > >> *select * from sysmaster:sysconfig or syscfgtab*
> > >>
> > >> Cordialement, Regards,
> > >>
> > >> Khaled Bentebal
> > >> ConsultiX
> > >> Tél: 33 (0) 1 39 12 18 00
> > >> Fax: 33 (0) 1 39 12 18 18
> > >> Mobile: 33 (0) 6 07 78 41 97
> > >> Email: khaled.bentebal@consult-ix.fr
> > >> Site Web: www.consult-ix.fr
> > >>
> > >> Le 29/07/15 16:42, FRANK a écrit :
> > >>> Folks,
> > >>>
> > >>> IDS12.10 FC4, Redhead Linux.
> > >>>
> > >>> I believed I saw this error before and can not recall its answer or
> > >>> explanation.
> > >>> /usr/informix/etc/alarmprogram.sh is the original script( no
> touched).
> > It
> > >>> was quite before, just started to complain two days ago after the
> > >> instance
> > >>> bounce .
> > >>>
> > >>> Other instances have the same configuration, and DO NOT have this
> > error.
> > >>>
> > >>> LTAPEDEV /dev/null> > >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > >>>
> > >>> Any comments?
> > >>>
> > >>> Thanks
> > >>> Frank
> > >>>
> > >>> 14:17:12 Maximum server connections 237
> > >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns
> > >> blocked
> > >>> 9, Plog used 19338, Llog used 96819
> > >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > >>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > >>> 0x2596520e." "" 23001
> > >>> 14:17:21 CDR Spool transaction queue completed
> > >>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > >>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> > >>> 0x25a712d1 Interval: 466446
> > >>>
> > >>> --001a1147b218ce8885051c0497ba
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >
> >
> >
>
>
*******************************************************************************
> > >>> Forum Note: Use "Reply" to post a response in the discussion forum.
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >>
> > >
> >
> >
>
>
*******************************************************************************
> > >> Forum Note: Use "Reply" to post a response in the discussion forum.
> > >>
> > >>
> > >
> > > --001a11466196f84862051c0bd4fb
> > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --001a1135b4d2cfbaef051c19ac8e
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--bcaec53f39858128df051c19d430
Tried,
[informix@maggie ~]$ /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23
"Logical Log 218647 Complete,timestamp: 0x2596520e." "Logical Log 218647
Complete, timestamp: 0x2596520e." "" 23001
+ /usr/informix/etc/alarmprogram.sh
SENDER IS NULL NO MAIL WILL BE SENT
comments?
Thanks
Frank
On Thu, Jul 30, 2015 at 12:02 PM, Ricardo Henriques <
ricardoaireshenriques@gmail.com> wrote:
> Yes, but the script itself is KSH:
> [infx1210@tardis etc]$ head $INFORMIXDIR/etc/alarmprogram.sh
> #!/bin/ksh
> #
>
> ****************************************************************************
> #
> # Licensed Materials - Property of IBM
> #
> # "Restricted Materials of IBM"
> #
> # IBM Informix Dynamic Server
> # Copyright IBM Corporation 1996, 2011
> #
> [infx1210@tardis etc]$
>
> Have you already tried the test that Art asked?
> /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log
> 218647 Complete,
> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> 0x2596520e." "" 23001
>
> Keen regards.
>
> On Thu, 30 Jul 2015 at 16:52 FRANK <yunyaoqu@gmail.com> wrote:
>
> > Yes, ksh is there.
> >
> > use ksh ?
> >
> > it showed : /bin/sh /bin/sh -c......, see below log output.
> >
> > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > 0x2596520e." "" 23001
> >
> > Thanks
> > Frank
> >
> > On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <
> informix@bpatterson.com>
> > wrote:
> >
> > > Is ksh installed on this server? alarmprogram.sh uses ksh by default.
> Ive
> > > seen
> > > those types of messages on linux if ksh is not installed locally.
> > >
> > > Brad Patterson
> > >
> > > > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> > > >
> > > > Hi, Khaled,
> > > >
> > > > Yes, the script is the original IBM script, NO modification at all .
> > > >
> > > > --It had been working fine from the beginning ( upgrade time) no such
> > > info
> > > > in online log;
> > > > --Other instances have the exact same configuration and alarm script,
> > NO
> > > > such issue.
> > > >
> > > > I am hoping, probably another reboot could resolve it mysteriously
> ...
> > > >
> > > > Thanks
> > > > Frank
> > > >
> > > > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > > > khaled.bentebal@consult-ix.fr> wrote:
> > > >
> > > >> Frank,
> > > >>
> > > >> I do not see an error. The alarmprogram.sh script is provided by
> > default
> > > >> in the $INFORMIXDIR/etc directory
> > > >>
> > > >> It receives 6 parameters and depending on the alarm, a different
> > action
> > > >> is executed.
> > > >>
> > > >> In your case you are getting the following 6 parameters:
> > > >> *2
> > > >> 23
> > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > >> <empty string>
> > > >> 23001 *
> > > >>
> > > >> ==> meaning that the severity code is 2 (Information) and the class
> of
> > > >> the alarm is 23 which means that the logical log *218647 *was either
> > > >> full or a switch to a different log took place before the log was
> > > >> actually full (onmode -l for example).
> > > >>
> > > >> This is not an error, this is normal behavior. You will get this
> > > >> everytime a log is full.
> > > >>
> > > >> Are you sure that this script is in its initial state and was not
> > > >> modified at all ?
> > > >>
> > > >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > > >> *select * from sysmaster:sysconfig or syscfgtab*
> > > >>
> > > >> Cordialement, Regards,
> > > >>
> > > >> Khaled Bentebal
> > > >> ConsultiX
> > > >> Tél: 33 (0) 1 39 12 18 00
> > > >> Fax: 33 (0) 1 39 12 18 18
> > > >> Mobile: 33 (0) 6 07 78 41 97
> > > >> Email: khaled.bentebal@consult-ix.fr
> > > >> Site Web: www.consult-ix.fr
> > > >>
> > > >> Le 29/07/15 16:42, FRANK a écrit :
> > > >>> Folks,
> > > >>>
> > > >>> IDS12.10 FC4, Redhead Linux.
> > > >>>
> > > >>> I believed I saw this error before and can not recall its answer or
> > > >>> explanation.
> > > >>> /usr/informix/etc/alarmprogram.sh is the original script( no
> > touched).
> > > It
> > > >>> was quite before, just started to complain two days ago after the
> > > >> instance
> > > >>> bounce .
> > > >>>
> > > >>> Other instances have the same configuration, and DO NOT have this
> > > error.
> > > >>>
> > > >>> LTAPEDEV /dev/null> > > >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > > >>>
> > > >>> Any comments?
> > > >>>
> > > >>> Thanks
> > > >>> Frank
> > > >>>
> > > >>> 14:17:12 Maximum server connections 237
> > > >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, # Txns
> > > >> blocked
> > > >>> 9, Plog used 19338, Llog used 96819
> > > >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647
> Complete,
> > > >>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > >>> 0x2596520e." "" 23001
> > > >>> 14:17:21 CDR Spool transaction queue completed
> > > >>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > > >>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018, timestamp:
> > > >>> 0x25a712d1 Interval: 466446
> > > >>>
> > > >>> --001a1147b218ce8885051c0497ba
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > >>> Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > >> Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >>
> > > >>
> > > >
> > > > --001a11466196f84862051c0bd4fb
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >
> > >
> > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> > --001a1135b4d2cfbaef051c19ac8e
> >
> >
> >
> >
>
>
*******************************************************************************
> >
OK, Guys,
Just Confirmed with Sysadmin that the issue was created by the bash
package upgrade.
Version is
Jul 27 17:28:32 Updated: bash-4.1.2-33.el6.x86_64
Any tips for a quick fix from our Informix side or ..... ?
Thanks
Frank
On Thu, Jul 30, 2015 at 12:16 PM, FRANK <yunyaoqu@gmail.com> wrote:
> Tried,
>
> [informix@maggie ~]$ /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23
> "Logical Log 218647 Complete,timestamp: 0x2596520e." "Logical Log 218647
> Complete, timestamp: 0x2596520e." "" 23001
> + /usr/informix/etc/alarmprogram.sh
> SENDER IS NULL NO MAIL WILL BE SENT
>
> comments?
>
> Thanks
> Frank
>
> On Thu, Jul 30, 2015 at 12:02 PM, Ricardo Henriques <
> ricardoaireshenriques@gmail.com> wrote:
>
> > Yes, but the script itself is KSH:
> > [infx1210@tardis etc]$ head $INFORMIXDIR/etc/alarmprogram.sh
> > #!/bin/ksh
> > #
> >
> >
> ****************************************************************************
> > #
> > # Licensed Materials - Property of IBM
> > #
> > # "Restricted Materials of IBM"
> > #
> > # IBM Informix Dynamic Server
> > # Copyright IBM Corporation 1996, 2011
> > #
> > [infx1210@tardis etc]$
> >
> > Have you already tried the test that Art asked?
> > /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log
> > 218647 Complete,
> > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > 0x2596520e." "" 23001
> >
> > Keen regards.
> >
> > On Thu, 30 Jul 2015 at 16:52 FRANK <yunyaoqu@gmail.com> wrote:
> >
> > > Yes, ksh is there.
> > >
> > > use ksh ?
> > >
> > > it showed : /bin/sh /bin/sh -c......, see below log output.
> > >
> > > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > 0x2596520e." "" 23001
> > >
> > > Thanks
> > > Frank
> > >
> > > On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <
> > informix@bpatterson.com>
> > > wrote:
> > >
> > > > Is ksh installed on this server? alarmprogram.sh uses ksh by default.
> > Ive
> > > > seen
> > > > those types of messages on linux if ksh is not installed locally.
> > > >
> > > > Brad Patterson
> > > >
> > > > > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> > > > >
> > > > > Hi, Khaled,
> > > > >
> > > > > Yes, the script is the original IBM script, NO modification at all
> .
> > > > >
> > > > > --It had been working fine from the beginning ( upgrade time) no
> such
> > > > info
> > > > > in online log;
> > > > > --Other instances have the exact same configuration and alarm
> script,
> > > NO
> > > > > such issue.
> > > > >
> > > > > I am hoping, probably another reboot could resolve it mysteriously
> > ...
> > > > >
> > > > > Thanks
> > > > > Frank
> > > > >
> > > > > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > > > > khaled.bentebal@consult-ix.fr> wrote:
> > > > >
> > > > >> Frank,
> > > > >>
> > > > >> I do not see an error. The alarmprogram.sh script is provided by
> > > default
> > > > >> in the $INFORMIXDIR/etc directory
> > > > >>
> > > > >> It receives 6 parameters and depending on the alarm, a different
> > > action
> > > > >> is executed.
> > > > >>
> > > > >> In your case you are getting the following 6 parameters:
> > > > >> *2
> > > > >> 23
> > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >> <empty string>
> > > > >> 23001 *
> > > > >>
> > > > >> ==> meaning that the severity code is 2 (Information) and the
> class
> > of
> > > > >> the alarm is 23 which means that the logical log *218647 *was
> either
> > > > >> full or a switch to a different log took place before the log was
> > > > >> actually full (onmode -l for example).
> > > > >>
> > > > >> This is not an error, this is normal behavior. You will get this
> > > > >> everytime a log is full.
> > > > >>
> > > > >> Are you sure that this script is in its initial state and was not
> > > > >> modified at all ?
> > > > >>
> > > > >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > > > >> *select * from sysmaster:sysconfig or syscfgtab*
> > > > >>
> > > > >> Cordialement, Regards,
> > > > >>
> > > > >> Khaled Bentebal
> > > > >> ConsultiX
> > > > >> Tél: 33 (0) 1 39 12 18 00
> > > > >> Fax: 33 (0) 1 39 12 18 18
> > > > >> Mobile: 33 (0) 6 07 78 41 97
> > > > >> Email: khaled.bentebal@consult-ix.fr
> > > > >> Site Web: www.consult-ix.fr
> > > > >>
> > > > >> Le 29/07/15 16:42, FRANK a écrit :
> > > > >>> Folks,
> > > > >>>
> > > > >>> IDS12.10 FC4, Redhead Linux.
> > > > >>>
> > > > >>> I believed I saw this error before and can not recall its answer
> or
> > > > >>> explanation.
> > > > >>> /usr/informix/etc/alarmprogram.sh is the original script( no
> > > touched).
> > > > It
> > > > >>> was quite before, just started to complain two days ago after the
> > > > >> instance
> > > > >>> bounce .
> > > > >>>
> > > > >>> Other instances have the same configuration, and DO NOT have this
> > > > error.
> > > > >>>
> > > > >>> LTAPEDEV /dev/null> > > > >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > > > >>>
> > > > >>> Any comments?
> > > > >>>
> > > > >>> Thanks
> > > > >>> Frank
> > > > >>>
> > > > >>> 14:17:12 Maximum server connections 237
> > > > >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, #
> Txns
> > > > >> blocked
> > > > >>> 9, Plog used 19338, Llog used 96819
> > > > >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > > >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647
> > Complete,
> > > > >>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > > >>> 0x2596520e." "" 23001
> > > > >>> 14:17:21 CDR Spool transaction queue completed
> > > > >>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > > > >>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018,
> timestamp:
> > > > >>> 0x25a712d1 Interval: 466446
> > > > >>>
> > > > >>> --001a1147b218ce8885051c0497ba
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > > >>> Forum Note: Use "Reply" to post a response in the discussion
> forum.
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > > >> Forum Note: Use "Reply" to pos
Edit the top of the script to use the real ksh rather the link to bash ?
Cheers
Paul
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of FRANK
Sent: Thursday, July 30, 2015 12:42 PM
To: ids@iiug.org
Subject: Re: Process exited with return code 0 [35546]
OK, Guys,
Just Confirmed with Sysadmin that the issue was created by the bash
package upgrade.
Version is
Jul 27 17:28:32 Updated: bash-4.1.2-33.el6.x86_64
Any tips for a quick fix from our Informix side or ..... ?
Thanks
Frank
On Thu, Jul 30, 2015 at 12:16 PM, FRANK <yunyaoqu@gmail.com> wrote:
> Tried,
>
> [informix@maggie ~]$ /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23
> "Logical Log 218647 Complete,timestamp: 0x2596520e." "Logical Log 218647
> Complete, timestamp: 0x2596520e." "" 23001
> + /usr/informix/etc/alarmprogram.sh
> SENDER IS NULL NO MAIL WILL BE SENT
>
> comments?
>
> Thanks
> Frank
>
> On Thu, Jul 30, 2015 at 12:02 PM, Ricardo Henriques <
> ricardoaireshenriques@gmail.com> wrote:
>
> > Yes, but the script itself is KSH:
> > [infx1210@tardis etc]$ head $INFORMIXDIR/etc/alarmprogram.sh
> > #!/bin/ksh
> > #
> >
> >
>
****************************************************************************
> > #
> > # Licensed Materials - Property of IBM
> > #
> > # "Restricted Materials of IBM"
> > #
> > # IBM Informix Dynamic Server
> > # Copyright IBM Corporation 1996, 2011
> > #
> > [infx1210@tardis etc]$
> >
> > Have you already tried the test that Art asked?
> > /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log
> > 218647 Complete,
> > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > 0x2596520e." "" 23001
> >
> > Keen regards.
> >
> > On Thu, 30 Jul 2015 at 16:52 FRANK <yunyaoqu@gmail.com> wrote:
> >
> > > Yes, ksh is there.
> > >
> > > use ksh ?
> > >
> > > it showed : /bin/sh /bin/sh -c......, see below log output.
> > >
> > > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > 0x2596520e." "" 23001
> > >
> > > Thanks
> > > Frank
> > >
> > > On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <
> > informix@bpatterson.com>
> > > wrote:
> > >
> > > > Is ksh installed on this server? alarmprogram.sh uses ksh by
default.
> > Ive
> > > > seen
> > > > those types of messages on linux if ksh is not installed locally.
> > > >
> > > > Brad Patterson
> > > >
> > > > > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> > > > >
> > > > > Hi, Khaled,
> > > > >
> > > > > Yes, the script is the original IBM script, NO modification at all
> .
> > > > >
> > > > > --It had been working fine from the beginning ( upgrade time) no
> such
> > > > info
> > > > > in online log;
> > > > > --Other instances have the exact same configuration and alarm
> script,
> > > NO
> > > > > such issue.
> > > > >
> > > > > I am hoping, probably another reboot could resolve it mysteriously
> > ...
> > > > >
> > > > > Thanks
> > > > > Frank
> > > > >
> > > > > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > > > > khaled.bentebal@consult-ix.fr> wrote:
> > > > >
> > > > >> Frank,
> > > > >>
> > > > >> I do not see an error. The alarmprogram.sh script is provided by
> > > default
> > > > >> in the $INFORMIXDIR/etc directory
> > > > >>
> > > > >> It receives 6 parameters and depending on the alarm, a different
> > > action
> > > > >> is executed.
> > > > >>
> > > > >> In your case you are getting the following 6 parameters:
> > > > >> *2
> > > > >> 23
> > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >> <empty string>
> > > > >> 23001 *
> > > > >>
> > > > >> ==> meaning that the severity code is 2 (Information) and the
> class
> > of
> > > > >> the alarm is 23 which means that the logical log *218647 *was
> either
> > > > >> full or a switch to a different log took place before the log was
> > > > >> actually full (onmode -l for example).
> > > > >>
> > > > >> This is not an error, this is normal behavior. You will get this
> > > > >> everytime a log is full.
> > > > >>
> > > > >> Are you sure that this script is in its initial state and was not
> > > > >> modified at all ?
> > > > >>
> > > > >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > > > >> *select * from sysmaster:sysconfig or syscfgtab*
> > > > >>
> > > > >> Cordialement, Regards,
> > > > >>
> > > > >> Khaled Bentebal
> > > > >> ConsultiX
> > > > >> Tél: 33 (0) 1 39 12 18 00
> > > > >> Fax: 33 (0) 1 39 12 18 18
> > > > >> Mobile: 33 (0) 6 07 78 41 97
> > > > >> Email: khaled.bentebal@consult-ix.fr
> > > > >> Site Web: www.consult-ix.fr
> > > > >>
> > > > >> Le 29/07/15 16:42, FRANK a écrit :
> > > > >>> Folks,
> > > > >>>
> > > > >>> IDS12.10 FC4, Redhead Linux.
> > > > >>>
> > > > >>> I believed I saw this error before and can not recall its answer
> or
> > > > >>> explanation.
> > > > >>> /usr/informix/etc/alarmprogram.sh is the original script( no
> > > touched).
> > > > It
> > > > >>> was quite before, just started to complain two days ago after
the
> > > > >> instance
> > > > >>> bounce .
> > > > >>>
> > > > >>> Other instances have the same configuration, and DO NOT have
this
> > > > error.
> > > > >>>
> > > > >>> LTAPEDEV /dev/null> > > > >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > > > >>>
> > > > >>> Any comments?
> > > > >>>
> > > > >>> Thanks
> > > > >>> Frank
> > > > >>>
> > > > >>> 14:17:12 Maximum server connections 237
> > > > >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, #
> Txns
> > > > >> blocked
> > > > >>> 9, Plog used 19338, Llog used 96819
> > > > >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > > >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647
> > Complete,
> > > > >>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > > >>> 0x2596520e." "" 23001
> > > > >>> 14:17:21 CDR Spool transaction queue completed
> > > > >>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > > > >>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018,
> timestamp:
> > > > >>> 0x25a712d1 Interval: 466446
> > > > >>>
> > > > >>> --001a1147b218ce8885051c0497ba
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
****************************************************************************
***
> > >
Well, I'm stumped! I can't reproduce it, not even using
the ALRM_ALL_EVENTS, using 12.10.FC5 here. Not even modifying the
ALARMPROGRAM.
Check the CONSOLE file also.
But there must be something in the ALARMPROGRAM.
Can you share it?
On Thu, 30 Jul 2015 at 17:16 FRANK <yunyaoqu@gmail.com> wrote:
> Tried,
>
> [informix@maggie ~]$ /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23
> "Logical Log 218647 Complete,timestamp: 0x2596520e." "Logical Log 218647
> Complete, timestamp: 0x2596520e." "" 23001
> + /usr/informix/etc/alarmprogram.sh
> SENDER IS NULL NO MAIL WILL BE SENT
>
> comments?
>
> Thanks
> Frank
>
> On Thu, Jul 30, 2015 at 12:02 PM, Ricardo Henriques <
> ricardoaireshenriques@gmail.com> wrote:
>
> > Yes, but the script itself is KSH:
> > [infx1210@tardis etc]$ head $INFORMIXDIR/etc/alarmprogram.sh
> > #!/bin/ksh
> > #
> >
> >
> ****************************************************************************
> > #
> > # Licensed Materials - Property of IBM
> > #
> > # "Restricted Materials of IBM"
> > #
> > # IBM Informix Dynamic Server
> > # Copyright IBM Corporation 1996, 2011
> > #
> > [infx1210@tardis etc]$
> >
> > Have you already tried the test that Art asked?
> > /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log
> > 218647 Complete,
> > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > 0x2596520e." "" 23001
> >
> > Keen regards.
> >
> > On Thu, 30 Jul 2015 at 16:52 FRANK <yunyaoqu@gmail.com> wrote:
> >
> > > Yes, ksh is there.
> > >
> > > use ksh ?
> > >
> > > it showed : /bin/sh /bin/sh -c......, see below log output.
> > >
> > > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > 0x2596520e." "" 23001
> > >
> > > Thanks
> > > Frank
> > >
> > > On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <
> > informix@bpatterson.com>
> > > wrote:
> > >
> > > > Is ksh installed on this server? alarmprogram.sh uses ksh by default.
> > Ive
> > > > seen
> > > > those types of messages on linux if ksh is not installed locally.
> > > >
> > > > Brad Patterson
> > > >
> > > > > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> > > > >
> > > > > Hi, Khaled,
> > > > >
> > > > > Yes, the script is the original IBM script, NO modification at all
> .
> > > > >
> > > > > --It had been working fine from the beginning ( upgrade time) no
> such
> > > > info
> > > > > in online log;
> > > > > --Other instances have the exact same configuration and alarm
> script,
> > > NO
> > > > > such issue.
> > > > >
> > > > > I am hoping, probably another reboot could resolve it mysteriously
> > ...
> > > > >
> > > > > Thanks
> > > > > Frank
> > > > >
> > > > > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > > > > khaled.bentebal@consult-ix.fr> wrote:
> > > > >
> > > > >> Frank,
> > > > >>
> > > > >> I do not see an error. The alarmprogram.sh script is provided by
> > > default
> > > > >> in the $INFORMIXDIR/etc directory
> > > > >>
> > > > >> It receives 6 parameters and depending on the alarm, a different
> > > action
> > > > >> is executed.
> > > > >>
> > > > >> In your case you are getting the following 6 parameters:
> > > > >> *2
> > > > >> 23
> > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >> <empty string>
> > > > >> 23001 *
> > > > >>
> > > > >> ==> meaning that the severity code is 2 (Information) and the
> class
> > of
> > > > >> the alarm is 23 which means that the logical log *218647 *was
> either
> > > > >> full or a switch to a different log took place before the log was
> > > > >> actually full (onmode -l for example).
> > > > >>
> > > > >> This is not an error, this is normal behavior. You will get this
> > > > >> everytime a log is full.
> > > > >>
> > > > >> Are you sure that this script is in its initial state and was not
> > > > >> modified at all ?
> > > > >>
> > > > >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > > > >> *select * from sysmaster:sysconfig or syscfgtab*
> > > > >>
> > > > >> Cordialement, Regards,
> > > > >>
> > > > >> Khaled Bentebal
> > > > >> ConsultiX
> > > > >> Tél: 33 (0) 1 39 12 18 00
> > > > >> Fax: 33 (0) 1 39 12 18 18
> > > > >> Mobile: 33 (0) 6 07 78 41 97
> > > > >> Email: khaled.bentebal@consult-ix.fr
> > > > >> Site Web: www.consult-ix.fr
> > > > >>
> > > > >> Le 29/07/15 16:42, FRANK a écrit :
> > > > >>> Folks,
> > > > >>>
> > > > >>> IDS12.10 FC4, Redhead Linux.
> > > > >>>
> > > > >>> I believed I saw this error before and can not recall its answer
> or
> > > > >>> explanation.
> > > > >>> /usr/informix/etc/alarmprogram.sh is the original script( no
> > > touched).
> > > > It
> > > > >>> was quite before, just started to complain two days ago after the
> > > > >> instance
> > > > >>> bounce .
> > > > >>>
> > > > >>> Other instances have the same configuration, and DO NOT have this
> > > > error.
> > > > >>>
> > > > >>> LTAPEDEV /dev/null> > > > >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > > > >>>
> > > > >>> Any comments?
> > > > >>>
> > > > >>> Thanks
> > > > >>> Frank
> > > > >>>
> > > > >>> 14:17:12 Maximum server connections 237
> > > > >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, #
> Txns
> > > > >> blocked
> > > > >>> 9, Plog used 19338, Llog used 96819
> > > > >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > > >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647
> > Complete,
> > > > >>> timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > > >>> 0x2596520e." "" 23001
> > > > >>> 14:17:21 CDR Spool transaction queue completed
> > > > >>> 14:22:13 Checkpoint Completed: duration was 0 seconds.
> > > > >>> 14:22:13 Wed Jul 29 - loguniq 218648, logpos 0x1f0ae018,
> timestamp:
> > > > >>> 0x25a712d1 Interval: 466446
> > > > >>>
> > > > >>> --001a1147b218ce8885051c0497ba
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > > >>> Forum Note: Use "Reply" to post a response in the discussion
> forum.
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
*******************************************************************************
> > > > >> Forum Note: Use "Reply" to post a response in t
Change the script to use the ksh you have installed. Right now it is
executing with sh which is linked to bash.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Thu, Jul 30, 2015 at 12:41 PM, FRANK <yunyaoqu@gmail.com> wrote:
> OK, Guys,
>
> Just Confirmed with Sysadmin that the issue was created by the bash
> package upgrade.
>
> Version is
> Jul 27 17:28:32 Updated: bash-4.1.2-33.el6.x86_64
>
> Any tips for a quick fix from our Informix side or ..... ?
>
> Thanks
> Frank
>
> On Thu, Jul 30, 2015 at 12:16 PM, FRANK <yunyaoqu@gmail.com> wrote:
>
> > Tried,
> >
> > [informix@maggie ~]$ /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2
> 23
> > "Logical Log 218647 Complete,timestamp: 0x2596520e." "Logical Log 218647
> > Complete, timestamp: 0x2596520e." "" 23001
> > + /usr/informix/etc/alarmprogram.sh
> > SENDER IS NULL NO MAIL WILL BE SENT
> >
> > comments?
> >
> > Thanks
> > Frank
> >
> > On Thu, Jul 30, 2015 at 12:02 PM, Ricardo Henriques <
> > ricardoaireshenriques@gmail.com> wrote:
> >
> > > Yes, but the script itself is KSH:
> > > [infx1210@tardis etc]$ head $INFORMIXDIR/etc/alarmprogram.sh
> > > #!/bin/ksh
> > > #
> > >
> > >
> >
> ****************************************************************************
> > > #
> > > # Licensed Materials - Property of IBM
> > > #
> > > # "Restricted Materials of IBM"
> > > #
> > > # IBM Informix Dynamic Server
> > > # Copyright IBM Corporation 1996, 2011
> > > #
> > > [infx1210@tardis etc]$
> > >
> > > Have you already tried the test that Art asked?
> > > /bin/sh -x -c /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log
> > > 218647 Complete,
> > > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > 0x2596520e." "" 23001
> > >
> > > Keen regards.
> > >
> > > On Thu, 30 Jul 2015 at 16:52 FRANK <yunyaoqu@gmail.com> wrote:
> > >
> > > > Yes, ksh is there.
> > > >
> > > > use ksh ?
> > > >
> > > > it showed : /bin/sh /bin/sh -c......, see below log output.
> > > >
> > > > 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > > /usr/informix/etc/alarmprogram.sh 2 23 "Logical Log 218647 Complete,
> > > > timestamp: 0x2596520e." "Logical Log 218647 Complete, timestamp:
> > > > 0x2596520e." "" 23001
> > > >
> > > > Thanks
> > > > Frank
> > > >
> > > > On Thu, Jul 30, 2015 at 11:10 AM, Brad Patterson <
> > > informix@bpatterson.com>
> > > > wrote:
> > > >
> > > > > Is ksh installed on this server? alarmprogram.sh uses ksh by
> default.
> > > Ive
> > > > > seen
> > > > > those types of messages on linux if ksh is not installed locally.
> > > > >
> > > > > Brad Patterson
> > > > >
> > > > > > On 29 Jul, 2015, at 17:20 PM, FRANK <yunyaoqu@gmail.com> wrote:
> > > > > >
> > > > > > Hi, Khaled,
> > > > > >
> > > > > > Yes, the script is the original IBM script, NO modification at
> all
> > .
> > > > > >
> > > > > > --It had been working fine from the beginning ( upgrade time) no
> > such
> > > > > info
> > > > > > in online log;
> > > > > > --Other instances have the exact same configuration and alarm
> > script,
> > > > NO
> > > > > > such issue.
> > > > > >
> > > > > > I am hoping, probably another reboot could resolve it
> mysteriously
> > > ...
> > > > > >
> > > > > > Thanks
> > > > > > Frank
> > > > > >
> > > > > > On Wed, Jul 29, 2015 at 11:47 AM, Khaled Bentebal <
> > > > > > khaled.bentebal@consult-ix.fr> wrote:
> > > > > >
> > > > > >> Frank,
> > > > > >>
> > > > > >> I do not see an error. The alarmprogram.sh script is provided by
> > > > default
> > > > > >> in the $INFORMIXDIR/etc directory
> > > > > >>
> > > > > >> It receives 6 parameters and depending on the alarm, a different
> > > > action
> > > > > >> is executed.
> > > > > >>
> > > > > >> In your case you are getting the following 6 parameters:
> > > > > >> *2
> > > > > >> 23
> > > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > > >> Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > > >> <empty string>
> > > > > >> 23001 *
> > > > > >>
> > > > > >> ==> meaning that the severity code is 2 (Information) and the
> > class
> > > of
> > > > > >> the alarm is 23 which means that the logical log *218647 *was
> > either
> > > > > >> full or a switch to a different log took place before the log
> was
> > > > > >> actually full (onmode -l for example).
> > > > > >>
> > > > > >> This is not an error, this is normal behavior. You will get this
> > > > > >> everytime a log is full.
> > > > > >>
> > > > > >> Are you sure that this script is in its initial state and was
> not
> > > > > >> modified at all ?
> > > > > >>
> > > > > >> Check the values of the parameters LTAPEDEV and ALARMPROGRAM :
> > > > > >> *select * from sysmaster:sysconfig or syscfgtab*
> > > > > >>
> > > > > >> Cordialement, Regards,
> > > > > >>
> > > > > >> Khaled Bentebal
> > > > > >> ConsultiX
> > > > > >> Tél: 33 (0) 1 39 12 18 00
> > > > > >> Fax: 33 (0) 1 39 12 18 18
> > > > > >> Mobile: 33 (0) 6 07 78 41 97
> > > > > >> Email: khaled.bentebal@consult-ix.fr
> > > > > >> Site Web: www.consult-ix.fr
> > > > > >>
> > > > > >> Le 29/07/15 16:42, FRANK a écrit :
> > > > > >>> Folks,
> > > > > >>>
> > > > > >>> IDS12.10 FC4, Redhead Linux.
> > > > > >>>
> > > > > >>> I believed I saw this error before and can not recall its
> answer
> > or
> > > > > >>> explanation.
> > > > > >>> /usr/informix/etc/alarmprogram.sh is the original script( no
> > > > touched).
> > > > > It
> > > > > >>> was quite before, just started to complain two days ago after
> the
> > > > > >> instance
> > > > > >>> bounce .
> > > > > >>>
> > > > > >>> Other instances have the same configuration, and DO NOT have
> this
> > > > > error.
> > > > > >>>
> > > > > >>> LTAPEDEV /dev/null> > > > > >>> ALARMPROGRAM $INFORMIXDIR/etc/alarmprogram.sh
> > > > > >>>
> > > > > >>> Any comments?
> > > > > >>>
> > > > > >>> Thanks
> > > > > >>> Frank
> > > > > >>>
> > > > > >>> 14:17:12 Maximum server connections 237
> > > > > >>> 14:17:12 Checkpoint Statistics - Avg. Txn Block Time 0.005, #
> > Txns
> > > > > >> blocked
> > > > > >>> 9, Plog used 19338, Llog used 96819
> > > > > >>> 14:17:15 Logical Log 218647 Complete, timestamp: 0x2596520e.
> > > > > >>> 14:17:15 Process exited with return code 0: /bin/sh /bin/sh -c
> > > > > >>> /usr/informix/etc/alarmprogram.sh 2 23 "Logic