The new server are currently setting up and mounted it will be installed as soon as possible, there some chance that the old server come back online but please try to don't do major modification on your site if the server came back as those will be lost.

Backup will be restored from today as we started newest backup as soon the server comeback earlier, this is a emergency maintenance and free month will be applied to every account affected simply open a ticket to billing to request the free month before September 30th

Please bear with us while we resolve this issue.

ETA: 1hPM EST (GMT-4) account will comeback once the server are properly configured and secured, everything should be completed by 1hPM but your site might be back online early before ETA.

UPDATE 12h30PM: Some data need still to be moved, so we need to update ETA to 3hPM

UPDATE 15h30PM: Most account has been restored there around 10 account remaining.

UPDATE 17h30PM: Everything has been fixed, Fantastico will need to be reinstalled but other module are already installed.

We’ll let you know what’s going on as things progress!

Update – Sept 1th 14h00pm: Filesystem check found inconsistencies and is repairing them, so while this will not take days and days and days, it may be a few more hours.  We apologize for the inconvenience, and will get you back up and running as soon as possible.

Update – Sept 1th 17h45pm: Unfortunately, this is taking longer than expected to complete. There’s not much else we can do until the fsck is complete so that data doesn’t get corrupted. We will update this post as soon as it is finished.

Update – Sept 02th 9h00am: Well, we started the rebuild currently, cPanel will be installed and site restored and we hope to get it setup by the afternoon.

Update – Sept 02th 13h00pm: Hello, as we talk the service as been restored, we will announce a small maintenance windows to within a couple of week for this servers since it might return on read only mode.

Update 8hAM:

After the upgrade we mentioned some strange issues on the host server,
we have found the problem the problem is an overheated IOH (North Bridge).
We will replace the motherboard of the server within one hour, sorry for
this inconvenience.

_________________
Update 9hAM: 
The problem still exist with the new motherboard of the same vendor, on moment of writing this post our supplier
is on his way with a new motherboard of another vendor for this server. 

This means the server will be offline once again for 30 till 40 minutes.

We know this is not fine, but we want stable host servers for our customers, we hope you understand that.
We will do our best to reduce the downtime of the virtual private servers.

---------

Update:

The motherboard is replaced and the virtual private servers are running again.
It looks like the host server is stable again, but we will still monitor closely.

This account is currently locked out because a brute force attempt  was detected. Please wait 10 minutes and try again. Attempting to login again will only increase this delay. If you frequently experience this problem, we recommend having your username changed to something less generic.

Run the following as root in SSH.

mysql cphulkd
mysql> delete from brutes;
mysql> delete from logins;

Update: we got confirmation from our staff engineer that the problem would be fixed before 6hAM EST
Update: NL4 got a jump start and is wheeling it down the highway now. If you are still having issues with a site hosted on this machine please contact our support team from the cP.

1) Go to WHM > Tweak Settings and change the Apache port:

The port on which Apache listens for HTTP connections. Specifying a specific IP will prevent Apache from listening on all other IPs. (default: 0.0.0.0:80)

To:
0.0.0.0:8081

----------

2) Grab a copy of the nginx installation script:

-----------

3) If you receive this error when trying to install:

access key doesn't exist create it in WHM

Then go to WHM > Cluster/Remote Access > Setup Remote Access Key and click on the "Generate New Key" button.

4)  At that point, then re-run "./nginxinstaller install" command. Rebuild Apache and then restart nginx and Apache

/scripts/rebuildhttpdconf
/etc/init.d/nginx restart
/etc/init.d/httpd restart

There seems to be some issues with Global harddrive and we think we should replace this disk asap. As the drive is going into read-only mode frequently.

The machine crashed after the raid array became degraded and upon rebooting the file-system went into read-only mode so we will need to take the machine down into single user mode to run an fsck (file-system check).

Unfortunatly since the issue is recurring, we prefer to remplace directly the hdd!
Here are the errors being displayed in message log

Jul 16 14:24:30 global kernel: end_request: I/O error, dev sdb, sector 9215749
Jul 16 14:24:31 global kernel: ata3: EH complete
Jul 16 14:24:31 global kernel: SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
Jul 16 14:24:31 global kernel: sdb: Write Protect is off

