Better stack/error tracing

[lianna-blanca]

We have frequently had an issue in which queued jobs break but do not give us enough information to trace the error.

For example:

[ERROR] No current controller available in /var/www/mysite/releases/3eb2e804b2209d2b9b6d5880414ba25caf2e399b/vendor/silverstripe/framework/src/Control/Controller.php at line 524 {"exception":"[object] (Exception(code: 512): No current controller available in /var/www/mysite/releases/3eb2e804b2209d2b9b6d5880414ba25caf2e399b/vendor/silverstripe/framework/src/Control/Controller.php at line 524 at /var/www/mysite/releases/3eb2e804b2209d2b9b6d5880414ba25caf2e399b/vendor/symbiote/silverstripe-queuedjobs/src/Services/JobErrorHandler.php:41)"} []

This ⬆ error has happened many times, and has been caused by several different circumstances, some of which we still haven't been able to trace.

A more detailed stack/error trace in the error messages, for this and similar issues, would be extremely helpful for future debugging.

Related

• No current controller when indexing for search silverstripe-elemental#1338

[GuySartorelli]

Hi,
Thanks for reporting this. Please use the issue templates (either "Bug Report" or "Feature Request") when creating issues.

Please provide information about how to reproduce this problem and what version it was.

[lianna-blanca]

Hi @GuySartorelli I apologise - I used the bug report template initially, but the step of how to reproduce it is not something I can provide because it happens in multiple circumstances, on mulitple project sites, and we haven't been able to identify the cause, let alone reproduce it.

As to the versions, this happens on 5.2.0 for multiple sites.

[GuySartorelli]

Part of the purpose of the template is to discourage reporting bugs that can't be reproduced - because if it can't be reproduced there's not really anything we can do about it, so the issue will just sit around in the tracker forever.

If there's any time sensitivity for this, I'll be happy to help chase down the root cause if I'm able to reproduce locally in the project you're experiencing this in (contact me on slack) - but in the meantime without any way to reproduce this we won't be able to fix it.

[blueo]

Just linking silverstripe/silverstripe-elemental#1338 here as a related issue (has some steps to reproduce)