Krydos

Sometimes my crazy theories pan out... I'm not going to question it; just going to chalk it up as a win.

Isn't IMAP usualy port 143? I thought port 21 was usually FTP, but I guess you can use whatever port for whatever you want as long as it's open and both the server and the client both know what protocol they are using to communicate.

I ran the script on August 16th and I remember it terminated successfully.

Yeah, it shows up correctly in all of my browsers too I guess. It's just 1 pixel wide and I didn't notice it at first. I tried uploading .jpg and .JPG images to my own stevie account and I can't get the type to be set to text/x-generic that way. I guess it was just a coincidence. So much for that theory.

Stevie's current load is 40 which is really high, and when the server load is that high it can cause issues. MySQL seems to be affected more by high server load than apache and php, etc so usually the first thing to stop working is your database connection. I just viewed your site and it loaded just fine. As the server load drops lower it will become more stable.

http://gazzola.co.cc/ is listed as the main domain for the account gazzola in the heliohost account database and the site is loading fine.

Does it show up correctly in your browser when you try to view it though? Maybe it's browser specific error?

Oh that's interesting. It seems any of the images you upload with lowercase extensions work and any you upload with all caps extensions don't work. Check out http://alphapete.com/images/ This works http://alphapete.com/images/moon.jpg But this doesn't http://alphapete.com/images/header2.JPG and gives this error Easy fix is to just rename your files with a lowercase .jpg extension before you upload them. On a lot of windows and dos environments caps or lower names are interchangeable, but on most *nix environments caps and lower are interpreted differently.

Testing this a bit on my johnny account. Sent email from hotmail to default johnny email account; received this response: Also tried sending email from horde using default johnny email account. The first attempt to send didn't have the default from address set correctly, but this might be a bug in horde and was easily fixable through options: After fixing the settings like it said to this is the error when trying to send an email to hotmail: I was thinking this might just be because Hotmail has a vendetta of some sort against heliohost emails, but I tested it with gmail and half a dozen other emails and it gives the same error each time. So then I created a new email account test@krydos1.heliohost.org and logged into horde with the new account. I had to change the from address to the new test@ because it was still set to krydos1@ but that's horde's problem I think still. Emails sent from this new account work, and emails sent to this account are also received. Summary: The default account (username@username.heliohost.org) seem to be the only ones that have any issues, but any created email account will work as expected.

Moved...

Google+ is fine. When I first heard about it I just laughed and asked why the heck the world needed another version of Facebook? Then I used it a bit and it's pretty decent and different enough from all the other social media stuff that it might be able to carve itself out a little niche. I've liked pretty much everything google has done, and the privacy stuff is fine with me. It's annoying to see retarded ads that don't don't appeal to me at all than it is to see kind of cool ads that I might actually be interested in, ya know? It's fine with me if they get to know me a little to show me stuff that I like anyways. The only problem I have with google is all the damn censorship they've taken it upon themselves to do lately. Screw that. Censorship is bs. It's not my fault that 98% of internet users are retarded and download every virus they come within six bytes of. I want to see the entire internet, not just the portion you have arbitrarily decided should be available to me. Meh!

Looks like the account in question has been deleted. Probably the users added it to deletion queue themselves.

I don't think xaav was refering to you personally when he used the word you, and furthermore this thread is discussing why Helionet is unstable. Helionet is these forums and the main website, or also known as cody; there are no user accounts on cody. While simultaneously watching htop running on cody and johnny I can say that there are plenty of times when cody will be running really sluggish and laggy but only using ~5% cpu. Meanwhile johnny will be using the other 95% plus more if he could get it and the physical processors are pegged out at 100%. I don't know how the virtualization is set up, but is there anyway to reserve some cpu time specifically for cody to use? Perhaps there is some way to set all the johnny processes a lower priority and the cody processes a higher cpu priority with nice? I have seen mysql hogging a lot of processor, but then again I have seen cron, ror, mongrel, etc really hog all the cpu too. It's definitely johnny that is causing the problems though. Hopefully some of these ideas and observations might help.

Cool utility. That could prove to be very useful. By the way, Piotr GRD, I moved your post and pinned it in the customer service forum next to your pinned server monitor. Sorry for whisking your post away, but that is way too useful of a tool to have buried in this thread that will likely be closed and buried soon enough, and I wanted your account to be the thread creator. I usually hesitate to be so heavy handed in my moderation/editing, but here is where your post went: http://www.helionet.org/index/index.php?showtopic=10223

Split this topic from it's original location, posted it here, and pinned it here next to Piotr GRD's server monitor so it will be easier to find. Thank you for all your great contributions.

Please Clear your cache.

Yeah, your site is loading fine now. Seems there was a database error and it's all worked out now.

To summarize: Johnny has 179 accounts queued for deletion; the oldest of which last logged on February 27th. Stevie has 616 accounts queued for deletion; the oldest of which last logged on July 4th.

All server and services should be fully functional at this time. Thank you for your patience during this process. I don't think anyone expected this software upgrade to cause as much downtime and problems as it did, but we are far more protected against vulnerabilities now than we were before and everything should hopefully run a lot better. Once again thank you for your continued patience during our downtime as we performed major upgrades on our servers. As a bonus all accounts should now have twice as much storage space as before. (Now 500mb, up from 250mb.)

Glad your problem got solved! Please spare a few minutes to take our brief survey: http://feedback.heliohost.org/ Your participation in this survey is greatly appreciated.

The high server load that was causing MySQL errors should now be back to normal because the servers are finished upgrading their software. Closing...

Since the high server load caused by the software upgrades has now passed the database errors should be gone now too. Closing...

Software upgrades are finished now and everything should be fully functional again. Closing...

The servers have had a lot of load and therefore a lot of errors and downtime over the last few days, but the software upgrades are done now and everything should be fully functional now. Closing...

Glad your problem got solved! Please spare a few minutes to take our brief survey: http://feedback.heliohost.org/ Your participation in this survey is greatly appreciated.