Archive for the 'Tech Talk' Category

Recover a Corrupt File System

The Linux File system

The Linux file system is a collection of directories and files stored on the disk. You can verify which file system your server utilizes by running the below command:

[root@example ~]# df –T
Filesystem    Type   1K-blocks      Used       Available    Use%   Mounted on
/dev/sda1     ext3      5160576    1795916   3102516    37%       /
tmpfs            tmpfs     1048576         0            1048576    0%     /dev/shm

By running the command df –T  (print file system type) , we can see this server has an Ext3 file system. Ext3 is an enhanced version of Ext2 with improved journaling, which allows for greater reliability and even faster file system recoveries.

A Corrupt File System

If you are in the middle of doing a system update or scaling the machine’s resources and the machine is then powered off unexpectedly, the server might suffer from a corrupt file system. When the file system becomes corrupt, it is unable to boot into normal mode.

You are able to verify if the file system is corrupt by rebooting the machine into Recovery through the Zunicore User portal. Once the machine is rebooted into Recovery, you can try to run the following commands to determine the file system’s status:

[root@onapp ~]# mkdir /zunicore
[root@onapp ~]# mount /dev/sdb1 /zunicore
EXT3-fs warning: mounting fs with errors, running e2fsk is recommended

Restore the Corrupted System

You can easily restore a corrupted file system while using Zunicore’s Recovery feature. To correct the file system, you will need to run the fsck command. Fsck is a file system check utility that can check the system for inconsistencies and also repair discovered issues.

When you are using the Zunicore Recovery feature, your disk’s drive is labeled sdb1. So, you will need to run the fsck command against /dev/sdb1.

[root@onapp ~]# fsck -yf /dev/sdb1
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Filesystem contains large files, but lacks LARGE_FILE flag in superblock.
Fix? yes

The fsck option –y will fix errors without prompting you each time the system attempts to fix a discovered issue.  The –f option will perform a quick check of any system that was not properly unmounted  before a system halt.

Once the fsck command is complete, you can reboot the system into normal mode.

Anycast DNS & Zunicore

Anycast DNS & Zunicore

At Zunicore, we have made it incredibly easy to add, remove, and manage domains with our Anycast DNS.

Anycast DNS provides a network of reliable DNS servers that are capable of adding automatic failover for the DNS servers, high availability, simplicity, and increased security. Anycast has built in reliability and high availability for DNS services because it is a thoroughly dispersed geographical network of servers functioning with “heartbeat” monitoring. Heartbeat monitoring continuously tests the server for functionality. If a server fails to respond to the heartbeat monitoring, the server will no longer be available for DNS services and will be removed from the routing table of available servers. Anycast is incredibly easy and simple to use because it allows a resolver’s query to be routed to the closest topological Anycast server using layer-3 routing.  Your DNS services are also more secure using the Anycast DNS system because decreased man-in-the-middle attacks against the DNS servers and localized DDOS attacks that would affect only a section of the Anycast system instead of the entire Anycast network.

To begin managing your domains with Anycast DNS through the Zunicore User portal, you can use our Domain Management utility underneath the dropdown menu Services  > Domains > Manage.

Make sure to read our step by step DNS Knowledge Base article ‘Zunicore DNS Management’ 

Create a Custom Zunicore Template

With last week’s blog post “Installing WordPress on your Zunicore Cloud Server”, we introduced how incredibly easy it is to set up a CMS on a Zunicore Cloud server. We would like to take that even a step further and show you how simple it is to create the CMS as a customized template so you can build future Virtual Machines with a preconfigured CMS . With using a preconfigured CMS web server as a template, you can save the steps of configuring the machine, installing the necessary packages, and creating a new database.

After making the WordPress server, the next step would be to create a backup of the server. This ensures we have a known working copy of the VM stored in our Resource Pool. With a copy of our server stored as a backup, we can easily restore the server back to a known working configuration or even create a Template based off of this server.  A template of the server will allow us to easily provision a Virtual Machine with a pre-built Web server, database,  and CMS.

If you have already made the desired changes to your CMS, you will now make the backup. This can easily be done by clicking the ‘Create Backup’ button from the Disk tab on the Virtual Machine’s Detail Page.  For a more thorough walkthrough which covers backing up your Zunicore Virtual Machine, see our previous blog post “Server Backup”.

After you create the backup,  you are now able to create a Template based on that backup.  Below is an example of the backups listed for a Virtual Machine.  You can click  the ‘Convert to Template’ option to create the Template.

Once you select the Template Conversion button, you are then presented an option for naming the Template. Provide the Template a recognizable name so you can easily identify which Template to use for a provision. In this example, we will provide the customized Template the name: Blog Template.

