Bug #21100
closed
When cf-serverd starts it can kill an unrelated process
Added by Benoît PECCATTE over 2 years ago.
Updated about 2 years ago.
Description
This is due to a race condition in the lock handling:
- cfengine interprocess locks are stored in lmdb
- when cf-serverd starts, it holds a lock and releases it on stop
- when it restarts, it checks this lock and if it expired, it tries to kill the owning process
- sometime with pid turnover, it can be possible that this pid has been reused by another process in the meantime
We should add a check to make sure we only ever kill cfengine processes
- Target version changed from 6.2.14 to 6.1.20
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2597
- Target version changed from 6.1.20 to 6.1.21
- Target version changed from 6.1.21 to old 6.1 issues to relocate
- Pull Request changed from https://github.com/Normation/rudder-packages/pull/2597 to https://github.com/Normation/rudder-packages/pull/2665
- Target version changed from old 6.1 issues to relocate to 6.2.20
- Regression set to No
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.20, 7.1.7 and 7.2.1 which were released today.
Also available in: Atom
PDF