Ssh – Starting jetty service from SSH

daemonjettyservicessh

I am trying to start jetty service from ssh using the command:

ssh -t myhost "sudo /sbin/service jetty6 start"

All works well, service comes up but after the command terminates and the connection closes down, the Jetty service goes down, too. If I log into ssh and do the "service" command manually, all works fine.

I have tried to use the recipe from this answer, that didn't work either.

Best Answer

Before:

# service jetty status
 * Jetty servlet engine is not running.

Use(localhost:2022 virtual machine hostname):

$ ssh -p 2022 localhost "sudo service jetty start"
 * Starting Jetty servlet engine. jetty
 * Jetty servlet engine started, reachable on http://u1004s01:8080/. jetty
   ...done.
$

Result:

# service jetty status
 * Jetty servlet engine is running with pid 2623, and is reachable on http://:8080/

Command service not need go to the background. Add output command:

ssh myhost "sudo /sbin/service jetty6 start;sleep 60;sudo /sbin/service jetty6 status;ps aux | grep jetty"

Related Solutions

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

SSH – Bad Owner or Permissions on ~/.ssh/config

I needed to have rw for user only permissions on config. This fixed it.

chmod 600 ~/.ssh/config

As others have noted below, it could be the file owner. (upvote them!)

chown $USER ~/.ssh/config

If your whole folder has invalid permissions here's a table of possible permissions:

Path	Permission
.ssh directory (code)	0700 (drwx------)
private keys (ex: `id_rsa`) (code)	0600 (-rw-------)
`config`	0600 (-rw-------)
public keys (*.pub ex: `id_rsa.pub`)	0644 (-rw-r--r--)
`authorized_keys` (code)	0644 (-rw-r--r--)
`known_hosts`	0644 (-rw-r--r--)

Sources:

openssh check-perm.c
openssh readconf.c
openssh ssh_user_config fix_authorized_keys_perms

Best Answer

Related Solutions

Ssh – How to automate SSH login with password

SSH – Bad Owner or Permissions on ~/.ssh/config

Related Topic