Zammad Websocket overflows the system log

Technical assistance
1

Infos

  • Used Zammad version: 5.3.0-1670492123.7c45d087.bionic
  • Used Zammad installation type: Unknown but not Docker
  • Operating system: Ubuntu 18.04 LTS / 64 bit
  • Browser + version: Irrelevant

Behavior

The system log syslog in /var/log is overflowing with zammad-websocket-1.service messages. Within a few days, the file reaches >200 GB in size. Due to the intensive logging the system gets overloaded, is slow on the one hand and on the other hand crashes every few days with HTTP error 500. After a reboot the HTTP error 500 is gone, but the log is still filled.

Entries are created at any time, regardless of whether users are using Zammad or not. The crash regularly occurs when not in use between 11 pm and 6 am.

The error messages are as follows and repeat tens of thousands of times per second:

Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: ajax clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: websocket clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: ajax clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: websocket clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: ajax clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: websocket clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: ajax clients: 0
Jan 29 06:29:25 www2 zammad-websocket-1.service[220]: 2023-01-29T06:29:24Z:client(-) Status: websocket clients: 0

How can the entries be turned off? Or is there an error or wrong configuration that causes the entries?

2

Hello again. Does nobody have an idea or can support us?

3

Not sure how much traffic your instance gets but I have extremely huge instances under my control with like 100 agents + that do not behave that way.

Ensure that your environment is a production one - as you can’t tell what installation method you have, I also am unable to provide you better links and hints rather than: Welcome to Zammad’s documentation! — Zammad documentation

By default Zammad does not log to STDOUT (syslog) - there’s a switch to disable that behavior, see:
https://docs.zammad.org/en/latest/appendix/configure-env-vars.html

This would allow you to actually logrotate based on file sizes as a workaround.

4

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.