Upon a shutdown or reboot, the system shuts down sw-collectd. Further along, it will end wdcollect and the following will occur:
init: psa-wdcollect main process (pid) killed by KILL signal init: psa-wdcollect main process ended, respawning wdcollect[pid]: Language en-US is used for sending e-mail messages. wdcollect[pid]: Failed to connect to database server during the startup. New attempts will be made if needed. wdcollect[pid]: Server started
I believe this is preventing the un-mounting of drives which in the end freezes the shutdown process on:
Please stand by while rebooting the system...
After this occurs, I have to force the VM off and then boot again.
I have a very perplexing problem. Like clockwork, every 7 days I find my Windows 2003 server to be unresponsive. I use remote desktop to login to find that it has unexpectedly shutdown. The even code is 6008 and I researched it through the MS link and it says it can be cause by unplugging the power cord or manually rebooting the server through a switch. Is it possible the UPS at my host has my server on some sort of timer that automatically kills the power once a week? There aren't any scheduled tasks to reboot it, and this is a fresh install as far as I know.
Futurehosting did a migration this morning on my VPS and after the migration my site is reverted back to old backup in February. Both on my old VPS and new VPS Ips shows the same old backup files not the current one. I panicked and quickly told the support and they did the restoration to the recent backup file from my old VPS but I checked my site again and its still show the same old files. I have lost total of 3 months of hard work and there's no way for me for getting the files back. From their VPS plan "All VPSs include Future Protect which makes a backup every 6 hours." I did not get the recent backup instead of last February backup. This is outrageous and there's no sleep for me on tonight while I'm going to create all those missing files.
Why has Ipower turned into a such a poor hosting service? I have been with them for years and now they are leaving me little choice, but to find a new provider. For years they were able to provide me with a smooth service. Over the last year I have experienced tons of down time, long wait time for customer service, and recently downed email service for way toooo long.
I recently logged into my Windows Server 2003 OS Server via Remote Desktop and was met with a message/box saying Why did this computer shutdown. It had a dropdown field for a reason and then empty text fields for Problem ID and Comment.
What steps can I take to figure out what happened?
So justgotvps.com gives me a pageload error, and now when I go to any of my (many) domains that are hosted on JustGotVPS I get some "Close my sale for me" BS site?
I can't SSH/Telnet into my VPS anymore (connection refused). Did I just get scammed for 6 months worth of fees? Time to reverse the charges; I'm more pissed because I just got set up there and I don't have a recent backup with the new configuration...
Wanted to share a bit (read vent a bit if you're cynical ).
Just got the following e-mail from hostmonster.
----------- Dear Dale:
Your web hosting account for ibycus.com has been deactivated (reason: site causing performance problems).
Although your web site has been disabled, your data may still be available for up to 15 days, after which it will be deleted.
If you feel this deactivation is in error, please contact customer support as soon as possible.
Thank you, Support
For support go to Toll-Free: (866) 573-4678 -------------
Apparently, there are two files on my website that are being hit quite a bit, and causing the server to slow down. (I admit, its a busy site, and the files are very big).
The files aren't new there, and neither is the traffic, but the plug was pulled with no warning what so ever, and no offer of remediation on their part beyond refunding the remaining portion of my contract (I would hope so too!).
I can understand that they may not be able to continue to host my site due to the volume of traffic it generates, but they really could have handled this much better.
I am a SolarVPS customer. So far, I have been really happy with their service - setup was very smooth, I had to contact support a couple of times at the start and they were really quick, and otherwise I've had simply no problems.
I was alerted yesterday to the fact that my site was down. I immediately logged into the box, and found that Apache and MySQL had stalled. I restarted them, and everything was ok. So then I started to look into the problem.
Then I noticed this in my logs:
Sep 3 23:07:26 myvps shutdown: shutting down for system halt Sep 3 23:08:41 myvps exiting on signal 15 Sep 4 03:14:22 myvps syslogd 1.4.1#18: restart.
It seems that my VPS was shut down for 4 hours and then brought back up. My Apache and MySQL didn't come back up properly after the restart (ok, my fault here, a configuration issue), so I was down for about 17 hours.
Anyway, I didn't do this shutdown, and I don't think my box was hacked and someone else did it, because even if they did, by my reasoning, it wouldn't have been down for 4 hours.
So I wrote an email to SolarVPS. They got back to me really quickly, asking me to send my server ip's and my root password (I had initially only sent my customer number). I was not really happy sending my root password over email to them, so I just sent them the server IP's.
I then got an email back saying that it was standard procedure to send my root password to the over email, and that it was secure because their helpdesk is secure. I don't know how they are securing the email connection from me to their helpdesk though (of course, it isn't secure, because email is sent in plain text), so I still haven't sent them this. I don't need them to log into my server anyway, I can see that it went down, I just wanted to know if they had brought the machine down for a reason. The whole root password over email thing is not the problem anyway.
What concerned me is the rest of their response.
They told me that they had not brought the machine down on purpose. I sent them the log lines I pasted above, and their response was:
- shows that your VPS has been shut down, just like the owner of the VPS would have shut it down using "halt" command. This issue appears when the VPS is overloaded (RAM is almost 100% used, and CPU is upto 90-100%), and in this case Virtouzzo shuts the VPS down in order to avoid resources abuse on the entire node and not to affect the other VPS's.
This is the part that concerns me. As I understood it, the Virtualization software is there to keep you in a box, and restrict the amount of resources that a person can take up so it doesn't affect others. If my server is under heavy load, I can understand if it becomes slow, but I don't find it acceptable for it to be shut down for 4 hours!
Is this usual policy for VPS's? If this is the case, I guess I'm going to have to look for dedicated, because this is not acceptable to me. Although my server is rarely under high load, I don't want to have to worry that it might disappear for hours if it is.
It would be great to hear some opinions from people with more experience in this area than me. If true, this is definitely something people should mention as a disadvantage to VPS's.
I have Plesk 11.5 (service provider mode) on a Windows 2008 server IIS7.Most of my sites are developed in .asp and therefore i use a custom 500-100.asp error page that check s the IP of the visitor then displays either a friendly error, or if its my IP a full error of what has happened (it also emails me the error). This allows me to debug pages easily whilst developing and to keep an eye on anyone trying SQL Injection hacks on my sites (as the error and email also have session variables and IP address).I dont have root access to the server as it is a Webfusion dedicated server.I have following the Plesk documentation -
1) Switch on custom errors for the subscription 2) Look in virtual directories and navigate to error documents 3) Find the error in question (500:100) and change it to point at either a file or URL
FILE - I had the data centre add in the 500-100.asp error page in to the virtual template so that my page is available in the list of virtual files - this didn't work but that maybe because its not a static page??
URL - when i add the path it says its incorrect, if i add a fully qualified address, it accepts it but it doesn't work.give me a specific example of the URL that can be entered relative to the root as the format in the documentation isn't accepted. The last step is to restart IIS which is also an issue as i cant seem to do this from the Plesk panel..It is as if it isn't catching the 500:100 error, and only catching the general 500 error??
We are about to shift from linux server to plesk for some reasons given by our management.
I am interested to know that Plesk 8.X or 9.X comes with MS SQL edition in built? or we have to install that separately? This is for a hosting server so the server should have both MY SQL and MS SQL both, how to shift this in plesk, is it possible?
Also if we install plesk will it come with tomcat server? or not? some hosting clients need Java with tomcat?
I have a windows server with plesk 7.6 i want to install the new version of plesk 8.6, how can I do? I want my domain names (4) be working well with the new version of plesk. I don't know if I backup my domains, plesk 8.6 will recognize from 7.6.
the main reason I want plesk 8.6 is because i want to use the latest version of php and also i want to install wordpress and I think the new plesk will be working fine with these programas
do you have any ideas how can I keep my domain working after I install new plesk?
The my sql seems to take much load in my VPs, configuration file is as follows
set-variable=local-infile=0 datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock user=mysql # Default to using old password format for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). old_passwords=1