Invalid JSON response after upgraded Ubuntu from 18.04 to 20.04

38 views
Skip to first unread message

Luke Robertson

unread,
May 2, 2022, 3:51:40 PM5/2/22
to munkireport
I am on MunkiReport 3.1.1.3364. We upgraded the server from 16 to 18.04 LTS with no issues. We now upgraded Ubuntu to 20.04 and we had a couple of issues. SQL wasn't working but I got that working again. Now I can access the reports and see the dashboard. 

However, any time I open up a report, it gives this error message

2022-05-02_12h50_20.png


I am on PHP 7.4.3. I also get this error when going to Admin > Database

SQLSTATE[42000]: Syntax error or access violation: 1231 Variable 'sql_mode' can't be set to the value of 'NO_AUTO_CREATE_USER' (SQL: select * from information_schema.tables where table_schema = munkireport and table_name = migrations)

Xavier Xavier

unread,
May 2, 2022, 3:54:34 PM5/2/22
to munki...@googlegroups.com
v3.1.1 is old. 

MunkiReport 5.7.1 is the latest

Required PHP 7.4 which you have. Clients would need new Python2.7 installer (see MR GitHub) and new client agent deployed

-x

On May 2, 2022, at 12:51 PM, Luke Robertson <lrobe...@srvusd.net> wrote:

I am on MunkiReport 3.1.1.3364. We upgraded the server from 16 to 18.04 LTS with no issues. We now upgraded Ubuntu to 20.04 and we had a couple of issues. SQL wasn't working but I got that working again. Now I can access the reports and see the dashboard. 

However, any time I open up a report, it gives this error message

<2022-05-02_12h50_20.png>


I am on PHP 7.4.3. I also get this error when going to Admin > Database

SQLSTATE[42000]: Syntax error or access violation: 1231 Variable 'sql_mode' can't be set to the value of 'NO_AUTO_CREATE_USER' (SQL: select * from information_schema.tables where table_schema = munkireport and table_name = migrations)

Statement of Confidentiality: The contents of this e-mail message and any attachments are intended solely for the addressee. The information may also be confidential and/or legally privileged. This transmission is sent for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction, or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail and delete this message and its attachments, if any.

E-mail is covered by the Electronic Communications Privacy Act, 18 USC SS 2510-2521 and is legally privileged.


--
You received this message because you are subscribed to the Google Groups "munkireport" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munkireport...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munkireport/2dc4fe7b-60ee-4b07-a73b-844cedcb32e3n%40googlegroups.com.
<2022-05-02_12h50_20.png>

Luke Robertson

unread,
May 2, 2022, 4:31:03 PM5/2/22
to munkireport
Yes, I did see that there are much newer versions.  I have no idea how to update the reports to the latest version. Also, isn't the munkireports just pulling info from the database? I don't understand how updating clients would fix the error message shown. This worked before upgrading SQL to 8 and php to 7.4
Reply all
Reply to author
Forward
0 new messages