ul 16 14:26:22 global kernel: sdb: Current [descriptor]: sense key: Medium Error
Jul 16 14:26:22 global kernel: Add. Sense: Unrecovered read error - auto reallocate failed
Jul 16 14:26:22 global kernel:
Jul 16 14:26:22 global kernel: Descriptor sense data with sense descriptors (in hex):
Jul 16 14:26:22 global kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jul 16 14:26:22 global kernel: 00 8c 9f 05
Jul 16 14:26:22 global kernel: end_request: I/O error, dev sdb, sector 9215749
Jul 16 14:26:22 global kernel: ata3: EH complete
Jul 16 14:26:22 global kernel: SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
Jul 16 14:26:22 global kernel: sdb: Write Protect is off
Jul 16 14:26:22 global kernel: SCSI device sdb: drive cache: write back

SQL are currently not usable due to read-only mode and we will keep the server online until a new disk is installed.

Hardware are not something we have control over it, so please bear with us until account are restored to a new hard drive.

Support Ticket will remain on hold since further update will come once everything is settled you can through follow our status page to see where the process is!

16h Update: Server will be shutdown to be able to install the new hard drive, server will be back to normal at around 21H (EST)

17h Update: HDD as been replaced and restore as been started account

1h24 Update: Account as been restored unfortunately the backup currently present is a 4 days old backup newest backup will be restore within few hour via rsync! Sorry about late update we we're busy with the drive and preferred restore account from backup servers to get your site online as more fast as possible! nameserver should resolve properly within few second from this update!

Update: Well, we lost the data on the old drive  actually this happened because the I/O tree was corrupted and drive had lost its FS type configuration, if you want us to restore any backup you take on your own open a ticket to get it restored.

20% of your monthly invoices will be credited to active user on NL1 server per our SLA!

Tomorrow our team will move up the servers again to a new tested hardware to be sure everything work properly, in this case nameservers and hostname will be completely different alpha will not be used anymore as nameserver and udns.in not used anymore, email with new details will be sent to every NL4 users with those details once the migration as been completed.

Domain purchased with us, will be automatically get there nameserver updated so you won't need to update it, however every other domain not registered with us will need to be modified.

Maintenance windows as usually during offpeak hour: 11h PM to 12h PM don't try to modify or edit anything during the maintenance  because it will not be available later.

Hopefully the new server will be stable and recurring issue you are experiencing fixed.

UPDATE:

Postponed to 29 June 5hPM to 6HPM on 29 June

UPDATE 29/06 6hPM:

The Migration as been successfully completed.

All files on UNIX (including Linux and other UNIX variants) machines have access permissions. In this way the operating system knows how to deal with requests to access the files. There are three types of access:

• Read - Denoted as r, files with read access can be displayed to the user.
• Write - Denoted as w, files with write access can be modified by the user.
• Execute - Denoted as x, files with execute access can be executed as programs by the user.

Access types are set for three types of user group:

• User - The owner of the file.
• Group - Other files which are in the same folder or group.
• World - Everyone else.

The web server needs to be able to read your web pages in order to be able to display them in a browser. The following permissions need to be set in order for your web site to function properly.

• All HTML files and images need to be readable by others. The value for this is 644 (readable by User, Group and World, and writable by User). It is set automatically when you upload files.
• All folders need to be executable by others. The value for this is 755 (readable by User, Group and World, writable by User, executable by User, Group and World). It is set automatically when you create a folder.
• All CGI files (all files in the cgi-bin folder) need to be executable by other. The value for this is 755 (readable by User, Group, and World, writable by User, executable by User, Group, and World). It is not set automatically when you upload files. You need to change file permissions manually.

It is important that none of your files or folders is writable by anyone else. Any file or folder which is writable by others can be erased by them.

Scheduled Maintenance on 09/06/2010 @ 3H AM to 3H30 AM

*Scheduled maintenance may change at any moments a new email will be sent out in case.

UPDATE: Migration as been completed successfully