Prev: Dir Files & Size
Next: Match lines, group and sum
From: James on 18 Jul 2006 13:40
James wrote:
> Hello,
>
> I work for a company who uses Legato Networker to backup their HP-UX
> systems.
>
> The problem is Legato. It seems that on one particular server, Legato
> wants to fail at least once a week. Multiple sites are supported
> solely by me, and I have spent many weeks restoring Legato directories
> when it crashes or encounters wierd problems, and then updating the
> indexes and checking on the settings to make sure nothing has changed
> (online and offline notes are kept on the settings for each server).
>
> The thing that makes this difficult is that I am not allowed to install
> software such as snort, sudo or tripwire. Furthermore, it seems that
> although a limited number of people know the root password (i.e 1-2
> people plus myself, as I am root), certain things are happening that
> would require the root password. Physical security is not optimal, and
> I have to sleep a small number of hours to keep my sanity, otherwise I
> would be onsite or connected otherwise all the time.
>
> A recent issue that concerns me is the numbe of times it's primary
> daemons disappear from the process table, forciong me to go in and
> restart it manually and watch the system. I had written a script to
> automatically check and restart the processes, but it didn't work
> correctly so it was removed from cron.
>
> No signs of external intrusion are found, so it seems to me it would be
> a system issue or internal access to the console for some odd reason to
> only kill this application nightly this week.
>
> Here is the script that was written:
> #!/bin/sh
> outfile="/nsr_up.txt"
> touch $outfile
> echo "Number of processes on host total: `ps -ef | grep nsr | wc -l`"
> >> $outfile
> ps -ef | grep nsrd
> if [ "$?" -eq 0 ]; then
> echo "Exit value of last command was unsuccessful" >> $outfile
> /opt/networker/bin/nsrd
> /opt/networker/bin/nsrexecd
> echo "" >> $outfile
> echo "NSR processes started at `date`" >> $outfile
> echo "Number of NSR process running on host total: `ps -ef | grep nsr
> | wc -l`" >> $outfile
> ps -ef | grep nsr >> $outfile
> sleep 1
> fi
> mailx root(a)myhost.ext < $outfile
> mailx me(a)externaladdr.ext < $outfile
> rm $outfile
>
>
> Can someone point out why:
> 1. These Legato issues are occurring
> 2. Why this script is overloading processes (nsrd loads at least one
> nsrexecd and two nsrexex processes when started)
>
> Thanks.

BTW, the primary shell is /bin/sh.

A few other notes that I've encountered.
Legato continually has issues with Cleaning Tapes and predefined slots,
Read error: no such device or addess,
The client one week decides it's a server resulting in a license issue
that was resolved

Thanks in advance.

From: Ines Schmitt on 18 Jul 2006 15:06
X-No-archive: yes

Hi James,

we are running Networker 7.1.3 on HPUX Itanium and beside the problem of
the non-existing persistent binding solution for tape devices it is
running well. Version 5.5 seems to be rather old, since 7.3.1 is the
current release. I am sorry that I could not help with your specific
problem but I would like to give You a link to a mailinglist where many
Legato networker users gave really helpful tips. I guess You will find a
helpful answer there. HTH

http://www.lsoft.com/scripts/wl.exe?SL1=NETWORKER&H=LISTSERV.TEMPLE.EDU

Ines

Am 18.07.2006 hast Du geschrieben:

>James wrote:
>>
>> Can someone point out why:
>> 1. These Legato issues are occurring
>> 2. Why this script is overloading processes (nsrd loads at least one
>> nsrexecd and two nsrexex processes when started)
>>
>> Thanks.

>BTW, the primary shell is /bin/sh.

>A few other notes that I've encountered.
>Legato continually has issues with Cleaning Tapes and predefined slots,
>Read error: no such device or addess,
>The client one week decides it's a server resulting in a license issue
>that was resolved


From: Chuck Whealton on 28 Jul 2006 12:34

James wrote:
> James wrote:
> > Hello,
> >
> > I work for a company who uses Legato Networker to backup their HP-UX
> > systems.
> >
> > The problem is Legato. It seems that on one particular server, Legato
> > wants to fail at least once a week. Multiple sites are supported
> > solely by me, and I have spent many weeks restoring Legato directories
> > when it crashes or encounters wierd problems, and then updating the
> > indexes and checking on the settings to make sure nothing has changed
> > (online and offline notes are kept on the settings for each server).
> >
> > The thing that makes this difficult is that I am not allowed to install
> > software such as snort, sudo or tripwire. Furthermore, it seems that
> > although a limited number of people know the root password (i.e 1-2
> > people plus myself, as I am root), certain things are happening that
> > would require the root password. Physical security is not optimal, and
> > I have to sleep a small number of hours to keep my sanity, otherwise I
> > would be onsite or connected otherwise all the time.
> >
> > A recent issue that concerns me is the numbe of times it's primary
> > daemons disappear from the process table, forciong me to go in and
> > restart it manually and watch the system. I had written a script to
> > automatically check and restart the processes, but it didn't work
> > correctly so it was removed from cron.
> >
> > No signs of external intrusion are found, so it seems to me it would be
> > a system issue or internal access to the console for some odd reason to
> > only kill this application nightly this week.
> >
> > Here is the script that was written:
> > #!/bin/sh
> > outfile="/nsr_up.txt"
> > touch $outfile
> > echo "Number of processes on host total: `ps -ef | grep nsr | wc -l`"
> > >> $outfile
> > ps -ef | grep nsrd
> > if [ "$?" -eq 0 ]; then
> > echo "Exit value of last command was unsuccessful" >> $outfile
> > /opt/networker/bin/nsrd
> > /opt/networker/bin/nsrexecd
> > echo "" >> $outfile
> > echo "NSR processes started at `date`" >> $outfile
> > echo "Number of NSR process running on host total: `ps -ef | grep nsr
> > | wc -l`" >> $outfile
> > ps -ef | grep nsr >> $outfile
> > sleep 1
> > fi
> > mailx root(a)myhost.ext < $outfile
> > mailx me(a)externaladdr.ext < $outfile
> > rm $outfile
> >
> >
> > Can someone point out why:
> > 1. These Legato issues are occurring
> > 2. Why this script is overloading processes (nsrd loads at least one
> > nsrexecd and two nsrexex processes when started)
> >
> > Thanks.
>
> BTW, the primary shell is /bin/sh.
>
> A few other notes that I've encountered.
> Legato continually has issues with Cleaning Tapes and predefined slots,
> Read error: no such device or addess,
> The client one week decides it's a server resulting in a license issue
> that was resolved
>
> Thanks in advance.

James... HP-UX 11.x includes a "template" in /sbin/init.d that you can
use to put together a decent Legato NetWorker startup. Don't forget to
include the runlevel links to make it work.

As far as your NetWorker processes go, not having one of my company's
HP-UX systems in front of me, to the best of my memory, it SHOULD be:

Server - 1 nsrd process, 2 nsrexecd processes
Client - 2 nsrexecd processes

Remember, I haven't used 5.5 for years, so take that with a grain of
salt.

Good luck!
Charles R. Whealton
Charles Whealton @ pleasedontspam.com

 | 
Pages: 1
Prev: Dir Files & Size
Next: Match lines, group and sum