Re: can't connect to client

[Michael Stauffer]

Thanks for the reply Joi. Nothing you suggested seemed to be an issue, but
I did just restart xinetd on the client and it's working now! Very strange,
because I'd swear I tried that before. But who knows. It's working now
which is great. Thanks again.

-M

On Wed, Dec 17, 2014 at 6:40 PM, Joi L. Ellis 
wrote:

>  With the NIS change… did that involve changing the hostname or IPs the
> server appears to be using as seen from the client?  Is your xinetd using
> tcpwrappers? Do you need to update /etc/hosts.allow, hosts.deny, and/or
> ~amanda/.amandahosts?  Is the new Amanda UID reflected properly in
> xinetd.conf?  Perhaps bouncing xinetd may suffice to solve the issue, if
> you haven’t rebooted the whole host since the NIS changes.
>
>
>
> Is there an iptables  firewall on the client that needs updating?
> AppArmor or SELinux updates?
>
>
>
>
>
> *From:* owner-amanda-us...@amanda.org [mailto:
> owner-amanda-us...@amanda.org] *On Behalf Of *Michael Stauffer
> *Sent:* Wednesday, December 17, 2014 16:31
> *To:* amanda-users@amanda.org
> *Subject:* can't connect to client
>
>
>
> Amanda 3.3.4
>
> CentOS 6.5 (server and client)
>
> Hi,
>
>
>
> I'm having trouble connecting to a client. It used to work. The only thing
> I can think of that's changed since the last time it worked is that the NIS
> server changed. But that seems to be working fine and the amandabackup user
> is available on the client (the server is not using NIS).
>
>
>
> Note that the server works with other clients just fine.
>
>
>
> amcheck on the client shows this:
>
>
>
> WARNING: tesla: selfcheck request failed: recv error: Connection reset by
> peer
>
>
>
> The amandabackup uid changed with the NIS server change, so I went through
> these dirs on the client to make sure files were owned by amandabckup:disk
> (except where they should be owned by root):
>
>
>
> /usr/sbin
>
> /etc/amanda
>
> /usr/libexec/amanda
>
> /var/lib/amanda
>
>
>
> xinetd is running on the client.
>
>
>
> 'netstat -a | grep amanada'  shows:
>
> tcp0  0 *:amanda*:*
>   LISTEN
>
>
>
> Here's the tail of /var/log/amanda/server/jet1/amcheck..debug from
> the server:
>
>
>
> ...
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: make_socket
> opening socket with family 2
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: connect_port:
> Try  port 571: available - Success
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: connected to
> 170.212.169.49:10080
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: our side is
> 0.0.0.0:571
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: try_socksize:
> send buffer size is 65536
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: try_socksize:
> receive buffer size is 65536
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: tcpm_send_token:
> data is still flowing
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients:
> security_stream_seterr(0x1eeb050, recv error: Connection reset by peer)
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients:
> security_seterror(handle=0x1ee6e50, driver=0x3efe86fce0 (BSDTCP) error=recv
> error: Connection reset by peer)
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients:
> security_close(handle=0x1ee6e50, driver=0x3efe86fce0 (BSDTCP))
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients:
> security_stream_close(0x1eeb050)
>
> Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck: pid 1157 finish time Wed
> Dec 17 17:27:50 2014
>
>
>
> Can anyone help me figure this out? Thanks!
>
>
>
> -M
>

RE: can't connect to client

[Joi L. Ellis]

With the NIS change… did that involve changing the hostname or IPs the server 
appears to be using as seen from the client?  Is your xinetd using tcpwrappers? 
Do you need to update /etc/hosts.allow, hosts.deny, and/or 
~amanda/.amandahosts?  Is the new Amanda UID reflected properly in xinetd.conf? 
 Perhaps bouncing xinetd may suffice to solve the issue, if you haven’t 
rebooted the whole host since the NIS changes.

Is there an iptables  firewall on the client that needs updating?  AppArmor or 
SELinux updates?


From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On 
Behalf Of Michael Stauffer
Sent: Wednesday, December 17, 2014 16:31
To: amanda-users@amanda.org
Subject: can't connect to client

Amanda 3.3.4
CentOS 6.5 (server and client)
Hi,

I'm having trouble connecting to a client. It used to work. The only thing I 
can think of that's changed since the last time it worked is that the NIS 
server changed. But that seems to be working fine and the amandabackup user is 
available on the client (the server is not using NIS).

Note that the server works with other clients just fine.

amcheck on the client shows this:

WARNING: tesla: selfcheck request failed: recv error: Connection reset by peer

The amandabackup uid changed with the NIS server change, so I went through 
these dirs on the client to make sure files were owned by amandabckup:disk 
(except where they should be owned by root):

/usr/sbin
/etc/amanda
/usr/libexec/amanda
/var/lib/amanda

xinetd is running on the client.

'netstat -a | grep amanada'  shows:
tcp0  0 *:amanda*:* 
LISTEN

Here's the tail of /var/log/amanda/server/jet1/amcheck..debug from the 
server:

