welcome[bot]
commented
3 years ago :wave: Thank you for opening your first issue. I'm just an automated bot that's here to help you get the information you need quicker, so please ignore this message if it doesn't apply to your issue. If you're looking for support, you should try the Slack group by registering your email address at https://cachethq-slack.herokuapp.com. Alternatively, email support@alt-three.com for our Professional support service (please note, this a paid service.) If you're issue is with documentation, you can suggest edits by clicking the Suggest Edits link on any page, or open an issue at https://github.com/CachetHQ/Docs
jbrooksuk
Hello,
I'm experiencing an issue with Cachet 2.4 which I hope one of you might know how to fix.
There's quite a few subscribers (more than 2000) in my application, and when I create an incident that notifies subscriber, it takes a long time to process and then ends in a 504 error. The component status wasn't changed and incident didn't get created. In the logs I found that the max execution time got exceeded so I increased that, as well as nginx time out values.
After sufficiently increasing the max_execution_time all notifications seem to get sent, the incident gets created and the status gets changed, but I still end up with a 504 error while no error gets logged.
This brings me to two issues:
What could be the cause of still receiving a 504 error in this case?
What could be the cause of this request taking such a long time in the first place? I have set up Cachet with QUEUE_DRIVER=database so I'd expect messages to get queued, however this does not seem to be happening.
I'd be happy to receive any suggestions.