Recently the Apache recompailed with eAccelerator after that the below error log has created and also the Apache got crash when reach high traffic.
[notice] child pid 13013 exit signal Segmentation fault (11) [notice] child pid 13054 exit signal Segmentation fault (11)
Due to this problem I ran the /scripts/upcp --force and again recompailed the Apache with eAccelerator.
later the signal Segmentation fault error not created but instead of above error the following error has been creating. And also again recompailed the without eAccelerator still the below error creating.
Parallels Plesk autoinstaller emailed me 03:34 to confirm that Parallels Plesk was successfully updated, but ever since then /var/log/httpd/error_log has entries every 5 minutes stating 'child pid xxxxxx exit signal Segmentation fault (11)'.
i am having a problem getting a dedicated server running for Unreal Tournament GOTY. everytime i create a dedicated server i get this error in the console:
Log: AInternetLink Resolve failed: Can't find host master.mplayer.com (WSANO_DATA) ScriptLog: UdpServerUplink: Failed to resolve master server address, aborting.
I signed up with with Dediwebhosting in November of 2007 and canceled my service on good terms June 1st 2008. It was my first experience with a dedicated server and, at the time, my primary focus was a budget solution.
The server was used for hosting my web design clients (around 50), which were mostly smallish & semi-dynamic websites with an average of 4GB/month bandwidth per account. The domain linked in my signature was one of the sites hosted on the server.
Setup & Billing:
Being completely new to dedicated hosting, their sales team was very friendly and helpful with my novice questions. When I was ready to order, I faxed my photo ID & credit card info to them and was set up within a day. The entire process was a lot less painful than I was expecting.
I went with their B600 package (P4 2.8ghz, 1GB, 129GB HD, 100Mbit, 600GB Transfer) - which fit perfectly with the budget I was working with (85.00 + extra for cPanel).
Support:
Although they don't provide any management services, their support department was always quite fast (around 30 minutes) in taking care of any rDNS or IP requests I had. They also made a very good effort in trying to help me with some issues I was having with AOL's mail server (which never got resolved, but was no fault of their own).
Also, I think it also bears mentioning that their support personnel sound like real people. Instead of getting 'it's fixed' or 'this has been done' responses....they usually responded in complete (even multiple) sentences. That may not be important to you (and I don't really mind the short responses), but it was something I noticed and was appreciative of.
Reason for leaving:
Aside from the inability for my hosting clients to send/receive mail from AOL accounts (which was a big deal for the type of people I host), my primary reason for leaving was that my design business was growing and I was ready for an upgrade to more powerful hardware. I found a great deal on a dual-core system with Pacific Rack and decided to move on. I was also hoping that moving to a different data center would clear up the AOL problems (which it did).
They were quick to process my cancellation request - so no problems there.
Overall Experience & Recommendation:
Aside from the AOL issues, my experience with Dediwebhosting was very positive (and I don't blame them for the AOL issues). Their support was friendly, fast and they made an effort to help me with an issue that went beyond their service agreement.
As mentioned above, I rarely received complaints of service or network issues from my hosted clients...so I can vouch for reliablity. As my first dedicated server, I can also say that they helped to make the experience much less intimidating than I thought it would.
Their website is kind of ugly and in need of an update...but as a designer, I'm overly-critical of such things.
So yes, I would definitely recommend Dediwebhosting to someone looking for an entry-level, budget solution (they offer bigger systems, but entry-level is the one I have experience with). I can't promise that AOL would work for you...but I don't think you'd be disappointed with everything else.
As many of you may have already read my initial review or the New York NOC I wanted to leave an additional exit review of the company and share a personal recommendation.
It started a little over a month ago when I jumped VPS providers and initially purchase 2 VPS plans . Initially the boxes were rock solid. I could get to my websites, admin area, and have support tickets responded to in a timely manner. Roughly a week later I ended up moving another site to it’s own VPS . This is when I noticied my first issues. CONSTANT ERROR MESSAGES stating the backend was down and to please restart it.
I would launch a support ticket, roughly 2 hours later the backend would be rebooted and I could once again access the admin panel and do what I needed to. Like clockwork when I would try to login again later to my admin panel I would be hit again with the backend was down (hypervm would be in a constant refresh). Sometimes my sites would remain online and sometimes they would go down too. This got frustrating but was bearable (I thought). Within a few days I see a BIGGER problem arise. I woke up one morning to find error alerts coming in and realizing 2 VPS’s had been offline for hours on end. I again launch another support ticket for the backend to be rebooted. I get a response everything is ok so I go about my day. I later receive an e-mail stating all of my sites were showing a mysql connect error and panic. Come to find out they had corrupted this time when the backend went down, I repair and optimize and everything is ok. VERY next day I wake up and check my nightly logs to make sure the nightly backup was loaded onto my home server. I don’t see it and find I received an e-mail from lxadmin stating it could not backup the database. Once again…..corrupted. This has been going on since that time frame on almost a daily basis. The backups are iffy if they will come in since when the backend gets overloaded and crashes in the middle of the night, it immediately corrupts all db’s on the VPS. I could understand 1 VPS doing this…..but 3? Come on….
Now comes Thanksgiving, my boxes go down for roughly 5 hours before reboot and once again I have to repair them on a blackberry with ssh since I am away (never fun to type that on a bb). I am back online and go about my day…….then…..Friday. My box goes down at 5pm…..I send in a support ticket to have it rebooted. The next morning at 11am it finally gets turned back on and I get a response that it must have been on my end since everything looks ok from there (granted 3 monitoring services were all showing it down). Once again…..corrupted. I rebuild and think the SLA was 99.9% so I send in a nice message to ask about it. Here is the response:
Posted: 11/29/2008 12:33 Hey Guys. Since one of the VPS accounts was down for 17 hours do I qualify for the 99.9% SLA? (3 Monitoring Services show the outage happened at 5:34PM last night and I have recovery notifications for this morning at 11:16AM) Thanks ---------------------------- IP Address: 71.76.239.xx Andy StaffPosted: 11/30/2008 20:49 Hi Ryan, Unfortunately our SLA applies to network uptime and not power or hardware related. I'm sorry for the inconvenience. ------------------------------- The New York NOC Inc. www.thenynoc.com Visit our new forums! [url]
So……99.9% SLA does not cover if no one is in the datacenter to reboot the box because it is off-line…..I thought SLA’s covered your box being on-line, am I wrong?
So now after too many corruptions to count, support taking longer and longer in between responses I am left looking over my books. Last year alone between Thanksgiving and the following Sunday I brought in roughly $2300 dollars in sales. This year for the past 4 days I have brought in $10…… I have had some longtime recurring customers so I asked them for any feedback on what we could do to earn there business again. Out of 40+ people all but one stated that if I could fix the sites downtime they would return (the other responses was of course to lower prices). Second suggestion they had was to fix my e-mails from ending up in their spam box. Yes I was sold ALL dirty ip’s which had all been blacklisted. Some major isp’s worked with me and allowed me in…(some)
Before I get flammed for choosing these guys, they truly were great up front so obviously I got fooled. I have no doubt they are great for some people but I simply can not drive my business into the ground because I went cheap and in the end got what I deserved. I moved to futurehost today and almost **** myself when a response ticket was answered in under a minute (kinda scary for a low priority ticket).
With this said, before you consider NewYorkNoc simply ask yourself if your business or site is important to you, if you can afford to lose business, and if you want constant downtime along with mysql corruptions daily. I am not saying they are the worst as they were helpful at first. Just EXPECT that when the deal is that good, you are being oversold. There is no other explanation in my books.
To sum this up:
Uptime: 3 out of 10 (there were up sometimes) Customer Service: 2 out of 10 (would have given higher I did not have to repeatedly e-mail over the backend issues) Price: 10 out of 10 (admit it, the price point these guys have is good) Value: 1 out of 10 (I made a bad choice, I lost a ton of money in business and now have to work hard to recover my losses and rebuild relationships) Recommend to others: 2 out of 10 (why 2? This place might be good for offsite backup maybe?)
This review is NOT out of spite due to my recent downtime. This review is merely my opinion and personal experiences and not written to bash NYNOC. If your happy with them then you are doing well. If you are considering them…….I urge you to think elsewhere. All my data is off the VPS and I am running before the backend crashes again corrupted my DB’s.
Code: Non-zero exit status returned by script. Output stream: 'Failed to install site: Not Found '. Error stream: 'Failed to install site: Not Found '.
I hope your day is going good. I've been trying to fix a problem I had all week. I receive daily email notification that "example.[url]" does not resolve to any IP. However, when in WHM, it already contains Server Main Ip: 208.53.183.125. I've tried a few solutions from the web, but to no avail:
IMPORTANT: Do not ignore this email. The hostname (example.mydomainname.com) resolves to . It should resolve to 208.53.183.125. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.
Some are all of these problems can be caused by /etc/resolv.conf being setup incorrectly. Please check this file if you believe everything else is correct.
You may be able to automaticly correct this problem by using the 'Add an A entry for your hostname' under 'Dns Functions' in your Web Host Manager
1) Within WHM, I have the following:
-Add an A entry for your hostname (I only have one listed) Hostname: example.mydomainname.com Server Main Ip: 208.53.183.125
-Primary/secondary nameserver Primary Nameserver: ns1.mydomainname.com (A entry = 208.53.181.26) Secondary Nameserver: ns2.mydomainname.com (A entry = 208.53.181.27)
-Additional IP my webhost gave me to use: 208.53.181.26 (used in primary name server) 208.53.181.27 (used in secondary name server) 208.53.181.28
-Current DNS Zone listing: example.com (my website URL that is currently working) example.mydomainname.com (hostname I made myself that contains the server main IP) ns1.mydomainname.com (A entry = 208.53.181.26) ns2.mydomainname.com (A entry = 208.53.181.27)
2) My edit "edit /etc/resolv.conf" contains the following: Search localdomain nameserver 66.90.68.25 nameserver 66.90.68.26
Issue: I receive daily email notification that "example.mydomainname.com" does not resolve to any IP. However, when in WHM, it already contains Server Main Ip: 208.53.183.125.
I've been having this problem for a while now. I have a dedicated linix server running with the cpanel. I've setup my own nameservers and for the most part it all runs without a problem. However, every now and then the domains will not resolve for many people.
This may only last a few minutes but it happens regularly. There doesn't seem to be any pattern. The server is still available via IP address. Also, any domain name set as a nameserver with the registrar is not affected by this problem. All other domains are affected. This problem has persisted over many cpanel updates.
I have gone through all the nameserver files (I can think of or have read about) looking for something that may be causing this but everything looks normal.
Currently I get problems that domains at certain places not open.
Like e.g I write my server IP XXX.XXX.XXX.XXX it works fine and I get ping reply also, but at the same time I write [url]it would not resolve.
Similarly in web browser I write server IP it gives cpanel page but on same computer I write [url]I get page cannot be opened, when I refresh the page at certain times then it would open. Now once it is opened in the same computer it would work fine here.
In some internet connections it works fine i.e no problems, in some connections get similar problems that domains does not resolve properly.
the DNS Server never resolves, i create one account on my server, i put the nameservers... about 6 Hours ago and nothing, i setup the Domain DNS and nothing, what can be? how i can fix this?
My VPS was a clean build 2 weeks ago and so far i have installed cpanel and configured everything and added accounts. I began that one of my scripts that uses gethostbyaddr($ip) was failing to resolve any of the ip's it received. I made another PHP file to test this, with this code:
PHP Code:
<?phpecho file_get_contents[url];?>
Resulting in:
Warning: file_get_contents() [function.file-get-contents]: php_network_getaddresses: getaddrinfo failed: Name or service not known
The thing is, the VPS is resolving domains just fine
;; ANSWER SECTION: google.com. 300 IN A 64.233.167.99 google.com. 300 IN A 64.233.187.99 google.com. 300 IN A 72.14.207.99
;; AUTHORITY SECTION: google.com. 343652 IN NS ns2.google.com. google.com. 343652 IN NS ns3.google.com. google.com. 343652 IN NS ns4.google.com. google.com. 343652 IN NS ns1.google.com.
;; ADDITIONAL SECTION: ns1.google.com. 343143 IN A 216.239.32.10 ns2.google.com. 343143 IN A 216.239.34.10 ns3.google.com. 343143 IN A 216.239.36.10 ns4.google.com. 343143 IN A 216.239.38.10
Yesterday we registerd and created 2 domains in our server. Everything is ok, files uploaded, dns zones created, httpd virtual host created...
The problem is that trying to browse the site trough http://www.site.com redirects me to [url] my main server IP address, this page shows a cPanel Welcome message.
But, using [url], the site is loaded ok, withouth any problems.
DNS zone shows:
Code: ; cPanel 11.11.0-BETA_16977 ; Zone file for site.com $TTL 14400 @ 86400 IN SOA mydns1.wolo.com. admin.hostingserver.com. ( 2007092601 ; serial, todays date+todays 86400 ; refresh, seconds 7200 ; retry, seconds 3600000 ; expire, seconds 86400 ) ; minimum, seconds
site.com. 86400 IN NS mydns1.wolo.com. site.com. 86400 IN NS mydns2.wolo.com.
site.com. IN A IP_ADDRESS
localhost.site.com. IN A 127.0.0.1
site.com. IN MX 0 site.com.
mail IN CNAME site.com. www IN A IP_ADDRESS ftp IN A IP_ADDRESS Apache virtual host code
I set up a domain in plesk 8 (LAMP), but the www version of the domain doesn't resolve via the browser, wheras the non-www version does. I set the nameservers (and glue records) yesterday.
Why might this be? Could this be due to dns propagation?
i use centos based server. yesterday everything was OK. but now, when i connect via SSH, my server can't resolve hosts. wget, ping, or curl don't work. also i use VNC to remote desktop. when try to open a page via firefox, it says server not found.