PDA

View Full Version : 02/01/07 - VPS Security Updates


Jeff
02-01-2007, 12:43 PM
Today, Thursday, February 1st, at approximately 3 PM EDT, we will be applying critical security updates to the following VPS nodes:

VPS1
VPS2
VPS3
VPS4

This will require reboots of each node.

Q. How can I determine which VPS node I am hosted on?
A. Traceroute to your VPS, and one of the last hops will appear as eq.ash.v#.myriadnetwork.com, where "#" will be the number that corresponds to the node you are hosted on.


Q. How long will the downtime be?
A. This is not able to be determined until the maintenance is fully complete. Any VPS nodes that have maintained prolonged periods of uptime may require an automatic file system check (fsck). The length of time for fsck runs depends directly on the size of the disk. Some VPS nodes have larger disks than others.


Q. I was not notified about the downtime!
A. Please, visit the following thread which explains how to automatically receive notifications, via email, of new threads posted in the Server & Network Status forum: Automatically receive notifications (http://forum.myriadnetwork.com/showthread.php?t=113)


Q. FTP isn't working since my server was rebooted.
A. The cause is almost surely due to the FTP service not being in the startup scripts.

There are 2 options for restarting the service:

1. If you are using cPanel, log into WHM, and under the Restart Services section, and click the "FTP Server (ProFTPd/PureFTPd)" link. Or,

2. As root from the shell:
/etc/rc.d/init.d/pure-ftpd start

If you want FTPd to start up at reboot time, add the following line to /etc/rc.d/rc.local:
/etc/rc.d/init.d/pure-ftpd start

Alternately, you could do it the most common way, which is to add the symlink inside /etc/rc.d/rc3.d to point to /etc/rc.d/init.d/pure-ftpd (note that this assumes your ftpd service is PureFTPd, and not another service).

Jeff
02-01-2007, 03:59 PM
Hi,

The updates have not yet begun, but we will be posting information when we are ready to proceed.

Jeff
02-01-2007, 05:01 PM
Maintenance on VPS1 will begin shortly.

Jeff
02-01-2007, 05:24 PM
VPS1 is being rebooted at this time.

Jeff
02-01-2007, 05:29 PM
After providing 277 days of continuous uptime, VPS1 is now running a mandatory file system check (fsck). Updates will be provided when the server is back online.



/: clean, 92125/256512 files, 420019/512064 blocks
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda5
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
Activating swap partitions: [ OK ]
Finding module dependencies: [ OK ]
Checking filesystems
/vz has gone 277 days without being checked, check forced.

Jeff
02-01-2007, 05:36 PM
VPS2 is being rebooted at this time.

Jeff
02-01-2007, 05:49 PM
VPS2 is now back online as are all VEs on the node.

Jeff
02-01-2007, 05:52 PM
VPS3 is now being rebooted and will undergo an fsck.

Jeff
02-01-2007, 05:57 PM
Details on the VPS3 fsck:


Remounting root filesystem in read-write mode: [ OK ]
Activating swap partitions: [ OK ]
Finding module dependencies: [ OK ]
Checking filesystems
/vz has gone 284 days without being checked, check forced.


We will provide an update when it is back online.

Jeff
02-01-2007, 06:43 PM
VPS1 has been online for about 18 minutes now and all VE nodes are up.

Jeff
02-01-2007, 06:47 PM
VPS3 is now up and VEs are being started.

Jeff
02-01-2007, 06:53 PM
All servers on VPS3 are now up.

VPS4 will be done later this evening - anywhere from an hour from now to later some time.

Jeff
02-01-2007, 08:04 PM
VPS4 will be rebooted within the next few minutes.

Jeff
02-01-2007, 08:12 PM
VPS4 is up and VEs are coming online now.

Jeff
02-01-2007, 08:16 PM
All VDS servers are now up and running.

That concludes this maintenance. Thanks for your patience and understanding as to why these critical upgrades were applied.