From: Martin Becze <mjbecze@riseup.net>
To: 44820@debbugs.gnu.org
Subject: bug#44820: MPD fails after respawning too often
Date: Fri, 27 Nov 2020 05:31:29 -0600 [thread overview]
Message-ID: <84307412-1cbe-79dd-bebd-b272a3732665@riseup.net> (raw)
In-Reply-To: <87mtz3um48.fsf@gnu.org>
I also ran into this problem. Here is the relevnat part of
/var/run/mpd/<mpd-user>/log
> exception: Failed to create pid file "/var/run/mpd/<mpd-user>/pid": Permission denied
A quick dirty fix is just to chown the /var/run/mpd folder so that mpd
can create its pid file.
On 11/27/20 4:31 AM, Ludovic Courtès wrote:
> Hi,
>
> Simon <lists@netpanic.org> skribis:
>
>> On a recent pull, MPD will not start any more.
>>
>> Herd status reports:
>>
>> Status of mpd:
>> It is stopped.
>> It is disabled.
>> Provides (mpd).
>> Requires (user-processes).
>> Conflicts with ().
>> Will be respawned.
>> Last respawned on Mon Nov 23 10:22:07+0100 2020.
>>
>>
>> Reading my messages, I find:
>>
>> Nov 23 10:22:07 localhost shepherd[1]: Respawning mpd.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been started.
>> Nov 23 10:22:07 localhost shepherd[1]: Respawning mpd.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been started.
>> Nov 23 10:22:07 localhost shepherd[1]: Respawning mpd.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been started.
>> Nov 23 10:22:07 localhost shepherd[1]: Respawning mpd.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been started.
>> Nov 23 10:22:07 localhost shepherd[1]: Respawning mpd.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been started.
>> Nov 23 10:22:07 localhost shepherd[1]: Respawning mpd.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been started.
>> Nov 23 10:22:07 localhost shepherd[1]: Service mpd has been disabled.
>> Nov 23 10:22:07 localhost shepherd[1]: (Respawning too fast.)
>>
>>
>> Unfortunately, there are no further messages as to why the service is
>> disabled, or why the daemon is respawning too often.
>
> Does /var/log/mpd/mpd.log or similar contain useful info?
>
> Could you share your ‘mpd-configuration’?
>
> There have been two changes recently, which fixed the mpd system test,
> but perhaps they introduced other issues:
>
> https://git.savannah.gnu.org/cgit/guix.git/log?id=bb124f6e9c0af0a23736f233c2ea2c9c9b4a40a6
>
> Thanks for reporting the issue,
> Ludo’.
>
>
>
next prev parent reply other threads:[~2020-11-27 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 13:24 bug#44820: MPD fails after respawning too often Simon
2020-11-27 10:31 ` Ludovic Courtès
2020-11-27 11:31 ` Martin Becze [this message]
2020-11-27 19:29 ` Simon Streit
2020-12-03 17:05 ` Ludovic Courtès
2020-12-03 21:00 ` Simon Streit
2020-12-03 21:34 ` Martin Becze
2020-12-07 8:44 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84307412-1cbe-79dd-bebd-b272a3732665@riseup.net \
--to=mjbecze@riseup.net \
--cc=44820@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).