Heroku - the last audit failed

I deployed to the free tier of Heroku, installation completed and I created a new project according to the docs. Any audit I try fails with ‘The last audit failed’.

This is what I get from the Heroku worker logs:

2019-10-27T15:47:35.68956+00:00 heroku[worker.1]: Starting process with command /bin/sh -c ./start_celery.sh 2019-10-27T15:47:36.266342+00:00 heroku[worker.1]: State changed from starting to up 2019-10-27T15:47:37.368018+00:00 app[worker.1]: curl: (3) URL using bad/illegal format or missing URL 2019-10-27T15:47:38.852602+00:00 app[worker.1]: [2019-10-27 15:47:38,852: INFO/Beat] beat: Starting… 2019-10-27T15:47:38.855018+00:00 app[worker.1]: [2019-10-27 15:47:38,854: INFO/Beat] Writing entries… 2019-10-27T15:47:39.082199+00:00 app[worker.1]: [2019-10-27 15:47:39,080: INFO/MainProcess] Connected to redis://h:**@ec2-52-18-237-146.eu-west-1.compute.amazonaws.com:7329// 2019-10-27T15:47:39.095578+00:00 app[worker.1]: [2019-10-27 15:47:39,095: INFO/MainProcess] mingle: searching for neighbors 2019-10-27T15:47:39.882045+00:00 app[worker.1]: [2019-10-27 15:47:39,881: INFO/Beat] Writing entries… 2019-10-27T15:47:39.9033+00:00 app[worker.1]: [2019-10-27 15:47:39,903: INFO/Beat] Scheduler: Sending due task One shot update all configurations (audits.tasks.get_wpt_audit_configurations) 2019-10-27T15:47:40.122999+00:00 app[worker.1]: [2019-10-27 15:47:40,122: INFO/MainProcess] mingle: all alone 2019-10-27T18:24:49.532125+00:00 app[worker.1]: [2019-10-27 18:24:49,531: INFO/MainProcess] mingle: all alone 2019-10-27T18:24:49.561495+00:00 app[worker.1]: [2019-10-27 18:24:49,561: INFO/MainProcess] celery@8272834f-a28a-4468-abab-746b4a485da4 ready. 2019-10-27T18:24:53.29708+00:00 app[worker.1]: [2019-10-27 18:24:53,296: INFO/Beat] Writing entries… 2019-10-27T18:25:17.877172+00:00 app[worker.1]: [2019-10-27 18:25:17,876: INFO/MainProcess] Received task: audits.tasks.request_audit[3d77d34e-a82f-44e7-896a-4d2def0bfc29]
2019-10-27T18:25:17.890522+00:00 app[worker.1]: [2019-10-27 18:25:17,890: INFO/MainProcess] Received task: audits.tasks.request_audit[f2204075-d67e-4ef2-8bf8-73c927ed5ed7]
2019-10-27T18:25:17.897282+00:00 app[worker.1]: [2019-10-27 18:25:17,897: INFO/MainProcess] Received task: audits.tasks.request_audit[5a0e3787-ff36-4df8-92d2-335c1db45e00]
2019-10-27T18:25:18.154933+00:00 app[worker.1]: [2019-10-27 18:25:18,154: INFO/ForkPoolWorker-4] Task audits.tasks.request_audit[5a0e3787-ff36-4df8-92d2-335c1db45e00] succeeded in 0.2557556260144338s: None 2019-10-27T18:25:18.161287+00:00 app[worker.1]: [2019-10-27 18:25:18,160: INFO/ForkPoolWorker-3] Task audits.tasks.request_audit[f2204075-d67e-4ef2-8bf8-73c927ed5ed7] succeeded in 0.2693798690161202s: None 2019-10-27T18:25:18.162534+00:00 app[worker.1]: [2019-10-27 18:25:18,162: INFO/ForkPoolWorker-2] Task audits.tasks.request_audit[3d77d34e-a82f-44e7-896a-4d2def0bfc29] succeeded in 0.2837241839733906s: None

[mbinkhorst]

Yes it was! I double-clicked the code and of-course it splits at the period.

[phacks]

Hi @mbinkhorst! Sorry to hear that—there’s a way to try and get a little bit more information about why the audit failed:

1. Login to the admin interface
2. Click on Audits
3. Select one of the audits that failed (if all audits failed, the most recent should do)
4. Scrolling down all the way to the bottom, you should see the WPT Results User URL field (see screenshot below)
5. Copy and paste that link in a new browser tab, this will hopefully display either the results (if the WPT audit went OK but there was a problem in Falco’s parsing of results) or a WPT error page with a little bit more details on the problem

Could you have a look and see if you can get additional info on why the audits failed?

As a side note, I’ll be creating an issue to add a new doc section for troubleshooting failed audits 😃