wpa-supplicant spams into logfiles

[Hans <hans.ullrich@loop.de>]

Hi all,

since some time I discovered, that wpa-supplicant is spamming into syslog and 
daemon.log. This means, both logs are bloating to gigantic filesize.

This is what it spams:

May 11 21:06:52 localhost wpa_supplicant[5871]: ctrl_iface exists and seems to 
be in use - cannot override it
May 11 21:06:52 localhost wpa_supplicant[5871]: Delete 
'/run/wpa_supplicant/wlan0' manually if it is not used anymore
May 11 21:06:52 localhost wpa_supplicant[5871]: Failed to initialize control 
interface '/run/wpa_supplicant'.#012You may have another wpa_supplicant 
process already running or the file was#012left by an unclean termination of 
wpa_supplicant in which case you will need#012to manually remove this file 
before starting wpa_supplicant again.
May 11 21:06:52 localhost NetworkManager[1517]: <error> [1462993612.556366] 
[supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): 
(wlan0): error adding interface: wpa_supplicant couldn't grab this interface.
May 11 21:06:52 localhost NetworkManager[1517]: <info> (wlan0): supplicant 
interface state: starting -> down
May 11 21:06:52 localhost wpa_supplicant[5871]: ctrl_iface exists and seems to 
be in use - cannot override it
May 11 21:06:52 localhost wpa_supplicant[5871]: Delete 
'/run/wpa_supplicant/wlan0' manually if it is not used anymore
May 11 21:06:52 localhost wpa_supplicant[5871]: Failed to initialize control 
interface '/run/wpa_supplicant'.#012You may have another wpa_supplicant 
process already running or the file was#012left by an unclean termination of 
wpa_supplicant in which case you will need#012to 

And so on....

Any hints, what is happening?

I also discovered, that my wlan is sometimes not correctly reconized at boot. 

The solution then is to remove and reload the kernel module (rmmod ath5k. 
modprobe ath5k, then restart wicd.)

Maybe this is related to this?

I will be happy of any help.

Best regards

Hans