HUGE qcallback-events_err.log is Growing out of Control!

General Help
1

The qcallback-events_err.log file is growing huge (30 gigabytes for this single file) and filling up my hard drive, causing the system to send me storage alerts. All that the log contains, is thousands and thousands of lines like these, repeated over and over:

2022-07-03 09:06 -07:00: (node:4515) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.

2022-07-03 09:06 -07:00: Timeout duration was set to 1.

2022-07-03 09:06 -07:00: (node:4515) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.

2022-07-03 09:06 -07:00: Timeout duration was set to 1.

2022-07-03 09:06 -07:00: (node:4515) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.

2022-07-03 09:06 -07:00: Timeout duration was set to 1.

2022-07-03 09:06 -07:00: (node:4515) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.

2022-07-03 09:06 -07:00: Timeout duration was set to 1.

2022-07-03 09:06 -07:00: (node:4515) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer.

2022-07-03 09:06 -07:00: Timeout duration was set to 1.

How can I fix this? Thanks!

2

Have you bought the vqplus commercial module and using queue callback? If not, easiest to just disable the module with

fwconsole ma uninstall vqplus

It may be necessary to reset the daemons and restart asterisk with

fwconsole restart
3

Yes we have purchased the vqplus commercial module and have queue callback set up.

So it would be good to keep that functionality working.

Thanks!

4

Open a support ticket, I’ve not seen this before.