Troubleshooting

Common problems and solutions.

Default passwords

OS: Debian 9.1

For security reasons, password authentication is disabled on the system SSH server. The only way to access the system is the public key authentication. The private key for your Skycharge system can be downloaded here: link

Check the system connection

Is the Skycharge system powered on?
Is the Skycharge system connected to your LAN? From a computer connected to the same LAN, launch the following command:

ping skydevice.local

Check if skycharged is running properly

When the Skycharge system is powered on, skycharged is automatically started. To verify the status of skycharged you can invoke the following command:

# systemctl status skycharged

The output will be similar to this:

● skycharged.service - Skycharge server
  Loaded: loaded (/lib/systemd/system/skycharged.service; enabled; vendor preset     Active: active (running) since Sat 2017-12-23 18:13:48 UTC; 34min ago
Process: 1962 ExecStart=/usr/sbin/skycharged 0.0.0.0 5555 --daemon --pidfile /v Main PID: 1963 (skycharged) 
  Tasks: 4 (limit: 4915)
 CGroup: /system.slice/skycharged.service
     └─1963 /usr/sbin/skycharged 0.0.0.0 5555 --daemon --pidfile /var/run/s
Dec 23 18:13:48 beaglebone systemd[1]: Starting Skycharge server...
Dec 23 18:13:48 beaglebone systemd[1]: Started Skycharge server.

As you can see the process is "loaded" and in the state "active (running)".

From superuser it is possible to stop skycharged by launching the following command:

# systemctl stop skycharged

Output:

root@beaglebone:/home/debian# systemctl status skycharged ● skycharged.service - Skycharge server
   Loaded: loaded (/lib/systemd/system/skycharged.service; enabled; vendor preset
   Active: inactive (dead) since Sat 2017-12-23 18:48:55 UTC; 9s ago
  Process: 1962 ExecStart=/usr/sbin/skycharged 0.0.0.0 5555 --daemon --pidfile /v Main PID: 1963 (code=killed, signal=TERM)
Dec 23 18:13:48 beaglebone systemd[1]: Starting Skycharge server...
Dec 23 18:13:48 beaglebone systemd[1]: Started Skycharge server.
Dec 23 18:48:55 beaglebone systemd[1]: Stopping Skycharge server...
Dec 23 18:48:55 beaglebone systemd[1]: Stopped Skycharge server. lines 1-10/10 (END)

From superuser it is possible to start skycharged by launching the following command:

# systemctl start skycharged

Output:

root@beaglebone:/home/debian# systemctl status skycharged ● skycharged.service - Skycharge server Loaded: loaded (/lib/systemd/system/skycharged.service; enabled; vendor preset
   Active: active (running) since Sat 2017-12-23 18:49:53 UTC; 3s ago
   Process: 2004 ExecStart=/usr/sbin/skycharged 0.0.0.0 5555 --daemon --pidfile /v   Main PID: 2005 (skycharged) Tasks: 4 (limit: 4915)
CGroup: /system.slice/skycharged.service
    └─2005 /usr/sbin/skycharged 0.0.0.0 5555 --daemon --pidfile /var/run/s Dec 23 18:49:53 beaglebone systemd[1]: Starting Skycharge server...
Dec 23 18:49:53 beaglebone systemd[1]: Started Skycharge server.

Skycharge system login refused

If the below login command fails:

ssh [email protected]

And the output looks similar to this:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is 60:78:55:26:12:09:93:dc:ed:84:bd:d3:36:88:fb:95.
Please contact your system administrator.
Add correct host key in /var/root/.ssh/known_hosts to get rid of this message. Offending key in /var/root/.ssh/known_hosts:15 RSA host key for 192.168.188.33 has changed and you have requested strict checking. Host key verification failed.

You may need to fix the host key with the following command:

ssh-keygen -R skydevice.local

Example:

ssh-keygen -R skydevice.local

/var/root/.ssh/known_hosts updated.
Original contents retained as /var/root/.ssh/known_hosts.old
....
The authenticity of host '192.168.188.33 (192.168.188.33)' can't be established.
RSA key fingerprint is 60:78:55:26:12:09:93:dc:ed:84:bd:d3:36:88:fb:95. Are you sure you want to continue connecting (yes/no)?
yes
...
debug1: Next authentication method: password [email protected]'s password:
temppwd

In the above example, we answered "yes" and when requested, we typed the password "temppwd".