SAVEGRP not logging to savegrp.log

Question

Networker 7.4 w/ LGTsc07064 hotfix Server is Win 2K3 SP2 Clients are mostly Win2K3 SP2, some NT 4.0 4 of 7 groups do not log anything to savegrp.log or have any e-mail notification (using BLATT). Client\group configurations are similar. Things I've tried: 1. Recreating groups\clients
otifications , still no output 2. CLI savegrp -vvv -c 'bad client' (multiple lines of 'index \db6\46ca0000\ : The system cannot find the path specified) 3. CLI savegrp -vvv -c (everything reports properly) 4. Tried SMTPMAIL vice Blatt, no change We have gone from truncated messages for all savegroups prior to the hotfix to full messages for some, no messages for others, after the hotfix. Any ideas? Iain Hamilton CFB Borden

ble1 · Answer

Any special reason why you use 7.4? If not you should go to 7.3.3.

hamiltonid · Answer

Other than this problem and getting double print outs of the SSID's everyday, 7.4 is working fine. I see no reason, at this time, to downgrade. Even this is a minor issue from our point of view.
I'm currently working on determining if the problem is related to the amount of text in the messages as when the e-mail is NOT sent, the savegrp and daemon logs are not populated. I have taken a group of twelve servers and as I add them to a new group (taking away any possible problems from savepnpc) everything is fine until number nine, after that, no messages. I'm thinking there might be an issue with the allowed size for the messages and after the size is exceeded, no more message.
Still working on it,,,

Iain

hamiltonid · Answer

The 'magic' size appears to be somewhere around 10KB of text, once you exceed that no savegrp.log entries, no e-mails. 'Status' stills works from the NMC.Any ideas?Iain

ble1 · Answer

There is a patch of course, but I still don't see your reason for 7.4...

ble1 · Answer

You're thinking is wrong - that's exactly why I asked for your reasons of going to 7.4 There are several LGTsc ids covering this issue - you may wish to check it out with support.

hamiltonid · Answer

Why we are using 7.4 is immaterial. The fact is we are using it and we have a small problem. I would think there is more inherent risk with downgrading than staying with a product that seems to be working relatively well.
Is there a patch after 7064?

NetWorker

SAVEGRP not logging to savegrp.log

Was this post helpful?