On 2008-05-27 12:21, Peter Viertel revealed:

PV> I messed it up back when I had 733 by fiddling with the setting for 
PV> maximum jobsdb size. I'd added a zero to the end thinking that 
PV> allowing it to be bigger would mean less issues with its GC routines 
PV> but Emc told us to put it back to the default and it seemed to work 
PV> since then.

The settings we have changed, per EMC support recommendation is to lower 
the data retention in the jobsdb to three days, and increase the size to 
100MB. This has had no effect, at least not a positive one. :)

Another thing we have changed, also per their recommendation is to 
increase the number of TCP connections that can be opened or be half-open 
per second. I also belive that has no effect, especially considering that 
we still see the same problems. :P

PV> Have you tried moving the whole jobsdb directory aside and restarting 
networker?

Several times, it works OK for a day or two, but then the messages start 
appearing in the logs indicating that stuff can't talk to it, some 
savesets get aborted due to inactivity, nsrjobd takes lots of CPU and 
memory etc etc, until nothing works. That process takes about a week tops.

PV> I share your pain with emc support.

Yes. Nothing has really changed during the last years when it comes to 
their ability to identify and solve software bugs. Although, I am getting 
the feeling that the industry as a whole is closing in to the EMC 
networker level of support (sadly enough).

//Oscar

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER