[Solved] My Website Gives Internal Server Error

[ominitric]

Website domain: Cybernilitary.ml

Account name: Cyber

Server: Johnny

Can access website gives internal server error

[wolstech]

Johnny hasn't worked in several days now. cPanel is also broken on Johnny.

[Giuseppe]

HelioHost username: glebinho

server: Johnny

HelioHost main domain: custom-soft.ru

Hello, dear support! I have found my site to be unavailable. I need the backup of the site so I could transfer it to another server. Can I have the backup or anything that could be extracted out of Johnny?

Thanks.

[wolstech]

All available files and data can be downloaded via FTP. Your databases will be found as .sql files in your home folder.

[Giuseppe]

Thank you so much! I have gained access to all my files, but the sql file inside my home folder is empty despite the correct naming. How could I have my database exported? A link to the myphpadmin would do.

[wolstech]

Phpmyadmin is no longer working, so there's no link to give.

 

Escalating so krydos can check. Do note though that if your database used innodb, its currently unrecoverable.

[Krydos]

The .sql file in your home directory is 237K. Why do you say it's empty?

[Giuseppe]

I seem to have no access to my home dir with ftp then. The only sql file I can access is /glebinho_babu.sql which is 783 bytes large. Could you please give a hint how can I gain access to my home dir, please?

[Krydos]

Oh, I was looking at the account cyber of the person who started this thread. It looks like maybe you just posted on someone else's support request instead of creating your own, or are both accounts yours?

 

Here's why your backup contains no information

+------------------------------+--------+
| TABLE_NAME                   | ENGINE |
+------------------------------+--------+
| babu_assets                  | InnoDB |
| babu_associations            | InnoDB |
| babu_banner_clients          | InnoDB |
| babu_banner_tracks           | InnoDB |
| babu_banners                 | InnoDB |
| babu_categories              | InnoDB |
| babu_contact_details         | InnoDB |
| babu_content                 | InnoDB |
| babu_content_frontpage       | InnoDB |
| babu_content_rating          | InnoDB |
| babu_content_types           | InnoDB |
| babu_contentitem_tag_map     | InnoDB |
| babu_core_log_searches       | InnoDB |
| babu_extensions              | InnoDB |
| babu_finder_filters          | InnoDB |
| babu_finder_links            | InnoDB |
| babu_finder_links_terms0     | InnoDB |
| babu_finder_links_terms1     | InnoDB |
| babu_finder_links_terms2     | InnoDB |
| babu_finder_links_terms3     | InnoDB |
| babu_finder_links_terms4     | InnoDB |
| babu_finder_links_terms5     | InnoDB |
| babu_finder_links_terms6     | InnoDB |
| babu_finder_links_terms7     | InnoDB |
| babu_finder_links_terms8     | InnoDB |
| babu_finder_links_terms9     | InnoDB |
| babu_finder_links_termsa     | InnoDB |
| babu_finder_links_termsb     | InnoDB |
| babu_finder_links_termsc     | InnoDB |
| babu_finder_links_termsd     | InnoDB |
| babu_finder_links_termse     | InnoDB |
| babu_finder_links_termsf     | InnoDB |
| babu_finder_taxonomy         | InnoDB |
| babu_finder_taxonomy_map     | InnoDB |
| babu_finder_terms            | InnoDB |
| babu_finder_terms_common     | InnoDB |
...

[Giuseppe]

Might that mean that it is absolutely unrecoverable, and I should not expect anything more?

[wolstech]

Correct at least for now. We have no way of recovering innoDB databases from Johnny at this time. We HIGHLY recommend MyISAM for exactly this reason.

 

InnoDB offers a bunch of advanced features, but makes disaster recovery extremely difficult to impossible.

 

Down the road (I.e. months or years), we might be able to get them once johnny is fixed, but I wouldn't count on it.