Nathan Johnson

Should be working now.

Thanks, it's working now.

@Nathan Johnson - Which site were you referring to? Is it working now?

 

@Xaav - Just curious. What was the fix?

The site I was referring to is weebuild.heliohost.org. It's working now.

I suggest .tk. It is short and easier, and it is a TLD (for Tokelau). You can get one at: www.dot.tk If you don't like this type of domain, I suggest .cz.cc or .cu.cc.

I'm getting this error again:

Warning: mysql_connect() [function.mysql-connect]: Too many connections in /home1/pjphost/public_html/employee/mail/config.php on line 4

I'm on Stevie and my username is 'pjphost'

I'm on Stevie and I'm getting this error too. Also when I try to open phpMyAdmin, I am getting the error that Kli is getting:

Sometimes, when I'm using phpMyAdmin, I also sometimes get "#1045 - Access denied for user 'root'@'localhost' (using password: NO)".

Okay, it has been down all day today now. What's wrong with Stevie?

Maybe, as xwinuser has said, adding another server or something would really help. But I know that won't happen, but if it was possible that would probably really balance out everything. Also how much sites are hosted on Stevie? It seems like a lot to be down so much.

Hopefully it will be fixed soon. I probably could have gotten loads of stuff done today on my PHP application that I'm making if it wasn't down. Good luck guys on getting Stevie back up and running.

I'm wondering, what server is down the most often: Stevie or Johnny? It seems like (lately) Stevie has been down more than Johnny, but I don't know because I'm not on Johnny. So what is actually down the most?

Anyone know when Stevie will be back up? It has been down since last night

It's been down for quite a while now. I do hope Stevie will be up soon. Good luck to the HelioHost team! I agree with Bill (@animove), you guys all rock!

Edit: It's back up! Thanks HelioHost!

I close them all the time, as early as possible. I wasn't aware of any auto-closing at end of page (there might well be, I've never really given it any thought or read up on it). However if it frees up a connection slot a few milliseconds earlier on a shared server, being wrong dosen't do any harm.

Yeah, I'm gonna start closing them. They do close by themselves at the end of the page, but I think closing them sooner would be much better as it is only getting some info from the database, putting the info into variables, and that's it, so closing it after would be better, because if it closes it at the end, it is a longer-open connection.

Also, the manual says:

Using mysql_close() isn't usually necessary, as non-persistent open links are automatically closed at the end of the script's execution.

But, once again, closing it before the end of the page is probably better.

This is probably stating the obvious, but sometimes we overlook these things.

 

Could it be that you're not closing connections after use?

They may be accumulating if many connections are established within a short amount of time. Some sort of loop elsewhere which skips a closure may also be responsible for this.

 

I don't know the settings on Stevie, but max_conn on Johnny is 30 and i'd expect much of the same there, it wouldn't take much clicking through pages to exceed that limit, especially if there's more than 1 active user at this stage.

 

Just a thought...

I've heard that closing MySQL connections isn't required. They automatically close at the end of the page. But, I'll try closing all them manually with mysql_close(). Thanks

It is odd that it wasn't happening before, though...

I'm not seeing that error right now.

Yeah, it isn't right away. It only happens after I click around and stuff.

Hi

I keep getting this error:

It used to never do this. What could be happening? This is the code of 'connection.php':

<?php
$username = "username_here";
$password = "password_here";
$con = mysql_connect("localhost",$username,$password);
if (!$con)
 {
 die('<br /><br /><strong style="font-family: arial;">Could not connect to the database: ' . mysql_error() . '</strong>');
 }
?>

Am I doing something wrong?

 

What's wrong with Ajax? Ajax is a lot better than doing a bunch of page refreshing. It is a lot faster. The old version was horrible compared to this one.

 

Does that mean you do not use a browser that does not refresh?

 

Do not rely on a website to do your bidding rely on yourself!

 

Rely on websites and you have given up control.

 

If Refresh is what you really want use Opera.

 

All other browsers for web development are still learning. That includes Chrome.

What I meant is going to all of these different pages and stuff to reply... Ajax makes it a lot faster and easier. And, I only use webkit based browsers like Chrome

I don't know why Stevie has been down so long, I'm mad too.

This board is going insane.

 

Why all the Ajax?

What's wrong with Ajax? Ajax is a lot better than doing a bunch of page refreshing. It is a lot faster. The old version was horrible compared to this one.

Who is causing these downtimes? Whoever is taking up a lot of the server resources I think should be banned... they're harming everyone's sites. It seems like Stevie has been going down more than Johnny (is that true, or is Johnny worst?)

This happens so frequently, I do wonder why stevie is not killed off!

This Ajax board is a nightmare!

What idiot thought Ajax was a solution to efficiency?

Like Flash not really what the Internet is all about.

Boys with toys!!

This AJAX board is a lot better than the old one. The AJAX makes it a lot easier to use and faster. I love the notification and message box at the top and how there's a much better loading indicator now. Also, AJAX has nothing to do with Flash, if you didn't know

@Tjoene: Thanks for letting us know.

This is what I'm seeing now:

Will Stevie be up any time soon? It's been down all day.

When I try going to http://stevie.heliohost.org:2082/ and http://weebuild.heliohost.org, they both don't load. This is the error I'm getting for both of them:

I don't know why it won't load. Are you guys doing any maintenance?

Edit: I just noticed in the server load image that Stevie is down. Is this because someone is taking up too much resources again?

If you need to send a lot of emails (without harming the server or anyone's site), you might be able to integrate SendGrid into your script. They have a free plan and a paid plan. I haven't set this up on my scripts before, but I'm going to try it someday.

What happens if we use AJAX? Would that cause errors?

 

It shouldn't cause errors as long as there aren't 50 people spamming your site or something.

Okay, that's good. I know I wont have that much users on so I think I'm good.

What happens if we use AJAX? Would that cause errors?

I do want to point out the fact that it takes about 1/10 of a second to serve a static resource, and since browsers fetch two resources at a time, you would need (10*8)/2, or 40 clients per second to cause this error.

Thanks for letting us know that.

Yeah, the older one (I wonder how long ago that one was developed?) was a lot slower and I like this a lot better. Like how when you reply it automatically slides down the reply instead of refreshing the page, and how when you edit it it scrolls down and stuff. All of the new features make HelioNet a lot faster, better, and easier to use.

Okay, thanks.

Oh ok. I'll just put the 'refresh.png' image into the 'icons.png' CSS sprite instead so it will all be one connection. Don't connections close after the image is loaded?

What server is your site on?

Sorry, forgot to put that in my post. My site is on Stevie.

This is a really strange issue. One time it is "images/icons.png" that has the error and then I reload the page and that one doesn't have the error, but "images/refresh.png" has it that time.

Does anyone know what could be causing this?

I looked in JS Console:

It's getting on my nerves because sometimes one image wont display and then other times another image wont display.

Hopefully there's a fix to it.

By the way, I'm using Google Chrome. I also tried in Safari and Firefox and they both were having this issue.