Random.. means Random....

Kensino

Perch
I do not know what part of random the support does not understand. I have been getting random issues for over a week where I get a error saying that tomcat engine is down.

Everytime I contact support via my ticket of live chat they tell me sorry this is working fine nothing is wrong. Hince the random part of the issue, it does not happen all the time.

The last couple times I had an issue they restarted apache and the issue was solved. I should not have to call support dept and have them restart apache everytime I get this error page. They need to figure out what is going on in the first place.

I have submitted screen shots with my ticket of the error message and still they tell me there is no error. I guess I just made the screen shots in Photoshop, idk.

When I say random, it means .... random. I don't know how to explain the word, but it means not happens all the time. So when they check it, the issue might not happen.

I keep getting an error page that support tells me does not exist.
 
We don't have tomcat servers at all for client sites, if you are getting a tomcat error it sounds like something being served up from your ISP cache or proxy serveror something like this.

This is on your website? or the control panel?
 
The error I get says "This is a server issue" and says that one possible reason for the error is a service like tomcat being down.

I don't know what is causing this.

I get the error randomly everywhere in the website, inside the admin control panel, browsing the forum, browsing normal html pages, everything.

There is a screen shot of the error message exact text attached to my ticket. If it was an ISP issue I would think I would get it on other websites as well. I use the internet all day long for my job, and have never seen this issue on any website except my own. I am on the internet from sun up to sun down designing websites.

Ticket ID: PVY-30837-148
 
For the last 2 day I have been having the same intermittent problem with with php scripts on web 5. It occurs on my own service account and on the accounts of at least 2 of my clients. See example.

I notice that at these times the control panel runs slowly, so perhaps it's just congestion between Jodo and my ISP.....
 

Attachments

  • screenshot.jpg
    screenshot.jpg
    94.2 KB · Views: 55
For the last 2 day I have been having the same intermittent problem with with php scripts on web 5. It occurs on my own service account and on the accounts of at least 2 of my clients. See example.

I notice that at these times the control panel runs slowly, so perhaps it's just congestion between Jodo and my ISP.....
I think its unlikely that me and you have the same ISP, because I am in the USA and you are in New Zealand.

It seems I am not the only person getting the exact same error randomly since this week so its not an issue with my ISP.

And when tech support restarts apache it fixes the problem. So its a server issue.

I don't know what is being done about it, support keeps telling me that everything is working ok, nothing is wrong. If that is true why do I get the error messages
 

Attachments

  • error500.jpg
    error500.jpg
    65 KB · Views: 50
For the last 2 day I have been having the same intermittent problem with with php scripts on web 5. It occurs on my own service account and on the accounts of at least 2 of my clients. See example.

I notice that at these times the control panel runs slowly, so perhaps it's just congestion between Jodo and my ISP.....

That it quite a bit different than tomcat errors. Tomcat is not even installed on the web server, so it can't give errors. Praveen has resolved a perl abuse issue on a domain on web5.
 
That it quite a bit different than tomcat errors. Tomcat is not even installed on the web server, so it can't give errors.

I haven't suggested it is Tomcat. The error message generated by H-Sphere is obviously a generic one indicating some service is down. I am just reporting that I have seen the same error as Kensino, about 4 ot 5 times over the last 2 days.

Each time it happened, it took 2 minutes before H-Sphere threw up the error page (1 minute 59 seconds to be precise). The symptom only appears for a few minutes each time. I notice it happening while working using a back-office application (php) hosted on a sub-domain under my service account. So far I have identified that when it happens, it affects php scripts on 2 other accounts also hosted on web5, but not plain HTML pages, It also does not affect php scripts on web7 or web13.

If it wasn't for the fact that I use the back-office script in sittings of an hour or so at a time, I probably would not be aware of the problem. Certainly my clients are unaware.
 
OMFG I MY WEBSITE IS DOWN AGAIN. At 6:46 PM -600 It is completely down with random tomcat error message, I've tried a ton of other websites and my website is the only website I can't connect to.
 
I did PING on 8 different websites, Google, JodoHost, Microsoft, etc... All working correctly.

I did PING on my webisite and it says "Unable to resolve host. The server is not responding."

I still think I might have to switch hosts. This has been almost a week now and nothing getting fixed. If it was my ISP then all websites would be down. Every single website I try is working correctly except mine.

I just checked with my dad who lives 5 states away. He tried to load my website and got an error saying tomcat was down. Its not just me and I've been holding in Live Chat for 10 mins.
 
It just came back up at 7:00:00 PM -600, right on the dot.

Edit: As of 7:06 PM -600 its starting to run really laggy and slow again, pages are loading but they are taking a good 30-40 seconds to load.

Edit: 7:09 PM -600 Its offline again just says "Page Cannot Be Dispalyed" now.
 
@Kensino, they are not Tomcat errors. The are "Internal Server Errors". The error description mentions Tomcat by way of an example of a service.

Haven't seen the error today, and I'm hoping I won't. Been checking regularly for last 15 minutes. No sign of problem or even slowdown.

Although I don't think it is the case here, page loading problems don't have to be related to only Jodo or your ISP. When you're at the end of the world like we are here in NZ and most Internet traffic is international and not domestic as in USA, you soon learn that there can be many reasons why some sites behave normally, some load slowly and some don't load at all :frusty:
 
I am loading up your site alright, but what you are saying is totally different here, ping not working, site down, they are different issues fully. It is NOT a tomcat error, that is a "for example" error text, it is not saying tomcat is down, there is no such thing as tomcat on your server.

Praveen has looked through your logs as well here, as you have a ticket in as well he is actively checking and monitoring it.
 
Praveen has moved your site away from fastcgi, and seeing if you continue to see this issue or not.
 
I don't know by my website is complete offline now again. I get a "Page Cannot Be Displayed" error now. For the past several minuets.

Most likely causes:
The website is under maintenance.
The website has a programming error.
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

Tell him to check it right now.
 
I don't know by my website is complete offline now again. I get a "Page Cannot Be Displayed" error now. For the past several minuets.

Most likely causes:
The website is under maintenance.
The website has a programming error.
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

Tell him to check it right now.

check the status forums, he was changing it and the other mode has an error, he's working on it.
 
Ah, well I figured it was just the normal, as Its been up and down so much lately.

Should be better now, the problem is a known issue. I did not know that web3 was running in this fastcgi mode.

We knew it would have problems as it does not have enough file descriptors compiled in and is a bug, we've got it reported. It is off fastcgi mode now.
 
Back
Top