On Fri, May 25, 2012 at 01:06:45PM -0400, Brian Cuttler wrote:
> 
> Charles,
> Jean-Louis,
> 
> I did include the amgetconf reserved-tcp-port info in my email,
> I get the same results you do.
> 
> I am logged in as root when running amcheck.
> 
> I was afraid that was an IPv6 error, was running it out of the
> box and didn't expect it to be turned on.
> 
> How do I turn off IPv6?

Out of the box xinetd's config is

~
# default: off
# description: Amanda backup client
#
service amanda
{
        socket_type     = dgram
        protocol        = udp
        wait            = no
        user            = amanda
        group           = amanda
        server          = /usr/lib/amanda/amandad
        disable         = no
        server_args     = -auth=bsdudp amdump
}

There was some improvement after I removed the IPv6 address from
/etc/hosts, rebooted the system but still see an IPv6 address on
eth0 and the loop back address. (not sure if I had one on eth1 before).

kaveri:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:30:48:CE:7F:92  
          inet addr:172.16.1.34  Bcast:172.16.255.255  Mask:255.255.0.0
          inet6 addr: fe80::230:48ff:fece:7f92/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18970 errors:2 dropped:281 overruns:0 frame:2
          TX packets:2811 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2222237 (2.1 Mb)  TX bytes:290771 (283.9 Kb)
          Interrupt:40 Base address:0x8000 

eth1      Link encap:Ethernet  HWaddr 00:30:48:CE:7F:93  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:1 dropped:0 overruns:0 frame:1
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Base address:0xc000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:132 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:9929 (9.6 Kb)  TX bytes:9929 (9.6 Kb)

I seem to no longer see an IPv6 address in the amcheck.*.log


Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 577: owned 
by vnas.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 578: owned 
by ipdd.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 579: owned 
by decbsrv.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 580: owned 
by sntp-heartbeat.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 581: owned 
by bdp.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 582: owned 
by scc-security.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 583: owned 
by philips-vc.
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Skip port 584: owned 
by keyserver.
Fri May 25 13:57:44 2012: amcheck-clients: make_socket opening socket with 
family 2
Fri May 25 13:57:44 2012: amcheck-clients: connect_port: Try  port 585: 
available - Success
Fri May 25 13:57:44 2012: amcheck-clients: connect_portrange: Connect from 
0.0.0.0:585 failed: Connection refused
Fri May 25 13:57:44 2012: amcheck-clients: connect_portrange: connect to 
172.16.1.34:10080 failed: Connection refused
Fri May 25 13:57:44 2012: amcheck-clients: stream_client: Could not bind to 
port in range 512-1023.
Fri May 25 13:57:44 2012: amcheck-clients: 
security_seterror(handle=0x7f30710cd4e0, driver=0x7f30709f7860 (BSDTCP) 
error=Connection refused)
Fri May 25 13:57:44 2012: amcheck-clients: 
security_close(handle=0x7f30710cd4e0, driver=0x7f30709f7860 (BSDTCP))
Fri May 25 13:57:44 2012: amcheck-clients: security_stream_close(0x7f30710b69d0)
Fri May 25 13:57:44 2012: amcheck: pid 4212 finish time Fri May 25 13:57:44 2012

                                                thank you,

                                                Brian


IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.


Reply via email to