Troubleshooting

Enable debug mode

To get Munkireport to be more verbose about errors, add the following line to .env

DEBUG=TRUE

Blank listings page

After an upgrade some/all listings pages are empty. This could be caused by an upgrade to the datatables javascript framework. Clear local storage to fix the caching issue.

Open a javascript console in your browser and type:

localStorage.clear()

Another option is to hold ⇧ (Shift) and click reload.

Cannot write to Sqlite DB

After install and running the migrate script, the DB connection is still throwing write-errors.

Check in the munkireport interface that the database is writeable (Admin/Show System Status) If it is showing as connectable but not writeable, confirm that the user running the webserver, has write-access to the file. If write-access is currently set for the user, check if SELinux is turned on and alerting for the www service accessing the db.sqlite file. If the issue is SELinux, either disable it altogether, to confirm functionality, or add rules to allow the service to access the db file.

Clients Not Full Updating

If the clients are not updating all the modules, you can check the output of /usr/local/munkireport/munkireport-runner or the error logs of your web server (apache, nginx, IIS, etc). If the following is found on the client:

Sending items (6MB)
a:1:{s:5:"error";s:16:"No items in POST";}

It is most likely the post_max_size setup in the php.ini file.

You may end up with something like this in the server logs:

2020/02/10 08:56:48 [error] 678#678: *31036651 FastCGI sent in stderr: "PHP message: PHP Warning:  Unknown: POST Content-Length of 9219851 bytes exceeds the limit of 8388608 bytes in Unknown on line 0" while reading response header from upstream, client: ip_address, server: domain.edu, request: "POST /report/index.php?/report/check_in HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.2-fpm.sock:", host: "domain.edu"

Update the php.ini file and check that it uploads completely.