Re: [Networker] Cannot Bind Socket ...

Come to think of your case, it would solve the problem, because your filer
should backup to its directly attached storage, and having it to go to
nsrserverhost could cause problem.

What could be happening in my case maybe that my storage node might be
going to the networker server too..

Sincerely,

Arun Sondhi
CCNP,CCDP

Ph: +1 414.382.0206
Extn: 20206




"Macina, Conrad" <Conrad.Macina AT pfizer DOT com>
Sent by: Legato NetWorker discussion <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
11/10/2003 07:37 AM
Please respond to Legato NetWorker discussion; Please respond to "Macina,
Conrad"


        To:     NETWORKER AT LISTMAIL.TEMPLE DOT EDU
        cc:
        Subject:        Re: [Networker] Cannot Bind Socket ...


I don't have a clue what the cause is, but it is not related to the number
of clients. We have two servers with 300+ clients and no problem. The
problem occurred on a server that backs up only itself and one client.



-----Original Message-----
From: asondhi AT ra.rockwell DOT com [mailto:asondhi AT ra.rockwell DOT com]
Sent: Monday, November 10, 2003 8:32 AM
To: Legato NetWorker discussion; Conrad Macina
Cc: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Cannot Bind Socket ...



Which probably could help us, but do you know what causes this? We don't
have too many clients, we are in process of moving clients to this server


Sincerely,

Arun Sondhi
CCNP,CCDP

Ph: +1 414.382.0206
Extn: 20206



        Conrad Macina <conrad.macina AT PFIZER DOT COM>
Sent by: Legato NetWorker discussion <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>


11/10/2003 06:32 AM
Please respond to Legato NetWorker discussion; Please respond to Conrad
Macina



        To:        NETWORKER AT LISTMAIL.TEMPLE DOT EDU
        cc:
        Subject:        Re: [Networker] Cannot Bind Socket ...



We had a similar problem a month or so ago, also on NetWorker 6.1.3 on
Solaris, but with restores on a NetApp Filer configured as an NDMP client.
The "official" Legato recommendation (after checking all the usual address
resolution stuff) is Solution ID legato26973:
  Increase connection port range to 35,000. The default range is from
10,001 to 30,000.
  nsrports -s server -C 10001-35000

That didn't work for us. What did work was changing the sequence of
storage
nodes in the client definition. It had been:
  nsrserverhost
  mopppgnas1
(the latter is the Filer). Changing it to
  mopppgnas1
  nsrserverhost
Fixed the problem.

I hope our situation isn't too different from yours.

Conrad Macina
Pfizer, Inc.
Morris Plains NJ



On Fri, 7 Nov 2003 11:41:59 -0600, Arun Sondhi <asondhi AT RA.ROCKWELL DOT COM>
wrote:

>Hi,
>
>We have a Networker 6.1.3 running on Solaris 8 with DDS and Silo. Since
>three days ago we are getting these errors. There are several entries of
>these in the log file. On 11/04 all the backups failed, last night the
>backups didn't fail, but nwadmin is reporting some of the groups are
>running, but they are over and notification has even sent the information
>...
>
>
>
>11/04/03 11:01:58 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:01:59 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:01:59 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:02:00 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:02:01 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:02:01 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:02:02 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>11/04/03 11:02:03 ansrd: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>
>11/04/03 11:02:34 nsrmon #21246: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>
>11/06/03 22:37:31 nsrexec: Cannot bind socket to connection port in
>configured port range on system mkeubak01.
>
>Sincerely,
>
>Arun Sondhi
>CCNP,CCDP
>
>Ph: +1 414.382.0206
>Extn: 20206
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=





--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=



--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=