WTF!?!?!?

[Silent Bob]

I just rebooted my linux machine and when it got to starting lpd it said

"date+time: ThisAddressDoesNotExist: bad"

earlier in the startup sequence it had said that the name was localhost.localdomain (I was too lazy to change it). So I get given the chance to log on to ThisAddressDoesNotExist :mad:


So I deactivated the ethernet interface and said it not to activate on boot and rebooted the system. It said that it failed stopping lpd.

But on starting up again, guess what, it went back to being called localhost.localdomain.

So I set the ethernet interface to activate on boot and all the weirdness started again. :mad: :mad:

Anyone know what's happening?

[ 11 July 2001: Message edited by: Silent Bob ]

[bdg1983]

??? Something not setup correctly in /etc/hosts or HOSTNAME?

[Silent Bob]

/etc/hosts is properly set up for when the comp is named localhost.localdomain. and HOSTNAME just contains localhost.localdomain

Earlier in the boot sequence it says setting hostname to localhost.localdomainthen when it starts lpd it says starting lpd: 2001-07-11-12:01:34.454 Get_local_host: hostname 'ThisAddressDoesNotExist' bad

I can't figure it out. Also the hostname is left as ThisAddressDoesNotExist

Any takers?

[ 11 July 2001: Message edited by: Silent Bob ]

[Silent Bob]

If boot into runlevel 3 and do the following

# HOSTNAME=localhost.localdomain ; export # HOSTNAME
# hostname localhost.localdomain
# /etc/rc5.d/SL60lpd start

then

# exit

then login and startx. Everything looks as though it is back to normal, but if I ping anywhere else, it says that it is pinging from ThisAddressDoesNotExist rather than from localhost.localdomain

Any takers as to what's happening?

[ 11 July 2001: Message edited by: Silent Bob ]

[Silent Bob]

plz?

[Strike]

Okay, a bit more information here would help. Namely - distro, ethernet card type, how lpr was installed, and what your network setup is like.

[Silent Bob]

I can't tell you exactly what the ethernet card is (I am fairly sure it's a 3com) but the Kernel module is 3c90x

If I set the ethernet interface so that it doesn't activate at boot, then when I reactivate it after boot everything is fine. If I set it to activate at boot my comp gets named ThisAddressDoesNotExist.

I am using RedHat 7. All I have done with regard to network setup is to give the machine a static IP and to let it know where our gateway is, but that was well before this hassle started

We have netmasking in place and all our machines have 192.168.0.X addresses with a 255.255.255.0 netmask

here is an extract from my boot.logJul 12 17:22:46 localhost rhnsd: rhnsd shutdown succeeded
Jul 12 17:22:46 localhost rc: Stopping keytable: succeeded
Jul 12 17:22:46 localhost xfs: xfs shutdown succeeded
Jul 12 17:22:46 localhost gpm: gpm shutdown succeeded
Jul 12 17:22:47 localhost sshd: sshd shutdown succeeded
Jul 12 17:22:47 localhost sendmail: sendmail shutdown succeeded
Jul 12 17:22:47 localhost xinetd: xinetd shutdown succeeded
Jul 12 17:22:47 localhost atd: atd shutdown succeeded
Jul 12 17:22:47 localhost crond: crond shutdown succeeded
Jul 12 17:22:48 localhost lpd: lpd shutdown succeeded
Jul 12 17:22:48 localhost identd: identd shutdown succeeded
Jul 12 17:22:48 localhost dd: 1+0 records in
Jul 12 17:22:48 localhost dd: 1+0 records out
Jul 12 17:22:48 localhost random: Saving random seed: succeeded
Jul 12 17:22:48 localhost apmd: apmd shutdown succeeded
Jul 12 17:22:49 localhost nfslock: lockd shutdown succeeded
Jul 12 17:22:49 localhost nfslock: rpc.statd shutdown succeeded
Jul 12 17:22:49 localhost portmap: portmap shutdown succeeded
Jul 12 17:22:50 localhost syslog: klogd shutdown succeeded
Jul 12 17:24:18 ThisAddressDoesNotExist syslog: syslogd startup succeeded
Jul 12 17:24:18 ThisAddressDoesNotExist syslog: klogd startup succeeded
Jul 12 17:24:19 ThisAddressDoesNotExist portmap: portmap startup succeeded
Jul 12 17:24:19 ThisAddressDoesNotExist nfslock: rpc.lockd startup succeeded
Jul 12 17:24:20 ThisAddressDoesNotExist nfslock: rpc.statd startup succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Mounting proc filesystem: succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist sysctl: net.ipv4.ip_forward = 0
Jul 12 17:24:05 ThisAddressDoesNotExist sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 12 17:24:05 ThisAddressDoesNotExist sysctl: net.ipv4.ip_always_defrag = 0
Jul 12 17:24:05 ThisAddressDoesNotExist sysctl: kernel.sysrq = 0
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Configuring kernel parameters: succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist date: Thu Jul 12 17:23:58 IST 2001
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Setting clock (localtime): Thu Jul 12 17:23:58 IST 2001 succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Loading default keymap succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Activating swap partitions: succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Setting hostname localhost.localdomain: succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Initializing USB controller (usb-uhci): succeeded
Jul 12 17:24:05 ThisAddressDoesNotExist rc.sysinit: Mounting USB filesystem: succeeded

