Tag Info

Hot answers tagged

5

ssh provides a connected stream from the local system running your rsync to another instance running on the remote server. The local rsync starts it as part of the ssh connection process - it is not the same instance of rsync that might be running as a daemon on that remote server. What is an ssh stream? An ssh stream is what you use when you ssh to a ...


3

If you follow your description the command becomes "obvious" (at least, when you see it...). You really weren't far off with your attempt, though: ssh user@remote tar czf - /my/directory/ > /my/local/destination/archive.tgz (The "duplicate" link cited by Marco provides a cleaner solution. To create this command here I've simply followed the style of ...


3

It sounds like you created a key but you didn't configure the account on the server to authorize that key. Copy the contents of id_rsa.pub to the server and add it to ~/.ssh/authorized_keys. Do not copy id_rsa to the server, and keep it protected. This file contains the private key and the server doesn't need to see that. Note that if the key is stored in ...


3

do not mix zones and zpools concepts Your zones are on top of zpools and these zpools are in suspended. first fix the zpool: Check status zpool status <zpool-name> then depending on the output take the proper action to fix it. Ensure that your devices disks that are part of the zpools are there. Check Oracle Documentation here


2

You could, though it may become unwieldy, add entries to your ~/.ssh/config for each descriptive name you want, then you can just ssh <name> and you can have the correct user/host etc. automatically applied. Here's an example from my config host abc hostname 1.2.3.4 User root LocalForward 5951:192.168.1.1:5901 ProxyCommand ssh 1.2.3.4 nc ...


2

glibc upgrades often require restarting running daemons (because the name service switch [NSS] ABI changes, or just to get the daemon to actually used the upgraded version). That's probably what you're seeing.


2

You can't use variable expansion in /etc/environment (which is why you see an unexpanded $PATH in the output from echo $PATH). /etc/environment is read by the pam_env module not a shell script so just simple assignments. You probably want to add this stuff to /etc/profile or add a file under /etc/profile.d/. See Can you use variables when editing ...


2

Host * IdentityFile ~/.ssh/my_key_rsa.pub You've specified the wrong key file here. You need to specify the private key file, not the public key file. The private key file is the one without the .pub extension: Host * IdentityFile ~/.ssh/my_key_rsa


2

Subsystem sftp intenal-sftp Should be "internal".


2

There's a little tool called screen which is able to do this from you. You can detach from a screen session and let it run in background so you can close the SSH connection. After reconnection you can reatach to the screen. http://thesystemadministrator.net/cpanel/how-to-install-and-use-screen-in-linux


1

Dave C. above is correct about the problem being ssh not running. As I said in a comment, there was not anything in any log file that showed a problem. Stopping/Starting ssh did not have any effect, nor showed any errors anywhere. I just needed to drop the container and build a new one.


1

Try to use pdsh. A lot of examples available on Project Page If you like to use simple bash script: #!/bin/bash HOSTS="host1 host2 host3" USER=root CMD="ls" for host in $HOST; do ssh ${USER}:{$host} "$CMD" done In all cases you would need to tune no-password auth using keys and append to ssh command: -i /path/to/key Example to use: #!/bin/bash ...


1

There is a theoretical limit of sorts: eventually the latency (which has a minimum value due to the fact that each hop must add an overhead of a few CPU instructions) will become so high that it will be larger than TCP timeouts. However you will have given up the system as unusable long before it reaches that stage.


1

After discussing this in a chat and debugged the issue, it turned out that the required directive PermitTunnel yes was not in place and active. After adding the directive to /etc/ssh/sshd_config and reloading sshd by service sshd reload this was resolved. We added -v to the ssh command to get some debugging information and from that we found: debug1: ...


1

Try the following: /usr/bin/sftp -b - USER@remote.server.com <<EOF ... The "-b -" puts sftp in batch mode while still reading from the command line. Batch mode will (on my system) exit sftp and return a non-zero exit code when one of the sftp commands fails.


1

In my case adding this string to /etc/ssh/sshd_config solved the problem: X11UseLocalhost no



Only top voted, non community-wiki answers of a minimum length are eligible