Search the Community

Username: kairion, server: VPS67 I'm not sure why but it seems my VPS got stuck while rebooting after some changes on OpenLiteSpeed and CyberPanel. To be honest I'm kinda puzzled since it didn't happen on DigitalOcean on my prior test but since it's bothersome I'll try not to look into it. So could I ask what is the price for a new rebuild? I'll stick with KeyHelp for stability for my site and later I'll join the queue to get another VPS as a test lab for OpenLiteSpeed (I'll use docker to be able to create/destroy it without bothering support all the time 😅). PS.: Sorry for the trouble.

This is not a specific issue but a general question. Is there a way to manually reboot my HelioHost VPS without contacting customer support? I know I can just type reboot in the console to have it restart, but I'm talking about cases where the command line is inaccessible, for example because of high load or an out-of-control process (which happened to me recently). It would be nice if there was some way to expose the vmware commands for a hard power-on/power-off—not that I would use it much, but it'd be a safety net I'd know was there if something went wrong.

First I would like to say thank you for all of your time and effort for providing us with such a wonderful service. When trying to access my site I get this error: Unknown storage engine 'InnoDB' [1286] When I checked the engines tab in phpmyadmin it showed MyISAM MyISAM storage engine MRG_MYISAM Collection of identical MyISAM tables MEMORY Hash based, stored in memory, useful for temporary tables BLACKHOLE /dev/null storage engine (anything you write to it disappears) CSV CSV storage engine InnoDB Supports transactions, row-level locking, and foreign keys ARCHIVE Archive storage engine PERFORMANCE_SCHEMA Performance Schema FEDERATED Federated MySQL storage engine And when clicking on the InnoDB entry I am told: InnoDB Supports transactions, row-level locking, and foreign keys This MySQL server does not support the InnoDB storage engine. There is no detailed status information available for this storage engine. So it would seem that there is no InnoDB engine preent in the database. However , in order for me to recieve the initial error Unknown storage engine 'InnoDB' [1286] InnoDB would have had to have been present when the database was written, and now it is not. In order for me to resolve this error I must delete all log files and restart the mysql database. How would I be able to do that? Thanx again .

I often work through the middle of the night. This is also when most companies reboot their servers for scheduled maintenance. Do you guys reboot? When? How often? Both servers at once?