Postinst verbose:
Preparing to unpack …/corridor_0%3a10.0.0-3_all.deb …
Unpacking corridor (10.0.0-3) …
Processing triggers for man-db (2.7.5-1) …
Setting up corridor (10.0.0-3) …
- set -e
- true ’
#####################################################################
INFO: BEGIN: corridor postinst configure’ ’
#####################################################################
’
- case “$1” in
- mkdir --parents /var/lib/corridor
- true ‘INFO: debhelper beginning here.’
- deb-systemd-helper unmask corridor-init-logged.service
- deb-systemd-helper --quiet was-enabled corridor-init-logged.service
- deb-systemd-helper enable corridor-init-logged.service
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-init-logged.service → /lib/systemd/system/corridor-init-logged.service.
- deb-systemd-helper unmask corridor-init-snat.service
- deb-systemd-helper --quiet was-enabled corridor-init-snat.service
- deb-systemd-helper enable corridor-init-snat.service
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-init-snat.service → /lib/systemd/system/corridor-init-snat.service.
- deb-systemd-helper unmask corridor-data.service
- deb-systemd-helper --quiet was-enabled corridor-data.service
- deb-systemd-helper enable corridor-data.service
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-data.service → /lib/systemd/system/corridor-data.service.
- deb-systemd-helper unmask corridor-init-forwarding.service
- deb-systemd-helper --quiet was-enabled corridor-init-forwarding.service
- deb-systemd-helper enable corridor-init-forwarding.service
Created symlink /etc/systemd/system/multi-user.target.wants/corridor-init-forwarding.service → /lib/systemd/system/corridor-init-forwarding.service.
Created symlink /etc/systemd/system/systemd-networkd.service.requires/corridor-init-forwarding.service → /lib/systemd/system/corridor-init-forwarding.service.
- deb-systemd-helper unmask corridor.target
- deb-systemd-helper --quiet was-enabled corridor.target
- deb-systemd-helper enable corridor.target
Created symlink /etc/systemd/system/multi-user.target.wants/corridor.target → /lib/systemd/system/corridor.target.
- ‘[’ -d /run/systemd/system ‘]’
- systemctl --system daemon-reload
- deb-systemd-invoke start corridor-init-logged.service corridor-init-snat.service corridor-data.service corridor-init-forwarding.service corridor.target
sudo journalctl -u corridor*
– Logs begin at
25 debian systemd[1]: Started corridor’s relay list.
25 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
25 debian corridor-data[1917]: :25 socat[1923] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
26 debian systemd[1]: Starting corridor’s forwarding…
26 debian systemd[1]: Starting corridor’s logging…
26 debian systemd[1]: Starting corridor’s source NAT…
27 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
27 debian corridor-data[1917]: :27 socat[1949] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
27 debian systemd[1]: Started corridor’s source NAT.
28 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
28 debian corridor-data[1917]: :28 socat[1993] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
28 debian corridor-init-forwarding[1936]: net.ipv4.ip_forward = 1
28 debian corridor-init-forwarding[1936]: net.ipv6.conf.all.forwarding = 0
28 debian systemd[1]: Started corridor’s forwarding.
29 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
29 debian corridor-data[1917]: :29 socat[2032] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
30 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
30 debian corridor-data[1917]: :30 socat[2057] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
31 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
31 debian corridor-data[1917]: :31 socat[2068] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
32 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
32 debian corridor-data[1917]: :32 socat[2093] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
33 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
33 debian corridor-data[1917]: :33 socat[2195] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
34 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
34 debian corridor-data[1917]: :34 socat[2212] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
35 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
35 debian corridor-data[1917]: :35 socat[2228] E connect(5, AF=1 “/var/run/tor/control”, 22): No such file or directory
36 debian corridor-data[1917]: /usr/sbin/corridor-data: 39: /usr/sbin/corridor-data: cannot open /var/run/tor/control.authcookie: No such file
52 debian corridor-data[1917]: 515 Authentication failed: Wrong length on authentication cookie.
53 debian corridor-data[1917]: :53 socat[3031] E write(1, 0x2551aa0, 7963): Broken pipe
55 debian corridor-data[1917]: :55 socat[3072] E write(1, 0x853aa0, 7963): Broken pipe
56 debian corridor-data[1917]: :56 socat[3101] E write(1, 0x1235aa0, 7963): Broken pipe
57 debian corridor-data[1917]: :57 socat[3119] E write(1, 0x1de4aa0, 7963): Broken pipe
59 debian corridor-data[1917]: :59 socat[3127] E write(1, 0x10daaa0, 7963): Broken pipe
00 debian corridor-data[1917]: :00 socat[3138] E write(1, 0x14eeaa0, 7963): Broken pipe
01 debian corridor-data[1917]: :01 socat[3148] E write(1, 0x2668aa0, 7963): Broken pipe
03 debian corridor-data[1917]: :03 socat[3161] E write(1, 0xee1aa0, 7963): Broken pipe
04 debian corridor-data[1917]: :04 socat[3189] E write(1, 0x80daa0, 7963): Broken pipe
05 debian corridor-data[1917]: :05 socat[3206] E write(1, 0x1b9caa0, 7963): Broken pipe
07 debian corridor-data[1917]: :07 socat[3218] E write(1, 0xecfaa0, 7963): Broken pipe
08 debian corridor-data[1917]: :08 socat[3245] E write(1, 0x2072aa0, 7963): Broken pipe
09 debian corridor-data[1917]: :09 socat[3272] E write(1, 0x1e36aa0, 7963): Broken pipe
11 debian corridor-data[1917]: :11 socat[3298] E write(1, 0x9f0aa0, 7963): Broken pipe
12 debian corridor-data[1917]: :12 socat[3315] E write(1, 0xfb3aa0, 7963): Broken pipe
13 debian corridor-data[1917]: :13 socat[3338] E write(1, 0x1845aa0, 7963): Broken pipe
15 debian corridor-data[1917]: :15 socat[3359] E write(1, 0x705aa0, 7963): Broken pipe
16 debian corridor-data[1917]: :16 socat[3370] E write(1, 0xe9eaa0, 7963): Broken pipe
17 debian corridor-data[1917]: :17 socat[3377] E write(1, 0xf7daa0, 7963): Broken pipe
19 debian corridor-data[1917]: :19 socat[3394] E write(1, 0x1d6eaa0, 7963): Broken pipe
20 debian corridor-data[1917]: :20 socat[3413] E write(1, 0x1dd6aa0, 7963): Broken pipe
22 debian corridor-data[1917]: :22 socat[3422] E write(1, 0x2034aa0, 7963): Broken pipe
lines 1-53
sudo systemctl status corridor*
● corridor-init-logged.service - corridor’s logging
Loaded: loaded (/lib/systemd/system/corridor-init-logged.service; enabled; vendor
Drop-In: /lib/systemd/system/corridor-init-logged.service.d
└─qubes-service.conf, qubes.conf
Active: activating (start) since
Main PID: 5776 (corridor-init-l)
CGroup: /system.slice/corridor-init-logged.service
├─5776 /bin/sh -e /usr/sbin/corridor-init-logged
└─8636 sleep 1
debian systemd[1]: Starting corridor’s logging…