Unfortunately, some users not familiar with Virtuozzo will often attempt to manually override the disabled Windows Update options, for example by downloading and manually installing Windows Updates. All will be fine until a container restart is attempted which will fail with the following errors or something similar:

Failed to start Virtual Private Server ’21656′. System error 1:
Virtuozzo API function call ‘VzkrnlStartVps’ failed dwErr = 0x000004FB

This generally means the VPS was updated using Windows update, as above – with Virtuozzo you can only install approved patches from SWSoft/Parallels (http://www.parallels.com)

In order to fix this, the easiest method would be to restore a recent VPS Container backup. However, this may not always be an option with users either having no backups, or backups which are out of date.

In order to begin fixing this, we will need to resynchronize the problem Container’s system files with that of the Host Node Operating System. If these file differs from the Host Node, the VPS Container simply cannot start ie. Copying the “c:\Windows\System32\drivers\” folder.

To do this you must log into the Virtuozzo Host Node via RDP, open a command prompt, and perform the following, which simply replaces what was patched/replaced with what the Host Node is using:

copy c:\WINDOWS\system32\drivers\ c:\vz\privte\VEID\root\c\WINDOWS\system32\drivers\

Where “VEID” is the VPS Container ID.

Now, because the VPS Container is down, Virtuozzo will most likely have unmounted the root file system for this container. Which means you will have to temporarily mount the file system in order to make changes to the file system, which you can perform with the following steps:

1) Make sure the container is stopped

vzctl stop VEID

You may also wish to backup the containers file system at this point eg. Do copy of z:\vz\private\VEID\root.efd for emergency cases.

2) a) Mount the root.efd file

vzdskctl mount z:\vz\private\VEID\root.efd GUID – making sure the root.efd path is correct for this container.

2) b) To obtain the container’s unique GUID required above:

vzcfgt get VEID GUID

This will return the unique GUID in the form “{799251BE-720C-468E-B877-913F49476001}”

3) Once the vzdskctl mount command returns “SUCCESS”, the file system for the container is mounted and you can copy the Windows System files over.

4) Once you’ve finished copying:

vzdskctl umount GUID

This will unmount the file system, so you can attempt to start the container again. However, you may also want to assimilate the VPS Container by running the following command from the Virtuozzo BIN folder (usually C:\Program Files\SWsoft\Virtuozzo\BIN):

vzfsctl assimilate VEID

Now to restart the container either via PIM or command line

vzctl start VE

Related posts:

1. Unsuspend Plesk Domain Accounts Occasionally Plesk can be a little temperamental and suspend accounts...

In Windows, goto Start -> Run and cd to your Plesk “bin” folder – typically c:\Program Files\Parallels\Plesk\admin\bin

Then type the following:

domain.exe –on yourdomain.com

This can take a little while but you should see “SUCCESS, status of domain changed”, and the domain will again appear as “Active” from your Plesk Control Panel.

No related posts.

tail -f /var/log/exim_mainlog

If you need to restart or rebuild Exim, you can dump your databases
* /etc/exim.conf
* /var/spool/exim/db

Which Exim just rebuilds automatically by issuing the following command via SSH:

