wolstech

The NAS itself probably won't get a name since it's not a server in the conventional sense, it's a storage appliance. The network switch in the rack lacks a name too... If the NAS were to fail entirely, we'd lose access to the accounts on Tommy's extended disk (the NAS disk usually appear as a partition like any other, odds are these accounts will get stored in /home1 or something similar). For Lily, fi it ends up being built how I imagine, Lily won't boot if the NAS is down. Tommy's cPanel would still let them log in, but their site would be down (likely giving a 503 Service Unavailable or some similar error because Apache would respond, but can't connect to IIS to pass the requests through) and their files and any DBs stored on would be inaccessible. Mail/DNS/etc. would still work, and provided their account is on the non-NAS half of Tommy, it could be converted to a Tommy account at the expense of their data.

What program is producing that message? Also, how are you trying to send mail? I've never seen that message before. Also, can you provide the entire, un-edited message (including the addresses and IPs)?

To be honest, we don't show individual load sort of on purpose. Part of that is because there's no way to provide a meaningful number because high load is "high relative to other users", not "high relative to idle". For example, if the server happens to be rather quiet, your account can cause quite a bit of load without anything happening. If the server's busy though.... The other issue is that if users know where their upper limit is, they'll stay right below it, hogging as much as they can without getting suspended. By moving the limits dynamically and not telling you where they are, it makes it close to impossible to defeat. The limits are high enough though that reasonable software will run just fine. I've been here 7 years with numerous applications and sites on my account, and have never managed to suspend myself for load (on the other hand, I did manage to get suspended for malware at one point after an un-updated WP install for my minecraft server got hacked). As for free registrations, yes we'll offer them again once we have the space to do so, and yes, it would be reasonable to assume that as the server becomes more crowded again from free accounts, the tolerance for load suspensions will probably be decreased to reduce load-related lag and downtime. They may or may not both happen at the same time though.

Create the subdomain kliklampung.kliklampung.heliohost.org in cPanel, then check if the domain shows up in Aliases (or possibly in Addon Domains if you tried adding it there in the past). Once it shows up, wait 12 hours and clear your cache. If you can't get it to show up, let me know and I'll have someone look at it for you. This is a known issue on Johnny with addon and alias domains.

Pretty much. A visitor to a website would never see it. They'll visit yourdomain.heliohost.org like they always have. We actually already own the server. What we had to buy was a NAS to make the server useful. The actual server is a unit named Katie. The owner donated it late last year because he needed half of it for personal projects. The other half is what will become Lily. The problem is that it has like 30GB of space, which isn't even enough to install Windows (Server 2016 wants 25GB, and the ISO is 8GB...). The GoFundMe was held so we could purchase a NAS to get the additional space we need to actually use it. Some of the space from the NAS will also be used for Tommy so we can offer free accounts again. Right now, the Lily half just runs a tiny CentOS VM with the linux version of HelioMine 24/7 since its useless for anything else until we install the storage. The storage hardware has been ordered and shipped to the data center, hopefully it'll get installed in the next few weeks so I can actually start building this.

Did they check in spam? Johnny email tends to go to spam a lot due to the amount of spam and phishing that originates from the server. Try writing a very basic script that uses mail() to send yourself something, and see if you receive the test email. Also, please be aware that if the recipient is using outlook.com/hotmail.com, they may not be able to receive emails from HelioHost. As of now this should only affect Tommy users, but there is a known issue with HelioHost and Microsoft services.

Did you make sure to set your file permissions correctly? They need to be 644, but often upload as 664 and need to be changed (Apache does not like files writable by the group). Also, try renaming your .htaccess file so it's ignored and see if your site works without it. Invalid .htaccess files will cause a 500 error. If you're running Python/Perl/etc., scripts, be sure the shebang line is correct and that the file is in the cgi-bin folder. @Bailey: 99% of the time it's not the script. Nearly all 500 errors we see are permissions or htaccess related.

What is your account's username and what server are you on?

If you're going to find a mail service, consider that a dedicated IP address may work for you as well ($12/year). I'm pretty sure mail will come from the dedicated IP if you have one, so it won't look like it's coming from tommy...Krydos can confirm that if you're interested.

He'll email it to you if he has one, and usually posts in here saying it was emailed.

If you're not sure whether we might receive a spam report (or whether your users will get your mail), this is a useful tool for making sure your mail doesn't look like spam to a filter: https://www.mail-tester.com/ (It can take a few revisions to find something that's friendly to both users and filters )

And if it wasn't obvious from Krydos' response, your website violates our TOS and cannot be unsuspended: http://wiki.helionet.org/Terms I hate these social media bots...

One of our other root admins. He's the one who maintains the servers. I mostly do customer support and abuse prevention.

Please clear your cache. If you've done this and it's still showing Queued only when on your computer, the issue may be caused by your ISP caching websites. Unfortunately, there is nothing we can do about that except suggest you wait until their cache expires.

Alright. Krydos will grab the logs and post them when he can.

Should be localhost for the host name. Username and password are whatever you set in cpanel when you created the database user (make sure you granted the user permissions to the database). Also, be sure you didn't mess up the username or DB name, all of your database users and database names start with cridus10_ Finally, when naming your WAR file, be sure you name it with your username in front (e.g. cridus10_something.war) so the context paths are correct. If you don't, it won't be able to find any resources like CSS files that are bundled with it.

Moving so Krydos can check for a backup.

It keeps causing load too quickly and getting suspended again. I don't want to keep unsuspending it, because each time it causes load, it just makes everyone else's sites slow or go down. I'll let Krydos identify the file so you know exactly what to fix before we unsuspend you. If need be we can also rename the offending files to disable them for you.

We have to get them and post the relevant portions since they're shared with all users and consequently contain sensitive information about other user accounts on Tommy. Please note that the Tomcat version on Tommy differs from that of Johnny (Tommy has 8.5, Johnny had 7.0) as well, so if you build for Tomcat 7.0, it's possible that's the cause. Moving so Krydos can look at it for you and post the logs.

They were lost during a crash a while back. We tell everyone not to use InnoDB because we've had such bad experiences with it (its stupidly sensitive to improper shutdowns destroying the data, usually colo power outages or servers crashing due to load). We've lost InnoDB data more times than I can count. On the other hand, we've never lost MyISAM data in our 13 years of operation. We may have a backup, but no guarantees. What was the name of the database?

High load again. Your software is using too many resources. If you don't know what's causing it, let us know and we'll be happy to help you find the problem. Unsuspended.

You're on Tommy now. Thank you for the donation. If you see a queued page or a 404 error, please clear your browser cache and flush your OSes DNS.

Were they InnoDB tables? If so, what we're their names?

Moving.

It is ESXI. Eddie contains Tommy and Cody. Odds are high that it's just a dead battery in the server. The servers did lose power a few weeks back during an HE outage and it probably lost the time then. To my knowledge, the clock on Eddie isn't actually used for anything beyond ESX internal functions/logs, since the VMs set their clock over NTP, hence why it's gone unnoticed until now.