We have experience of this too, but it is not a sudo fault in our
implementation. As the sudo command is being logged to what you define
as syslog, I would suggest looking there.
The problem we have is that logs are merged from many machines and
sometimes the process we're using gets stuck and the messages queue up.
There is a timeout to allow processing to continue and the messages are
stored, to be forwarded when the comms are sorted out again (stop/start
of our syslog manager on the affected machine)
Robin Battersby-Cornmell
Unisys, Liverpool
-----Original Message-----
From: Justin Alcorn [mailto:justin at jalcorn.net]
Sent: Tuesday, July 15, 2008 7:45 PM
To: sudo-users at sudo.ws
Subject: [sudo-users] sudo very slow
I'm using Debian Etch, and confirmed that my sudo package is up to date
(
1.6.8p12-4)
I have multiple Debian machines, and sudo runs fine on all except this
one.
It happens to be my DNS, DHCP and samba server.
sudo takes a long time. strace sudo su - shows me delays in what looks
like trying to send a log entry.
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
socket(PF_FILE, SOCK_DGRAM, 0) = 4
fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
connect(4, {sa_family=AF_FILE, path="/dev/log"}, 16) = 0
send(4, "<85>Jul 15 14:41:22 sudo: ro"..., 90, MSG_NOSIGNAL
---pause----
...
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
getpid() = 3648
socket(PF_FILE, SOCK_DGRAM, 0) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
connect(3, {sa_family=AF_FILE, path="/dev/log"}, 16) = 0 send(3,
"<86>Jul 15 14:41:48 su[3648]: Su"..., 60, MSG_NOSIGNAL
---pause---
...
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
send(3, "<86>Jul 15 14:42:18 su[3648]: + "..., 47, MSG_NOSIGNAL
---pause---
...
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0
send(3, "<38>Jul 15 14:42:43 su[3648]: (p"..., 80, MSG_NOSIGNAL
--pause--
...
As you can see, it took more than a minute. Sometimes it is much
longer.
Exiting from the sudo shell also is delayed, as is logging on via SSH.
I've looked around thinking it's a reverse DNS, but I can do a reverse
lookup and get a PTR record.
Ideas?
--
--
Justin B. Alcorn
***********************************
This email is sent in confidence for the addressee only.
Unauthorised recipients must preserve this confidentiality and should please advise the sender immediately by returning the original email to us without reading it, taking a copy or disclosing it to anyone else. Please also destroy and delete the email from your computer.
We have taken reasonable precautions to ensure that no viruses are transmitted to any third party. Unisys Insurance Services Limited does not accept any responsibility for any loss or damage resulting directly or indirectly from the use of this email or its contents.
Unisys Insurance Services Limited is authorised and regulated by the Financial Services Authority, is a member of the UNISYS group of companies and provides outsourcing services to the Financial Services Industry
Unisys Insurance Services Limited Registered in England No. 4087012
Registered Office: Bakers Court, Bakers Road, Uxbridge, UB8 1RG