Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+NetWorker\s+7\.5\.x\s+and\s+tight\s+nsrports\s+settings\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Networker\]\s+NetWorker\s+7\.5\.x\s+and\s+tight\s+nsrports\s+settings\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>; Date: Fri, 14 Aug 2009 14:27:47 -0400; 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; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-08/msg00159.html (13,200 bytes)
2. Re: [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>; Date: Sat, 15 Aug 2009 07:49:49 -0400; Sorry to keep responding to my own posts, but I've just discovered that what I pointed out yesterday is not completely correct. With the current releases of 7.5.1 -- use "nsrports -S 7938-7940", and; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-08/msg00163.html (14,125 bytes)
3. [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>; Date: Tue, 5 May 2009 14:23:26 -0400; 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 c; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-05/msg00035.html (12,402 bytes)
4. Re: [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: Michael Borkowski <mikeb AT uwaterloo DOT ca>; Date: Tue, 5 May 2009 14:48:42 -0400; This seem's to work for us: 1. Stop Networker services 2. Empty /nsr/tmp and /nsr/res/nsrladb directories 3. Start networker services 4. Issue nsrports -S 7937-7940 5. Stop networker services 6. Star; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-05/msg00037.html (11,808 bytes)
5. Re: [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: "Blackburn, Marvin" <mblackburn AT GLENRAVEN DOT COM>; Date: Tue, 5 May 2009 15:14:55 -0400; 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 proble; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-05/msg00038.html (13,730 bytes)
6. Re: [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>; Date: Tue, 5 May 2009 15:32:12 -0400; 1. Stop Networker services 2. Empty /nsr/tmp and /nsr/res/nsrladb directories 3. Start networker services 4. Issue nsrports -S 7937-7940 5. Stop networker services 6. Start networker services We got; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-05/msg00039.html (12,467 bytes)
7. Re: [Networker] NetWorker 7.5.x and tight nsrports settings (score: 1): Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>; Date: Tue, 5 May 2009 15:31:53 -0400; Is your error only on reboots? No. If I get it running and then stop it and try to start it again, it's the same game all over again. What do you mean about starting ntp afterward? -- Frank Swasey |; /usr/local/webapp/mharc-adsm.org/html/Networker/2009-05/msg00040.html (12,598 bytes)

Current List: 1 - 7
Page: [1]