...
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: make_socket opening 
socket with family 2
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: connect_port: Try  
port 571: available - Success
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: connected to 
170.212.169.49:10080
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: our side is 
0.0.0.0:571
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: try_socksize: send 
buffer size is 65536
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: try_socksize: receive 
buffer size is 65536
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: tcpm_send_token: data 
is still flowing
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: 
security_stream_seterr(0x1eeb050, recv error: Connection reset by peer)
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: 
security_seterror(handle=0x1ee6e50, driver=0x3efe86fce0 (BSDTCP) error=recv 
error: Connection reset by peer)
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: 
security_close(handle=0x1ee6e50, driver=0x3efe86fce0 (BSDTCP))
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck-clients: 
security_stream_close(0x1eeb050)
Wed Dec 17 17:27:50 2014: thd-0x1a0e4b0: amcheck: pid 1157 finish time Wed Dec 
17 17:27:50 2014

Can anyone help me figure this out? Thanks!

-M

Re: Can't connect to client on Solaris 10

[Jean-Louis Martineau]

You are using the bsdtcp auth mechanism, you must configure the client 
for it.


/etc/services: add
amanda  10080/tcp


SCOPENAME=VALUE
 name="amanda"
 endpoint_type="dytream"
 proto="tcp"
 isrpc=FALSE
 wait=FALSE
 exec="/libexec/amanda/amandad"
 user="amandabackup"


Jean-Louis

Abilio Carvalho wrote:
Hi. I tried to install amanda on a solaris 10 box (sparc) but it's not  
responding to amchecks.



amcheck's log gives:

1241020517.034653: amcheck-clients: make_socket opening socket with  
family 2
1241020517.034674: amcheck-clients: connect_port: Try  port 703:  
available - Success
1241020517.035322: amcheck-clients: connect_portrange: Connect from  
0.0.0.0.703 failed: Connection refused
1241020517.035333: amcheck-clients: connect_portrange: connect to  
193.73.134.4.10080 failed: Connection refused
1241020517.035347: amcheck-clients: stream_client: Could not bind to  
port in range 700-710.
1241020517.035361: amcheck-clients:  
security_seterror(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)  
error=Connection refused)
1241020517.035370: amcheck-clients: security_close(handle=0x8fe73b0,  
driver=0x2a9620 (BSDTCP))

1241020517.035378: amcheck-clients: security_stream_close(0x8ff1900)
1241020517.271757: amcheck-server: changer: << EXITSTATUS 0
1241020517.271782: amcheck-server: changer: << current 99 0 1
1241020517.271799: amcheck-server: changer_query: changer return was  
99 0 1

1241020517.271831: amcheck-server: changer_query: searchable = 1
1241020517.271843: amcheck-server: changer_find: looking for NULL  
changer is searchable = 1

1241020517.271856: amcheck-server: changer: >> -slot current
1241020522.034995: amcheck-clients:  
security_handleinit(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP))
1241020522.036002: amcheck-clients:  
security_streaminit(stream=0x8ff1900, driver=0x2a9620 (BSDTCP))
1241020522.037590: amcheck-clients: connect_port: Skip port 700: owned  
by epp.
1241020522.038124: amcheck-clients: connect_port: Skip port 701: owned  
by lmp.
1241020522.038651: amcheck-clients: connect_port: Skip port 702: owned  
by iris-beep.
1241020522.041874: amcheck-clients: make_socket opening socket with  
family 2
1241020522.041895: amcheck-clients: connect_port: Try  port 703:  
available - Success
1241020522.042523: amcheck-clients: connect_portrange: Connect from  
0.0.0.0.703 failed: Connection refused
1241020522.042535: amcheck-clients: connect_portrange: connect to  
193.73.134.4.10080 failed: Connection refused
1241020522.042549: amcheck-clients: stream_client: Could not bind to  
port in range 700-710.
1241020522.042563: amcheck-clients:  
security_seterror(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)  
error=Connection refused)
1241020522.042602: amcheck-clients: security_close(handle=0x8fe73b0,  
driver=0x2a9620 (BSDTCP))

1241020522.042611: amcheck-clients: security_stream_close(0x8ff1900)

On the client, /etc/services has the following lines:

amanda  10080/udp
amandaidx   10082/tcp
amidxtape   10083/tcp

and inetadm -l svc:/network/amanda/udp:default reports the following:

SCOPENAME=VALUE
  name="amanda"
  endpoint_type="dgram"
  proto="udp"
  isrpc=FALSE
  wait=TRUE
  exec="/libexec/amanda/amandad"
  user="amandabackup"
default  bind_addr=""
default  bind_fail_max=-1
default  bind_fail_interval=-1
default  max_con_rate=-1
default  max_copies=-1
default  con_rate_offline=-1
default  failrate_cnt=40
default  failrate_interval=60
default  inherit_env=TRUE
default  tcp_trace=FALSE
default  tcp_wrappers=FALSE


However, netstat -a | grep amanda OR netstat -a | grep 1008 returns  
nothing. I have no idea how to proceed anymore. Can anyone help?


Abilio


