wolstech

Did you edit your website's code to use the new password you set? The password for the DB user matti76 should be your cPanel password, so changing the cPanel password will change the DB user's password too. Anything that uses that database user will need to be told what the new password is. If it still refuses to work after you've made sure the website code has the right password, make sure they match by changing the cPanel password again and checking the "Synchronize MySQL Password" checkbox to force the DB user's password to change. I don't recommend using your cPanel account as a database user for security reasons, but lets get it working first. #1874 is because InnoDB has gone read only again due to a crash yesterday morning. I'd advise not using InnoDB since many times when MySQL crashes, InnoDB data has a habit of getting lost. I recommend you convert the InnoDB database to MyISAM, which is much more fault-tolerant. We've never lost MyISAM data in our 10+ years of operation. We've lost all of our InnoDB data several times this year alone. You can convert the database to MyISAM as follows. This will also fix the #1874 error: Make a copy of the .sql fileSearch the copy of the .sql file for Engine=InnoDB and replace all instances with Engine=MyISAMCreate a new database.Import the edited copy of the .sql into the database using PhpMyAdmin to restore the content.

Try changing your cpanel password, then log out and in again. After that, try recreating the users again.

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.

Marko has it. Tommy is current unreleased, and as a result is invitation only right now. Also, for those who did get a Tommy invitation: if it was sent to an email address that currently is used by a Stevie account, you need to delete the Stevie account before the invitation will work.

Postgres does not crash as far as I'm aware. Not too many use it though.

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

This appears to be fixed.

I've been here 5 years, and Stevie MySQL has always crashed a lot. I think it's load-related, but Krydos would know for sure exactly why it crashes.

MySQL died again... Escalating.

Typically, they fill up as a result of broken code that never exits (php), due to email clients that check too frequently (imap), or similar reasons. Logging into cpanel causes a 500 error due to processes, though that one should clear on its own when you log off. I've never had to ask for a process kill at any point. There is no away to see or do it yourself.

The SQL error is likely something wrong with the syntax of whatever statement would normally generate the data for that field. Seeing that no specific error number or message is shown, there's no way to tell what happened from that picture. Also, do you have a license for IPB? I looked at your site, and it appears to be pirated/nulled, which violates our TOS. If you don't have a license, please delete the entire IPB install or you will be suspended for copyright infringement. I'll go ahead and mark this answered since the software in question has been removed.

Domain changed. Please give it 24-48 hours to update and start working.

That's what this tutorial explains...how to park a .tk domain. Alias is just the paper_lantern theme's name for a parked domain.

I don't see an SQL error, I see a general 500 error. Whatever code feeds the genre section is outputting a 500 error.

It works for me. It's possible that it's been blocked where you are though or was down when you tried it. Either way, thanks for pointing it out

Your account is suspended for inactivity. It can be renewed here: http://heliohost.org/classic/support/scripts/renew

Escalating.

Django is a very big pain to make work here...in fact, it's probably the most difficult thing to use that we offer. If you search the forum for Django, you'll find an example from Byron showing how to use it. No idea on memcached.

If you see spam, feel free to hit report on the posts. The report button email us a link and issue description so we can clean them up quicker. Otherwise their spam will sit on the board until we log on next and see it.

Tommy doesn't have a set release date. Python 3 is used by changing the shebang line in your file. Try using /usr/local/bin/python3.2 as the python path.

First, be careful with the cron. Cron is limited to two runs per day per account. Make sure the job is set to no more than once every 12 hours (or if you have 2 separate jobs, each once a day, and so on). Second, we have another who also asked about Python Modules. I don't know if these can be installed or not. Escalating.

Please clear your cache.

Usually a few days, but sometimes up to a week. He hasn't been as active as normal recently due to work and other things in his life. I'm waiting on a response about a forum spam issue myself. It's worth remembering that we're all volunteers too, so HelioHost is something we fit in when we can. We don't get anything in return for our time.

Banned. (They're bots. We've been having problems with spam lately. They sign up by the hundred. )

I recommend leaving your home directory alone (except backups, if you made them, those are safe to delete). Most of the folders are system folders, and if you delete them, you'll find your account broken, typically beyond repair (you have to delete the whole thing and sign up again to fix that). What you want to do is open the public_html folder, and delete everything inside except cgi-bin. Then go in cPanel, remove all addon and parked domains, remove all subdomains except for your main domain (if listed), under MySQL you should delete your users and drop your databases, and under email, delete your email accounts. Also check for unwanted FTP accounts. Beyond that, we recommend just deleting your account and signing up again.