Your message dated Sun, 1 Feb 2015 12:56:01 +0500
with message-id <20150201075601.ga12...@belkar.wrar.name>
and subject line Re: Bug#776306: mpdscribble: Fails to start because of error 
in pidfile creation
has caused the Debian Bug report #776306,
regarding mpdscribble: Fails to start because of error in pidfile creation
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 ow...@bugs.debian.org
immediately.)


-- 
776306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpdscribble
Version: 0.22-5
Severity: grave
Justification: renders package unusable

With default configuration the service tries to create its pidfile in 
folder '/var/run/mpdscribble', but such a folder is not created by 
installation script, nor it persists to system reboot. This cause the 
system-wide service to fail to start with the following error.

mpdscribble[359]:
  Failed to create pidfile /var/run/mpdscribble/mpdscribble.pid:
  No such file or directory
mpdscribble.service: main process exited, code=killed, status=5/TRAP
systemd[1]: Unit mpdscribble.service entered failed state.

Obvious (and tested) workarounds include:

1. After each reboot, create the folder '/var/run/mpdscribble' owned by
   mpdscribble:mpdscribble with permissions ug+rwX (~default).
2. Disable pidfile creation, by commenting the corresponding line in
   /etc/mpdscribble.conf .

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mpdscribble depends on:
ii  adduser                3.113+nmu3
ii  debconf [debconf-2.0]  1.5.55
ii  init-system-helpers    1.22
ii  libc6                  2.19-13
ii  libglib2.0-0           2.42.1-1
ii  libmpdclient2          2.9-1
ii  libsoup2.4-1           2.48.0-1
ii  lsb-base               4.1+Debian13+nmu1
ii  ucf                    3.0030

mpdscribble recommends no packages.

Versions of packages mpdscribble suggests:
pn  mpd  <none>

-- debconf information:

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
On Mon, Jan 26, 2015 at 03:03:08PM +0100, Marco Solieri wrote:
> With default configuration the service tries to create its pidfile in 
> folder '/var/run/mpdscribble', but such a folder is not created by 
> installation script, nor it persists to system reboot. This cause the 
> system-wide service to fail to start with the following error.
> 
> mpdscribble[359]:
>   Failed to create pidfile /var/run/mpdscribble/mpdscribble.pid:
>   No such file or directory
> mpdscribble.service: main process exited, code=killed, status=5/TRAP
> systemd[1]: Unit mpdscribble.service entered failed state.
> 
> Obvious (and tested) workarounds include:
> 
> 1. After each reboot, create the folder '/var/run/mpdscribble' owned by
>    mpdscribble:mpdscribble with permissions ug+rwX (~default).
> 2. Disable pidfile creation, by commenting the corresponding line in
>    /etc/mpdscribble.conf .
No, the default /etc/mpdscribble.conf already has this line commented out.

-- 
WBR, wRAR

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to