Fw: onbar hangs

You could also try increasing the debug level for onbar, see what its doing when its stuck. ----- Original Message ----- From: "Doug McAllister" <doug.mcallister@nospam.fmr.com> To: <informix-list@iiug.org> Sent: Wednesday, August 13, 2003 16:45 Subject: Re: onbar hangs > How about something simple like maybe the storage manager is waiting for a > tape mount? > When the onbar is hanging, don't just kill it but go into your storage > manager and see what it thinks is happening. > > "rkusenet" <rkusenet@sympatico.ca> wrote in message > news:bgro1s$rbvfo$1@ID-75254.news.uni-berlin.de... > > IDS 9.21.UC4 > > Solaris 2.6 > > > > EDS takes our backup using onbar. What we have observed is that, > > quite frequently onbar hangs. By hangs it means, onbar processes > > keep running indefinitely. Since the backup is taken daily, all > > subsequent backups also hang until the earlier on is killed. > > > > I have a script to look for onbar process 15 hours after it > > starts, and if it finds one, it sends a mail as follows:- > > > > ========================================= > > onbar is still running on flx10 > > root 15709 15703 0 00:50:14 ? 0:00 /bin/sh > /opt/informix/bin/onbar -b -L 0 > > root 15878 15711 0 00:51:14 ? 0:00 > /opt/informix/bin/onbar_d -b -L 0 > > root 15879 15711 0 00:51:14 ? 0:00 > /opt/informix/bin/onbar_d -b -L 0 > > root 15873 15711 0 00:51:14 ? 0:00 > /opt/informix/bin/onbar_d -b -L 0 > > root 15872 15711 0 00:51:14 ? 0:00 > /opt/informix/bin/onbar_d -b -L 0 > > root 15871 15711 0 00:51:14 ? 0:00 > /opt/informix/bin/onbar_d -b -L 0 > > root 15874 15711 0 00:51:14 ? 0:00 > /opt/informix/bin/onbar_d -b -L 0 > > root 15711 15709 0 00:50:14 ? 0:01 > /opt/informix/bin/onbar_d -b -L 0 > > ========================================= > > > > The ssyadmin then kills the processes indicated above. > > > > Once they kill the client process, we get this message in online.log > > ======================================= > > 15:04:10 Archive on logs02 ABORTED. > > 15:04:10 Aborted by client. > > 15:04:10 Archive on logs03 ABORTED. > > 15:04:10 Aborted by client. > > 15:04:10 Archive on logs04 ABORTED. > > 15:04:10 Aborted by client. > > 15:04:10 Archive on physdbs ABORTED. > > 15:04:10 Aborted by client. > > 15:04:11 Archive on fdbs04 ABORTED. > > 15:04:11 Aborted by client. > > 15:04:11 Archive on gdbs01 ABORTED. > > 15:04:11 Aborted by client. > > =======================================> > In other words, the backup is useless. > > > > Earlier on, it use to be once/twice a month. Now it is once/twice a week. > > What could be wrong with it. Why does onbar hang for 15 hours without > doing > > anything. > > > > > > > > > > sending to informix-list