Loading...
 
Skip to main content

Features / Usability


503 Service Unavailable message on a single, upper level page

francis wrote:
Hum well big bizarre problem! ...

Sorry if I implied otherwise. I have access to PHPMyAdmin and the databases I create. It is the MySQL error logs I do not seem to have access too. Along with the Apache logs. And I see no way to have a debug feature enabled to give me logs when trying to render a page via a tikiwiki URL. It is a 15 year old VPS service (shared host) which is a pseudo-VM without access to the MySQL, sendmail, etc shared resource installations. (I have my own servers as well but have kept these very public sites on a public hosting service as they monitor and patch security flaws more quickly than I can. So uptime is usually better. When my servers were inside the University computer center, they were hacked every few months.)

Hostgator will not backup if you have too many inodes. I have a separate image gallery with tens of thousands of images that creates over 100k inode entries. So I do my own backups with beyondcompare to my own servers. But I only run them once a month as the sites do not change often enough. Realize they have redundant disks and back them up multiple times a day. So restore things on a crash. Just they do not give you access to those backups they do.

Hundreds of images are working fine. Just these two on these two pages flaked out. I discovered my backup of the image files is on a server I cannot access at the moment. So will have to wait till I get that access again to restore those two image files — in case they were corrupted in some way. (As mentioned, when downloaded, they look fine. But trying to view inside a TikiWiki page gives me the 503 error.) File permissions on the folder and files are all identical and open as expected.

Am waiting to when I have access to the backup of the image folder from previous months to verify the image files did not change. Next would be to try and figure out if the PHP image processing that is setup in the new updates is somehow barking on these two particular JPG files.