Support of the day Posts

How to Prepare a Data Center for a Disaster

How to Prepare a Data Center for a Disaster

When it comes to planning any IT solution, preparing your data center for disaster with data backup is one of many items on an IT professional’s checklist. 

Some IT administrators take it seriously where others simply make sure the hardware and software is capable of handling the necessary business tasks before they configure everything to be backed up on a realistic schedule.  Once everything is in place, the system is disregarded and a disaster recovery strategy goes untested. (more…)

Minecraft Server – Setup Guide

Instructions to a user to manage Minecraft server:

1.       Login via ssh.

a.       Download an ssh client like putty.exe (http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe)

b.      After the download is complete run the putty application.

c.       In the “Host Name (or IP address) field enter the IP address provided above.

d.      In the “Saved Session” filed enter a name to refer to this server as and click “Save”.

e.      The saved details will now be available under the name you gave it each time you run the software.

f.        Click the name you gave it and click “Open” to launch the connection.

g.       The first time you connect you will be prompted to approve the security, click “Yes”.

h.      You will then be prompted for a user name, type “root” and hit enter. This user name is case sensitive. (your mouse does not work in this interface)

i.         You will then be prompted for a password, type the password provided in the server details email and hit enter. This password is case sensitive.

j.        You are now logged in

2.       Type ”./start” to start the server.

3.       To add your Minecraft user as an administrator of the Minecraft server type “op username”.

4.       You can now connect to the server with your Minecraft client software.

a.       Open the Minecraft executable you downloaded when you created a Minecraft account at Minecraft.net (https://s3.amazonaws.com/MinecraftDownload/launcher/Minecraft.exe)

b.      Enter the username and password provided to you when you purchased your account with Minecraft.net.

c.       Select to “Remember Password” if you’re on a private computer and don’t want to retype the password each time you log in.

d.      Click “Login” and then select the “Multiplayer” option.

e.      Click “Add Server” and type any name for the “Server Name” field, this is what it will appear as when you open the client not the server.

f.        Type the IP address provided in your server details email as the “Server Address”.

g.       Click “Done and it will return you to a page that lists all of the servers you have saved.

h.      Click the name you gave the server and then “Join Server”. This should connect you to your Minecraft server.

i.         You can issue additional moderator (operator) commands in the typing fields from the client by typing “/” before the commands.

i.      For example “/op username” would give that username operator rights.

ii.      For example “/ban username” would ban that user from connecting to your server.

5.       From the ssh interface (CLI – command line interface) type “help” for local commands that can be issued at the server.

6.       Other commands with similar format are “stop”, “deop”, “ban”, “gamemode” (0 for standard 1 for creative).

7.       To rollback the world to a previously saved version, stop the game and type “./rollback”. Hourly backups for the last 30 days, or however long the server has been active) should be displayed.

Support of the day: Dead Scripts

If you regularly work with scripts on any Unix or Linux platform and it gets killed when you logout from ssh, the session dies or the scripts stops working after x time then you need to deown it and fork it to the background.
So instead of running
/your/script/filename
run
nohup /your/script/filename &
What this does is start the script, the nohup deowns the scripts (meaning that it has no owner so you can logout without killing the process) and the & at the end sends the process to the background. This is the alternative method to run something from within screen but this version works good with a crontab.
FYI the crontab is a file and a program (both named the same) that executes commands (opening files, sending email, any command that you could do via the regular shell) at specific interval or times.

Support of the day: Getting the old Ubuntu desktop back on 10.11

So, you’ve installed Ubuntu 11.10 and found out that it’s all gone and replaced by what seems to be too good of a qualificative of a sidebar and what appears to be a poignant attempt to kill all interest on an open source Operating System. Fear not as we can still make the best of it.
Ubuntu had a very easy, kind interface since the times of 7.04, about 4 years ago, menu on the top, bar on the bottom, happy explorer on the chair, never a miscommunication, yet this has been replaced by a mac-os-ish-windows-7 look. To get rid of this, follow this guide that I’ve just re-checked for you: (more…)

Support of the day: SSH Keys (Passwordless login via SSH)


This week’s tip: SSH Keys (or i do not like typing my long cryptic password everytime I need to access my server)
If you’ve been following my other tips you might remember that ssh uses different authentication options, credentials, domain login, password, you name it, one of these is via ssh keys.


Imagine your car. You’re used to use a key to open the door and start the engine once or twice per day. How about if you were a messenger that has to do this 40, 50, 60 times per day, it gets tiresome, wouldn’t it be great for the car to open the door and automatically start the engine when it senses that it’s you?
Same principle, bit different.
(Please note, that this tutorial is aimed to linux to linux connections, putty has a local key generator that could be technically used as the same.)


1. Creating the keys and their folder
First, create the local folder, type mkdir /home/$USER/.ssh (type it just like that)
Then the key: ssh-keygen -t dsa (anything it asks just press enter)


2. Copying the key to the remote server
Move to the ssh folder: cd /home/$USER/.ssh
Copy the file: scp id_dsa.pub yourremoteuser@remoteip:./id_dsa.pub


3. Adding the key on the remote server
First log in to the remote server via ssh as usual
Then add the key to the remote server’s key list:
cd /home/remoteusername/
mkdir .ssh
mv id_dsa.pub .ssh/
cd .ssh/
check if there is a file named authorized_keys, if not then create it:
touch authorized_keys
finally add the key:
cat id_dsa.pub >> authorized_keys


4. Activating the keys usage on the remote server.
Type: nano /etc/ssh/sshd_config
And look for AuthorizedKeysFile and make sure that it’s uncommented (meaning that there is no # symbol before that word) and that next to it says .ssh/authorized_keys
Save (ctrl + x) and restart the ssh service.


5. Testing.
Log out of the remote server and try to login again, this time it will not ask for a password.