wolstech

Moud2k and moud are on the same server, so there's no difference in performance. Also, you just registered moud on 11/9 and moud2k on 11/10, so they're both new. The fact that two nearly identical accounts were registered resulted in your suspension. I've unsuspended moud2k and suspended moud. The domain still hasn't set up yet though. If you still see queued in 24 hours, let me know.

MySQL has been fixed.

You're only allowed one account. The account moud2k isn't working because it's suspended for having two accounts. Your other account moud is not working because your domain is configured incorrectly on dot.tk's website. See this tutorial for proper configuration instructions: http://www.helionet.org/index/topic/26236-tutorial-setting-up-tk-domain-alias-to-your-hostnameheliohostorg/ (You only need to do STEP 1 since it's your main domain).

I can't, but Krydos can see the logs if they exist. What I don't know, is if the logging is even on...we turned off a lot of logs for performance reasons (with 11,000+ users on the server, logs can get large, fast).

I do the same when I install a new version of my main application. Set the software up, load dummy data in whatever new feature I added, play with it, check data, debug if needed, truncate the tables, repeat with different data a few times. That definitely won't bother anything.

I doubt it, but there's no real way of knowing. It could've been any of the 11,000+ users that we have on the server, and sometimes it's not a user's fault at all (data corruption for instance). Out of curiosity, what were you doing at the time it crashed?

This support request is being escalated to our root admin.

MySQL crashed while you were using it, which is why you started seeing those errors in the middle of your task. It's already escalated here: http://www.helionet.org/index/topic/26558-mysql-down/

It crashes due to the fact that it has over 11,000 users and countless more databases...all it takes is one abusive user or one corrupt database to crash it. Escalating...again.

You can convert the database to MyISAM as follows. This will also fix the #1874 (InnoDB read only) error: Make a copy of the .sql file you want to import.Search 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.We don't recommend using InnoDB on Stevie since the data gets lost or the server goes read-only quite regularly due to crashes.

What are you getting for output? An empty file? An error message?

I was unaware they were ever enabled on Johnny...we turned off a lot of the logging for performance reasons. I'll escalate this and see what Krydos says. He may have just forgotten.

Tommy is not yet released, and Johnny is crashed. You can only sign up on Stevie, which accepts only a few hundred registrations per day. You may need to sign up on our old website if you're having issues. The server monitor here shows when signups on Stevie are available: http://heliohost.grd.net.pl/monitor/

Seems to be working now.

It was down earlier but is currently working for me.

It takes 24-48 hours to start working after you add it. It shows queued until the server finishes setting it up.

Um...seems to still be down.

Looks like this crashed again... Escalating.

You need to configure the domain DNS at your registrar. In your registrar's control panel, create two NS records for that domain, pointed to ns1.heliohost.org and ns2.heliohost.org, remove all other records, then try again.

Squirrelmail should work. The database server is messed up on Stevie right now, and those issues with horde and round cube are caused by the softwares inability to use its database.

Just sign up on Stevie. If you need a domain removed, please let us know which domain it is and I will escalate for you. Your Johnny files and databases are available via FTP because Johnny crashed. The databases can be found in your home folder as .sql files.

Try another internet connection such as a cell phone on its data plan. It's possible that your ISP has cached the page. The site is working for me.

Please clear your cache.

You're suspended for multiple accounts. Users are limited to one account. The account emagrece has been unsuspended.

InnoDB went read-only again from the crash on Friday. Can this be fixed please?