onbar and OmniBack II

HP UX 11.x, Informix DS 7.24.UC5, using Omniback II storage manager Recently, we are experiencing a very odd phenomenomenomenon (!?). We have been using onbar for a number of months now with no real problems ( a few minor ones loosing logs, but thats another story ). We re-booted our server last night and now, whenever a logical log fille is archived ( using the log_full.sh ), it leaves the "onbar -l" process in limbo eating up CPU time. It started causing problems when 35 onbar processes were identified and the system was running like a dog ( with no legs ). The bar_act.log file contains nothing of any significance ( apart from the fact that it reports that the logical logs have been archived ), the online.log file contains nothing ( except reporting that the logical log archives are successful ), and omniback is also reporting all things are fine. The storage manager references all the logical logs that are reportedly archived, but the onbar processes are still hanging around. Having called Informix Tech Support ( Marco is still on it !! ) we had to "kill -9" the child onbar process which freed up the sessions and reported that:- 13:31:23 Logical Log 12814 Complete. 13:31:27 Logical Log 12814 - Backup Started 13:32:38 Logical Log 12814 - Backup Completed 13:32:38 Process exited with return code 1: /bin/sh /bin/sh -c /home/informix/etc/log_full.sh 2 18 "Log Backup completed: 12814." "Logical Log 12814 - Backup C omplet Oddly enought though, the oncfg_baanshm.0 file doesn't contain a list of the successfully archived logs (???). Does anyone have the remotest idea as to what is going on ?? P.S. Re-booting the server is currently not an option, unless a very, very good argument is put forward - granted, saying that they don't have any logical log archives and the system may become corrupt may just sway them... TIA as usual Sean

In article <36d40f41.0@145.227.194.253>, "Sean Kelsey" <chilliinc@hotmail.com> wrote: > HP UX 11.x, Informix DS 7.24.UC5, using Omniback II storage manager > > Recently, we are experiencing a very odd phenomenomenomenon (!?). We have > been using onbar for a number of months now with no real problems ( a few > minor ones loosing logs, but thats another story ). > > We re-booted our server last night and now, whenever a logical log fille is > archived ( using the log_full.sh ), it leaves the "onbar -l" process in > limbo eating up CPU time. It started causing problems when 35 onbar > processes were identified and the system was running like a dog ( with no > legs ). > > The bar_act.log file contains nothing of any significance ( apart from the > fact that it reports that the logical logs have been archived ), the > online.log file contains nothing ( except reporting that the logical log > archives are successful ), and omniback is also reporting all things are > fine. > > The storage manager references all the logical logs that are reportedly > archived, but the onbar processes are still hanging around. > > Having called Informix Tech Support ( Marco is still on it !! ) we had to > "kill -9" the child onbar process which freed up the sessions and reported > that:- > > 13:31:23 Logical Log 12814 Complete. > 13:31:27 Logical Log 12814 - Backup Started > 13:32:38 Logical Log 12814 - Backup Completed > 13:32:38 Process exited with return code 1: /bin/sh /bin/sh -c > /home/informix/e> tc/log_full.sh 2 18 "Log Backup completed: 12814." "Logical Log 12814 - > Backup C > omplet > > Oddly enought though, the oncfg_baanshm.0 file doesn't contain a list of the > successfully archived logs (???). > > Does anyone have the remotest idea as to what is going on ?? > > P.S. Re-booting the server is currently not an option, unless a very, very > good argument is put forward - granted, saying that they don't have any > logical log archives and the system may become corrupt may just sway them... > > TIA as usual > > Sean > > Sounds like an Informix problem to me...just curious...what OmniBack version are you using 3.0 or 2.55 ? -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Just to give you the answers. Apparently, Omniback, when shut-down, didn't recognise that one of its processes had failed to die, so when re-started, omniback saw its process there and didn't say a word. The process had, in fact, died when we re-initialised the server last Tuesday (don't ask). So, we killed all omniback processes and re-started it. onbar now works fine and all omniback archives appear to be going successfully. Sean Sean Kelsey wrote in message <36d40f41.0@145.227.194.253>... >HP UX 11.x, Informix DS 7.24.UC5, using Omniback II storage manager > >Recently, we are experiencing a very odd phenomenomenomenon (!?). We have >been using onbar for a number of months now with no real problems ( a few >minor ones loosing logs, but thats another story ). > >We re-booted our server last night and now, whenever a logical log fille is >archived ( using the log_full.sh ), it leaves the "onbar -l" process in >limbo eating up CPU time. It started causing problems when 35 onbar >processes were identified and the system was running like a dog ( with no >legs ). > >The bar_act.log file contains nothing of any significance ( apart from the >fact that it reports that the logical logs have been archived ), the >online.log file contains nothing ( except reporting that the logical log >archives are successful ), and omniback is also reporting all things are >fine. > >The storage manager references all the logical logs that are reportedly >archived, but the onbar processes are still hanging around. > >Having called Informix Tech Support ( Marco is still on it !! ) we had to >"kill -9" the child onbar process which freed up the sessions and reported >that:- > >13:31:23 Logical Log 12814 Complete. >13:31:27 Logical Log 12814 - Backup Started >13:32:38 Logical Log 12814 - Backup Completed >13:32:38 Process exited with return code 1: /bin/sh /bin/sh -c >/home/informix/e>tc/log_full.sh 2 18 "Log Backup completed: 12814." "Logical Log 12814 - >Backup C >omplet > >Oddly enought though, the oncfg_baanshm.0 file doesn't contain a list of the >successfully archived logs (???). > >Does anyone have the remotest idea as to what is going on ?? > >P.S. Re-booting the server is currently not an option, unless a very, very >good argument is put forward - granted, saying that they don't have any >logical log archives and the system may become corrupt may just sway them... > >TIA as usual > >Sean > > >

Sean Kelsey wrote: > > HP UX 11.x, Informix DS 7.24.UC5, using Omniback II storage manager > > Recently, we are experiencing a very odd phenomenomenomenon (!?). We have > been using onbar for a number of months now with no real problems ( a few > minor ones loosing logs, but thats another story ). > > We re-booted our server last night and now, whenever a logical log fille is > archived ( using the log_full.sh ), it leaves the "onbar -l" process in > limbo eating up CPU time. It started causing problems when 35 onbar > processes were identified and the system was running like a dog ( with no > legs ). Sounds like onbar is prompting the log_full.sh script and it is not responding so the onbar process hangs waiting for input. Art S. Kagel