I think this is new…today I updated my freePBX 15 server through the web-ui and now when I do a fwconsole restart I see this:
Running FreePBX startup...
Running Asterisk pre from Firewall module
Running Asterisk pre from Sysadmin module
Running Sysadmin Hooks
Restarting fail2ban
fail2ban Restarted
Updating License Information for 1xxxxxxxxx
Checking Vpn server
Starting Asterisk...
[============================] 1 sec
Asterisk Started
Running Asterisk post from Core module
Running Asterisk post from Pagingpro module
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'link' cannot be null
[root@pbx ~]#
Broadcast message from [email protected] (Mon Jul 26 18:47:20 2021):
Firewall service now starting.
Any ideas? My webbrowser crashed during the update process.
EDIT: I also saw the sha1 error with Zulu during the update…by the way
I think I once registered a new version of DPMA with it…and later found out that it wasn’t necessary to register.
But isn’t the error related to Zulu with missing link entries in one table?
Does anybody know, who is complaining about the empty table asterisk.zulu_interactions_stream_links? Which module is it? Maybe I can downgrade it…
Zulu is already disabled…so it must be some other module…am I wrong?
Maybe others have the same problem, but havent done a “fwconsole restart” since the last updates!
EDIT: The error above means “You are trying to store a null value in a NOT NULL column.”…so which module is doing it?
So it is obviously zulu but something somewhere is calling it direct (which is always dumb for this reason) I can’t grep it out because it is in an obfuscated module
ok…it was the notifications table. I changed the link-column and allowed NULL. Now the error during fwconsole restart is gone.
In the notifications table there are two new entries with link-value NULL and they belong to the paging pro module. Interesting…
Don’t worry about the tampered file. I have to adjust CID-Superfecta to work with Umlaute and Herold.at
EDIT: My working hypothesis is that there is a bug in the newest version of the Dashboard or whatever handles the notifications…or it is the paging-pro module, which reports in the wrong format
By the way…no paging groups use any calendar. So I don’t know where the message comes from.
Still dont know if this is unique to my freePBX 15 server. If notifications stop working on other machines (especially the page pro ones), we would know…
EDIT: It might be related to the fact that I upgraded this machine from freePBX 14 to 15. Another possibility is that during the recent module updates something went wrong. Everything seems to work so far…