Next 502 error may be a doozy.

[Robbie]

Hi all, I just wanted to let you all know the next time we have a 502 error, it may be a longer one than usual. We're still not 100% sure whats causing it, usually when it happens, I just restart the service, but this time, the host wants me to leave it down so they can log in and evaluate the actual broken condition. This means the downtime will be a little extended compared to usual. I'm hoping it won't take too long to figure out, and I'm hoping it won't happen at a time when I'm not awake to let them know about it.

Anyways, I apologize for all the hiccups, and hopefully this will work it out...we're on a faster/better server, but there's some little nuance that we haven't figured out yet, and I think it's being triggered by some broken code left behind from the search engine optimization engine we used to use.

[Robbie]

I was expecting it to happen this morning like it usually does, but I guess not...maybe later...am keeping an eye on things.

[ChickPea]

Hehe, this has got a 'watched kettle' feel to it. As soon as your attention's on something else, it'll go down.

[Jayne Cobb]

502 can be a tricky one to solve. I can think of quite a few causes off the top of my head. Hopefully it is something simple and easy to fix. Best of luck to the tech support!

[Robbie]

Its php crashing from fastcgi concurrency timed with an rsyslog close during a cron job.

Sometimes.

Lol

Posted mobile using Tapatalk

[Jayne Cobb]

its php crashing from fastcgi concurrency timed with an rsyslog close during a cron job.

Sometimes.

Lol

posted mobile using tapatalk

dem cron jobs! :p