This covers shutting down the comp while it still was called localhost.localdomain and then the first part of the boot sequence.

[yogee]

Im a little confused by you guys. Lpd is printer suport. When i installed redhat 7.1 i got the same thing at boot time. It also said that there where no printers defined on the netowrk or system. I went into the system and found the lpd script and it told me it was for

_____________________
#!/bin/sh
#
# lpd This shell script takes care of starting and stopping \
# lpd (printer daemon).

_______________________________

I just removed it from the startup. If i had a printer on the system then i would understand i needed to configure it some way. Im thinking that you have no printer or you havent defined it some how in the system. Im also thinking that you guys think it has some thing to do with the network cards. This is couse im confused and not that i think your missing some thing, but just maybe? Do you have a printer on this system?

[hux]

this is a guess, but has the NIC gone south?

I thought lpd was printer support too.

[bdg1983]

I thought of that too as for the reason for suggesting modifying HOSTNAME and localhost as lpd may read from these files. I'm not sure if it does though, but who knows as it may fix the problem.

[Silent Bob]

The lpd thing isn't the problem but it is symptomatic of the problem. It was the thing that first alerted me to these weird goings on. We do have a network printer though.

The thing is that this hasn't always happened. I just rebooted the comp a few days ago and things went pear-shaped.

Oddly enough HOSTNAME is always contains localhost.localdomain

I don't think that the NIC has gone south because I can still access the internet through our network without any difficulty but I think that the ethernet connection is certainly related to the problem.

I have a workaround which is: disabling the ethernet interface, not letting it activate at boot, and activating it manually after boot.

What I am going to try is putting the activation of the ethernet at the end of the boot sequence, just to see if that would make a difference. All I need to know is how to change the order of the boot sequence.

[ 13 July 2001: Message edited by: Silent Bob ]

[bdg1983]

Why not assign a proper HOSTNAME instead of the default. I always do.

[Silent Bob]

I guess so. I'm just busy being unimaginative :)

But seriously I'd also like to solve this problem out of the spirit of enquiry

[hux]

well, fer what it's worth, I had a windows machine do something similar here, in that it kept giving an unknown address error when attempting a network logon....bout drove me crazy trying to figure out what the problem was...turned out the nic was bad, and reporting a bogus mac addy, which turned out to be the same one as another machine in the department..same problem, user could surf internet, couldn't hit any network resources..no idea how it was gatting an ip addy with a bogus mac, but it was. I'd give it a shot if I had a spare one laying around...sounds like it's unable to communicate with that network printer, causing lpd to fail...

[Silent Bob]

hux

that sounds like a good suggestion. As soon as I have the time I'll take the card out of this (windows) box swap them and see what happens.

Watch this space (or don't, if you couldn't care less :))

[yogee]

Watching - waiting - twiddeling thumbs -

[hux]

I hope he didn't suffer a severe jolt from the power supply or something :)

[Silent Bob]

Yeah that'll learn me to hot-swap NIC's :)

Our sysadmin told me that we don't have any spare NIC's lying around, and my windoze machine needed its one for a lengthy download (Redhat 6.2)

In the words of an eternal procrastinator 'I'll do it on Monday' :)

[yogee]

Aw man! Now the weekend waiting is gonna kill me!

[Silent Bob]

Ok for all you people who have been following this saga :)

Swapping the NICs made no difference. I am all out of ideas, but I do have my workaround. Also I won't be rebooting for quite some time now since my Linux PC is now acting as a Bugzilla server and I can't just shutdown/reboot/break stuff on a whim anymore :(

Anyways thanks for all the help and suggestions

[Silent Bob]

Hmmmm....

I ran the sonar screensaver (I have it set up to ping our network and report the other computers as blips) Anyway every computer on our LAN was reported as ThisAddressDoesNotExist while the hosts outside the LAN (i.e. www.linux.org) (http://www.linux.org)) showed up properly.

I ran a network sniffer from a windows box and it picks up all the IPs and computer names etc. properly (edit: except the Linux box and a win9x machine which both show up as ThisAddressDoesNotExist, although it does give the proper IPs).

Any idea what's up (this could be a network problem rather than a Linux problem)

Thanks


Every address I add to /etc/hosts now shows up properly when I ping it etc. However before all this started ping a computer gave me it's IP anyway even if it wasn't in /etc/hosts.


[ 17 July 2001: Message edited by: Silent Bob ]

[Silent Bob]

:o :o :o Do I feel embarrassed :o :o :o

I apologise to all those people who have given me helpful suggestions in this thread for wasting their time.

Sorry!

I looked at the network configuration utility (in RH) and deleted an entry I (as in I was the one who fscked things up :o) had made in the Routing section.

Voíla

On reboot it all works again (edit: apart from it saying that any other comps I ping on the network are ThisAddressDoesNotExist)

[ 17 July 2001: Message edited by: Silent Bob ]

[bdg1983]

No need to feel like that. After all, we all benefit and can learn from others experiences.

But it does prove a point where some (not you) get impatient when their questions cannot be answered. Sometimes we just don't know what the solution is and sometimes it's just some little thing that was overlooked and we could not possibly see this unless we were sitting right in front of that persons pc.

Glad to hear you got it fixed. Happy Linuxing.

[hux]

well, I'm just glad to hear you didn't get electrocuted :)

don't feel bad, we all make O**** errors...pronounced like ocean, try it...