Bug #13982
closed
cf-serverd may listen on port 8080 preventing rudder-jetty from running
Added by Nicolas CHARLES almost 6 years ago.
Updated almost 6 years ago.
Category:
Server components
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Description
Add a check to prevent rudder agent component from listening on port 8080, and preventing rudder-jetty from starting
sometimes, cf-serverd or cf-execd listen on port 8080 ,and rudder-jetty can't start
we hsould have a check in rudder agent health to detect this case and restore in a proper state all services
- Subject changed from Add a check to prevent rudder agent component from listening on port 8080, and preventing rudder-jetty from starting to cf-serverd may listen on port 8080 preventing rudder-jetty from running
- Description updated (diff)
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Small
- Priority changed from 0 to 67
ss -lnpt | grep cf-execd && service restart rudder-agent
- Effort required changed from Small to Very Small
- Priority changed from 67 to 80
The impacted services were at least:
- cf-execd
- cf-serverd.
It is MOST likelly:
- cf-serverd is stopped for something,
- rudder webapp start a generation and does a SIGHUP/ SIGKILL or a restart if stopped => cf-serverd is restarted as a child of the webapp, inheriting the webapp files/socket (even if we tell the child to not have thme, because shell and unix)
- choas ensues.
This is solved in 5.0 because the agent use systemd and the restart is clean in that case.
Pre-5.0, implement the health check.
- Target version changed from 4.3.8 to 4.3.9
- Assignee set to Benoît PECCATTE
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/201
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.9 and 5.0.5 which were released today.
Changelog
Changelog
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by