Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #10968] Race condition when using systemd unit file #3838

Closed
icinga-migration opened this issue Jan 13, 2016 · 6 comments
Closed
Labels
bug
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Jan 13, 2016

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10968

Created by leeclemens on 2016-01-13 23:54:50 +00:00

Assignee: jflach
Status: Resolved (closed on 2016-01-14 09:13:33 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:40 +00:00 (in Redmine)

Icinga Version: 2.4.1
Backport?: Already backported
Include in Changelog: 1

I noticed on a server without mariadb.service present (or presumably another service/unit further requiring network), that icinga2.service would attempt to start before network (race) and would usually fail with critical/ApiListener: Cannot bind TCP socket for host.

Adding 'network.target' to the [Unit] After argument in the unit file resolved the race condition.

CentOS Linux release 7.2.1511 (Core)
icinga2-common-2.4.1-1.el7.centos.x86_64

Pull request:
#60

Changesets

2016-01-14 09:11:38 +00:00 by leeclemens 984eaf5

Add network.target to unit file

Icinga2 fails with 'Cannot bind TCP socket for host',
if other services requiring network.target are not installed.

Signed-off-by: Jean Flach <jean-marcel.flach@netways.de>

fixes #10968

2016-02-23 08:19:59 +00:00 by leeclemens 9ceb1d6

Add network.target to unit file

Icinga2 fails with 'Cannot bind TCP socket for host',
if other services requiring network.target are not installed.

Signed-off-by: Jean Flach <jean-marcel.flach@netways.de>

fixes #10968
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 14, 2016

Updated by jflach on 2016-01-14 09:13:26 +00:00

  • Target Version set to 2.5.0
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 14, 2016

Updated by leeclemens on 2016-01-14 09:13:33 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset 984eaf5.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 14, 2016

Updated by mfriedrich on 2016-01-14 09:27:13 +00:00

  • Assigned to set to jflach
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 14, 2016

Updated by seferovic on 2016-01-14 13:34:53 +00:00

Would it be possible to get this fix into 2.4.2? Thx!

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 14, 2016

Updated by mfriedrich on 2016-01-14 13:37:40 +00:00

  • Target Version changed from 2.5.0 to 2.4.2
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 09:58:40 +00:00

  • Backport? changed from Not yet backported to Already backported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.