rm -fv /var/spool/exim/db/*

Then to start Exim:

/scripts/eximup –force

No related posts.

To create a simlink you can do the following:

cd /var/lib/mysql/
touch mysql.sock
chmod 1777 mysql.sock
chown mysql.mysql mysql.sock

Create a symlink for the sock file :-
ln -s /var/lib/mysql/mysql.sock /tmp

Restart mysql :- service mysql restart

Then your MySQL service should be back to normal.

No related posts.

A Linux Server is not Windows XP and if reboot fail you usually still connect by SSH and do something. This commands will show you how to remotely hard reboot machine. Hard reboot mean that shutdown scripts will not run and machine reboot immediately without syncing hard disk drives, shutdown applications etc, it’s more like hitting the reset button.

echo 1 > /proc/sys/kernel/sysrq

echo b > /proc/sysrq-trigger

This commands enable sysrq and after this calls fast reboot. If you want to force shutdown machine try this.

Force shutdown

echo 1 > /proc/sys/kernel/sysrq

echo o > /proc/sysrq-trigger

This came handy, when I had a server that had some IO error and it can no longer read from disk, only few cached binaries into memory kept it running (kernel, SSHD, bash), I could still access the machine via SSH but can no longer do anything, forcing the reboot as mentioned above was my only resort, and it worked like charm…

No related posts.

In this document I use Debian Etch 4.0 for all nodes. Therefore the setup might differ a bit for other distributions. The two data nodes were x64 to use all of the 8GB RAM. Servers were compiled from source so you should be able to make it running on any platform. The MySQL version I use in this setup is 5.1.24-rc. It’s a release candidate, but I wanted to use 5.1 to take advantage of Memory-Disk Based tables.

Beginning with MySQL 5.1.6, it is possible to store the non-indexed columns of NDB tables on disk, rather than in RAM as with previous versions of MySQL Cluster.[More here]

This howto is just a scratch to make it running, for many of you I am suggesting to read some off docs from MySQL page to be prepared to how manage the whole cluster and always know whats going on.

This document comes without warranty of any kind! Bare in mind you need to make tests and prepare your databases before using it in production mode.

http://www.howtoforge.com/setting-up-a-loadbalanced-mysql-cluster-with-mysql5.1

Related posts:

1. Linux Server Type: Restoring MySQL SimLink. If you’re unable to restart mysqld and troubleshooting the cause:...

vzup2date

In order to update the templates, add a -t to the command thusly:

vzup2date -t

It should be noted that if Virtuozzo is installed on the server, the standard Redhat up2date command should never be run.

If you are running Virtuozzo on a Windows server, then you can run the Virtuozzo update utility accessed through the Start menu.

Related posts:

1. Virtuozzo: Fixing Windows VPS Container Start Errors Due to the way the Virtuozzo virtualization platform works, all...

No problem, check out this nice tutorial on email notification for root logins. Keeping track of who logs into your server and when is very important, especially when you’re dealing with the super user account. We recommend that you use an email address not hosted on the server your sending the alert from

1. Login to your server and su to root, I know the irony!

2. cd /root

3. pico .bashrc

4. Scroll to the end of the file then add the following:
echo ‘ALERT – Root Shell Access (YourserverName) on:’ `date` `who` | mail -s “Alert: Root Access from `who | cut -d”(” -f2 | cut -d”)” -f1`” you@yourdomain.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Replace YourServerName with the handle for your actual server
Replace you@yourdomain.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it with your actual email address

5. Crtl + X then Y

Now logout of SSH, close the connection?and log back in! You should receive an email address of the root login alert a few minutes afterwards.

Note: This is a great tool for servers that have multiple admins or if you give someone SSH access for whatever reason, although you should give out the root password to as few people as humanly possible and be sure to change it often.

This will not magically alert you when a hacker runs the latest kernel exploit on your server and logs into SSH because they will create their own SSH/telnet connection. You should keep your system up to date, install a firewall and follow the latest security releases.

No related posts.

Hope that helped a little

And if you want to check out whats happening in the mySql cache just run this comand

mysql -e “SHOW STATUS LIKE ‘%qcache%’;”

Related posts:

1. Linux Server Type: Restoring MySQL SimLink. If you’re unable to restart mysqld and troubleshooting the cause:...

mysqldump -uUSER -pPASSWORD txp_database > txp_database.sql

puts the entire thing in one nicely portable text file.

on a new server it takes

mysql -uUSER -pPASSWORD txp_database < txp_database.sql

to import it.

Related posts:

1. Linux Server Type: Restoring MySQL SimLink. If you’re unable to restart mysqld and troubleshooting the cause:...

The Crontab File’s Syntax
To tell cron what you want it to run, and how often you want it to run it, you need to create a crontab file. A crontab file is just a text file with the following syntax:

Code:

minute hour day-of-month month-of-year day-of-week command

Each of the above columns can be in one of the following formats (these examples are for the minute column):
30
Run command at 30 minutes past the hour.

0-59/10
Run command once every 10 minutes, for entire hour.

15-30
Run command once every minute, from 15 to 30 minutes past the hour.

0,10,50
Run command at 0 minutes past the hour, 10 minutes past the hour, and 50 minutes past the hour.
*
Run command once every minute.

And here’s the range of numbers available for each of the time and date columns:
Minute : 0-59
Hour : 0-23
day-of-month : 0-31
month-of-year : 1-12
day-of-week : 0-6
(0=Sun, 1=Mon, 2=Tue, 3=Wed, 4=Thu, 5=Fri, 6=Sat)
Here’s an example crontab file:

Code:

30 0 * * * ./backup.sh
0,10,50 9-15 * * * ./compute.sh
0-59/10 * * * 1,3,5 ./netgrab.sh
30 0 * * * ./backup.sh

Run the backup.sh script (located in your home directory) at half-past (30) midnight (0), on every day of the month (*), and every day of the year (*), and every day of the week (*).
0,10,50 9-15 * * * ./compute.sh

Run the compute.sh script every 0 minutes, 10 minutes, and 50 minutes past the hours (0,10,50), between 9am and 5pm (9-15), every day of the year.

0-59/10 * * * 1,3,5 ./netgrab.sh

Run the netgrab.sh script every 10 minutes (0-59/10), every Monday, Wednesday, and Friday (1,3,5).

Creating and Submitting Your Crontab File to Cron

There are two methods to create/modify and submit a crontab file:

Method 1
Create a crontab file in a text editor. You can call it whatever you want and save it wherever you like. Now you have to submit the crontab file. To do this enter:
crontab filename
…replacing filename with the location and name of your crontab file e.g. if the file was named crontab and was in your current directory you would enter:
crontab crontab

Method 2

crontab -e
To open your default editor (which is Vi). When saving the file just enter :wq without specifying a Filename; to quit Vi, and automatically submit the crontab file.

Note
When you sumbit a file, a copy of it is stored in the /var/spool/cron directory, with your username as the filename. So if I submitted the file mycron whilst logged into the account laurence, a copy would be stored as /var/spool/cron/laurence. It’s this file the cron daemon uses, and not the master file you created if you used method 1. If you used Method 2 then only one copy of the file exists. Never directly edit files in /var/spool/cron. Cron will not be updated and you can potentially mess things up. Instead use either Method 1 or 2 again, to modify your crontab file.

Listing and Removing Your Crontab File
To display the contents of your crontab file held in the /var/spool/cron directory, enter:
crontab -l
And to remove your crontab file from the /var/spool/cron directory, enter:
crontab -r

Restricting Users
By default only root can submit and modify a crontab file. To allow users to have their own crontab file add their username to the /etc/cron.allow file, e.g:
john
julie
Indicating that john and julie are now permitted to submit their own crontab file.

Putting Theory Into Practice
Here’s a handy little automation exercise for you to try out. It will backup the contents of your home directory to a .tar.gz file each morning at 2.30a.m.
If you haven’t already done so, enter:
su -c ‘pico /etc/cron.allow’
…and add your username to this file to allow you to submit crontab files.
/ 1
If you’re not already in your home directory, enter:
cd
/ 2
Enter:
pico backup
…and enter the following:
rm backup.tar.gz
tar cfz backup.tar.gz .
…then press Ctrl+o to save the file, and Ctrl+x to exit.

/ 3 -
Now make the script executable by entering:
chmod +x backup

/4 -
Enter:
crontab -e

/ 5 -
Press i to enter Insert mode and enter the following:

30 2 * * * ./backup

…then press Esc to return to Command mode, and enter:
:wq
…to exit Vi and submit your crontab file. That’s all there is to it. Now you can spend hours thinking of bigger and better ways to make your life as a system administrator an easy one.

If you don’t have access to cron, consult your local admin. And
remember, in shell you can access the cron manual by doing :

man cron
Or
man crontab

Some good additional links:

1. http://www.clockwatchers.com/cron_main.html
2. http://www.linuxforums.org/tutorial…orial-4017.html

Related posts:

1. Rebuilding/Restarting Exim Mail Server When troubleshooting the Exim log file: tail -f /var/log/exim_mainlog If...

Create a file called database_backup.sh and also an empty directory called mysql_backup. The database_backup.sh script should have the following info :

————————————————-
#!/bin/sh

date=`date ‘+%m-%d-%y’`
mysqldump -u database_username -pdatabase_password database_name > ~/mysql_backup/database_name.$date
————————————————-

Run the script that performs the backup job.

————————————————-
* 23 * * * your_userid /path/to/backup/script
————————————————-

Set this script up to run every night, etc. as a cron job. It will save an sql dump of your database every night in the mysql_backup.

No related posts.

PRM (Process Resource Monitoring) monitors the process table on a given system and matches process id’s with set resource limits in the config file or per-process based rules. Process id’s that match or exceed the set limits are logged and killed; includes e-mail alerts, kernel logging routine and more…

Installation:

First  the package:
wget http://www.rfxnetworks.com/downloads/prm-current.tar.gz

Extract it:

tar xvfz prm-current.tar.gz

The current version of prm as of this writing is 0.5, so lets cd to the 0.5 extracted path:
cd prm-0.5/

And finally run the enclosed install.sh script:
./install.sh

Download the current release of PRM distributed under the GNU GENERAL PUBLIC LICENSE:
- http://www.r-fx.ca/downloads/prm-current.tar.gz

All projects on rfxnetworks.com are free for use and distribution in accordance with the gnu gpl; funding for the continued development and research into this and other projects, is solely dependent on public contributions and donations.

R-FX Networks
ReadMe
http://www.rfxnetworks.com/appdocs/README.prm
Version History:
http://www.rfxnetworks.com/appdocs/CHANGELOG.prm

No related posts.

• use the arrows to select the boot entry you want to modify
• press e to edit the entry
• use the arrows to go to kernel line
• press e to edit this entry
• at the end of the line add the word single (there should be a space between like  / single)
• press ENTER to go back to the parent menu
• press b to boot this kernel

As root, changing password does not ask for your old password. Now, you can change root’s password by typing:

bash# passwd root

You’ll be asked to re-type the password for verification. Once you’re finished, the password will be changed and you can reboot by typing shutdown -r now at the prompt; then you can log in to root as before

My boot loader is LILO

At LILO boot loader type linux single and press [ENTER] key:
Boot: linux single
When you get the # prompt you will need to type passwd root to reset password:
# passwd
Reboot system:
# sync
# reboot

No related posts.

system-config-network

No related posts.

Common SSH Commands or Linux Shell Commands,
ls : list files/directories in a directory, comparable to dir in windows/dos.
ls -al : shows all files (including ones that start with a period), directories, and details attributes for each file.

cd : change directory ? ? cd /usr/local/apache : go to /usr/local/apache/ directory
cd ~ : go to your home directory
cd – : go to the last directory you were in
cd .. : go up a directory cat : print file contents to the screen

cat filename.txt : cat the contents of filename.txt to your screen

tail : like cat, but only reads the end of the file
tail /var/log/messages : see the last 20 (by default) lines of /var/log/messages
tail -f /var/log/messages : watch the file continuously, while it’s being updated
tail -200 /var/log/messages : print the last 200 lines of the file to the screen

more : like cat, but opens the file one screen at a time rather than all at once
more /etc/userdomains : browse through the userdomains file. hit to go to the next page, to quit

pico : friendly, easy to use file editor
pico /home/burst/public_html/index.html : edit the index page for the user’s website.

vi : another editor, tons of features, harder to use at first than pico
vi /home/burst/public_html/index.html : edit the index page for the user’s website.

grep : looks for patterns in files
grep root /etc/passwd : shows all matches of root in /etc/passwd
grep -v root /etc/passwd : shows all lines that do not match root

touch : create an empty file
touch /home/burst/public_html/404.html : create an empty file called 404.html in the directory /home/burst/public_html/

ln : create’s “links” between files and directories
ln -s /usr/local/apache/conf/httpd.conf /etc/httpd.conf : Now you can edit /etc/httpd.conf rather than the original. changes will affect the orginal, however you can delete the link and it will not delete the original.

rm : delete a file
rm filename.txt : deletes filename.txt, will more than likely ask if you really want to delete it
rm -f filename.txt : deletes filename.txt, will not ask for confirmation before deleting.
rm -rf tmp/ : recursively deletes the directory tmp, and all files in it, including subdirectories. BE VERY CAREFULL WITH THIS COMMAND!!!

last : shows who logged in and when
last -20 : shows only the last 20 logins
last -20 -a : shows last 20 logins, with the hostname in the last field

w : shows who is currently logged in and where they are logged in from.

netstat : shows all current network connections.
netstat -an : shows all connections to the server, the source and destination ips and ports.
netstat -rn : shows routing table for all ips bound to the server.

top : shows live system processes in a nice table, memory information, uptime and other useful info. This is excellent for managing your system processes, resources and ensure everything is working fine and your server isn’t bogged down.
top then type Shift + M to sort by memory usage or Shift + P to sort by CPU usage

ps: ps is short for process status, which is similar to the top command. It’s used to show currently running processes and their PID.
A process ID is a unique number that identifies a process, with that you can kill or terminate a running program on your server (see kill command).
ps U username : shows processes for a certain user
ps aux : shows all system processes
ps aux –forest : shows all system processes like the above but organizes in a hierarchy that’s very useful!

file : attempts to guess what type of file a file is by looking at it’s content.
file * : prints out a list of all files/directories in a directory

du : shows disk usage.
du -sh : shows a summary, in human-readble form, of total disk space used in the current directory, including subdirectories.
du -sh * : same thing, but for each file and directory. helpful when finding large files taking up space.

wc : word count
wc -l filename.txt : tells how many lines are in filename.txt

cp : copy a file
cp filename filename.backup : copies filename to filename.backup
cp -a /home/burst/new_design/* /home/burst/public_html/ : copies all files, retaining permissions form one directory to another.

kill: terminate a system process
kill -9 PID EG: kill -9 431
kill PID EG: kill 10550
Use top or ps ux to get system PIDs (Process IDs)

EG:
PID TTY TIME COMMAND
10550 pts/3 0:01 /bin/csh

10574 pts/4 0:02 /bin/csh

10590 pts/4 0:09 APP

Each line represents one process, with a process being loosely defined as a running instance of a program. The column headed PID (process ID) shows the assigned process numbers of the processes. The heading COMMAND shows the location of the executed process.

Putting commands together
Often you will find you need to use different commands on the same line. Here are some examples. Note that the | character is called a pipe, it takes date from one program and pipes it to another.
> means create a new file, overwriting any content already there.
>> means tp append data to a file, creating a newone if it doesn not already exist.
< send input from a file back into a command.

grep User /usr/local/apache/conf/httpd.conf |more
This will dump all lines that match User from the httpd.conf, then print the results to your screen one page at a time.

last -a > /root/lastlogins.tmp
This will print all the current login history to a file called lastlogins.tmp in /root/

tail -10000 /var/log/exim_mainlog |grep domain.com |more
This will grab the last 10,000 lines from /var/log/exim_mainlog, find all occurances of domain.com (the period represents ‘anything’,
– comment it out with a so it will be interpretted literally), then send it to your screen page by page.

netstat -an |grep :80 |wc -l
Show how many active connections there are to apache (httpd runs on port 80)

mysqladmin processlist |wc -l
Show how many current open connections there are to mysql

No related posts.

The compromise is at the root level and a rootkit has been installed. This rootkit will attach to several syscalls within the kernel and begin serving malicious javascript to random web visitors.

This root compromise is not related to cPanel directly, as it has been reported on many different control panels on many different servers. The compromise is at the system level, and only Redhat 4, CentOS 4, and FC6 appear to be vulnerable at this time. We are actively researching this issue and will have an in-depth analysis of current information posted soon.

http://forums.cpanel.net/showthread.php?t=74963&page=10&highlight=centos5

[root\@cpanel ~]# mkdir 1
mkdir: cannot create directory `1': No such file or directory
[root\@cpanel ~]# touch 2
touch: cannot touch `2': No such file or directory

tcpdump -nAs 2048 src port 80 | grep "[a-zA-Z]\{5\}\.js'"

root@server log]# tcpdump -nAs 2048 src port 80 | grep "[a-zA-Z]\{5\}\.js'"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 2048 bytes
<script language='JavaScript' type='text/javascript' src='ateyc.js'></script>
<script language='JavaScript' type='text/javascript' src='taopp.js'></script>
1311 packets captured
2627 packets received by filter
0 packets dropped by kernel

No related posts.

I will use the following software:

• Web Server: Apache 2.2 with PHP 5.1.6
• Database Server: MySQL 5.0
• Mail Server: Postfix
• DNS Server: BIND9 (chrooted)
• FTP Server: Proftpd
• POP3/IMAP server: Dovecot
• Webalizer for web site statistics

In the end you should have a system that works reliably, and if you like you can install the free webhosting control panel ISPConfig (i.e., ISPConfig runs on it out of the box).

I want to say first that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you!

Read the full article here

Related posts:

1. Linux Server Type: Restoring MySQL SimLink. If you’re unable to restart mysqld and troubleshooting the cause:...

mod_gzip – what’s that, anyway?

mod_gzip – serving compressed content by the Apache webserver
mod_gzip is an external extension module for the WWW’s most popular web server Apache, created in autumn, 2000.
Its implementation allows for using the compression method gzip for a significant reduction of the volume of web page content served over the HTTP protocol.

If you are having difficulties with getting mod_gzip to work when compiled with using easyapache, then you can go and use this step by step manual install.

Log into you server using shell and your root account and download mod_gzip-1.3.26.1a.tgz (or whatever the latest version) from sourceforge.net

I used

wget http://optusnet.dl.sourceforge.net/sourceforge/mod-gzip/mod_gzip-1.3.26.1a.tgz
after that

tar -zxvf mod_gzip-1.3.26.1a.tgz
cd mod_gzip-1.3.26.1a

make APXS=/usr/local/apache/bin/apxs
make install APXS=/usr/local/apache/bin/apxs

Then edit your httpd.conf file

pico /etc/httpd/conf/httpd.conf

and add the following (in the AddModule stuff):

first uncomment:

#LoadModule gzip_module libexec/mod_gzip.so
to
LoadModule gzip_module libexec/mod_gzip.so

and

#AddModule mod_gzip.c
to
AddModule mod_gzip.c

and after AddModule mod_gzip.c add this below

<IfModule mod_gzip.c>
mod_gzip_on Yes
mod_gzip_can_negotiate Yes
mod_gzip_static_suffix .gz
AddEncoding gzip .gz
mod_gzip_update_static No
mod_gzip_command_version ‘/mod_gzip_status’
mod_gzip_temp_dir /tmp
mod_gzip_keep_workfiles No
mod_gzip_minimum_file_size 500
mod_gzip_maximum_file_size 500000
mod_gzip_maximum_inmem_size 60000
mod_gzip_min_http 1000
mod_gzip_handle_methods GET POST
mod_gzip_item_exclude reqheader “User-agent: Mozilla/4.0[678]”
mod_gzip_item_include file \.html$
mod_gzip_item_include file \.shtml$
mod_gzip_item_include file \.htm$
mod_gzip_item_include file \.shtm$
mod_gzip_item_include file \.php$
mod_gzip_item_include file \.phtml$
mod_gzip_item_exclude file \.js$
mod_gzip_item_exclude file \.css$
mod_gzip_item_exclude file \.wml$
mod_gzip_item_include file \.pl$
mod_gzip_item_include file \.cgi$
mod_gzip_item_include handler ^cgi-script$
mod_gzip_item_include mime ^text/html$
mod_gzip_item_include mime ^text/plain$
mod_gzip_item_include mime ^httpd/unix-directory$
mod_gzip_item_include mime ^application/x-httpd-php
mod_gzip_item_include handler ^perl-script$
mod_gzip_item_exclude mime ^image/
mod_gzip_dechunk Yes
mod_gzip_add_header_count Yes
mod_gzip_send_vary Yes
</IfModule>

Then restart apache with

service httpd restart

That’s about it. There is nothing too typical about installtion and getting it to work, except for in cases where one is using mod_proxy also for proxying a back-end httpd in which case mod_gzip would fail because of a bug. Other than that it works fine.

Compiled tutorial with info from Anup

Oh, and nearly forgot; you can check if you have successfully installed gZip by going here : http://leknor.com/code/gziped.php?

No related posts.

There is an easy way around with the scp command

Log into your old server where you want to move that big tar file from and

scp yourlarge3gigfile.tgz root@newserverIP.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it :/home/
(enter the root pass for the new server and let it copy the file over)

If you run SSH on a different port (that is, not the default port 22) and you need to scp then it can be done by:

scp -P <port> yourlarge3gigfile.tgz root@newserverIP.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it :/home/

For example, if your ssh/scp is on port 2000 then:

scp -P 2000 yourlarge3gigfile.tgz root@newserverIP.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it :/home/

the above command will connect to scp/ssh port 2000 and copy the file to the remote user’s home directory in the remote server.

If you use SSH key based authentication then when you scp, scp will not ask for user’s password. It will copy your file to the remote server using your ssh private key. Example,

scp -i your_private_key yourlarge3gigfile.tgz root@newserverIP.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it :/home/

the above command will use your ssh private key and copy the file (file.txt) in the remote_user’s home directory.

No related posts.