Fedora 11 sudo has a 20 second start delay

manuleka · 06-11-2009, 03:18 PM

i'm using Fedora 11 which i installed a couple of days back...
i added my user name to the sudoer list but everytime i run the sudo command it takes at least 20 + seconds before anything happens... this happens everytime i run sudo...

in comparison to running su things happen immediately... anyone else experiencing this?

now everytime i install or run a command requiring root access i just use su...

ramram29 · 06-11-2009, 03:39 PM

looks like an authentication problem. Are you using ldap as authentication? Have you looked at the logs.

manuleka · 06-11-2009, 04:47 PM

Quote:

Originally Posted by ramram29

looks like an authentication problem. Are you using ldap as authentication? Have you looked at the logs.

sorry mate i'm quite a Linux noob... how can i check the type of authentication i'm using? and where can i find these logs?

cheers

marozsas · 06-13-2009, 03:51 PM

sorry to hijack this thread but I am having the same problem

Code:

[miguel@quadbit /]$ time sudo pwd
/

real	0m20.408s
user	0m0.009s
sys	0m0.012s
[miguel@quadbit /]$

This is a new install (not an upgrade) of F11 using basic authentication (shadow passwords).
/etc/sudoers has a line:

Code:

miguel    ALL=(ALL)       ALL

(or it can be "miguel ALL=(ALL) NOPASSWD: ALL" too - no difference)

jamescondron · 06-13-2009, 04:03 PM

Well, lets check the logs then. Try a sudo command, then

Code:

tail /var/log/auth.log

marozsas · 06-13-2009, 04:13 PM

I guess you mean "/var/log/secure" as "auth.log" doesn't exist in Fedora (at least mine does not exist)
In a terminal

Code:

$ date; time sudo pwd
Sat Jun 13 18:10:02 BRT 2009
/

real	0m15.354s
user	0m0.008s
sys	0m0.012s
$

and at the same time the log output from /var/log/secure:

Code:

# tail -f /var/log/secure
Jun 13 18:10:02 quadbit sudo:   miguel : TTY=pts/1 ; PWD=/ ; USER=root ; COMMAND=/bin/pwd

As you can see, the event is logged immediately. The command execution takes about 15s.

marozsas · 06-14-2009, 11:26 AM

uhmm...Am I using MS Windows or what ?
Because, this morning my Fedora wake up "normal", I mean,

Code:

$ time sudo pwd
/

real	0m0.028s
user	0m0.009s
sys	0m0.010s
$

I do nothing, I didn't changed /etc/sudoers, I didn't installed anything, I didn't updated anything.
Yesterday even after several boots it wasn't fixed.

Code:

$ sudo last  |grep "boot" | grep "Jun 13"
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 19:31          (05:10)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 15:34          (02:40)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 14:34          (00:50)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 14:32          (00:00)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 14:30          (00:01)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 14:24          (00:04)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 11:27          (01:09)    
reboot   system boot  2.6.29.4-167.fc1 Sat Jun 13 08:45          (03:51)

I don't known why today is working but is is.
I hate random behaviours like this....looks like I am using Windows.

chrism01 · 06-14-2009, 08:01 PM

Could be an autoupdate from the repos? Fedora is a bleeding edge distro, so I wouldn't be entirely surprised.

marozsas · 06-15-2009, 09:24 AM

Quote:

Originally Posted by chrism01

Could be an autoupdate from the repos? Fedora is a bleeding edge distro, so I wouldn't be entirely surprised.

No, I didn't set autoupdate (System/Preferences/Software Updates).
Also, rpm -qa --last do not show any packages installed/updated in this period.

I read about a similar behaviour in Ubuntu forums and it was caused by the fingerprint reader used with GDM to authenticate users in the last Ubuntu. The description of the problem also says it fixes by them self but it returns after 12hours, according to the original post !

Lets see what happens for now. So far, so good for me....

PS: for manuleka: And about you ? You still has the problem or it was "fixed" too ?
very strange indeed....

manuleka · 06-15-2009, 06:10 PM

@ maroz

yes it is really weird... unfortunately for me the problem still persists

but hopefully the next update will somehow resolve the problem... i've installed Fedora 11 three times due to partition issues and other problems but on all three ocasions two i can remember had the sudo delay issue

i am in no mood for another reinstall - i've customized everything on my setup and installed alot of softwares i will make do with the problem even if fixing it is impossible, well nothing is impossible but i'm a novice and don't wanna stuff up my setup - too much work. Plus i don't seem to have the time

marozsas · 06-15-2009, 06:24 PM

oh no ! I am just came to home and sudo is having that annoying delay AGAIN !
Looks like somehow it is related to the same problem that Ubuntu user I mentioned is having too...

The strange is in my work place I installed F11 in my desktop and applied the same updates and in that computer I had no problems with sudo.

I will update this thread for any news.

jefro · 06-15-2009, 07:38 PM

Root is doing something maybe. Not sure how to tell what it is.

rohandhruva · 06-16-2009, 08:11 AM

I was facing the same problem. This happens if you change the hostname during the install process. I have set the hostname of my system to "fedora". The installer assumes that people will not change the default of "localhost.localdomain".

To solve the problem, edit the file /etc/hosts

Code:

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 <ADD_YOURS_HERE>
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 <ADD_YOURS_HERE>

Just add your hostname to the end of both the lines as shown above, that should solve the problem.

marozsas · 06-16-2009, 02:10 PM

Quote:

Originally Posted by rohandhruva

I was facing the same problem. This happens if you change the hostname during the install process. I have set the hostname of my system to "fedora". The installer assumes that people will not change the default of "localhost.localdomain".

Yes, this is what I did different in my work place and in my home.
At workplace I left the default localhost.localdomain and added my machine name at end of lines after the first boot. In my home I changed it at installation time and never go back to /etc/hosts again.

How do you figure out this ?
Most interesting than the fix itself is how you came to this...

Anyway, thank you !

rohandhruva · 06-16-2009, 02:25 PM

I had experienced such "long unnecessary" delay problem in the past with KDE - the KDE startup takes very long if the localhost entry is not there. But once it starts, it works perfectly. I was experiencing the exact same symptom with this sudo issue - very long to start, and then works perfectly. Hence, the first thing which came to my mind was "hosts file".

Also, a bit of googling turned up this result - http://forums.fedoraforum.org/showpo...94&postcount=4 Though that person does not post the fix itself, from there on it was quite easy to figure out