You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was getting errors that the database could not save data to the database.
I figured out that even though I did the latest init.sql I was still missing the api_host column.
Trying to use the 01-migration.sql produced this error.
ERROR 1101 (42000) at line 1: BLOB/TEXT column 'api_host' can't have a default value
So, I removed the default value from the schema and it now works!
I had to add $e->getMessage() to the db commit message so I could see that the column was missing. I think the api_host column should be in the init.sql rather than having to run upgrade scripts on initial installs????
Neat module and I hope to learn more about it now that it is working:-)
The text was updated successfully, but these errors were encountered:
commit b83545d provides a default value for api_host which apparently only works for postgresql. The intentation of that default value was to keep the up-to-that-point default value (localhost) in place. We could drop that default value and provide a UPDATE [...] SET api_host = 'localhost' WHERE api_host IS NULL directly after adding the column.
I wasn't able to get this plugin running on latest debian with mysql. So i reinstalled icinga2 using postgres and it still does not work... Can you please make sure that it installs on fresh debian install with icinga2?
I was getting errors that the database could not save data to the database.
I figured out that even though I did the latest init.sql I was still missing the api_host column.
Trying to use the 01-migration.sql produced this error.
ERROR 1101 (42000) at line 1: BLOB/TEXT column 'api_host' can't have a default value
So, I removed the default value from the schema and it now works!
I had to add $e->getMessage() to the db commit message so I could see that the column was missing. I think the api_host column should be in the init.sql rather than having to run upgrade scripts on initial installs????
Neat module and I hope to learn more about it now that it is working:-)
The text was updated successfully, but these errors were encountered: