Re: lpr: unable to get official name for local machine
> Please can anyone tell me what might have sparked the message: > lpr: unable to get official name for local machine Sorry folks, I have found how I caused this - it was by deleting a line n.n.n.n bay from /etc/hosts. ( I got the lpr source to find that out, I find if I put the same IP numbers as localhost for the local machine (bay) that is enough to satisfy lpr.) The line deletion was done while trying to cope with a ppp problem. So I have had my faith in fsck restored. I hope I can rely on it to alert me by filename if something is spoilt beyond recovery. clare -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
lpr: unable to get official name for local machine
Hi group: Please can anyone tell me what might have sparked the message: lpr: unable to get official name for local machine I have re-installed the lpr from lpr_5.9-13.1.deb, but no cure that way. hostname gets the right answer for the machine name (bay). Root can cat to lp2 and print. /etc/printcap seems normal. Using the official 1.3 CD-rom, I had a functional lpr until my CD-ROM got a series of errors which caused overwriting on the disk and hung the machine. fsck then had to clobber some files but I don't know which. Perhaps I am supposed to record all those inode numbers but if so there has to be a way to make fsck do it - should I be getting them recorded? I don't understand why read errors should have such a major effect, even if my hardware is a bit weird. By that I mean that when mounting the CD-Rom I often have to do it twice, as below: bay# mount -t iso9660 /dev/sjcd mnt mount: block device /dev/sjcd is write-protected, mounting read-only SJCD: timeout in state 4 end_request: I/O error, dev 12:00, sector 64 isofs_read_super: bread failed, dev 12:00 iso_blknum 16 block 32 mount: wrong fs type, bad option, bad superblock on /dev/sjcd, or too many mounted file systems bay# mount -t iso9660 /dev/sjcd mnt mount: block device /dev/sjcd is write-protected, mounting read-only ISO9660 Extensions: RRIP_1991A bay# - I have installed maybe 50 packages off it with no problem; until this series of errors while reading xemacs-support. I had similar problems with an earlier version of debian with this CD-rom reading and was hoping this newer version would be proof against it. clare -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd) fixed.
Name resolving works again on my machines! Still don't know what exactly happened though. It seems that the reason for bind not working out of the 1.3-box for me, is that I answered '' where I should have answered 'none' to bindconfig (at least that is the only difference that I can think of.) Looking at the files, the big difference was a missing '@' in front of the line for localhost. When I placed the '@' back in the configuration file on the machine that had a working named before the 1.3 upgrade, it worked again as well. Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
SOLVED: lpr: unable to get official name for local machine
Brian K Servis writes: > >For those of you following this here is an update. > >It appears to be some sort of name lookup failure. I can't figure it >out. When I try and print with lpr it fails with the error given in >the subject. This turns out is just an indicator of something else. I >have a stand alone machine that I dial in to my isp and run slirp to >emulate ppp. So, I have given my machine a bogus name of >servis.snet. Before I upgraded to 1.3 I could ping, finger, telnet, >etc to servis.snet. Now nothing seems to be able to figure out what >servis.snet is. My conf files are: > Well, it turns out that /etc/host.conf only had permissions 1 -rw--- 1 root root 20 Jun 6 16:52 /etc/host.conf and this was screwing everything up. I changed it to 1 -rw-r--r-- 1 root root 20 Jun 6 16:52 /etc/host.conf and I am back to normal! Yipee! I don't know how it got changed, I don't remeber doing it by hand. It seemed to happed during the upgrade to 1.3 but I checked the base-files package and it doesn't set the permissions wrong. It is a mystery but a lesson as well. Take note. NONE of the docs, HOW-TO's, man pages seem to mention the permisions required of the conf files otherwise I would have found this long ago. Live and learn I guess. Brian -- Mechanical Engineering [EMAIL PROTECTED] Purdue University http://widget.ecn.purdue.edu/~servis -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
On Fri, 6 Jun 1997, J.P.D. Kooij wrote: : :On Thu, 5 Jun 1997, Nathan E Norman wrote: : :> For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a :> server that is authoritative for a few zones ... no problems at all. : :I forgot to mention the following: I let the install script change my :existing setup, did you do this too? I believe I did - it certainly has the "new" style named.boot, etc. : :> I realise this doesn't assist you in solving your immediate problem, but :> I'm not so sure that the Debian package is to blame.. : :Well, I'm not really authoritative on bind matters, but I thought that on :previous ( < 1.3 ) installations, you could issue "nslookup localhost" :and it would work then. Now I get: : : calypso# nslookup localhost : *** Can't find server name for address 127.0.0.1: Non-existent host/domain : *** Default servers are not available : Here's what I get when I execute 'nslookup localhost': Server: endor Address: 0.0.0.0 Name:localhost.cfni.com Address: 127.0.0.1 Notice that I did defy the package default of specifying the local IP address as a nameserver in resolv.conf and instead left it as 0.0.0.0, as the first edition BIND book suggests. I have no idea if this matters :) (I also would not call myself a BIND guru). I also see that I have a localhost entry in my primary SOA zone file ... and I don't have a named.local file, which named.options seems to expect to exist. It looks like I may have gotten lucky :) If you like I can send snippets of my zone files. etc. if that would somehow be helpful. -- Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED] finger [EMAIL PROTECTED] for PGP public key and other stuff Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72 -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
On Thu, 5 Jun 1997, Nathan E Norman wrote: > For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a > server that is authoritative for a few zones ... no problems at all. I forgot to mention the following: I let the install script change my existing setup, did you do this too? > I realise this doesn't assist you in solving your immediate problem, but > I'm not so sure that the Debian package is to blame.. Well, I'm not really authoritative on bind matters, but I thought that on previous ( < 1.3 ) installations, you could issue "nslookup localhost" and it would work then. Now I get: calypso# nslookup localhost *** Can't find server name for address 127.0.0.1: Non-existent host/domain *** Default servers are not available -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
For what it's worth, I upgraded from 1.2 to 1.3 about a week ago on a server that is authoritative for a few zones ... no problems at all. I realise this doesn't assist you in solving your immediate problem, but I'm not so sure that the Debian package is to blame.. -- Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED] finger [EMAIL PROTECTED] for PGP public key and other stuff Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72 -- On Thu, 5 Jun 1997, J.P.D. Kooij wrote: : :To me it looks like nameserving doesn't quite work out-of-the-box in :upcoming debian 1.3. : :I've upgraded a box to frozen and that broke a working bind :configuration, I don't know how badly because I haven't really had the :time to look into it. :On fresh installations, nslookup can't find even localhost. : : : :-- :TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to :[EMAIL PROTECTED] . :Trouble? e-mail to [EMAIL PROTECTED] . : -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
To me it looks like nameserving doesn't quite work out-of-the-box in upcoming debian 1.3. I've upgraded a box to frozen and that broke a working bind configuration, I don't know how badly because I haven't really had the time to look into it. On fresh installations, nslookup can't find even localhost. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine
For those of you following this here is an update. It appears to be some sort of name lookup failure. I can't figure it out. When I try and print with lpr it fails with the error given in the subject. This turns out is just an indicator of something else. I have a stand alone machine that I dial in to my isp and run slirp to emulate ppp. So, I have given my machine a bogus name of servis.snet. Before I upgraded to 1.3 I could ping, finger, telnet, etc to servis.snet. Now nothing seems to be able to figure out what servis.snet is. My conf files are: /etc/hostname servis /etc/hosts 127.0.0.1 localhost loopback servis.snet servis /etc/resolv.conf domain snet search snet ecn.purdue.edu nameserver 128.46.131.20 nameserver 128.46.131.20 nameserver 128.46.131.20 /etc/host.conf order hosts,bind multi on /etc/init.d/network ifconfig lo 127.0.0.1 route add -net 127.0.0.0 I don't know if named should be running or not. If I start it with the default config it tries to reach 198.41.0.4 in /var/named/named.root and fails because I am not connected. If I start named when I have connected with ppp programs still do not resolve what servis.snet is and give hostname failures. When I issue 'hostname' it returns 'servis' but if I call host name with any commandline options it gives 'hostname: Unknown host' error. PLEASE HELP ME FIGURE THIS OUT, EVEN IF IT IS TRIVIAL! Thanks in advance, Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
Brian K Servis <[EMAIL PROTECTED]> writes: [snip] > WAIT A MINUTE..I just discovered something as I was checking the > log files. ifconfig is making kerneld try to load some net-pf-4 and > net-pf-5 module? What is this? I can't find any reference to it in > the kernel-source. > > %root% date ; ifconfig lo 127.0.0.1 > Wed Jun 4 12:49:12 CDT 1997 > > [snippet of /var/log/daemon] > Jun 4 12:49:12 servis modprobe: can't locate module net-pf-4 > Jun 4 12:49:12 servis modprobe: can't locate module net-pf-5 > > This must be the root of the problem! Any pointers. Unfortunately this is unlikely. net-pf-4 and net-pf-5 are things like Appletalk and IPX, which you probably haven't compiled into your kernel. See `/etc/conf.modules'. I can't see what other problems there would be. Maybe someone else has experienced this and solved it? -- Carey Evans <*> [EMAIL PROTECTED] "Lies, damn lies, and computer documentation." -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine (fwd)
Carey Evans writes: >Brian K Servis <[EMAIL PROTECTED]> writes: > >[snip] > >> /etc/hosts: >> 127.0.0.1 localhost loopback >> widget-servis.ecn.purdue.edu >> widget-servis >> #(plus a bunch of other frequenctly used hosts at ecn.purdue.edu) > >[snip] > >> /etc/init.d/network: >> ifconfig lo 127.0.0.1 >> route add -net 127.0.0.0 dev lo > >I have found that having anything other that "localhost" after >127.0.0.1 caused me problems in the past. I use the dummy driver to >create a fake network: > >--- /etc/hosts --- >127.0.0.1 localhost >192.168.117.2 psyche.evansnet psyche www.evansnet news.evansnet > >[ 192.168.*.* are available for provate use; see RFC 1918. ] > >--- /etc/hostname --- >psyche > >--- /etc/init.d/network >#! /bin/sh >ifconfig lo localhost >route add -net 127.0.0.0 > >ifconfig dummy0 psyche >route add -net 192.168.117.0 > >[ dummy if it's in the kernel, dummy0 if it's a module. ] > >There still seem to be things that expect _one_, _permanently_ >connected interface and hostname. :-( > Ok, I think we are getting closer to figuring this out. I tried your suggestions(changed my "machine name" to servis.snet) and rebooted. /etc/hosts 127.0.0.1 localhost 192.168.1.1 servis.snet www.servis.snet ftp.servis.snet servis /etc/resolv.conf domain snet search snet ecn.purdue.edu nameserver 128.46.131.20 nameserver 128.46.131.20 nameserver 128.46.131.20 /etc/hostname servis /etc/init.d/network #ifconfig lo localhost ifconfig lo 127.0.0.1 route add -net 127.0.0.0 # create the dummy network ifconfig dummy 192.168.1.1 route add -net 192.168.1.0 However, when /etc/init.d/boot called /etc/init.d/network ifconfig complained about host name lookup failure of localhost! This is run before rc2.d parts are run. This is really starting to make me mad. I have read almost all the network related howto's, man pages on all the conf files, etc.(each giving slightly different methods of setup by the way) Even if I use the IP address in /etc/init.d/network it still doesn't fix the problem. WAIT A MINUTE..I just discovered something as I was checking the log files. ifconfig is making kerneld try to load some net-pf-4 and net-pf-5 module? What is this? I can't find any reference to it in the kernel-source. %root% date ; ifconfig lo 127.0.0.1 Wed Jun 4 12:49:12 CDT 1997 [snippet of /var/log/daemon] Jun 4 12:49:12 servis modprobe: can't locate module net-pf-4 Jun 4 12:49:12 servis modprobe: can't locate module net-pf-5 This must be the root of the problem! Any pointers. Sorry for the length of this but I am trying to give as much info as possible up front. Thanks, Brian -- Mechanical Engineering [EMAIL PROTECTED] Purdue University http://widget.ecn.purdue.edu/~servis -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine
Brian K Servis <[EMAIL PROTECTED]> writes: [snip] > /etc/hosts: > 127.0.0.1 localhost loopback > widget-servis.ecn.purdue.edu > widget-servis > #(plus a bunch of other frequenctly used hosts at ecn.purdue.edu) [snip] > /etc/init.d/network: > ifconfig lo 127.0.0.1 > route add -net 127.0.0.0 dev lo I have found that having anything other that "localhost" after 127.0.0.1 caused me problems in the past. I use the dummy driver to create a fake network: --- /etc/hosts --- 127.0.0.1 localhost 192.168.117.2 psyche.evansnet psyche www.evansnet news.evansnet [ 192.168.*.* are available for provate use; see RFC 1918. ] --- /etc/hostname --- psyche --- /etc/init.d/network #! /bin/sh ifconfig lo localhost route add -net 127.0.0.0 ifconfig dummy0 psyche route add -net 192.168.117.0 [ dummy if it's in the kernel, dummy0 if it's a module. ] There still seem to be things that expect _one_, _permanently_ connected interface and hostname. :-( -- Carey Evans <*> [EMAIL PROTECTED] "Lies, damn lies, and computer documentation." -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine
On Tue, 3 Jun 1997, Brian K Servis wrote: > Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name for local > machine widget-servis When my ISP drops my ppp connection I get the same thing. If I do a hostname localhost then printing works again. Mark. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine
Jens B. Jorgensen writes: > >Brian K Servis wrote: >> >> Help! >> >> Ever since I upgrade to frozen(May 25) I am having all kinds of problems >> with name resolution. Lpr is one of them, when lpd starts I get the >> following repeated 5 times in messages: >> >> Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name for >> local machine widget-servis >> >> I connect to my isp via dialup and us slirp to emulate ppp so I gave my >> machine a bogus name of widget-servis. >> >> I didn't have any problems before with 1.2. Other problems include ppp, ping, >> emacs, etc. Basically anything that trys to do a name resolve when starting >> or uses a name resolve. I didn't change any of my hostname, resolve.conf, >> hosts.* files during the upgrade. > >This may be true. However, perhaps one of these got changed anyway. >Why don't you include them in your post. This would be very helpful. > >-- >Jens B. Jorgensen >[EMAIL PROTECTED] > > Ok here goes: /etc/resolve.conf: domain ecn.purdue.edu search ecn.purdue.edu nameserver 128.46.131.20 nameserver 128.46.131.20 nameserver 128.46.131.20 /etc/host.conf: order hosts,bind multi on /etc/hostname: widget-servis /etc/hosts: 127.0.0.1 localhost loopback widget-servis.ecn.purdue.edu widget-servis #(plus a bunch of other frequenctly used hosts at ecn.purdue.edu) /etc/hosts.allow ALL: LOCAL /etc/hosts.deny ALL: PARANOID /etc/hosts.equiv #(empty) /etc/hosts.lpd #(empty) /etc/init.d/network: ifconfig lo 127.0.0.1 route add -net 127.0.0.0 dev lo Newly discovered info: I can ping 127.0.0.1 and it works if I ping widget-servis it gives a host unknown error, this used to work in before. Brian -- Mechanical Engineering [EMAIL PROTECTED] Purdue University http://widget.ecn.purdue.edu/~servis -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: lpr: unable to get official name for local machine
Brian K Servis wrote: > > Help! > > Ever since I upgrade to frozen(May 25) I am having all kinds of problems > with name resolution. Lpr is one of them, when lpd starts I get the > following repeated 5 times in messages: > > Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name for local > machine widget-servis > > I connect to my isp via dialup and us slirp to emulate ppp so I gave my > machine a bogus name of widget-servis. > > I didn't have any problems before with 1.2. Other problems include ppp, ping, > emacs, etc. Basically anything that trys to do a name resolve when starting > or uses a name resolve. I didn't change any of my hostname, resolve.conf, > hosts.* files during the upgrade. This may be true. However, perhaps one of these got changed anyway. Why don't you include them in your post. This would be very helpful. -- Jens B. Jorgensen [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
lpr: unable to get official name for local machine
Help! Ever since I upgrade to frozen(May 25) I am having all kinds of problems with name resolution. Lpr is one of them, when lpd starts I get the following repeated 5 times in messages: Jun 3 13:35:39 widget-servis lpd[374]: unable to get official name for local machine widget-servis I connect to my isp via dialup and us slirp to emulate ppp so I gave my machine a bogus name of widget-servis. I didn't have any problems before with 1.2. Other problems include ppp, ping, emacs, etc. Basically anything that trys to do a name resolve when starting or uses a name resolve. I didn't change any of my hostname, resolve.conf, hosts.* files during the upgrade. Any pointers please! I am stuck using minicom and zmodem to download things. It must me something simple but I just can't find it. Thanks, Brian -- Mechanical Engineering [EMAIL PROTECTED] Purdue University http://widget.ecn.purdue.edu/~servis -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
