Beacon server log file access issue

[DLTLab]

 Hello everyone,

We have successfully installed and setup a SCION virtual machine image using OpenVPN connection and it seams connected and working.

Currently, we are having an issue to check for the beacons' log file, as reported in error message below. Could someone help us to figure out what is the problem and how to fix it.

[Matthias Frei]

Hi there,

thank you for trying out SCIONLab!

At first sight, this looks like the configuration in your VM is incomplete. The "trust root configuration" (TRC) file is normally contained in multiple subdirectores of the configuration tar-ball that you download from the scionlab.org-website.

You can check that it has been properly copied into your VM, by running the following find command in the VMs scion installation directory:

$ find -name ISD*.trc

The expected output would be:

./gen/ISD17/ASffaa_1_131/br17-ffaa_1_131-1/certs/ISD17-V1.trc
./gen/ISD17/ASffaa_1_131/ps17-ffaa_1_131-1/certs/ISD17-V1.trc
./gen/ISD17/ASffaa_1_131/endhost/certs/ISD17-V1.trc
./gen/ISD17/ASffaa_1_131/cs17-ffaa_1_131-1/certs/ISD17-V1.trc
./gen/ISD17/ASffaa_1_131/bs17-ffaa_1_131-1/certs/ISD17-V1.trc

If you see fewer copies of this files, the configuration might have been corrupted in some way. As a first suggestion, you could try to restore the gen/-directory from the configuration tar.gz-file downloaded from scionlab.org.

Best Regards,

Matthias

[Adrian Perrig]

Hi,

Just to add to Matthias' message, you can see how to update the gen
folder in Step 4 of this tutorial (earlier steps may also be needed):
https://netsec-ethz.github.io/scion-tutorials/general_scion_configuration/vpn_setup/

Let us know if you encounter any issues.
Adrian

> --
> SCION Internet Architecture
> https://www.scion-architecture.net
> ---
> You received this message because you are subscribed to the Google Groups "SCION community" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to scion-communi...@googlegroups.com.
> To post to this group, send email to scion-c...@googlegroups.com.
> Visit this group at https://groups.google.com/group/scion-community.
> To view this discussion on the web visit https://groups.google.com/d/msgid/scion-community/0b727c9a-916f-4d3a-b698-9a784222ac04%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[DLTLab]

Thank you for your prompt reply.

I have tried the procedure you have suggested below and restored the gen/-directory from a fresh configuration tar.gz-file downloaded from scionlab.org.

However, I am still not able to access to the beacons' log file.The following is the output I got from this procedure.

ubuntu@ubuntu-xenial:~$ find -name ISD*.trc
./go/src/github.com/scionproto/scion/gen/ISD19/ASffaa_1_22f/endhost/certs/ISD19-V1.trc
./go/src/github.com/scionproto/scion/go/lib/infra/modules/trust/trustdb/testdata/ISD1-V1.trc
./go/src/github.com/scionproto/scion/go/lib/crypto/cert/testdata/ISD1-V2.trc
./go/src/github.com/scionproto/scion/go/lib/crypto/trc/testdata/ISD1-V1.trc
ubuntu@ubuntu-xenial:~$

--------------------------
ubuntu@ubuntu-xenial:~/go/src/github.com/scionproto/scion$ checkbeacons
2018-11-29 14:30:12.458863+0000 [DEBUG] (MainThread) Current party (/19-ffaa:1:22f/bs/party) members are: ['ISD-AS: 19-ffaa:1:22f Id: bs19-ffaa_1_22f-1 ([10.0.2.15]:31041)']
2018-11-29 14:30:12.459282+0000 [INFO] (MainThread) Started bs19-ffaa_1_22f-1
2018-11-29 14:30:12.812493+0000 [INFO] (MainThread) IF 1 activated.
2018-11-29 14:30:13.479992+0000 [INFO] (BS.worker) Successfully acquired ZK lock (epoch 1)
2018-11-29 14:30:13.480601+0000 [INFO] (BS.worker) Became master
2018-11-29 14:30:15.794374+0000 [DEBUG] (Elem.packet_recv) Found extension hdr of type (0, 1) with len 8B
2018-11-29 14:30:15.805173+0000 [DEBUG] (MainThread) Handling PCB from UDPMetadata: (19-ffaa:0:1303 (IPV4) 141.44.25.144):31041: 6b47509bde78, 2018-11-29 14:30:13+00:00, 19-ffaa:0:1301 5>1 19-ffaa:0:1303 48 [id: 696ba5e3b552c8d4]
2018-11-29 14:30:15.805771+0000 [CRITICAL] (MainThread) Local TRC not found!
2018-11-29 14:30:15.904723+0000 [INFO] (MainThread) Exiting
2018-11-29 14:30:15.906950+0000 [ERROR] (Dummy-5) Received SIGUSR2

Best regards,

DLTLab

[Matthias Frei]

Hi there,

Thank you for trying the suggested steps.

