Your message dated Fri, 11 Apr 2014 13:29:58 -0300
with message-id 
<CAAfdZj9CjFiCJp30WgK3fPfAr=SZZOZd6v9vmhQ9k4=cydt...@mail.gmail.com>
and subject line Re: Bug#620082: pulseaudio: Spams the system log when out of 
disk space, making the problem worse
has caused the Debian Bug report #620082,
regarding pulseaudio: Spams the system log when out of disk space, making the 
problem worse
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
620082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620082
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pulseaudio
Version: 0.9.21-4
Severity: normal

Hi,

Today I was hit by a full up disk problem that caused the bug I am talking
about; pulseaudio then fills up /var/log/syslog with the following messages,
every 5 seconds (yes, these are localized):

  Mar 29 22:59:21 nsk pulseaudio[18495]: pid.c: Failed to write PID file.
  Mar 29 22:59:21 nsk pulseaudio[18495]: main.c: Échec de pa_pid_file_create().
  Mar 29 22:59:21 nsk pulseaudio[18493]: main.c: Échec lors du démarrage du 
démon.

I think it cannot write the PID file because the disk is full, but spaming the
log like that worsen the problem, as /var is not on a separate partition here.
BTW, I found out about this problem because pulseaudio was also stuck at 100%
CPU (don't know if it's related; it's not like it's the first time I see that…)

I don't know exactly what it should do, but I see a lot of problem with
pulseaudio trying harder when things fail: sometime, it's better to just give
up.

Regards,
benjamin

PS: my changed config file is just some lines I commented; no actual change

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.37-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pulseaudio depends on:
ii  adduser                       3.112+nmu2 add and remove users and groups
ii  consolekit                    0.4.4-1    framework for defining and trackin
ii  libasound2                    1.0.23-2.1 shared library for ALSA applicatio
ii  libc6                         2.11.2-13  Embedded GNU C Library: Shared lib
ii  libcap2                       1:2.20-1   support for getting/setting POSIX.
ii  libdbus-1-3                   1.4.6-1    simple interprocess messaging syst
ii  libgdbm3                      1.8.3-9    GNU dbm database routines (runtime
ii  libice6                       2:1.0.7-1  X11 Inter-Client Exchange library
ii  libltdl7                      2.2.6b-2   A system independent dlopen wrappe
ii  libpulse0                     0.9.21-4   PulseAudio client libraries
ii  libsamplerate0                0.1.7-3    Audio sample rate conversion libra
ii  libsm6                        2:1.2.0-1  X11 Session Management library
ii  libsndfile1                   1.0.24-1   Library for reading/writing audio 
ii  libspeexdsp1                  1.2~rc1-1  The Speex extended runtime library
ii  libudev0                      166-1      libudev shared library
ii  libx11-6                      2:1.4.2-1  X11 client-side library
ii  libxtst6                      2:1.2.0-1  X11 Testing -- Record extension li
ii  lsb-base                      3.2-27     Linux Standard Base 3.2 init scrip
ii  udev                          166-1      /dev/ and hotplug management daemo

Versions of packages pulseaudio recommends:
ii  gstreamer0.10-pulseaudio     0.10.28-2   GStreamer plugin for PulseAudio
ii  libasound2-plugins           1.0.23-1+b1 ALSA library additional plugins
ii  pulseaudio-esound-compat     0.9.21-4    PulseAudio ESD compatibility layer
ii  pulseaudio-module-x11        0.9.21-4    X11 module for PulseAudio sound se

Versions of packages pulseaudio suggests:
ii  paman                         0.9.4-1    PulseAudio Manager
ii  paprefs                       0.9.9-2    PulseAudio Preferences
ii  pavucontrol                   0.9.9-1    PulseAudio Volume Control
ii  pavumeter                     0.9.3-1    PulseAudio Volume Meter
ii  pulseaudio-utils              0.9.21-4   Command line tools for the PulseAu

-- Configuration Files:
/etc/pulse/daemon.conf changed [not included]

-- no debconf information



--- End Message ---
--- Begin Message ---
On Fri, Apr 11, 2014 at 12:36 PM, Benjamin Cama <[email protected]> wrote:
> Hi Felipe,
>
> Le mardi 08 avril 2014 à 20:08 -0300, Felipe Sateler a écrit :
>> >  Today I was hit by a full up disk problem that caused the bug I am talking
>> >  about; pulseaudio then fills up /var/log/syslog with the following 
>> > messages,
>> >  every 5 seconds (yes, these are localized):
>> >
>> >   Mar 29 22:59:21 nsk pulseaudio[18495]: pid.c: Failed to write PID file.
>> >   Mar 29 22:59:21 nsk pulseaudio[18495]: main.c: Échec de 
>> > pa_pid_file_create().
>> >   Mar 29 22:59:21 nsk pulseaudio[18493]: main.c: Échec lors du démarrage 
>> > du démon.
>>
>> Can you still reproduce this issue? This bug was filed a long time ago
>> and it could have been fixed already. If you still can reproduce it
>> please reply so we can debug this. Otherwise, I'd like to close this
>> bug.
>
> Thanks for taking care of following this old bug! I tried to fill up my
> disk, but much things have changed: pulseaudio is now a per-session
> daemon, and I don't know where it stores its pid file. I tried to kill
> it and restart it with "pulseaudio --start" while the disk was full, and
> it didn't complain (nothing appear in the logs). I only filled up "/"
> though, and maybe the per-session daemon creates its pid somewhere in my
> home, which wasn't full? Anyway, I think you can close it.

Thanks for checking. I now see the PID file is created in
/run/user/<userid>/pulse, which is mounted on a tmpfs, so that this
problem is unlikely to occur.

Closing the bug then.

Thanks!

-- 

Saludos,
Felipe Sateler

--- End Message ---

Reply via email to