---
This e-mail is strictly confidential and may be privileged.
It is intended solely for the addressee. If you are not the intended
recipient, any copying, distribution or any other use of this message
is prohibited and may be unlawful. In such case, please notify the
sender Immediately and destroy this e-mail.


  

Re: Can't connect to client on Solaris 10

[Darin Perusich]

Where did you get the amanda package from?

What are the amanda ports defined as on the server? From the below
amcheck log it's trying to connect to port ranging from 700 to 710.

What is the output from 'inetadm |grep amanda'?

Abilio Carvalho wrote:
> Hi. I tried to install amanda on a solaris 10 box (sparc) but it's not  
> responding to amchecks.
> 
> 
> amcheck's log gives:
> 
> 1241020517.034653: amcheck-clients: make_socket opening socket with  
> family 2
> 1241020517.034674: amcheck-clients: connect_port: Try  port 703:  
> available - Success
> 1241020517.035322: amcheck-clients: connect_portrange: Connect from  
> 0.0.0.0.703 failed: Connection refused
> 1241020517.035333: amcheck-clients: connect_portrange: connect to  
> 193.73.134.4.10080 failed: Connection refused
> 1241020517.035347: amcheck-clients: stream_client: Could not bind to  
> port in range 700-710.
> 1241020517.035361: amcheck-clients:  
> security_seterror(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)  
> error=Connection refused)
> 1241020517.035370: amcheck-clients: security_close(handle=0x8fe73b0,  
> driver=0x2a9620 (BSDTCP))
> 1241020517.035378: amcheck-clients: security_stream_close(0x8ff1900)
> 1241020517.271757: amcheck-server: changer: << EXITSTATUS 0
> 1241020517.271782: amcheck-server: changer: << current 99 0 1
> 1241020517.271799: amcheck-server: changer_query: changer return was  
> 99 0 1
> 1241020517.271831: amcheck-server: changer_query: searchable = 1
> 1241020517.271843: amcheck-server: changer_find: looking for NULL  
> changer is searchable = 1
> 1241020517.271856: amcheck-server: changer: >> -slot current
> 1241020522.034995: amcheck-clients:  
> security_handleinit(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP))
> 1241020522.036002: amcheck-clients:  
> security_streaminit(stream=0x8ff1900, driver=0x2a9620 (BSDTCP))
> 1241020522.037590: amcheck-clients: connect_port: Skip port 700: owned  
> by epp.
> 1241020522.038124: amcheck-clients: connect_port: Skip port 701: owned  
> by lmp.
> 1241020522.038651: amcheck-clients: connect_port: Skip port 702: owned  
> by iris-beep.
> 1241020522.041874: amcheck-clients: make_socket opening socket with  
> family 2
> 1241020522.041895: amcheck-clients: connect_port: Try  port 703:  
> available - Success
> 1241020522.042523: amcheck-clients: connect_portrange: Connect from  
> 0.0.0.0.703 failed: Connection refused
> 1241020522.042535: amcheck-clients: connect_portrange: connect to  
> 193.73.134.4.10080 failed: Connection refused
> 1241020522.042549: amcheck-clients: stream_client: Could not bind to  
> port in range 700-710.
> 1241020522.042563: amcheck-clients:  
> security_seterror(handle=0x8fe73b0, driver=0x2a9620 (BSDTCP)  
> error=Connection refused)
> 1241020522.042602: amcheck-clients: security_close(handle=0x8fe73b0,  
> driver=0x2a9620 (BSDTCP))
> 1241020522.042611: amcheck-clients: security_stream_close(0x8ff1900)
> 
> On the client, /etc/services has the following lines:
> 
> amanda  10080/udp
> amandaidx   10082/tcp
> amidxtape   10083/tcp
> 
> and inetadm -l svc:/network/amanda/udp:default reports the following:
> 
> SCOPENAME=VALUE
>   name="amanda"
>   endpoint_type="dgram"
>   proto="udp"
>   isrpc=FALSE
>   wait=TRUE
>   exec="/libexec/amanda/amandad"
>   user="amandabackup"
> default  bind_addr=""
> default  bind_fail_max=-1
> default  bind_fail_interval=-1
> default  max_con_rate=-1
> default  max_copies=-1
> default  con_rate_offline=-1
> default  failrate_cnt=40
> default  failrate_interval=60
> default  inherit_env=TRUE
> default  tcp_trace=FALSE
> default  tcp_wrappers=FALSE
> 
> 
> However, netstat -a | grep amanda OR netstat -a | grep 1008 returns  
> nothing. I have no idea how to proceed anymore. Can anyone help?
> 
> Abilio
> 
> 
> ---
> This e-mail is strictly confidential and may be privileged.
> It is intended solely for the addressee. If you are not the intended
> recipient, any copying, distribution or any other use of this message
> is prohibited and may be unlawful. In such case, please notify the
> sender Immediately and destroy this e-mail.
> 
> 

-- 
Darin Perusich
Unix Systems Administrator
Cognigen Corporation
395 Youngs Rd.
Williamsville, NY 14221
Phone: 716-633-3463
Email: darin...@cognigencorp.com