Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Primarily Deb/Ubuntu, and some CentOS
Posts: 829
Rep:
Unable to scp files to Linux Mint machine
Hello all,
I'm unable to scp or to my LM 18.3 machine from my two other debian machines on same LAN via IP or hostnames. I can, however, scp from the LM machine to the debian machines via IP or hostname. The debian machines can scp to each other.
My LM machine has openssh-client and openssh-server installed.
Code:
myserver ~ # systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-04-16 22:41:56 CDT; 3s ago
Process: 4701 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Main PID: 4704 (sshd)
CGroup: /system.slice/ssh.service
└─4704 /usr/sbin/sshd -D
Apr 16 22:41:56 myserver systemd[1]: Starting OpenBSD Secure Shell server...
Apr 16 22:41:56 myserver sshd[4704]: Server listening on 0.0.0.0 port 22.
Apr 16 22:41:56 myserver sshd[4704]: Server listening on :: port 22.
Apr 16 22:41:56 myserver systemd[1]: Started OpenBSD Secure Shell server.
I've checked sshd_config and all seems fine, what else could I check?
Distribution: Primarily Deb/Ubuntu, and some CentOS
Posts: 829
Original Poster
Rep:
Here it is. It just stops here at a blinking cursor.
Code:
erik@debianserver:~$ ssh -vvv erik@linuxmintserver
OpenSSH_6.7p1 Debian-5+deb8u8, OpenSSL 1.0.1t 3 May 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 10.20.1.10 [10.20.1.10] port 22.
Note: Im changing my hostnames for this thread to generic names. In my original post I put "myserver". This is my Linux Mint machine, and I've renamed it here the above code. Just wanted to be clear on that.
Last edited by erik2282; 04-17-2019 at 08:12 AM.
Reason: clarification
Distribution: Primarily Deb/Ubuntu, and some CentOS
Posts: 829
Original Poster
Rep:
Ok, I found the problem after Googling some more. There was a cowsay line in root's .bashrc that it didn't like. After commenting that out, it works fine... *sigh
Interesting problem. I have never seen just a line.
Can you scp a single file?
I would also try using sftp and see if that works. Once logged in you can use the -r option to transfer an entire directory assuming your in its parent directory.
Distribution: Primarily Deb/Ubuntu, and some CentOS
Posts: 829
Original Poster
Rep:
The reason i was getting a line, i figure, is because at the top of the cowsay thing, there is a solid line at the top and it think thats what it was displaying, and it puked after that...
Since you use the -r option, I'd say use rsync instead.
The scp program has no real specification behind it other than "do what rcp did, but encrypted". So for many years, the recommendation has been to avoid it and use rsync or sftp instead.
The scp protocol is outdated, inflexible and not readily fixed. We recommend the use of more modern protocols like sftp and rsync for file transfer instead.
Distribution: Primarily Deb/Ubuntu, and some CentOS
Posts: 829
Original Poster
Rep:
Thank guys.
Turbo, wow, genuinely did not know this. I always just eeny-meeny-miney-moe picked one. lol... rsync is more extremely useful, so I'll stick with it going forward.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
