Forums

Hello,

After maintenance my website is not working. There are no errors shown in the errorfile... I tried to restart which takes more time the normal but it ends without an error. But... no restart is done because site doesn't respond.

I have a paid site also which works fine though?!!?

Is it because I m running Python 3.10?

I do see a 499 response on a request in the access log

GET / HTTP/1.1" 499 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36" "77.172.246.68" response-time=12.665

it is working again, thx Admin :)

Thanks for letting us know! It looks like after our system maintenance this morning, some SQLite databases were stuck in a "locked" state where processes would hang when they tried to access them. We just restarted the file locking service on the file server associated with your account, and as your site is working again now, we think that was probably the cause of the issues you were seeing.

I'm pretty sure thats correct!!

I have another (paid site) with the same problem... I resolved the problem there by doing this:

• disable the app
• download my SQLITE database to local
• upload it to PA again
• reload the app
• tried the site and all worked!!

Hope this helps you! With regards Jos

@stillhaveit -- thanks for the suggestion! That would work well to work around issues like this, as the newly-uploaded database file would be a different file (from the locking service's perspective) to the original one, so you'd be able to lock it again.

However, we believe that the underlying problem is now fixed -- if anyone is still seeing issues, please let us know.

My sites are working again, but we expect some kind of post-mortem and full disclosure of the incident, at least in my case.

Thx

Yes, absolutely. We'll be posting that to our blog.

Mine is currently not working with a connection using pyodbc to azure sqlserver. Having not changed anything my end I'm wondering if its related?

in my case odbcinst.ini for some reason had been zapped and was zero bytes long. I re-uploaded and all is well.

Glad to hear that!