Actions
Bug #12467
closed
CP error on client disconnect after reboot
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Force Exclusion
Affected Version:
2.5.2
Affected Architecture:
Description
How to reproduce:
1) Create CP zone "mycpzone" with default settings and Local Database authentication (maybe other is affected too)
2) Login to CP
3) Reboot the appliance
4) Open http://x.x.x.x:8002/index.php?zone=mycpzone on the client after appliance reboot
5) Click disconnect
6) Result:
Failed setsockoptFailed setsockoptrule 1: setsockopt(IP_DUMMYNET_DEL)rule 1: setsockopt(IP_DUMMYNET_DEL) Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/captiveportal.inc:1176) in /usr/local/captiveportal/index.php on line 177
Updated by Viktor Gurov over 3 years ago
addition:
for some reason I see .db file of deleted CP zone after reboot (also if 'rm /var/db/captiveportal*'):
# ls /var/db/captiveportal* /var/db/captiveportal_online_users /var/db/captiveportaldn.rules /var/db/captiveportalzone22.db /var/db/captiveportalzone999.db -- deleted and not present in config.xml
and a bunch of deleted zones lock files:
# ls /tmp/captiveportal*.lock /tmp/captiveportalcpzone555.lock /tmp/captiveportaldbzone11.lock /tmp/captiveportalzone11.lock /tmp/captiveportalcpzone666.lock /tmp/captiveportaldbzone22.lock /tmp/captiveportalzone22.lock /tmp/captiveportaldbcpzone555.lock /tmp/captiveportaldbzone999.lock /tmp/captiveportalzone33.lock /tmp/captiveportaldbcpzone666.lock /tmp/captiveportalrulesdn.lock /tmp/captiveportalzone999.lock # ls /tmp/rcprunecaptiveportal*.lock /tmp/rcprunecaptiveportalcpzone555.lock /tmp/rcprunecaptiveportaldbzone11.lock /tmp/rcprunecaptiveportalzone11.lock /tmp/rcprunecaptiveportalcpzone666.lock /tmp/rcprunecaptiveportaldbzone22.lock /tmp/rcprunecaptiveportalzone22.lock /tmp/rcprunecaptiveportaldbcpzone555.lock /tmp/rcprunecaptiveportaldbzone999.lock /tmp/rcprunecaptiveportalzone33.lock /tmp/rcprunecaptiveportaldbcpzone666.lock /tmp/rcprunecaptiveportalrulesdn.lock /tmp/rcprunecaptiveportalzone999.lock
something wrong with unlock()
see also #10891
Updated by Marcos M over 2 years ago
- Status changed from New to Resolved
- Release Notes changed from Default to Force Exclusion
Tested on latest snap - I'm not seeing this error in any logs, nor the extra files.
Actions