** Changed in: sudo (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/32906
Title:
sudo fails if it cannot resolve the local hostname
I agree, this bug isn't fixed in Quantal (as it wasn't in Precise):
# sudo hostname just-modified-my-hostname
# sudo whoami
sudo: unable to resolve host just-modified-my-hostname
root
# sudo cat /etc/lsb-release
sudo: unable to resolve host just-modified-my-hostname
DISTRIB_ID=Ubuntu
No, that's not this bug. This bug is about sudo *failing* if it can't
resolve the hostname, which is not what you have happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/32906
Title:
is this really fixed and gone for good? i see this in precise again.
i don't want sudo to make network lookups. i want a option to restrict it to
local operation only. for now only because it is annoying to wait for the
lookup. you already discussed the issues.
the networking features are nice
Martin, which version is it nominally fixed for? I see it in 9.04, on my
laptop whose hostname only resolves when it is in a location where the
local DNS server knows of it (this is deliberate, as I do not want my
hostname to map to 127.0.0.1 and its IP address changes).
--
sudo fails if it
Steve, the bug was fixed during 8.10 development and backported to 8.04.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
I'm still having this issue on Karmic, always I run a command as super
user:
sudo: unable to resolve host (my host)
The system seen unable to resolve my host even if my /etc/hosts seems
OK.
** Changed in: sudo (Ubuntu)
Status: Fix Released = Confirmed
** Attachment added: My /etc/hosts
This has been fixed long ago. Can you please open a new report?
** Changed in: sudo (Ubuntu)
Status: Confirmed = Fix Released
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you
My desktop computer has a public IP address that is reachable from the
local network as well as the internet at large.
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.
Believe me; I've tried all possible
Charles,
Your computer is using DHCP to acquire an IP address from the router.
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. Since you're connected
to a Telstra
I'm an ignorant newbie who just installed Ubuntu 8.04.1 Kernel 2.6.24-19
generic on an Advent 4211B (? = MSI Wind). One of my (fruitless)
attempts to get the wifi card working was with Ndiswrapper. I had
previously been using a wired connection to my Linksys WRT54G router,
which connected to the
Figure I'll try and get this right now that I've posted this in
seemingly nothing but duplicate bug reports:
So I've followed just about all tips, and none prove fruitful to me. The
following is a copy of my /etc/hosts file:
127.0.0.1 scotty
127.0.1.1 scotty-laptop
# The following lines are
For the benefit of others who come across this bug:
127.0.0.1 scotty
Don't do this. 127.0.0.1 should always resolve to 'localhost', not to
any other name.
scotty@:~$ hostname
scotty@:~$
This indicates that no hostname is set. To fix this temporarily, run:
sudo hostname
I fixed this also when I put in hosts file:
127.0.0.1 localhost hostname
127.0.1.1 hostname
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
This has happened to me ever since I upgraded from 7.10 to 8.04. Once I
go into network-admin and add jonolaptop-linux to Aliases sudo seems
to work. This solution isn't permanent though.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
** Changed in: sudo
Status: Confirmed = Fix Released
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I dont know if I just took the easy way. 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 manual configuration. Then I
unlocked. Then I went to the hosts tab. I deleted everyting out of the
hosts tab
i wrote left click on my network connection icon
Im sorry this icon is at the right side of the screen.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug is specifically about sudo (or gksudo etc.) failing completely.
The fix described here solves that problem.
You may still see some messages or warnings being printed; that should
be fixed but it's not this bug.
You may also see some programs corrupting your /etc/hosts file; that
is also
I noticed this as well. It looks like 1.6.9p10-1ubuntu3.2 reintroduced
this problem, at least on 32-bit. I didn't get to do much testing on it
but I did notice that it had returned. I can provide more details when
I get the chance to test but I'd say this problem is no longer fixed.
--
sudo
agreed , also experience the same issue when trying to install the updates
for the hardy.
have checked the local host file, few of the software are not being able to
install like alamin-server , its asking for the partial updates, but nothing
is been installed.
Hope it will be sorted out.
On
i had the problem today (hardy 8.04 32 bit install), with all the updates
installed...
so i believe there is still some problem
however I fixed it by using
gksu gedit /etc/hosts
and just adding the hostname in front of 127.0.0.1 (as mentioned earler)
is there a way that any configuration dump
I can confirm that the update fixed this bug, sudo is no longer
dysfunctional.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
chodo [2008-05-06 23:31 -]:
why doesn't it find the host anyway? Isn't this a bug as well?
No, that's usually a local configuration error, if /etc/hostname does
not have an entry in /etc/hosts.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
Copied to hardy-updates.
** Changed in: sudo (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs,
why doesn't it find the host anyway? Isn't this a bug as well?
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
yell0w, did you try the package in hardy-proposed? It should fix this
issue.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
This got three 'works for me's, and I am using it on both of my hardy
boxes, too, and verified that it works correctly there.
** Tags added: verification-done
** Tags removed: verification-needed
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
This bug was fixed in the package sudo - 1.6.9p12-1ubuntu1
---
sudo (1.6.9p12-1ubuntu1) intrepid; urgency=low
* Merge from debian unstable, remaining changes:
- debian/rules: Disable lecture, enable tty_tickets by default. (Ubuntu
specific)
- Add debian/sudo_root.8:
I happened to have my hostname a fqdn.
I changed the values of /etc/hosts around and ended up borking my sudo. I was
mortified since it's a remote machine.
After trying a few things suggested here and elsewhere, I ended up changing the
A record for my hostname to 127.0.1.1 and that got sudo
Note that the underlying bug seems to be a race condition and another
workaround may be to try the command 10 or 20 times as noted in
https://bugs.edge.launchpad.net/ubuntu/+source/hostname/+bug/113778
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
Hi Brian,
Brian Murray [2008-04-30 21:56 -]:
I recreated the bug using the test case provided on Hardy Heron with
sudo version 1.6.9p10-1ubuntu3. I then installed 1.6.9p10-1ubuntu3.1
from hardy-proposed and was then able to use sudo. However, I did
notice that 'unable to resolve host'
See http://www.cpqlinux.com/hostname.html to fix the issue in your
/etc/hosts and /etc/hostname files
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs,
Works when tested with and without a domain name, however the unable to
resolve host ... message still gets printed
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of
Bug recreated:
VMWare - occurs at the time of network changing via GUI (e.g. switching from
host only to NAT and reverse)
I cannot reproduce it with ifconfig ethX.
Looks like the culprit is the 127.0.1.1 entry at/in the GUI network
configuration - I can reproduce it by deleting the line and sudo
Pasi wrote on 2008-04-26: (permalink)
I find this very serious problem since ubuntu relies so heavily on sudo (the
lack of root account) and if that command fails there is no way to do anything.
sudo should not depend on network configurations. It sounds very very dangerous!
Quoting Asa Zernik:
Just saying, it's not like Ubuntu is any more dependent on sudo than any other
*X system.
--
Well by default the root user (UID 0) has no password set and is as such
effectively disabled (passwd -l root). Sure you can sudo su or sudo
-s but that is a function of sudo and
** Bug watch added: Gratisoft Bugzilla #285
http://www.gratisoft.us/bugzilla/show_bug.cgi?id=285
** Also affects: sudo via
http://www.gratisoft.us/bugzilla/show_bug.cgi?id=285
Importance: Unknown
Status: Unknown
--
sudo fails if it cannot resolve the local hostname and no MTA is
** Changed in: sudo
Status: Unknown = Confirmed
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Uploaded to hardy-proposed now, awaiting approval from another stable
release manager.
** Description changed:
On behalf of Adam Williamson [*]
[EMAIL PROTECTED]:~$ sudo scp 192.168.2.7:/etc/hosts /etc
[EMAIL PROTECTED]:~$ sudo nano /etc/hosts
sudo: unable to lookup ubuntu510
Patch looks good.
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Accepted into hardy-proposed. Please test and give some feedback here.
Thank you!
** Tags added: verification-needed
** Changed in: sudo (Ubuntu Hardy)
Status: In Progress = Fix Committed
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
Works for me, thanks.
barcc:~$ sudo id
sudo: unable to resolve host foobar
[sudo] password for barcc:
uid=0(root) gid=0(root) Gruppen=0(root)
--
sudo fails if it cannot resolve the local hostname and no MTA is installed
https://bugs.launchpad.net/bugs/32906
You received this bug notification
I recreated the bug using the test case provided on Hardy Heron with
sudo version 1.6.9p10-1ubuntu3. I then installed 1.6.9p10-1ubuntu3.1
from hardy-proposed and was then able to use sudo. However, I did
notice that 'unable to resolve host' showed up 2x. Like:
sudo: unable to resolve host bob
44 matches
Mail list logo
