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 #8734] startup.log broken when the DB schema needs an update #2752

Closed
icinga-migration opened this issue Mar 13, 2015 · 6 comments
Labels
bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

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

Created by seferovic on 2015-03-13 10:26:09 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-03-20 11:30:00 +00:00)
Target Version: 2.3.3
Last Update: 2015-03-20 11:30:09 +00:00 (in Redmine)

Icinga Version: r2.2.3
Backport?: Already backported
Include in Changelog: 1

I updated my Icinga 2.2.x to 2.3.2 and restarted the maschine. Since I was not aware of a DB schema update I simply started Icinga2 and took a look in the startup.log!

icinga2 --version
icinga2 - The Icinga 2 network monitoring daemon (version: v2.3.2)

startup.log

[2015-03-13 11:15:08 +0100] information/ConfigItem: Checked 2 HostGroup(s).
[2015-03-13 11:15:08 +0100] information/ConfigItem: Checked 3 ServiceGroup(s).
[2015-03-13 11:15:08 +0100] information/Co

I was expecting to find the same or similar information in startup.log like the one in icinga2.log

[2015-03-13 11:24:46 +0100] information/ConfigItem: Activated all objects.
[2015-03-13 11:24:46 +0100] critical/IdoMysqlConnection: Schema version '1.12.0' does not match the required version '1.13.0'! Please check the upgrade documentation.
Context:
        (0) Reconnecting to MySQL IDO database 'ido-mysql'

Changesets

2015-03-20 11:28:43 +00:00 by (unknown) 76b0c6d

Flush stderr in Application::Exit

fixes #8734

2015-03-20 11:28:52 +00:00 by (unknown) 4e680e6

Flush stderr in Application::Exit

fixes #8734
@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-03-13 10:39:42 +00:00

seferovic wrote:

Since I was not aware of a DB schema update

That one is easy: read the changelog and the announcements. We keep that there for that very reason.

The other thing is ugly and most likely caused by the quickfix in 2.3.2.

@icinga-migration
Copy link
Author

Updated by seferovic on 2015-03-13 12:02:25 +00:00

I was so eager to test the new version of Icinga2 and started the update before I could open up the doc on the other screen. Doc looks much better now. Thx :)

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-03-19 09:48:03 +00:00

  • Category set to libbase
  • Target Version set to 2.3.3

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-03-20 11:29:27 +00:00

  • Status changed from New to Assigned
  • Assigned to set to gbeutner
  • Estimated Hours set to 1

@icinga-migration
Copy link
Author

Updated by Anonymous on 2015-03-20 11:30:00 +00:00

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

Applied in changeset 76b0c6d.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-03-20 11:30:09 +00:00

  • Backport? changed from TBD to Yes

@icinga-migration icinga-migration added bug Something isn't working libbase labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.3.3 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant