Actions
Bug #12651
closed
VG
VG
``nginx`` logs an error that the port is already in use when restarting Captive Portal services
Bug #12651:
``nginx`` logs an error that the port is already in use when restarting Captive Portal services
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:
Description
After restarting Captive Portal on the Status / Services page or via clicking the restart icon, an error occurs:
nginx: 2021/12/29 20:53:50 [emerg] 86449#100550: bind() to 0.0.0.0:8002 failed (48: Address already in use) Dec 29 20:53:50 pfcp nginx: 2021/12/29 20:53:50 [emerg] 86449#100550: bind() to 0.0.0.0:8002 failed (48: Address already in use)
VG Updated by Viktor Gurov over 4 years ago
JP Updated by Jim Pingle over 4 years ago
- Assignee set to Viktor Gurov
- Target version set to CE-Next
- Plus Target Version set to 22.05
AF Updated by A FL over 4 years ago
possibly related to #10159
VG Updated by Viktor Gurov over 4 years ago
- Related to Todo #13100: Transition Captive Portal from IPFW to PF added
VG Updated by Viktor Gurov over 4 years ago
- Target version changed from CE-Next to 2.7.0
VG Updated by Viktor Gurov over 4 years ago
- Status changed from New to Feedback
JP Updated by Jim Pingle over 4 years ago
- Subject changed from nginx bind error on captive portal restart to ``nginx`` logs an error that the port is already in use when restarting Captive Portal services
- Status changed from Feedback to Closed
No bind error in logs when restarting a portal instance on current snapshots.
JP Updated by Jim Pingle over 4 years ago
- % Done changed from 0 to 100
Actions