EMC has finally provided a work around to me that is working 100% of the time!
Instead of using:
nsrports -S 7937-7940
use:
nsrports -S 7938-7941
Frank
On 5/5/09 3:14 PM, Blackburn, Marvin wrote:
We are having the same issues.
However, our systems seem to just stop responding after several days.
We have done what EMC suggested with starting the ntp afterwards, but
this hasn't fixed the problems.
Is your error only on reboots?
_____________________________________
"He's no failure. He's not dead yet."
William Lloyd George
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Francis Swasey
Sent: Tuesday, May 05, 2009 2:23 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] NetWorker 7.5.x and tight nsrports settings
I am finding that nsrexecd does not reliably start on systems where I
have used nsrports to
restrict the client to just having the four (4) ports it requires. I am
seeing this
specifically on linux clients. I have measured an average failure to
start of 65%. This is
with both 7.5 and 7.5sp1.
Since the EMC droid I'm working with is unable to find a machine to test
on (give me a break!)
-- can anyone else that has restricted the client to using just four
ports comment on whether
or not they are seeing the same problem?
Thanks,
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
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
| 