wolstech

The way we recommend you convert innodb tables to myisam is to make a backup as an sql file, replace all of the ENGINE=InnoDB with ENGINE=MyISAM in the backup SQL file, import it into a blank database, then edit your application Config to use that new database. Last i tried, attempting to use ALTER on the existing tables to change engine doesn't seem to work. Also don't bother trying to drop databases with innodb tables in them, since doing so wont succeed and will crash the MySQL server for everyone on the server...and it takes 10 minutes for it to restart.

That'd be nice, but it just adds complexity to an already complex system.

Because doing that type of stuff is not nearly as easy as it sounds when you have hundreds of users on the server. The server is not like your typical PC and is not nearly as easy to maintain or rebuild as a PC is. Rebuilding the bare system and your data would take days of downtime for thousands of websites, and getting everything back the way it was configuration-wise could take weeks or months of continuous tweaking. Besides, if we made and used backups, they'd restore these half-deleted databases. Once mysql is working properly, an admin can remove them for you. We won't upgrade mysql because it's broken and an upgrade might make the problem worse. It may be upgraded in the future. If you need a newer version for some reason, Johnny has MySQL 5.5 that isn't damaged. PHP will likely not be upgraded to latest because PHP 5.5 is not backward-compatible with a lot of programs due to function deprecation. We might get 5.4 at some point, but I don't know when that would be.

Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. To prevent this from happening in the future please remember to visit http://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.

Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. To prevent this from happening in the future please remember to visit http://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.

I have an app on there that uses it for secured mail server connections and haven't had any trouble, so yes we do.

That'd be a half-dropped database. It's related to Stevie's mysql issues. cPanel deletes it from your list of databases, but mysql then crashes trying to drop it. The result is cPanel thinking it's gone, and mysql still having it. I have 3 of these half-gone databases in my account from when I created new ones to convert to MyISAM tables. I can't get rid of them, and several others on here have reported the same. The solution seems to be to just ignore them until the mysql issues are fixed (who knows when that will be...).

For those who can't/don't want to download it, the post and file he is referring to is a copy of dosbox and Turbo C v3 packed in an NSIS installer... Dosbox is open source. Turbo C is commercial software that has a trial and licensed version, and I can't tell which one you included. I'd delete it just to be sure.

When I do a dig I'm seeing an SOA only for NS1. Whether that's because NS2 is down or because the SOA record just doesn't exist, I don't know. Either way, an admin will need to fix the issue with NS2. For the time being, contact the registrar and ask them to set the NS for you, telling them that your host only provides one (working) NS. We've had at least 1 other person with the same issue, and they were able to set it up by contacting the registrar. Alternately, you could create an A record to 216.218.192.170 instead. You already have your domain set as your Heliohost account's main domain, so this should work without any additional configuration.

An admin will need to look into the SOA record issue, but I wouldn't be surprised if the issue is actually because NS2 is down a lot. It's hosted on the same server as Johnny and is often impacted by the load Johnny creates. The server monitor seems to indicate that it something's been wrong with it for a while. In the mean time, your website should work fine with just NS1.

It's logging in as anonymous. You need to specify your FTP account's username and password in Filezilla's Site Manager settings.

Error 2013 is due to the crash. It occurs when you try to do things to innodb tables, like create or drop them. Best course of action is to just not use innodb tables. MyISAM is working normally. If you have to use them, you can move to Johnny, although it goes down quite a bit due to load.

This support request is being escalated to our root admin.

Please do not open a second topic for the same issue. Merged. Anyway, it may take a while before someone can look at this. Krydos is usually the one who handles this sort of thing; I'm not sure if the others can do it. I'll escalate it for you.

The code seems to have disappeared, but your font tag and h1 tag were closed in the wrong order if I remember right. Closing Font tag needed to be moved inside the h1 tag I believe. Also, for what it's worth, font tags are obsolete, as are the align attributes on several other tags. You shouldn't be using them, but rather using CSS instead.

Does it say if it was an access denied error or an error 2002? Error 2002 ("Cannot connect to the mysql server") is related to the crash. Access denied means your database user doesn't exist, isn't assigned to the database, or the password is incorrect. It is also worth noting that it is currently not possible to install Drupal from the distribution package or from softaculous on Stevie due to the damage, and many existing installs stopped working right due to their reliance on InnoDB and the now-frequent database server downtime.

Krydos is the one who typically handles this, so it's a matter of when he finds the time to look at your post and assign the IP address to you.

The first error is NS2 being down, which happens very frequently. The Heliohost server monitor shows that it hasn't been able to get data on it for the past several days. It's hosted on the same server as Johnny and is impacted by high load a lot, although the several days worth of "no data" entries in the server monitor look more like something broke. As long as NS1 is up, your site will still work. The PTR record warning has to do with reverse DNS for mail and is not an issue.

That error is normal. Most ports are blocked for security reasons, and we generally won't open them unless you have a legitimate reason. Do note that the odds of getting a port opened are quite low. In many cases, the first solution is to try reconfiguring whatever it is you are trying to connect to so that it listens on a common port that's not blocked. I know a few people on here run game servers on web ports like 443 or 8080 for this exact reason. Feel free to explain in this topic what port you need and why you think it should be opened. Please try to avoid PMs, as it makes it more difficult for us to help you. A PM can only be read by one person, and multiple admins and moderators may wish to read your post. If there's a reason you don't want it posted publicly, PM me and I can post it so only mods and admins can see it.

50 emails per day.

They're allowed, but they tend to get people suspended for high load if there's enough traffic, so I wouldn't recommend running them wide open like that one is. Would be best if he put a password on it.

An admin can say for sure but I highly doubt we will install this. Not only would it add more load, getting it to work with things like php would probably require quite a bit of reconfiguration. We currently don't offer any way to have hierarchical databases.

Please clear your cache.

That account is not showing as suspended or inactive. Have you tried resetting your password?

Check for a .htaccess file in public_html (use FTP or be sure to show hidden files in the cPanel file manager). Delete or rename it if you find it. Drupal creates one in the folder where you install it I think. (The reason Drupal didn't work is probably Stevie's database server being broken at the moment). Make sure that public_html has the right permissions. I believe the correct permissions are 750 (that's what mine is). The _vti_ stuff is frontpage extensions. There's a page for them in cPanel (it's at the bottom under the advanced group I believe). Go there and select to uninstall them. All of the _vti_ stuff and anything related will get fully removed when you do. Dropping old databases won't cause a 403 error. I'm not familiar with the CGI screen, so that might be another issue.