WAP131 error messages in log file /WANCfg.xml / WANIPCn.xml not found, responding ERROR 404

[steverack]

Hello There, On a WAP131, I am seeing below entries in the log-file, which start being populated roughly 6 hours after a power cycle. Firmware 1.0.1.4 (latest version) Time Stamp Severity Service Description Mar 29,2016 12:00:28 notice miniupnpd[1160] /WANCfg.xml not found, responding ERROR 404 Mar 29,2016 12:00:28 notice miniupnpd[1160] /WANIPCn.xml not found, responding ERROR 404 Mar 29,2016 11:59:34 notice miniupnpd[1160] /WANCfg.xml not found, responding ERROR 404 Mar 29,2016 11:59:34 notice miniupnpd[1160] /WANIPCn.xml not found, responding ERROR 404 Mar 29,2016 11:58:39 notice miniupnpd[1160] /WANCfg.xml not found, responding ERROR 404 Mar 29,2016 11:58:39 notice miniupnpd[1160] /WANIPCn.xml not found, responding ERROR 404 Mar 29,2016 11:57:47 notice miniupnpd[1160] /WANCfg.xml not found, responding ERROR 404 Mar 29,2016 11:57:47 notice miniupnpd[1160] /WANIPCn.xml not found, responding ERROR 404 Mar 29,2016 11:56:53 notice miniupnpd[1160] /WANCfg.xml not found, responding ERROR 404 ... The log file is full with these entries, The WAP 131 seems to be working fine, only that several times a day the AP seems to be "blackholing". The wireless connection stays up but no data is travelling through. After 1 minute or so, it works again. Tested with Windows 10 laptops, Windows 8 phones, iPads and iPhones, with same unsatisfying result. The AP is configured with 2 Vlans and connecting to an SG300-28 switch. I am not sure if both issues are related or separate. Does anyone have seen these entries and have a solution? Thanks

[steverack]

After reseting to factory defaults and manually re-applying the configuration, my WAP131 has been stable for 12 days now, which is good progress.

Still I am seeing above entries added the log-file every minute though.

Is anyone else seeing the same entries on their WAP131? I wonder what it means and if my device is somehow broken.

[mfurfaro1]

I see your same entry i my log...

i think is device linux based and is a notice from a service not disable by gui.

[Glenn Martin]

This is a "Not Found' message. I'll have to investigate what's not being found. What the status of your devices, are they still functioning?

[mfurfaro1]

Device non work fine...

We have some problem with ipad/iphone who disconect end no riconnect.(reason unknow there are similar post in the forum for other apn model with same issiu).

Apn 5ghz have problem (disappear) and only whit a reboot it return up and running.

Entry level cisco apn are non a good idea..

[steverack]

Thanks for asking Glenn.

My AP131 is still showing above error messages.

The other day I upgraded to firmware 1.0.2.2 and was hoping to get rid of above error messages. 4 days after reboot, they have come back.

At least the "blackholing" issue hasn't come back since last reboot. I am keeping an eye on the device.

I wouldn't care much about above entries, if there wasn't this "blackholing" issue, as these may be interrelated.

[steverack]

Since firmware version 1.0.2.8, the 'responding error 404' in the logs seems to be gone for good. 

Also the 'blackholing issue' hasn't come back since.

With 1.0.2.2 I could get rid of the 'blackholing issue' by disabling 'green ethernet' and 'bonjour'. With the new 1.0.2.8 I have re-enabled 'bonjour' and am yet to disable 'green ethernet' and see if it comes back.

Update 12th January 2017

After roughly 1 week the 'responding error 404' in the logs has come back :-/