Hard time limit exceeded for sentry.tasks.store.preprocess_event[......

304 views
Skip to first unread message

Jakub Kubień

unread,
Jun 16, 2016, 4:50:10 AM6/16/16
to sentry

Hi there.


I see a lot of this messages


Hard time limit (65s) exceeded for sentry.tasks.store.preprocess_event[......


and it looks like the worker die when this report is generated. Main concern is that i cant see some events that i summon for testing. They are lost and as i am newbie itno Sentry i dont know sure this is the case. Can you explain me further tasks.store.preprocess_event or this certain issue?

David Cramer

unread,
Jun 17, 2016, 3:54:43 AM6/17/16
to gets...@googlegroups.com, Jakub Kubień
There are likely soft timeouts somewhere, but unfortunately there’s numerous reasons why this might happen. I would double check your connection settings from the worker machine to make sure its not something obviously like bad network.
--
You received this message because you are subscribed to the Google Groups "sentry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to getsentry+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jakub Kubień

unread,
Jun 17, 2016, 4:49:25 AM6/17/16
to sentry, keca...@gmail.com
So it might happen when worker is trying to get additional data over the network? It is possible, because i am running sentry as POC on corporate network and now i am figuring out hot to enable Kerberos/SPNEGO for Sentry. I am thinking about some kind of proxy that will provide auth metadata for all requests made by sentry. What are you think about it and what proxy SW do you recommend ?

David Cramer

unread,
Jun 17, 2016, 6:29:32 PM6/17/16
to gets...@googlegroups.com, Jakub Kubień, keca...@gmail.com
The gist is there’s a lot of reasons this can happen. You’ll have to debug it.

Alternatively if you pay us a lot of money we’re happy to help, but in a typical setup there’s no reason this would be happen as things are extremely fast outside of e.g. JS source processing.
Reply all
Reply to author
Forward
0 new messages