[Scion] Unable to run SCION after update
Siddharth Mehrotra
the4daspect at gmail.com
Wed Sep 18 10:51:17 CEST 2019
Hi all,
I tried to run SCION after update from attachment point with ETHZ-AP as
downloading new configuration. I'm currently installing inside a VM with
use of OPENVPN to connect to SCION Lab.
I observed following scenarios:
1) After extracting configuration file from SCION coordination service, the
contents are reduced to:
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 18-09-2019 10:25 .vagrant
d----- 18-09-2019 10:23 gen
-a---- 13-06-2019 09:25 3618 README.md
-a---- 13-06-2019 09:25 3068 run.sh
-a---- 18-09-2019 10:22 3813
scion_lab_17-ffaa_1_c32.tar.gz
-a---- 18-09-2019 10:34 0
ubuntu-xenial-16.04-cloudimg-console.log
-a---- 18-09-2019 10:24 2484 Vagrantfile
Many SCION services are missing.
2) Although I was able to run the VM successfully and SSH to SCION.
However, it seems the connection to SCION was not successful. The below
command is after running Vagrant up:
default: WARNING:WARNING!: VPN could be unready. SCION may fail to start.
default: Created symlink from
/etc/systemd/system/scionlab.target.wants/scion-border-router at 17-ffaa_1_c32-1.service
to /lib/systemd/system/scion-border-router at .service.
default: Created symlink from
/etc/systemd/system/scionlab.target.wants/scion-certificate-server at 17-ffaa_1_c32-1.service
to /lib/systemd/system/scion-certificate-server at .service.
default: Created symlink from
/etc/systemd/system/scionlab.target.wants/scion-path-server at 17-ffaa_1_c32-1.service
to /lib/systemd/system/scion-path-server at .service.
default: Created symlink from
/etc/systemd/system/scionlab.target.wants/scion-beacon-server at 17-ffaa_1_c32-1.service
to /lib/systemd/system/scion-beacon-server at .service.
default: Created symlink from
/etc/systemd/system/scionlab.target.wants/scion-daemon at 17-ffaa_1_c32.service
to /lib/systemd/system/scion-daemon at .service.
default: Created symlink from
/etc/systemd/system/scionlab.target.wants/scion-dispatcher.service to
/lib/systemd/system/scion-dispatcher.service.
default: configure time sync
default: ntp.service is not a native service, redirecting to
systemd-sysv-install
default: Executing /lib/systemd/systemd-sysv-install enable ntp
default: configure unattended upgrades (automatic security upgrades)
default: SCIONLab VM ready
3) When I am inside the VM and I tried to check the connection I was
surprised to see this:
vagrant at scionlab-ffaa-1-c32:~$ checkbeacons
checkbeacons: command not found
Also fo this:
vagrant at scionlab-ffaa-1-c32:~$ tail -f $SC/logs/bs*.DEBUG
tail: cannot open '/logs/bs*.DEBUG' for reading: No such file or directory
tail: no files remaining
4)Memory Test:
vagrant at scionlab-ffaa-1-c32:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 992M 0 992M 0% /dev
tmpfs 200M 3.1M 197M 2% /run
/dev/sda1 9.7G 1.4G 8.3G 14% /
tmpfs 1000M 0 1000M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1000M 0 1000M 0% /sys/fs/cgroup
vagrant 136G 73G 64G 54% /vagrant
tmpfs 200M 0 200M 0% /run/user/1000
5) tun0 not found after performing ip a command.
PS: I am using Oracle Virtual Box 6.0 , Is it the compatibility issue ?
PS: I was able to run SCION successfully before the update with same
Virtual Box version and vagrant also.
Please look into this issue.
Thanks,
Sid
More information about the Scion
mailing list