systemd and hostapd

Andrej Shadura andrew at shadura.me
Fri Jun 15 03:38:31 PDT 2018


On 12 June 2018 at 18:44, Klaus Taeger <klaus.taeger at gps-stuttgart.de> wrote:
> Hello,
>
> Unfortunately the subscription to the forum went unanswered with the effect, that I cannot reply on an answer thread style. So I have to use a mail reply. My apologies for the loss of readability.
>
> To my original question (see below) the forum answer was: Check out the error messages of `journalctl -u hostapd.service`.
>
> That I did. But there was no error message. I quote the lines of the journalctl call after a systemctl restart of hostapd:
> Jun 12 18:35:50 siconstein systemd[1]: Stopping LSB: Advanced IEEE 802.11 management daemon...
> Jun 12 18:35:50 siconstein hostapd[2984]:  * Stopping advanced IEEE 802.11 management hostapd
> Jun 12 18:35:50 siconstein hostapd[2984]:    ...done.
> Jun 12 18:35:50 siconstein systemd[1]: Stopped LSB: Advanced IEEE 802.11 management daemon.
> Jun 12 18:35:50 siconstein systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon...
> Jun 12 18:35:50 siconstein hostapd[2990]:  * Starting advanced IEEE 802.11 management hostapd
> Jun 12 18:35:50 siconstein hostapd[2990]:    ...done.
> Jun 12 18:35:50 siconstein systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon.
>
> This is in line with the status=0/SUCCESS report of the ExecStart command in systemctl status and the green color of the `active (exited)`.
>
> We are still hoping to fix this behavior (again, see below) and appreciate any help.

It seems to me you’re using Debian and hostapd << 2.6-5? The upstream
hostapd doesn’t come with a systemd .service file, and the Debian
package didn’t have one either until that version, so systemd used a
sysv init script, which apparently didn’t always work correctly.

-- 
Cheers,
  Andrej



More information about the Hostap mailing list