Home > Ubuntu Unable > Ubuntu Unable To Lookup Via Gethostbyname

Ubuntu Unable To Lookup Via Gethostbyname

Paul Smith (psmith-gnu) wrote on 2008-05-29: #84 This bug is specifically about sudo (or gksudo etc.) failing completely. Just because it's a general solution doesn't mean it's a good solution. You are currently viewing LQ as a guest. pingusa:~# echo "127.0.0.1 localhost.localdomain localhost pingusa" > /etc/hosts Y vemos lo ke contiene ahora: pingusa:~# cat /etc/hosts Reiniciamos la mákina: pingusa:~# shutdown -r now Christian Inicie sesión o regístrese para comentar Source

Døving Solved: 2006-11-25 Last query: 2006-11-25 Last reply: 2006-11-24 Related bugs Link existing bug Related FAQ: None Link to a FAQ JBLinux (jlordan) said on 2006-11-24: #1 The question title is The network-dependent sudo failed, but the X11-dependent gksudo was OK. Para editar el Hosts, ingreso vi /etc/hosts abre el archivo e agrego: 127.0.0.1 localhost.localdomain localhost nombre El problema es que no se como guardar el cambio en el archivo, intente de I booted into Recovery mode, modified /etc/hosts to reflect the correct alias, i.e. {ipaddress} {Fully qualified name} {alias} 113.23.42.21 myhost.ubuntu.com myhost Now Synaptic works fine for me. check here

How do I get to it to change it? I didn't get to do much testing on it > but I did notice that it had returned. Isn't this a bug as well? It looks quite simple to do that, and assume that you'll have there 127:0.0.1 (in both IPv4 and v6)?!?!?!

Gracias de ante mano. Affecting: sudo (Ubuntu Hardy) Filed here by: Martin Pitt When: 2008-01-14 Confirmed: 2008-03-17 Assigned: 2006-10-06 Started work: 2008-03-17 Completed: 2008-05-06 Package (Find…) Status Importance Milestone Fix Released High Ubuntu ubuntu-8.04.1 Assigned It looks like 1.6.9p10-1ubuntu3.2 reintroduced this problem, at least on 32-bit. Døving (frode) said on 2006-11-24: #3 If you can't run any of the System/Administration programs, you can reboot to Recovery Mode, First find the current hostname: # cat /etc/hostname Then run

B. i want a option to restrict it to local operation only. Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest click here now When the Network wizard added my host to /etc/host, it forced itself to add the fully qualified domain name (myhost.ubuntu.com), while sudo is looking for the short name (myhost).

In fact I'm not convinced that sudo should ever be doing a hostname lookup. Steps to confirm the lack of a bug: I, too, use 2 terminals, 1 in a `sudo -s` session as a failsafe and a second to test for breakage of `sudo` There is no sane use-case for sudo to resolve the localhost unless enforced by policy, but even then the policy is wrong. Thanks in advance to all!

I go to my terminal, do [email protected]:$ su root , enter my password for the first ("admin") user created in the Ubuntu setup, and I immediately get a command line [email protected]:$ Dorin Lazăr (dorin-lazar) wrote on 2008-03-18: #26 Just because applications like gnome-terminal or mc are broken doesn't mean that on your local box there should definitely be no resolving done. I don't know about IPv6. If this is kept there is an gutsy-hardy update problem.

sudo should not depend on network configurations. this contact form When I set my hostname to "razor.pillars.net" then I always get the sudo warning, regardless of any /etc/hosts or /etc/sudoers modifications. Bruce Dubbs 2006-09-02 19:17:20 UTC PermalinkRaw Message Post by Chris LemireI don't think you understand the problem. gutsy) where a different hostname in /etc/hostname and /etc/hosts is accepted.

The -k actually worked, since in the next sudo command you had to enter your password again: > # hostname foobar > $ sudo -k > $ sudo true > [sudo] Changed in sudo: status: In Progress → Incomplete mon (javiermon-deactivatedaccount) wrote on 2008-03-13: #14 Hi Yesterday I did a dist-upgrade from gutsy, I haven't touched my sudoers file: sudo grep -v I can't edit the file. have a peek here you are aware that the X Window System is a client-server setup over the loopback interface aren't you?!?

I actually am certain that raising privileges on the local machine should not require networking bits at all. If you configure your local sudoers in a way that you have privileges on a machine 'foo', and no privs on a machine 'bar', and you change your hostname from 'bar' If I could "touch /etc/sudo_only_on_this_machine", or something similar that would tell sudo that I was only using it on one machine, I would be happy.

The time now is 07:25 AM.

On Fri, May 23, 2008 at 2:41 PM, agent 8131

Even on a single host, the desktop uses many networking protocols for interprocess communication. Vikas Bhasin (vikasb) wrote on 2008-05-23: Re: [Bug 32906] Re: sudo fails if it cannot resolve the local hostname and no MTA is installed #82 unnamed Edit (1.3 KiB, text/html; charset=UTF-8) Change the line with your old hostname to match the output of the previous command. Check This Out [email protected]:~$ hostname [email protected]:~$ This indicates that no hostname is set.

Does that not happen automatically? Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ Now what can I do? This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.

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 Use the nameservers for your ISP.Note that there used to be a file named /etc/hosts.conf, but it is neverused by the resolver in modern installations if nsswitch.conf exists.-- Bruce Chris Lemire Es una pescadilla que se muerde la cola.