Re: Printer & localhost:631 -- Don't Give Up Yet

From: Jeff Stevens (jeff_at_mossycup.com)
Date: 08/19/05

  • Next message: Henrique de Moraes Holschuh: "Re: Gigabit ethernet as second network interface troubles" 
    To: Charlie <aries-tao@bigpond.com>
Date: Thu, 18 Aug 2005 19:59:05 -0700

    Charlie,

    That looks like our winner. As you can see, you have three interfaces.
    The "lo" interface is your loopback interface. This should be
    configured with the IP address 127.0.0.1. Apparently it isn't.

    The quick fix is to run "ifconfig lo 127.0.0.1" as root and you'll be
    able to ping localhost. I'm not sure you'll be able to configure CUPS,
    as I think this is a name resolution issue as indicated in the CUPS
    logs.

    There is a reason for this however and I hope someone else will chime in
    here with some comments. In your email off list your /etc/hosts file
    has the following line at the top:

    127.0.0.1 localhost

    Let's change this to:

    127.0.0.1 localhost localhost.localdomain ariestao

    I haven't seen your /etc/network/interfaces file, but make sure you have
    a stanza in there somewhere along the lines of:

    # The loopback network interface
    auto lo
    iface lo inet loopback

    I *think* when your lo interface is restarted it should be assigned the
    address 127.0.0.1. Just for further verification, can you make sure
    your /etc/nsswitch.conf has a line like this:

    hosts: files dns

    We want to make sure that when CUPS starts and looks up the host
    "ariestao" it is configured to look in "files" (/etc/hosts) where it
    resolve correctly.

    Anyway, once you have verified nsswitch.conf is correct, restart CUPS
    and that name resolution error should be gone.

    Post again with your results.

    -Jeff

    > |- What does "ifconfig -a" show? Can you clarify what error your
    > browser
    > |- was giving when you tried to connect to http://127.0.0.1:631/?
    >
    > ariestao:~# ifconfig -a
    > eth0 Link encap:Ethernet HWaddr 00:C0:9F:38:31:75
    > BROADCAST MULTICAST MTU:1500 Metric:1
    > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > 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:4 Base address:0x1800
    >
    > lo Link encap:Local Loopback
    > LOOPBACK MTU:16436 Metric:1
    > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:0
    > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    >
    > ppp0 Link encap:Point-to-Point Protocol
    > inet addr:144.139.163.21 P-t-P:139.134.24.241
    > Mask:255.255.255.255
    > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:576 Metric:1
    > RX packets:1564 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:1162 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:3
    > RX bytes:596135 (582.1 KiB) TX bytes:59323 (57.9KiB) 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Henrique de Moraes Holschuh: "Re: Gigabit ethernet as second network interface troubles"

    Relevant Pages

    • Configuring management interface on Catalyst 4507
      ... The routed interface solution seems easy enough, ... then I would need to patch that routed interface into a switch port, ... Option 1 Configure a loopback interface for managing the switch. ...
      (comp.dcom.sys.cisco)
    • Re: Aliasing the loopback.
      ... >> permitted to see or be seen by any other network. ... Its my interface, if I want my other to connect to it, it can. ... Internal host loopback address. ... >computers, ...
      (comp.os.linux.networking)
    • Weird loopback interface problem
      ... When I telnet to port 25 on the loopback interface, ... lsof -i TCP shows the following info: ... when that route goes away again.. ...
      (SunManagers)
    • Re: lo0 for management
      ... have SNMP, AAA, syslog, etc configured) to use it, the router will use the ... IP address of the output interface as the source address of the packet. ... Configure the loopback to use a /32 mask. ... config for loopback0? ...
      (comp.dcom.sys.cisco)
    • Re: Terminal Server Setup
      ... ~ description GRE Tunnel Source Interface ... ~ Encapsulation ARPA, loopback not set ... ~ 0 output buffer failures, ...
      (comp.dcom.sys.cisco)