This SuSE 8.2 system has run 24/7 more than 2 years. hostname used to work, and the prompts would use it. Not any more, and I have no idea why, or when it broke, but it probably only broke within the past 3-8 weeks. #hostname (none) #uname -n (none) #uname -a Linux (none) 2.4.20-4GB #1 Fri Jan 14 15:08:13 UTC 2005 i586 unknown unknown GNU/Linux #cat /etc/HOSTNAME ax5t3.ij.net #nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53 ** server can't find ax5t3.ij.net: NXDOMAIN nslookup doesn't work on any of my puters. :-( SuSEconfig also returns "unknown host". Timestamp on 13 byte /etc/HOSTNAME is Nov 2003. Various 1st lines in /etc/resolv.conf have no apparent impact. Anyone have any idea how to fix this? -- "Love your neighbor as yourself." Matthew 22:39 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Fri, 29 Apr 2005, by mrmazda@ij.net:
This SuSE 8.2 system has run 24/7 more than 2 years. hostname used to work, and the prompts would use it. Not any more, and I have no idea why, or when it broke, but it probably only broke within the past 3-8 weeks.
Which is why reboots aren't all that bad afterall, at least it gives a clue what break when and why.
#hostname (none)
#uname -n (none)
#uname -a Linux (none) 2.4.20-4GB #1 Fri Jan 14 15:08:13 UTC 2005 i586 unknown unknown GNU/Linux
#cat /etc/HOSTNAME ax5t3.ij.net
How is your /etc/hosts file?
#nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53
** server can't find ax5t3.ij.net: NXDOMAIN
Yout DNS server config seems to be broken.
nslookup doesn't work on any of my puters. :-(
SuSEconfig also returns "unknown host". Timestamp on 13 byte /etc/HOSTNAME is Nov 2003. Various 1st lines in /etc/resolv.conf have no apparent impact.
Anyone have any idea how to fix this?
Systematically check all files involved, and next time use backups/logbooks when you make changes on a running system, without checking if it survives a reboot. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
Theo v. Werkhoven wrote: Thanks for the reply.
Fri, 29 Apr 2005, by mrmazda@ij.net:
This SuSE 8.2 system has run 24/7 more than 2 years. hostname used to work, and the prompts would use it. Not any more, and I have no idea why, or when it broke, but it probably only broke within the past 3-8 weeks.
Which is why reboots aren't all that bad afterall, at least it gives a clue what break when and why.
Where do I look for clues in this case? Whatever may have been in the logs surely would have expired out by now? /var/log/warn does have various errors. April 4 was the last entry beginning with ax5t3 (nmbd). The rest start with (none) ("kernel: usb-uhci.c" is 1st entry, followed 13 seconds later by rpc.statd[1070] with a gethostbyname error). /var/log/YaST2/* have no entries on April 4. /var/log/messages has no entries near the time of the warn messages, but indicates I was doing some samba reconfiguration attempts about (a few hours after) that time.
#hostname (none)
#uname -n (none)
#uname -a Linux (none) 2.4.20-4GB #1 Fri Jan 14 15:08:13 UTC 2005 i586 unknown unknown GNU/Linux
#cat /etc/HOSTNAME ax5t3.ij.net
How is your /etc/hosts file?
It works on all the rest of my puters. It starts out with 127.0.0.1 localhost loghost and includes 192.168.100.52 ax5t3.ij.net ax5t3
#nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53
** server can't find ax5t3.ij.net: NXDOMAIN
Yout DNS server config seems to be broken.
"I" don't have a DNS server. 207.22.166.61 belongs to my ISP, which can't see past NAT. I use hosts to handle all local puters.
nslookup doesn't work on any of my puters. :-(
SuSEconfig also returns "unknown host". Timestamp on 13 byte /etc/HOSTNAME is Nov 2003. Various 1st lines in /etc/resolv.conf have no apparent impact.
Anyone have any idea how to fix this?
Systematically check all files involved, and next time use
"all files involved" means what? IOW, what files I've not mentioned are involved? I have other Linux and other puters, and haven't found any differences in files I've looked at that could account for this.
backups/logbooks when you make changes on a running system, without checking if it survives a reboot.
Backups are nice. I do it with the files I change. The problem is figuring out which/where are the files YaST and YOU change, and which have gotten broken by something unknown. -- "Love your neighbor as yourself." Matthew 22:39 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Theo v. Werkhoven wrote:
#hostname (none)
#uname -n (none)
#uname -a Linux (none) 2.4.20-4GB #1 Fri Jan 14 15:08:13 UTC 2005 i586 unknown unknown GNU/Linux
#cat /etc/HOSTNAME ax5t3.ij.net
How is your /etc/hosts file?
It works on all the rest of my puters. It starts out with
127.0.0.1 localhost loghost
and includes
192.168.100.52 ax5t3.ij.net ax5t3
#nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53 Try going into YaST and check the network settings for the network card. If the settings don't look right change them and see it that helps. Or change them to something else and right back to what they should be,
On Sat, 2005-04-30 at 07:30 -0400, Felix Miata wrote: this will force an update to the settings. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
Try going into YaST and check the network settings for the network card. If the settings don't look right change them and see it that helps. Or change them to something else and right back to what they should be, this will force an update to the settings.
I looked, and never found anything suspicious, so I left it all alone in order not to disturb any timestamps on config files. Then I went into YaST Runlevel Editor. In there I found: boot.localhost No - - - - - - - - setup hostname and yp and do cleanup I turned it on, and checked the B box. Then I went to tty1, logged out and back in, and got my hostname prompt instead of (none) prompt. :-) hostname, uname -n & uname -a worked too. :-) Then I booted a 9.0 box to see how it was set, but that turned up no such runlevel setting. Looking in /etc/init.d/boot.d I see 11 files freshly written, including S09boot.localnet, which links to /etc/init.d/boot.localnet, last written Oct. 2004. I'm still too amateur about how all this works, but it looks to me like maybe S09boot.localnet was missing since April 4. Anyone else have a better idea, including why it ever got that way? And, why is there no boot.localnet in the 9.0 YaST Runlevel Editor (it's S10boot.localnet in /etc/init.d/boot.d)? -- "Love your neighbor as yourself." Matthew 22:39 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Sat, 30 Apr 2005, by mrmazda@ij.net:
Theo v. Werkhoven wrote:
Thanks for the reply.
Fri, 29 Apr 2005, by mrmazda@ij.net:
This SuSE 8.2 system has run 24/7 more than 2 years. hostname used to work, and the prompts would use it. Not any more, and I have no idea why, or when it broke, but it probably only broke within the past 3-8 weeks.
Which is why reboots aren't all that bad afterall, at least it gives a clue what break when and why.
Where do I look for clues in this case? Whatever may have been in the logs surely would have expired out by now? /var/log/warn does have various
Not if you use logrotated and the gzipped files are still there.
errors. April 4 was the last entry beginning with ax5t3 (nmbd). The rest start with (none) ("kernel: usb-uhci.c" is 1st entry, followed 13 seconds later by rpc.statd[1070] with a gethostbyname error). /var/log/YaST2/* have no entries on April 4. /var/log/messages has no entries near the time of the warn messages, but indicates I was doing some samba reconfiguration attempts about (a few hours after) that time.
Any chance your box is rooted? The use of rpc (for NFS I guess) on world reachable servers is not smart to say the least.
How is your /etc/hosts file?
It works on all the rest of my puters. It starts out with
127.0.0.1 localhost loghost
and includes
192.168.100.52 ax5t3.ij.net ax5t3
Good. Are /etc/nsswitch.conf and /etc/host.conf still there and valid?
#nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53
** server can't find ax5t3.ij.net: NXDOMAIN
Yout DNS server config seems to be broken.
"I" don't have a DNS server. 207.22.166.61 belongs to my ISP, which can't see past NAT. I use hosts to handle all local puters.
Then why are you trying to use nslookup? Does ax5t3 have a DNS entry with your ISP, and is it reachable from outside or not?
nslookup doesn't work on any of my puters. :-(
Nslookup needs DNS servers to be able to caugh up answers. If your ISPs DNS doesn't know the answer then NXDOMAIN is what you get.
SuSEconfig also returns "unknown host". Timestamp on 13 byte /etc/HOSTNAME is Nov 2003. Various 1st lines in /etc/resolv.conf have no apparent impact.
Anyone have any idea how to fix this?
Systematically check all files involved, and next time use
"all files involved" means what? IOW, what files I've not mentioned are involved? I have other Linux and other puters, and haven't found any differences in files I've looked at that could account for this.
I can't remember very well how 8.2 used to arrange and execute network setup scripts, so you just have to grep -r for e.g. 'HOSTNAME' in /etc and see where it calls /bin/hostname. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
Theo v. Werkhoven wrote:
Sat, 30 Apr 2005, by mrmazda@ij.net:
Theo v. Werkhoven wrote:
Thanks for the reply.
Fri, 29 Apr 2005, by mrmazda@ij.net:
This SuSE 8.2 system has run 24/7 more than 2 years. hostname used to work, and the prompts would use it. Not any more, and I have no idea why, or when it broke, but it probably only broke within the past 3-8 weeks.
Which is why reboots aren't all that bad afterall, at least it gives a clue what break when and why.
Where do I look for clues in this case? Whatever may have been in the logs surely would have expired out by now? /var/log/warn does have various
Not if you use logrotated and the gzipped files are still there.
errors. April 4 was the last entry beginning with ax5t3 (nmbd). The rest start with (none) ("kernel: usb-uhci.c" is 1st entry, followed 13 seconds later by rpc.statd[1070] with a gethostbyname error). /var/log/YaST2/* have no entries on April 4. /var/log/messages has no entries near the time of the warn messages, but indicates I was doing some samba reconfiguration attempts about (a few hours after) that time.
Any chance your box is rooted? The use of rpc (for NFS I guess) on
No idea.
world reachable servers is not smart to say the least.
I don't know what rpc is either.
How is your /etc/hosts file?
It works on all the rest of my puters. It starts out with
127.0.0.1 localhost loghost
and includes
192.168.100.52 ax5t3.ij.net ax5t3
Good. Are /etc/nsswitch.conf and /etc/host.conf still there and valid?
Each was last written more than a year before the problem started.
#nslookup ax5t3 Server: 207.22.166.61 Address: 207.22.166.61#53
** server can't find ax5t3.ij.net: NXDOMAIN
Yout DNS server config seems to be broken.
"I" don't have a DNS server. 207.22.166.61 belongs to my ISP, which can't see past NAT. I use hosts to handle all local puters.
Then why are you trying to use nslookup? Does ax5t3 have a DNS entry with your ISP, and is it reachable from outside or not?
Only reason I tried was an unexplained IRC suggestion.
nslookup doesn't work on any of my puters. :-(
Nslookup needs DNS servers to be able to caugh up answers. If your ISPs DNS doesn't know the answer then NXDOMAIN is what you get.
Do I need it at all when all my local puters are in the hosts files?
SuSEconfig also returns "unknown host". Timestamp on 13 byte /etc/HOSTNAME is Nov 2003. Various 1st lines in /etc/resolv.conf have no apparent impact.
Anyone have any idea how to fix this?
Systematically check all files involved, and next time use
"all files involved" means what? IOW, what files I've not mentioned are involved? I have other Linux and other puters, and haven't found any differences in files I've looked at that could account for this.
I can't remember very well how 8.2 used to arrange and execute network setup scripts, so you just have to grep -r for e.g. 'HOSTNAME' in /etc and see where it calls /bin/hostname.
I'm not exactly sure what you mean by "calls". Hostname shows up in a lot of files in the /etc tree: csh.cshrc profile permissions.easy permissions.paranoid permissions.secure ethers hosts.equiv hosts.lpd services Muttrc hosts **** hosts.allow **** postfix/access postfix/main.cf postfix/main.cf.default postfix/pcre_table postfix/regexp_table postfix/transport samba/smb-winbind.conf X11/susewm/AddEntrys/KDE_CONTROL/Net_advanced/dns.desktop X11/susewm/AddEntrys/KDE_CONTROL/Net_advanced/host.desktop X11/xinit/xserverrc X11/xdm/Xaccess X11/xdm/Xstartup X11/fs/config sysconfig/postfix sysconfig/susehelp sysconfig/network/dhcp sysconfig/network/scripts/ifstatus-wireless sysconfig/network/scripts/ifup-wireless sysconfig/network/scripts/oldnet2new.sh profile.d/complete.tcsh profile.d/complete.bash ppp/chap-secrets ppp/options ppp/pap-secrets /opt/kde3/share/applnk/Settings/YaST/Net_advanced/yast2-network-Host_Names.desktop /opt/kde3/share/applnk/Settings/YaST/Net_advanced/yast2-network-DNS_and_Host_Name.desktop /opt/kde3/share/applnk/SuSE/Settings/YaST/modules/Net_advanced/yast2-network-Host_Names.desktop /opt/kde3/share/applnk/SuSE/Settings/YaST/modules/Net_advanced/yast2-network-DNS_and_Host_Name.desktop init.d/boot.localnet init.d/rc init.d/skeleton cups/client.conf cups/cupsd.conf cups/cupsd.conf.y2 skel/.gnu-emacs skel/.xserverrc.secure Of the above, only hosts & hosts.allow have been written at or after the time hostname broke. I tried reusing some older than break-time (backup) versions of hosts, hosts.allow & resolv.conf, and restarting, but that didn't help. Does SuSE 8.2 put network-related config stuff somewhere besides the /etc tree? -- "Love your neighbor as yourself." Matthew 22:39 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
participants (3)
-
Felix Miata -
Ken Schneider -
Theo v. Werkhoven