From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: sirgazil@zoho.com, 35550 <35550@debbugs.gnu.org>
Subject: bug#35550: Installer: wpa_supplicant fails to start
Date: Sat, 04 May 2019 17:32:23 +0200 [thread overview]
Message-ID: <877eb62q2g.fsf@gnu.org> (raw)
In-Reply-To: <20190504140753.6wjgctw6ird7xj2b@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Sat, 4 May 2019 16:07:54 +0200")
Hi Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>> Could you also:
>>
>> 1. Let the installation image boot;
>>
>> 2. Confirm with ‘herd status wpa-supplicant’ that the ‘wpa-supplicant’
>> service is marked as stopped (failed to start);
>>
>
> $ herd status wpa-supplicant
> Status of wpa-supplicant:
> It is stopped.
> It is enabled.
> Provides (wpa-supplicant).
> Requires (user-processes dbus-system loopback syslogd).
> Conflicts with ().
> Will be respawned.
>
>
>
>> 3. Show the contents /var/run/wpa_supplicant.pid, and check whether
>> they correspond to the PID of a running ‘wpa_supplicant’ process.
>>
>
> There is no such file.
At this point, could you also check:
3b. The output of “pgrep -fa wpa_supplicant”.
The PID file was probably removed by the second attempt to start the
‘wpa-supplicant’ service.
Could you also try running (as root):
while herd restart wpa-supplicant; do : ; done
to see the frequency at which the service fails to start?
Thanks!
Ludo’.
next prev parent reply other threads:[~2019-05-04 15:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 19:31 bug#35550: Installer: wpa_supplicant fails to start Ludovic Courtès
2019-05-03 20:51 ` Ludovic Courtès
2019-05-04 15:28 ` Ludovic Courtès
2019-05-05 20:26 ` Ludovic Courtès
2019-05-05 22:21 ` Ludovic Courtès
2019-05-06 19:47 ` pelzflorian (Florian Pelz)
2019-05-07 7:53 ` Ludovic Courtès
2019-05-06 20:00 ` Danny Milosavljevic
2019-05-07 8:05 ` Ludovic Courtès
2019-05-08 14:32 ` Ludovic Courtès
2019-05-08 22:25 ` Ludovic Courtès
2019-05-09 6:46 ` pelzflorian (Florian Pelz)
2019-05-09 10:18 ` Ludovic Courtès
2019-05-11 18:13 ` Ludovic Courtès
2019-05-03 21:26 ` Ricardo Wurmus
2019-05-04 3:26 ` sirgazil
2019-05-04 12:49 ` Ludovic Courtès
2019-05-04 14:07 ` pelzflorian (Florian Pelz)
2019-05-04 15:32 ` Ludovic Courtès [this message]
2019-05-04 15:47 ` pelzflorian (Florian Pelz)
2019-05-04 21:14 ` Ludovic Courtès
2019-05-04 21:34 ` pelzflorian (Florian Pelz)
2019-05-05 16:29 ` 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=877eb62q2g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35550@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=sirgazil@zoho.com \
/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).