This still looks like an incomplete/corrupted gen/-directory. I have just checked that the tar-file that you've downloaded seems to contain the full configuration, so something seems to have been lost somewhere "on the way" to the VM. Unfortunately, the the instructions about updating the gen/-directory may be somewhat unclear when it comes to VMs -- please try the following steps:

- navigate to the directory of the unpacked tar file on your host-machine (i.e. not in the VM); this directory should contain, a Vagrantfile, a subdirectory gen/, and bunch of miscellaneous other files

- in this directory run the following command to copy the gen/ directory to the scion directory of the VM:

$ vagrant halt -f; vagrant up && vagrant ssh -c 'rm $SC/gen -r ; cp -r /vagrant/gen/ $SC/'

After this, the $SC/gen/ directory in the VM should contain the expected five .trc files.

Alternatively, or if this also fails, you can try to reset your VM completely, by running (from the same directory) `vagrant destroy` followed by `vagrant up && vagrant ssh`.

Best regards,

Matthias

[DLT Research Group]

Thank you very much dear Matthias for your suggestions,

I have tried to follow all the steps as you suggested. However I am still having the same problem.

The following is the detailed output I got after each step has been performed.

1. Result obtained after I run this  vagrant halt -f; vagrant up && vagrant ssh -c 'rm $SC/gen -r ; cp -r /vagrant/gen/ $SC/' command from the directory of the unpacked tar file on my SCION host-machine

PS D:\Workspace\VMs_Files\SCION_VMs\SCION_VMs\research...@gmail.com_19-ffaa_1_22f> vagrant halt -f; vagrant up && v

agrant ssh -c 'rm $SC/gen -r ; cp -r /vagrant/gen/ $SC/'

At line:1 char:29
+ vagrant halt -f; vagrant up && vagrant ssh -c 'rm $SC/gen -r ; cp -r  ...
+                             ~~
The token '&&' is not a valid statement separator in this version.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : InvalidEndOfLine

2. Alternatively, the following is the result obtained after I completely and successfully resetting my SCIONLab VM, by running (from the same directory) `vagrant destroy` followed by `vagrant up && vagrant ssh`.

ubuntu@ubuntu-xenial:~/go/src/github.com/scionproto/scion$ checkbeacons
2018-11-30 03:14:34.563241+0000 [DEBUG] (MainThread) Current party (/19-ffaa:1:22f/bs/party) members are: ['ISD-AS: 19-ffaa:1:22f Id: bs19-ffaa_1_22f-1 ([10.0.2.15]:31041)']
2018-11-30 03:14:34.564940+0000 [INFO] (MainThread) Started bs19-ffaa_1_22f-1
2018-11-30 03:14:35.167732+0000 [INFO] (MainThread) IF 1 activated.
2018-11-30 03:14:35.604369+0000 [INFO] (BS.worker) Successfully acquired ZK lock (epoch 1)
2018-11-30 03:14:35.604796+0000 [INFO] (BS.worker) Became master
2018-11-30 03:14:38.132738+0000 [DEBUG] (Elem.packet_recv) Found extension hdr of type (0, 1) with len 8B
2018-11-30 03:14:38.147460+0000 [DEBUG] (MainThread) Handling PCB from UDPMetadata: (19-ffaa:0:1303 (IPV4) 141.44.25.144):31041: 76aaf654e8f4, 2018-11-30 03:14:34+00:00, 19-ffaa:0:1301 5>1 19-ffaa:0:1303 88 [id: e31fbd1f0a0e37d8]
2018-11-30 03:14:38.148714+0000 [CRITICAL] (MainThread) Local TRC not found!
2018-11-30 03:14:38.162900+0000 [INFO] (MainThread) Exiting
2018-11-30 03:14:38.163548+0000 [ERROR] (Dummy-5) Received SIGUSR2

※ Please find in the attached file the content of the directory of the unpacked tar file of the SCIONLab VM on my host-machine, just in case you might need it in for you to understand what could be the problem with SCIONLab setup.

Sincerely,

-  DLTLab -

----------------------------------------------

--
SCION Internet Architecture
https://www.scion-architecture.net
---
You received this message because you are subscribed to the Google Groups "SCION community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scion-communi...@googlegroups.com.
To post to this group, send email to scion-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/scion-community.

To view this discussion on the web visit https://groups.google.com/d/msgid/scion-community/ce9c0723-e376-48aa-a7a0-fb75b5bad2f5%40googlegroups.com.

[Juan A. Garcia Pardo]

Hi!

The contents of unpacking the tar file seem correct, at least seen from the host machine. To verify, can you log into the VM (run `vagrant ssh` in that directory) and then in the VM, run:

sudo apt install tree ; tree $SC/gen

This will print a very similar looking output with the information about the contents of the gen folder inside the VM. You can write back with them, but if you see a difference, the easiest will be, as Matthias mentioned, to recreate the VM.

There is also a troubleshooting guide in https://netsec-ethz.github.io/scion-tutorials/general_scion_configuration/troubleshooting/  , but it always assumes your host is a Linux system. If the contents of the `tree` command before are okay, you could use the troubleshooting guide.

Please tell us how this went. Thanks and best regards,

Juan A.