Bug#811266: pulseaudio: log is flooded sometimes when combined with torsocks (torify)

[Felipe Sateler]

Control: tags -1 moreinfo

Hi,

On 17 January 2016 at 09:09, Andreas B. Mundt <andi.mundt at web.de> wrote:
> Package: pulseaudio
> Version: 7.1-2
> Severity: normal
>
> Dear Maintainer,
>
> when playing a stream using a music player with torsocks like:
>
>       torify mpg321 http://mp3stream1.apasf.apa.at:8000
>
> it happens sometimes that no music is played, instead the log is
> flooded with identical messages like:
>
>         pulseaudio[3148]: [pulseaudio] socket-server.c: accept(): Bad address
>
> On my system, 33 174 574 lines like the above ended up in
> /var/log/user.log within 73 seconds.  Yesterday, I ended up with no
> space left on my root partition because /var/log/user.log and
> /var/log/syslog both grow to a size of > 5G within minutes, before I
> realized the problem.
>
> I've not figured out yet when it works, it seems to fail only the
> first time after reboot.  Once pulseaudio is killed and tried again, it
> seems to work, also after stopping and starting again there where no
> issues so far.
>
> I'm not sure if this is only pulseaudio's problem, feel free to clone
> or reassign.

Could you attach a verbose log of when the problem happens?

https://wiki.ubuntu.com/PulseAudio/Log


Also, as a workaround you can try disabling logging with the
log-target option in default.pa (eg, set it to file:/dev/null)

-- 

Saludos,
Felipe Sateler