Now, when you create a new Virtual Machine within the same Resource Pool, you will see the new Template as an Operating System option underneath ‘Custom Templates’.

After the server is provisioned, you can open your browser to the server and use the WordPress wp-admin to begin managing your new CMS with the WordPress Dashboard.

Making a Template based off a customized Web Server with your desired configurations and options allows you to take advantage of the incredible control Zunicore provides.  You can easily provision a new Virtual Machine, create a CMS web server, backup the server, and then create the server as a Template for future provisions within a matter of minutes using the Zunicore Cloud.

Installing WordPress on your Zunicore Cloud Server

We have a lot of web developers taking advantage of the Zunicore flexibility while building and hosting their sites on the Zunicore Cloud. Some of their design and site integration with Content Management Systems (CMS) is truly remarkable. Their ability to create, customize, configure, backup, and even create the server as a customized template really showcases how incredibly advanced these users are and how easy it is for CMS developers to maximize efficiency using the Zunicore Cloud.

However, not all of our users are familiar with building a Content Management Server and web developing using Php or MySQL. So, to provide further insight into how simple it can be to set up a CMS using our Zunicore Cloud, we wanted to show how quick and easy it can be.

You will first need to install the basic packages:


These packages will allow you to build the CMS as a Linux web server and wget will retrieve the latest WordPress software.

#yum -y install mysql-server httpd php53  php53-mysql unzip wget


Make sure to turn on MySQL and Apache:

#service mysqld start; service httpd start

You will then need to make sure Apache and MySQL will start at run time:

#chkconfig httpd on; chkconfig mysqld on

Now, you will need to create a database for your WordPress server:

#mysql -u root -p
mysql> CREATE DATABASE wordpressblog;
mysql> GRANT ALL PRIVILEGES ON wordpressblog.* TO “wordpress”@”localhost” IDENTIFIED BY “zunicore” ;
mysql> Exit;

We use the below values for the configuration:

DATABASE name = wordpressblog

Username = wordpress

Password = zunicore

After you have created the database, change directories to /var/www/html. You will now download the latest WordPress package and unzip it in your directory:


Once this extracts, you can remove the download .zip and the unnecessary directory:

#rm ; mv wordpress/* ./ ; rmdir wordpress

Now, you will need to make wp-content/uploads and wp-content/cache writable by your web server:

#mkdir wp-content/uploads wp-content/cache

#chown apache:apache wp-content/uploads wp-content/cache

Next, you will need to edit the WordPress configuration file. First, copy wp-config-sample.php to wp-config.php:

#cp wp-config-sample.php wp-config.php

Then, edit /var/www/html/wp-config.php :

#vim /var/www/html/wp-config.php

Change the WordPress values correctly to match the database name, user, and password that was created earlier:

DB_NAME = the database name (wordpressblog)

DB_USER = user name (wordpress)

DB_HOST = localhost


You can now complete the set up your of WordPress CMS. Open up your web browser and enter your IP address/wp-admin/install.php in the url field. You should see the WordPress Welcome message on your browser.  This will start the process of creating a WordPress admin, adding the site name, and a description to your site:

Once you are done, you will then be forwarded to your first ever CMS!

At any point of the installation you are not comfortable with setting up the CMS or you would prefer an even easier experience, Standing Cloud provides you with a  CMS of your choice and an incredibly easy, point and click install process all while using the Zunicore Cloud.

Backup your virtual server through ssh to another cloud server

We offer a number of awesome features  our users can take advantage of so they can experience the true flexibility and control we believe they deserve. However, sometimes , we have some server administrators that would really prefer to do some tasks only on the command line  and call it a day. And although we offer a number of simple to use, intuitive features to  make server administrating as easy as possible, they have become hard wired with preferring to  run a command or two to find the solution they need.

We recently added new backup features in our portal that would allow users to make on-demand backups, scheduled backups, restore the server from a backup created, and even make a customized template from a backup. And despite how incredibly easy  these features are, a handful of  our Linux users still prefer to run their run backups through cron or SSH to another server. So for example, if they had a server in the UK and wanted to make sure they had access to their files at any time regardless of the status of their server, they would backup the server through SSH to a server in Toronto.

Occasionally, Support will receive a ticket from a client curious on how to backup the server through ssh. And all though we recommend to all clients that they take advantage of our backup utility in the Zunicore User portal, we offer our users the following command for backing up a server over ssh :

