1. Stop NetWorker

2. do rpcinfo -p localhost

3. If you see any 390XXX numbers, removed them with rpcinfo -d 390XXX

4. Check with lsof that 7937 and 7938 are not used

5. /sbin/init.d/networker start

If above does not do the trick, try to reboot the box.

Yeah, it is not there by default - you need to install it. Did you try to reboot the machine too?

ok, I assume if something was wrong with RPC that would be cleaned by reboots.  I assume there is nothing relevant in /var/adm/syslog/syslog.log?  If so, can you show me output of rpcinfo -p localhost please?

Server has been rebooted twice. Last as recently has mid-day...yesterday.

Btw, did this happens since you upgrade (since you mentioned 7.6.0 and 7.4.1?).  I ask this as I recently moved to 7.6.3.7 on 11.31 ia64 and the only reason I didn't went to 7.6.4.1 was certain ssl issue which I decided to skip by rather going to 7.6.4.2 which should be out by the end of this month.

Networker isn't running....thus my problem

I upgraded because EMC Support requested it.

It was working before, then we had an issue with the tape library. I stopped Networker, fixed the tape library issue, and haven't been able to start Networker again.

Upgraded from 7.6 to 7.6.4.1 yesterday at request of support to see if that would fix the issue. No...same problem.

No 390XXX ports at all listed as per rpcinfo.

Oh....and lsof is not on the server. I just searched the entire server for lsof....not there.

ok, this part is ok... I have hpux boxes in cluster so I did a test on standby node by shutting down nsr and I get similar:

# rpcinfo -p localhost

   program vers proto   port  service

    100000    4   tcp    111  rpcbind

    100000    3   tcp    111  rpcbind

    100000    2   tcp    111  rpcbind

    100000    4   udp    111  rpcbind

    100000    3   udp    111  rpcbind

    100000    2   udp    111  rpcbind

    100024    1   udp  49168  status

    100021    1   udp   4045  nlockmgr

    100024    1   tcp  49152  status

    100021    2   udp   4045  nlockmgr

    100021    3   udp   4045  nlockmgr

    100021    4   udp   4045  nlockmgr

    100133    1   udp  49168

    100021    1   tcp   4045  nlockmgr

    100133    1   tcp  49152

    100021    2   tcp   4045  nlockmgr

    100021    3   tcp   4045  nlockmgr

    100021    4   tcp   4045  nlockmgr

# telnet localhost 7937

Trying...

telnet: Unable to connect to remote host: Connection refused

# telnet localhost 7938

Trying...

telnet: Unable to connect to remote host: Connection refused

Please check the rest from previous email and then we more further.

How can I email you directly?

dpeaco@acxiom.com

The only thing from syslog is that you run via sudo networker.  What I would like to see is following:

- rpcinfo -p localhost output (do it as root)

- while NW is down (like now), do telnet localhost 7937 and let us know what output you get

- while NW is down (still ), do telnet localhost 7938 and let us know what output you get

- can you verify nsrauth is disabled (this is hardly related, but....)

- can you check /sbin/init.d/networker and if there is anuthing that sholdn't be (like someone was playing around and added -s

- do ps -ef | grep nsr just to make sure that previous attempts didn't left frozen process

- check if you have zombie processes

- check if /nsr/cores contains any cores recently generated (cd /nsr/cores; du -sk *)

Please send it here and from there we move on further.  I know very well what sudo is and what it does, but I would - at this point - prefer you do it as root without sudo (just to eliminate something else though slim chances are for that since after reboot it failed to start too)

DennisP wrote: How can I email you directly? dpeaco@acxiom.com

You don't.  I use forum... if you are concerned about some data to be exposed here, just replace offending string with foo or bar.