Hi, got my Lucee instance working fine, for a few days, then this morning
after updating to the new security fix, I started to get 502 Proxy errors.
I’m running Lucee 5, Linux 64bit, Apache/Tomcat
Seemed to be going swimmingly until then., may be a coincidence of course.
I am not sure where to start looking for this, but currently site down,
tried all the usual, httpd/tomcat/lucee and full server restart but same
deal, will open a page then start throwing 502 errors.
Had reasonably high traffic moments before this, not got anything
particularly new or popular posted, so I’m stumped.
Any ideas where to start?
Thanks
I have. no differenceOn Thursday, 1 September 2016 14:44:46 UTC+1, Tom Chiverton wrote:
It sounds like you have not tried undoing the update ?
Tom
Very peculiar, I fired up yesterdays instance and it was fine, until I
tried to update a particular item via our CMS, might be something to do
with a datatype and the Mysql driver or connection, any time I try to edit
that item, its borking a 502 and the server load goes way up.
Thing is, I’ve deleted the item, re-entered it and the same again.
Not had this before, same remote DB server, same code etc. have to get the
magnifying glass out and go through it.On Thursday, 1 September 2016 15:00:17 UTC+1, Nick Batt wrote:
I have. no difference
On Thursday, 1 September 2016 14:44:46 UTC+1, Tom Chiverton wrote:
It sounds like you have not tried undoing the update ?
Tom
It sounds like you have not tried undoing the update ?
Tom
Found what it was:
I was using a FileExists(myS3mapping) to see if a thumbnail had been
created. it was returning some form of XML data that Lucee didnt
understand. In our previous production server, this was not an issue:
Specific error:
“ERROR”,“http-nio-8888-exec-10”,“09/02/2016”,“12:12:26”,“”,";Failed to
sanitize XML document destined for handler class
org.jets3t.service.impl.rest.XmlResponsesSaxParser$ListBucketHandler;lucee.runtime.exp.NativeException:
Failed to sanitize XML document destined for handler class
org.jets3t.service.impl.rest.XmlResponsesSaxParser$ListBucketHandler
Hope this helps someone.
.On Thursday, 1 September 2016 16:25:31 UTC+1, Nick Batt wrote:
Very peculiar, I fired up yesterdays instance and it was fine, until I
tried to update a particular item via our CMS, might be something to do
with a datatype and the Mysql driver or connection, any time I try to edit
that item, its borking a 502 and the server load goes way up.
Thing is, I’ve deleted the item, re-entered it and the same again.
Not had this before, same remote DB server, same code etc. have to get the
magnifying glass out and go through it.
On Thursday, 1 September 2016 15:00:17 UTC+1, Nick Batt wrote:
I have. no difference
On Thursday, 1 September 2016 14:44:46 UTC+1, Tom Chiverton wrote:
It sounds like you have not tried undoing the update ?
Tom