Problems with a godaddy VPS, DNS and control panel
Hi all I have come looking for assistance with an issue regarding a godaddy VPS. I actually found this site searching for information and after reading some guides figured its probably best to join and post!
Basically a friend of mine has jumped in at the deep end with a VPS and doesnt have the time or experience to manage it, and has asked me to work out what the problem is with it. Not that my experience is substantial but at least I know a few basics
Anyway the site has been fine for 3-4 months and then all of a sudden last week it kept going offline. The first thing I noticed was that the DNS was not resolving, and that the process "Named (DNS Name Server)" was not running. Typing the IP in the address bar would take you to the site so it seems there is something wrong with "Named (DNS Name Server)"...?
I also noticed that there was only one IP configured to both NS1 and NS2, to which I am unsure if that will cause a problem? I have just enabled error logging on the server and waiting for an error print out.
I am led to believe nothing was changed, other than possibly incoming traffic
I just found this in tubropanel.log (I think its the control panel log)
2011-02-22 15:00:02,870 INFO HsqlDbSubsystem: backupDatabase(): Moving shutdown.sql.1 to shutdown.sql.2
2011-02-22 15:00:02,871 INFO HsqlDbSubsystem: backupDatabase(): Moving shutdown.sql to shutdown.sql.1
2011-02-22 15:00:02,906 ERROR [/]: log(): Servlet action threw unload() exception
javax.servlet.ServletException: Servlet.destroy() for servlet action threw exception
Edit: In the past 30 minutes I have had to restart the serivce "Named (DNS Name Server)" twice - do you know how I can find out how/why it crashed?
Considering the information I was able to provide does it sound like a misconfiguration of the server or a resource problem or possible faulty hardware?
Try entering the domain name into http://intodns.com and see what the report says. It should give you some detailed information.
You can have both ns1 and ns2 pointing to the same IP address, although there are reasons not to do it. The main one I know is that if the server goes down, so does the name server, so it looks like the site has completely disappeared instead of just gone off-line. The end result is that email TO the server bounces back to the sender. If you have name servers "distributed" on different servers, then the sending mail server knows the site is valid but off-line and will queue the mail for delivery later. There is no reason to buy another IP address for the same server to have two separate IP addresses for name servers on it; there's no benefit that I know of, as both name servers go down at the same time.
Am I right in thinking that Named (DNS Name Server) requires tomcat to run?
Nope Tomcat does not require DNS to run.
DNS error cannot bring down your server but other services can cause trouble that bring down server including dns.
According to your initial inspection, it could be the control panel.
PremiumReseller.com Hyper-V SSD VPS USA London Singapore
Reseller Hosting Cpanel PURE SSD CloudLinux Softaculous
Windows Reseller Asp.NET 4.5 MSSQL 2012 SmarterMail Enterprise
Ideally, you shouldn't see any values other than 0 in the failcnt column. The other values will help determine what horrible memory settings they have at Godaddy if that's the issue. Post the results here please.
Thanks for posting it. Generally the memory allocation goes like this:
Java asks for a certain initial heap allocation. If your current memory seen in privmpages(held) is below vmguarpages(barrier), it gets it. If it's between vmguarpages(barrier) and privvmpages(barrier), it gets it only if there's enough free from the host.
When Java needs to grow the heap or allocate some memory for threads, this request process happens again. Sometimes it fails and increments failcnt. You currently have 1186 failed allocations there since last reboot.
It's a bit hard to predict whether it'll fail or not since it's based on how loaded a given node may be.
You might be able to constrain java a bit and tell it to only go up to a certain heap size. There's the Xmx option when starting tomcat via the java command line. Additionally, allocating the starting heap at the final size helps alleviate the recurring allocation problem. That'll be the Xms option.
java -Xms64m -Xmx64m ...
Java will still need to dynamically allocate more memory for threads on top of this so you need to make sure there's still a bit of buffer room left after the initial startup.
I understand 256MB isn't much room to play with. Other things to try are decreasing the stack sizes for certain programs to reclaim some idle memory.