touch-packages team mailing list archive

[Jon Fawbert <jon@xxxxxxxxxxx>]

Specifically, the messages discussed are different:

May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED
May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33

vs from 57843:

May 10 20:06:37 Otherland wpa_supplicant[1741]: WPS-AP-AVAILABLE
May 10 20:07:37 Otherland wpa_supplicant[1741]: WPS-AP-AVAILABLE
May 10 20:08:37 Otherland wpa_supplicant[1741]: WPS-AP-AVAILABLE
May 10 20:09:48 Otherland avahi-daemon[1705]: Invalid query packet.
May 10 20:11:01 Otherland avahi-daemon[1705]: last message repeated 2 times
May 10 20:14:49 Otherland avahi-daemon[1705]: Invalid query packet.
May 10 20:15:37 Otherland avahi-daemon[1705]: last message repeated 2 times

and the fact that some posters are reporting that the first set of
messages are accompanied by repeated loss of wifi connectivity,
suggesting that they indicate a failure which is impactful to wifi
state.

Both sets of messages are repeated causing the spamming issue which
creates a smiliarity but not an identical match in my opinion.

I had no intention of causing offence however and apologise if any was
taken.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in “wpa” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv->nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions