This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
[dev.icinga.com #2978] Postgresql: Datetime field overflow on host and servicestatus cronks #867
Labels
Comments
Updated by mfrosch on 2012-08-13 14:28:34 +00:00 This bug is introduced by the changes in #2736 Commits: Problem: '0000-00-00 00:00:00' is a not supported timestamp in Postgres. The database schema sets '1970-01-01 00:00:00' as default in pgsql. I suggest the following changes:
This works with MySQL and PgSQL, tested that. The patch is required for Icinga Web 1.7.2 to work with a Pgsql IDO. |
Updated by mhein on 2012-08-13 14:54:08 +00:00
Applied in changeset 7940ba4. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2978
Created by mfrosch on 2012-08-13 13:24:24 +00:00
Assignee: (none)
Status: Resolved (closed on 2012-08-13 14:54:08 +00:00)
Target Version: (none)
Last Update: 2012-08-13 14:54:08 +00:00 (in Redmine)
I have some sql errors with cronks that use the hoststatus or servicestatus table.
Here are 2 examples:
http://mf-deb-sid/icinga-web/modules/cronks/viewproc/icinga-service-template/json
http://mf-deb-sid/icinga-web/modules/cronks/viewproc/icinga-host-template/json
Changesets
2012-08-13 14:51:20 +00:00 by mhein 1a5552c
2012-08-13 14:52:12 +00:00 by mhein 7940ba4
The text was updated successfully, but these errors were encountered: