Home > Sudo Unable > Sudo Unable To Lookup Via Gethostbyname

Sudo Unable To Lookup Via Gethostbyname

Only, as you can see, this utterly breaks Ubuntu…all I need to do to fix the sudo problem is edit /etc/hosts so is ‘ubuntu510′ (the name of the VM) rather Can you please post a recipe here? Password Linux - Software This forum is for Software issues. vBulletin 2000 - 2016, Jelsoft Enterprises Ltd.

When I set my hostname to "" then I always get the sudo warning, regardless of any /etc/hosts or /etc/sudoers modifications. It looks like 1.6.9p10-1ubuntu3.2 reintroduced this problem, at least on 32-bit. Precisely, I say that this non- bug can be closed/resolved/cancelled! Pablo Estigarribia (pablodav) wrote on 2008-08-08: #88 I fixed this also when I put in hosts file: localhost hostname hostname Scotty (miller-scott-j) wrote on 2008-08-23: #89 Figure I'll try

Personally, I keep the root account enabled, because I don't trust sudo. the please mention it don't ask for hosts file, i believe that is not the problem. As part of this transaction, the DHCP server typically also provides DNS server addresses so that your computer knows where to ask for translations from host name to ip addresses. During the installation and trial of drivers for that card, it has happened several times that sudo just stopped working, in the same manner as described here.

This gives you a root shell without requiring a password. 2) cp /etc/hosts /etc/hosts.backup 3) enter 'vim /etc/hosts' (or nano/pico, whatever console editor you like), and edit the line: localhost My strong belief, as an expert computer user, is that if no host was specified in the command line or sudoers file, there should be no resolving whatsoever. you already discussed the issues. you are aware that the X Window System is a client-server setup over the loopback interface aren't you?!?

Install it in debian/rules. (Ubuntu specific) - sudo.c: If the user successfully authenticated and he is in the 'admin' group, then create a stamp ~/.sudo_as_admin_successful. Believe me; I've tried all possible permutations suggested in this thread, plus a few of my own. Only, as you can see, this utterly breaks Ubuntu…all I need to do to fix the sudo problem is edit /etc/hosts so is ‘ubuntu510' (the name of the VM) rather His system is broken simply because he broke it. 2.

Freedom means "free to do anything, even if it is destructive." 3. Ubuntu Logo, Ubuntu and Canonical Canonical Ltd. This bug is about sudo *failing* if it can't resolve the hostname, which is not what you have happening. This can include the stacking of more specific *deny* rules together with rules that allow other access on all hosts; so even if sudo were fixed to be more lenient, the

If you'd like to contribute content, let us know. And it's not necessary for any kind of local work. Logging in as root via a virtual console is, by default, not possible. Quick and very easy fix.

Whenever I use sudo I get the error: "sudo: unable to resolve host" Martin Pitt (pitti) on 2008-04-28 Changed in sudo: milestone: none → ubuntu-8.04.1 Bug Watch Updater (bug-watch-updater) on Next by Date: Re: LVM and disk failure Previous by thread: Re: [root user] How to disable root account? Find More Posts by fakie_flip 09-03-2006, 04:52 AM #5 tredegar LQ 5k Club Registered: May 2003 Location: London, UK Distribution: Debian "Jessie" Posts: 6,085 Rep: Well, your Xserver is Changed in sudo: status: In Progress → Fix Committed B.

Now, when I reset the hostname with # hostname `cat /etc/hostname` everything works again on both dapper and hardy. I sanyone actually able to reproduce this? The time now is 12:33 PM. Source The only case where one could argue the necessity is if one uses an IP address as a Host_Alias.

problem should now be fixed. Why do you think so? Having a problem installing a new program?

Bug Watch Updater (bug-watch-updater) on 2008-06-11 Changed in sudo: status: Confirmed → Fix Released osxdude (osxdude999) wrote on 2008-06-15: #87 This has happened to me ever since I upgraded from 7.10

Surely sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on? [*] Originally from, If you consider that this is relevant and worth discussing, we can add Adam fakie_flip View Public Profile View LQ Blog View Review Entries View HCL Entries Visit fakie_flip's homepage! [email protected]:~/Desktop$ xclock Xlib: connection to ":0.0" refused by server Xlib: No protocol specified Error: Can't open display: :0.0 [email protected]:~/Desktop$ fakie_flip View Public Profile View LQ Blog View Review Entries View Forwarded upstream to (LP: #32906) * env.c: Do not clobber $HOME when not specifying -H or -s.

User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. Another fix I fixed mine by modifying the alias in the /etc/hosts file. Privacy and legal details Powered by WordPress and Prototype. have a peek here Gracias de ante mano.

Comment on this change (optional) Email me about changes to this bug report sudo (Ubuntu) Edit Fix Released High Martin Pitt Edit Ubuntu intrepid-alpha-1 You need to log in to However, instead of seeing only the problem > in the network settings, I want to point the design mistake in sudo. > What would've happened if my hostname was actually other The only thing I had to do to fix this problem was left click on my network connection icon on the top left hand corner of the screen and go to Authenticate this comment using OpenID.

Do you also get it twice in auth.log? Tango Icons Tango Desktop Project. I booted into Recovery mode, modified /etc/hosts to reflect the correct alias, i.e. {ipaddress} {Fully qualified name} {alias} myhost Now Synaptic works fine for me. Hope this helps, Joe Last edited by poofyhairguy; June 5th, 2005 at 12:00 AM.

I'd be very careful and get this resolved correctly. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. It only counts as this bug if you get a message about looking up hostnames, AND THE OPERATION FAILS, stranding you without any way to gain superuser privileges on the system On Fri, May 23, 2008 at 2:41 PM, agent 8131

switching from host only to NAT and reverse) I cannot reproduce it with ifconfig ethX. Once your hostname is fixed, you should install these updates - to prevent this problem from recurring in the future for you, and to address many other bugs that have been