Grommunio - Zcore Log in Admin GUI crashes when trying to open

Mister2

I have 2 VM's running the Grommunio ISO Appliance. I updated one yesterday morning and the other one yesterday evening. The one updated in the morning all works OK, logs included via the Admnin GUI. However, the instance updated yesterday evening included 2 additional updates:-

v | sle-update | kernel-default | 6.4.0-150600.23.78.1 | 6.4.0-150600.23.81.3 | x86_64 v | sle-update | mdadm | 4.3-150600.3.14.2 | 4.3+33.g22c212a5-150600.3.17.2 | x86_64

Since these 2 updates are the only differences in the two Grommunio Instances I believe one of these files is responsible for the crash of the Groomunio Zcore log in the Admin GUI.

The Admin API log show the following output immediately after the crash

[2025-12-18 14:47:31.042292]: [ERROR] (grommunio Admin API) Traceback (most recent call last): [2025-12-18 14:47:31.042292]: File "/usr/lib/python3.11/site-packages/flask/app.py", line 1484, in full_dispatch_request [2025-12-18 14:47:31.042292]: rv = self.dispatch_request() [2025-12-18 14:47:31.042292]: File "/usr/lib/python3.11/site-packages/flask/app.py", line 1469, in dispatch_request [2025-12-18 14:47:31.042292]: return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) [2025-12-18 14:47:31.042292]: File "/usr/share/grommunio-admin-api/api/core.py", line 204, in wrapper [2025-12-18 14:47:31.042292]: return call() [2025-12-18 14:47:31.042292]: File "/usr/share/grommunio-admin-api/api/core.py", line 169, in call [2025-12-18 14:47:31.042292]: ret = func(*args, **kwargs) [2025-12-18 14:47:31.042292]: File "/usr/share/grommunio-admin-api/endpoints/system/logs.py", line 35, in getLog [2025-12-18 14:47:31.042292]: return jsonify(data=LogReader.tail(log.get("format", "journald"), log["source"], n, skip, after)) [2025-12-18 14:47:31.042292]: File "/usr/lib/python3.11/site-packages/flask/json/__init__.py", line 170, in jsonify [2025-12-18 14:47:31.042292]: return current_app.json.response(*args, **kwargs) [2025-12-18 14:47:31.042292]: File "/usr/lib/python3.11/site-packages/flask/json/provider.py", line 215, in response [2025-12-18 14:47:31.042292]: f"{self.dumps(obj, **dump_args)}\n", mimetype=self.mimetype [2025-12-18 14:47:31.042292]: File "/usr/lib/python3.11/site-packages/flask/json/provider.py", line 180, in dumps [2025-12-18 14:47:31.042292]: return json.dumps(obj, **kwargs) [2025-12-18 14:47:31.042292]: File "/usr/lib64/python3.11/json/__init__.py", line 238, in dumps [2025-12-18 14:47:31.042292]: File "/usr/lib64/python3.11/json/encoder.py", line 200, in encode [2025-12-18 14:47:31.042292]: chunks = self.iterencode(o, _one_shot=True) [2025-12-18 14:47:31.042292]: File "/usr/lib64/python3.11/json/encoder.py", line 258, in iterencode [2025-12-18 14:47:31.042292]: return _iterencode(o, 0) [2025-12-18 14:47:31.042292]: File "/usr/lib/python3.11/site-packages/flask/json/provider.py", line 120, in _default [2025-12-18 14:47:31.043865]: raise TypeError(f"Object of type {type(o).__name__} is not JSON serializable") [2025-12-18 14:47:31.043865]: TypeError: Object of type bytes is not JSON serializable [2025-12-18 14:47:31.043865]: [WARNING] (grommunio Admin API) GET /api/v1/system/logs/Gromox zcore?n=100 from x.x.x.x-> 500 '{"message":"The server encountered an error while processing the request."}\n'

Hope the above helps the devs identify what might be the cause of the issue.

EDIT - Applying todays available updates (below), makes no difference to the error, so pretty sure something in the 2 files mentioned above are the cause of the issue.

All the other logs open without issue.

WalterH

This has already been discussed here in the forum; it is a known bug that has not yet been fixed.

Mister2

WalterH Is this recently as I don't seem to be able to find the post. I have been aware of the problem from around the end of October up until about 10 days ago where trying to access the logs in the Admin GUI all gave 'the server has encountered an error' issue, but this was fixed on both my appliance instances about 10 days ago. I have not had any issues accessing any of the logs in Admin GUI since about 10 days ago until last night after installing the 2 updates mention in my first post above. As I said in my first post, the instance that I have not applied the two updates on, the Gromox-zcore log is working normally still. So there definitely seems to be something caused by one or both of these updates.