wolstech
-
Posts
17,707 -
Joined
-
Last visited
-
Days Won
660
Everything posted by wolstech
-
Yeah, Stevie was acting up earlier. About 10 minutes after I posted, I got a flood of emails from my monitoring service saying it was going up and down repeatedly... Seems to be working now though.
-
@incog: Yep. Doesn't belong here. I'll move it for him though so he doesn't need to repost.
-
InnoDB tables were lost in the recent crash. The fix is to drop the database and restore your backups.
-
Empty response is when a server opens a connection then doesn't send anything to the client (in this, cloudflare). Odds are it was due to server load, especially if you are on Johnny. I see tons of ERR_EMPTY_RESPONSE in Chrome when trying to get pages to load from Johnny.
-
You have to change your account's main domain to a something.heliohost.org subdomain if you wish to do that. You can change the domain here: www.heliohost.org/home/support/scripts/domain The change takes about 24 hours to take effect once you do it.
-
The account uzair3 has been marked for deletion. When the deletion is complete, your old domain will show a queued page. You weren't able to delete it yourself because it was suspended for inactivity. Escalating so the theme can be changed to paper_lantern on account cwk.
-
Change your cPanel password, then log out and in again to fix PhpMyAdmin.
-
There is an advantage there, but it's far from mandatory in many cases. I have at least one application on my account that was adamant it needed InnoDB...it's been running on MyISAM for a year with zero issues. Full foreign key support/enforcement in the database is nice, but a decently-written program should be able to handle bad foreign keys without choking (granted it means the database isn't strictly valid...) All bets are off if Transactions are needed though...MyISAM doesn't understand them. If Inno didn't blow up as often as it does, I'd be more inclined to use it. The first crash here had me lose 2 months of data (had to restore a stale backup). Everything was converted to MyISAM then except some less-important applications. Those broke last week and ended up needing (recent 3-week-old) backups restored. -
Delete your old account here: http://heliohost.org/home/support/scripts/delete No limit when using external mail server. The limit on ours is 50 emails/day though. That 50 also includes emails sent with things like php's mail() function.
-
It's CPU and memory, not space. Basically, your program was hogging the server resources which makes everyone else's site slow, so we suspended you so everyone else could use their accounts. You don't have any way of monitoring it actually. The normal causes of this are programs that either need too many resources or are just malfunctioning. If it happens again, let us know and we can tell you what file is to blame for the load.
-
Change your cPanel password, then log out and in again. After that, delete the database user ovt00_mysql, then recreate it and reassign its permissions. Once you do that, check PhpMyAdmin to make sure your database contains all of its data.
-
If there was an old one, it wouldn't let you create the new one (I actually had this issue happen...I tried to drop one and it wouldn't let me make a new DB with the same name, Krydos had to drop it for me to get it to fully drop). Silly question, but did you use the same password on the new user? If you just used the password generator button, you need to edit the software's config file to make the passwords match. Just for testing, try using your cPanel username and password as your database user. While not recommended from a security standpoint, it'll at least prove that the database itself is functional since that user always has access to all databases in your account.
-
Did you assign that user to the database you created? Also, try using your cpanel account as the database user to see if it works.
-
Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.
-
Dd you make sure to reassign the database user to the database? Also make sure the database user h the right password.
-
The user must be deleted and recreated, not just get a password change. After you recreate it, make sure you assign it to the database again too.
-
I've not had any issues installing something using InnoDB then converting it's DB afterwards. I'm sure applications that won't work like this do exist, but they seem to be rather rare. For most, it's more because many programs have install scripts are just coded to import tables that are defined using it...the tables themselves don't care what format they are in, and the program using them is usually none the wiser if you change the engine, provided the schema stays the same.
-
Topics older than a certain date "fall off the bottom of the list" (they become hidden). You can still get to them by finding them through search though. Also, post counts don't update immediately, and in some forums, posts don't count at all, so your count may not always be a perfect reflection of your posts.
-
Please change your cPanel password, then log out and in again. After that, check that PhpMyAdmin works and that all your databases and their tables (especially InnoDB tables) are present. After that, go through your database users, delete and recreate them. Use the same password as last time (check in your software's config file for it if you don't know it). Make sure to reassign the users to their databases as well.
-
If the backup was created after the recent crash, the InnoDB tables in your database will be missing from your backup. A lot of them were lost in the recent crash (again). Not sure what the odds of us having a backup are, so I'll escalate this for you. Note though that we don't make backups for user data regularly, we may not have anything to restore. Routine backups of databases should be made through cPanel or PhpMyAdmin, and it is the user's responsibility to make them. Once you get this fixed, I would recommend converting the database tables to MyISAM so this won't happen again.
-
[Solved] Roundcube Webmail Not Connecting To Database
wolstech replied to qsgt's topic in Escalated Requests
The roundcube on cPanel is indeed broken. Escalating. -
Working for me now too. If you still see the error, please clear your cache.
-
My Website Is Not Connecting With Mysql Database
wolstech replied to rahuld147's topic in Customer Service
You need to use a backup from before the incident. -
This support request is being escalated to our root admin.
-
You're blocked by the firewall. Escalating so you can be unblocked.
