Server log fills up with acpid socket errors

Bug #247195 reported by Matt Zimmerman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Medium
Bryce Harrington

Bug Description

mizar:[~] ls -lh /var/log/Xorg.0.log
-rw-r--r-- 1 root root 23M 2008-07-10 09:14 /var/log/Xorg.0.log
mizar:[~] tail /var/log/Xorg.0.log
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
mizar:[~] grep -c acpid.socket /var/log/Xorg.0.log
351357

It seems to retry about once per second indefinitely. I'm not sure why acpid died, and restarting it fixes things, but it seems excessive to retry so often and generate a huge log file.

Related branches

Matt Zimmerman (mdz)
description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

from hw/xfree86/os-support/linux/lnx_acpi.c:

/* in milliseconds */
#define ACPI_REOPEN_DELAY 1000

but apparently that's all unnecessary by now, since the xserver should be getting all relevant acpi events from the keyboard, so the acpi-code could be dropped altogether.

Changed in xorg-server:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Nobu (benjo316) wrote :

I'm getting the same thing on Intrepid (8.10) Alpha, except I'm getting about 2 messages every second.

I have 8595 lines and counting and the system's been up for about 3 days. So an average of 30(3*24*60*60/8595) per second.

Revision history for this message
Nobu (benjo316) wrote :

It seems to have stopped now; My log has no ACPI errors from the 15th(no logs from before then) until today.

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 247195] Re: Server log fills up with acpid socket errors

On Sat, Aug 16, 2008 at 07:08:39PM -0000, Nobu wrote:
> It seems to have stopped now; My log has no ACPI errors from the 15th(no
> logs from before then) until today.

Probably your acpid is running again.

--
 - mdz

Bryce Harrington (bryce)
Changed in xorg-server:
milestone: none → intrepid-alpha-5
status: Confirmed → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

What do you guys think about this patch?

Revision history for this message
Bryce Harrington (bryce) wrote :

Upping priority because while it's just a warning message, the fact that it risks filling up the log file makes it more serious.

Changed in xorg-server:
importance: Low → Medium
Bryce Harrington (bryce)
Changed in xorg-server:
assignee: nobody → bryceharrington
Revision history for this message
Matt Zimmerman (mdz) wrote :

On Mon, Sep 01, 2008 at 10:45:06PM -0000, Bryce Harrington wrote:
> ** Changed in: xorg-server (Ubuntu)
> Assignee: (unassigned) => Bryce Harrington (bryceharrington)

I think it should probably reset the count when it successfully connects.

--
 - mdz

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg-server - 2:1.4.99.906-2ubuntu4

---------------
xorg-server (2:1.4.99.906-2ubuntu4) intrepid; urgency=low

  [ Bryce Harrington ]
  * 140_quell_acpid_errmsgs.patch: Don't fill the server log with errors
    from not being able to connect to acpid. (LP: #247195)

 -- Timo Aaltonen <email address hidden> Wed, 03 Sep 2008 10:48:24 +0300

Changed in xorg-server:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.