Project

General

Profile

Actions

Bug #12651

closed

``nginx`` logs an error that the port is already in use when restarting Captive Portal services

Added by Viktor Gurov 5 months ago. Updated 18 days ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Captive Portal
Target version:
Start date:
Due date:
% Done:

0%

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)


Related issues

Related to Todo #13100: Captive Portal ipfw->pf transitionIn ProgressViktor Gurov

Actions
Actions #2

Updated by Jim Pingle 5 months ago

  • Assignee set to Viktor Gurov
  • Target version set to CE-Next
  • Plus Target Version set to 22.05
Actions #3

Updated by A FL 4 months ago

possibly related to #10159

Actions #4

Updated by Viktor Gurov 26 days ago

  • Related to Todo #13100: Captive Portal ipfw->pf transition added
Actions #5

Updated by Viktor Gurov 26 days ago

  • Target version changed from CE-Next to 2.7.0
Actions #7

Updated by Jim Pingle 18 days 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.

Actions

Also available in: Atom PDF