nsrexecd errors during legato backups

[TD Clark]

Hello...I've been working with Legato support on a problem we've been experiencing on our L2000 v11.11 servers on our nightly backups. The errors we're seeing are in /nsr/logs/daemon.log. Text of the error messages: "nsrexecd: failed to write NUL handshake on 5: errno 32. Broken Pipe". Does anyone anyone have an idea what could be happening here? We've been banging our heads against the walls on this (ouch) and finally decided to check with the discussion board for thoughts. Thx!

[Robert-Jan Goossens]

Hi Todd,

All I can think off, is one of the tcp ports used by nsrexecd is in use by an other process.

If my memory serves me, nsrexecd uses 2914 and 2917.

Hope it helps,
Robert-Jan

[Elmar P. Kolkman · Accepted solution]

1) Checkout the networker mailinglist on this... http://listmail.temple.edu/archives/networker.html
2) Is this on the backup server or on a backup client? nsrexecd executes commands for networker, for instance the nsrmmd and nsrindexd processes on a server and the save commands on a client.
3) What version of Legato are you using?
4) Are there firewalls involved?
5) Does the L2000 completely fail its backups, or only partially?

On place to start looking: /nsr/cores/*
If on of those directories contains files, have legato start looking into those, probably the problem is with that command.

Hope I can help more if you give more info.

[T G Manikandan]

I think the problem is with the inactivity time period between the client and the server.

Are these messages coming up from a machine where the backup server was unable to connect to its client agent.

Else,if there is a parameter like keepalive which helps in making the session alive between the server and client.

[T G Manikandan]

Todd,

Legato guides point that these messages are "Informational"

check the attached error message guide