tar -cvpzf backup.tar.gz --exclude=/backup.tar.gz --exclude=/proc --exclude=/lost+found --exclude=/sys
 --exclude=/mnt --exclude=/media --exclude=/dev / | ssh username@IPADDRESS "(cat >filename.tar.gz)"
  • tar    command to create the archive
  • -c    create a new backup
  • -v    verbose mode
  • -p    preserves the permissions of the files
  • -z    compress the backup file with gzip
  • -f    the  file name
  • -exclude=    which directories to exclude from the backup.  This can change depending what you would like to achieve and what directories you need backed up.
  • |    pipe the output of tar through ssh  which will then run the cat command on Server B
  • ssh    remotely execute cat on the remote server to create the file name
  • username    the account on the remote server with root priviledges
  • IP   Address    the remote server you are backing up  to
  • filename    the destination file name you wish to give to the new backup on the remote server

In the above example, we have backed up the entire ServerA (excluding mounted directories, lost and found, proc, and media) to ServerB. We provide the back up a distinguishable name we can easily search for when we need to find the file for quick reference.

Once the command has finished, you can log in to the backup server (ServerB) and check if the backup was copied over.

Server Backup

At Zunicore, we understand at anytime while administering a server anything can happen. You could accidentally replace a directory, install a new package without thoroughly testing it’s impact on dependencies, or even overwrite an important configuration file. However, you can have peace of mind knowing Zunicore can get your server back online and restored within only a few clicks.

If you have purchased backup storage space for your Resource Pool, you can make a full backup of your server by selecting the ‘Disk’ tab on your Virtual Machine Details Page. You have the option to backup your server on demand and also to auto-schedule backups. Having the ability to backup your server on demand provides you the control you have come to expect from Zunicore while auto-scheduling your backups continues to meet your need for flexibility.

Once you have made your changes, installations, and configuration to your Zunicore server, click ‘Create Backup’ to instantly add the backup for your server. Now, if you need to revert your server to an earlier configuration, you can click the ‘restore’ icon to restore your server.

To read more about backups and your Zunicore server , log in now and read our Knowledge Base article Backup Virtual Servers and Template Creation


Why use Autoscaling

Zunicore Austoscaling is a feature which provides select operating systems the ability to dynamically add CPU cores and/or RAM as needed during load conditions.  When the load is removed, users are able to retire the Autoscaled CPU and/or RAM away manually so that users can save on compute resources.

What is Autoscaling

Zunicore has the ability to monitor running virtual images’ CPU and RAM load, and then to dynamically provide additional CPU and/or RAM to virtual images under load. The criteria for when Zunicore is to add the additional resources are set by the user.

For instance, Zunicore can be directed to add additional CPU cores at the rate of 25% (one fourth a CPU Core) per hour if the CPU load exceeds 60% for more than 15 minutes.

Many operating systems cannot accept added CPU or RAM without rebooting, and currently none are able to release unused resources without manually scaling resources down by the user.  To get around this limitation, Zunicore offers Autoscaling Load Balancers that allow additional virtual servers to be spun up and take load such as a burst of activity on a web site for instance and shutdown and remove servers when CPU or RAM load is gone.  While Autoscaling resources are used, the additional resources are billed hourly at a similar rate as normal non-Autoscaled resources, and those are in turn summarized on the monthly statement. Sign into your account to see our Load Balancing Knowledge Base article for creating a Load Balancer

Autoscaling is an ideal cost-control technique that allows a virtual image, like a web server subject to crowd-sourcing or other activity bursts, to automatically handle added load during peak hours.

Read the full guide  about enabling Autoscaling for your Zunicore Resources.

Twitter Updates

  • @PoonHealey Hello, We do not offer phone support for the Zunicore platform. You can get a hold of us with live chat. Live chat is av... 1 year ago
  • @artifaktCom Hello, An API will be available soon that will allow you to obtain this output. Right now, the API is undergoing signifi... 1 year ago
  • @jonathansuter Hello, We can reply back with any answers you need. Please update this with any questions that you have. 1 year ago
  • @RyanCorner Hello, We will forward this information to our development team. We will update this ticket when completed. 1 year ago
  • @beagile Hello, You would have to use the templates we offer. But if you spin up two VHDs on the server, you can always copy the data... 1 year ago
  • @indiejustin Hello Justin, Can you create a ticket in our internal system so i can verify you and then determine the issue of the VM. 1 year ago
  • @kangawallafox Hello Shaun. I am not seeing a ticket under your name. Please respond to the ticket via the user portal and we will respond. 1 year ago
  • @josephoenix Hello Joseph. Please submit a ticket to [email protected] stating you'd like to deactivate your account and we'll handle it. 1 year ago
  • @Open_Universe That is great to hear. If any assistance is needed, please let us know. Have a great day and enjoy your time in the cloud! 2 years ago
  • @Open_Universe If you can provide the email address that is associated with your account, we will create a ticket and inform you when ready 2 years ago


Get every new post delivered to your Inbox.