From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35550: Installer: wpa_supplicant fails to start Date: Sat, 04 May 2019 17:32:23 +0200 Message-ID: <877eb62q2g.fsf@gnu.org> References: <87sgtv8hcz.fsf@gnu.org> <16a80e1461c.1292821a927951.2710363725930741694@zoho.com> <87k1f64c5o.fsf@gnu.org> <20190504140753.6wjgctw6ird7xj2b@pelzflorian.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35620) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMweu-00038b-84 for bug-guix@gnu.org; Sat, 04 May 2019 11:33:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMwet-0003nD-4H for bug-guix@gnu.org; Sat, 04 May 2019 11:33:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:38462) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hMwes-0003n5-Q3 for bug-guix@gnu.org; Sat, 04 May 2019 11:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hMwes-0000Pf-J7 for bug-guix@gnu.org; Sat, 04 May 2019 11:33:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190504140753.6wjgctw6ird7xj2b@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Sat, 4 May 2019 16:07:54 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: "pelzflorian (Florian Pelz)" Cc: sirgazil@zoho.com, 35550 <35550@debbugs.gnu.org> Hi Florian, "pelzflorian (Florian Pelz)" skribis: >> Could you also: >>=20 >> 1. Let the installation image boot; >>=20 >> 2. Confirm with =E2=80=98herd status wpa-supplicant=E2=80=99 that the = =E2=80=98wpa-supplicant=E2=80=99 >> 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 =E2=80=98wpa_supplicant=E2= =80=99 process. >> > > There is no such file. At this point, could you also check: 3b. The output of =E2=80=9Cpgrep -fa wpa_supplicant=E2=80=9D. The PID file was probably removed by the second attempt to start the =E2=80=98wpa-supplicant=E2=80=99 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=E2=80=99.