UNSOLVED
Strange savepnpc problem.
I have a networker server 7.6.2.7 running on CentOS 5.7 and a Windows 2003 Server running the 7.6.2.7 client.
I have an incremental group which runs pre and post-scripts through savepnpc and this works well and have worked all the time.
I have also a Full group which should run the same pre and post scripts, but for some strange reason it doesn't. If I delete the group.res file, it does create it, but it doesn't run it. There is nothing in the savepnpc.log file on the client either. For some reason it simply ignores it.
In the /nsr/tmp/sg/{group}/sso.{client}.* files I can see savepnpc is run, but no sign of any output from the pre or post script, which by default is echo hello and bye.
I do run the client as a different user, because the real scripts should be run as that user. Could this be a problem? But why does then the incremental group work as the same user?
I run the savepnpc with -v but I don't get any additional useful output. Really problematic to debug this problem when you get nothing in the logs.
HI Tony,
This does look like a curious issue alright. savepnpc can be quite tricky to troubleshoot. Did you output your pre and post commands to files to see if those files are created? From what I can see there seems to be two differences between what works and what doesn't, the level of the backup and the user. You should test to identify which one of these is the problem. I'd guess that the user is the more likely issue here, with maybe the user not having the correct permissions to access the /nsr/tmp or something like that.
-Bobby
-D9 did help on this matter. I will investigate this further, but I found this in the log:
couldn't lock temp file 'C:\Program Files\Legato\nsr\tmp\Full.A-Archive.tmp'
The tmp file is locked. Another savepnpc may be running. The .tmp file inhibits preclntsave execution.
By stopping nw service and deleting everything under ../nsr/tmp I managed to start a succesful save, but it will take some time for it to complete. So stay tuned for further reports....
Ok. Solved this one. The problem was that the postcmd script never run to the end, which left the pstclntsave command running "forever". And the reason to that was my own mistake and it has actually nothing to do with networker at all.
My problem was, that the script ran a command with ssh to another server. But for some reason I had forgotten the "-n" option from the Full script. Which I had on the Incremental script. (The -n option will put the ssh program in the background.)
So I solved this one myself, but thanks for the -D9 tip. That led me to the real problem.
AllanW1
334 Posts
1033
0
Posted February 15th, 2012 12:00
Hi Tony,
I moved this one over for additional review..
Thanks,
Allan