EVERY task queue fails since 1st Feb 2016

133 views
Skip to first unread message

Andrea De Togni

unread,
Feb 3, 2016, 4:16:38 AM2/3/16
to Google App Engine
Hi

I'm using an app that does a lot of background processing with task queues (cron jobs). It's working fine since more than an year
with close to zero maintenance.
I'm using the PHPGS Library and have NOT updated it

Since 1st of Feb ALL of the tasks fails with the following errors: anyone has an idea? Thansk


0.1.0.1 - - [02/Feb/2016:23:14:00 -0800] "GET /tasks/add_headers_set_public.php?day=5 HTTP/1.1" 200 25 - "AppEngine-Google; (+http://code.google.com/appengine)" "appnexus-logfiles-groupm.appspot.com" ms=19787 cpu_ms=669 cpm_usd=1.70432e-7 instance=00c61b117c905876d64b20991b6bf0c755de83 app_engine_release=1.9.32 trace_id=5d7fd81b00a4e5c034d587ea1d3bfdd1
{
metadata:{…}
protoPayload:{…}
insertId:"2016-02-02|23:14:20.837140-08|10.106.174.66|-670402932"
httpRequest:{…}
operation:{…}
}
08:14:00.262
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:06.823
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:06.862
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.045
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.176
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.441
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.532
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.635
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.789
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:07.918
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.018
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.189
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.275
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.408
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.589
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.803
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:08.918
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:09.021
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:09.105
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile
08:14:09.232
Unsupported SSL context options are set. The following options are present, but have been ignored: cafile

Marcial Roman

unread,
Feb 3, 2016, 4:31:31 AM2/3/16
to Google App Engine
I believe this comment is quite relevant in existing Issue 12073: SSL Error in every call that GAE application makes to a secure server


...

Andrea De Togni

unread,
Feb 3, 2016, 4:35:46 AM2/3/16
to Google App Engine
Hi Marcial

thank you. I've had this issue intermittently in the past months and I was able to workaround it. However, since the 1st, it happens constantly and every single time, therefore the app does not work at all.

Nick (Cloud Platform Support)

unread,
Feb 3, 2016, 7:32:49 PM2/3/16
to Google App Engine
Hey Andrea,

If you believe you're affected by a production issue related to an issue in the platform, you should make a formal issue report in the Public Issue Tracker. Google Groups is meant more for general discussion of the platform and services, and it seems that while people in the Groups community could have good input on the issue, the best way to get a concrete investigation would be to post in the Public Issue Tracker. When you do so, be sure to set the label "Type-Production" on the issue so that it won't be visible to the public, and include as much information as possible to allow us to either investigate or reproduce the behaviour.

Regards,

Nick

Andrea De Togni

unread,
Feb 8, 2016, 11:37:08 AM2/8/16
to Google App Engine
It has solved by itself...I don't know what happened...
...

Nick (Cloud Platform Support)

unread,
Feb 8, 2016, 5:17:56 PM2/8/16
to Google App Engine
Hey Andrea,

That's great news. In future, feel free to make a posting to the Public Issue Tracker, as mentioned. 

Best wishes for your future development,

Nick
Reply all
Reply to author
Forward
0 new messages