Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

does not fail systemd unit file if folder inaccessible #46

Closed
adrelanos opened this issue Dec 12, 2019 · 1 comment
Closed

does not fail systemd unit file if folder inaccessible #46

adrelanos opened this issue Dec 12, 2019 · 1 comment

Comments

@adrelanos
Copy link
Contributor 

user@debian:~$ sudo journalctl | grep -i corridor
Dec 11 08:33:03 debian sudo[3338]:     user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/apt install corridor
Dec 11 08:35:15 debian systemd[1]: Started corridor's relay list.
Dec 11 08:35:15 debian systemd[1]: Starting corridor's forwarding...
Dec 11 08:35:15 debian systemd[1]: Starting corridor's logging...
Dec 11 08:35:15 debian systemd[1]: Starting corridor's source NAT...
Dec 11 08:35:15 debian corridor-data[3861]: Processing router list...
Dec 11 08:35:16 debian corridor-data[3861]: tee: /rw/corridor_relays.tmp: No such file or directory
Dec 11 08:35:16 debian systemd[1]: Started corridor's source NAT.
Dec 11 08:35:16 debian corridor-data[3861]: corridor_relays updated.
Dec 11 08:35:16 debian corridor-data[3861]: mv: cannot stat '/rw/corridor_relays.tmp': No such file or directory
Dec 11 08:35:17 debian corridor-init-forwarding[3865]: net.ipv4.ip_forward = 1
Dec 11 08:35:17 debian corridor-init-forwarding[3865]: net.ipv6.conf.all.forwarding = 0
Dec 11 08:35:17 debian systemd[1]: Started corridor's forwarding.
Dec 11 08:35:17 debian corridor-init-logged[3871]: corridor_logged updated.
Dec 11 08:35:17 debian systemd[1]: Started corridor's logging.
Dec 11 08:35:17 debian systemd[1]: Reached target corridor, a Tor traffic whitelisting gateway.

This error is ignored.

Dec 11 08:35:16 debian corridor-data[3861]: tee: /rw/corridor_relays.tmp: No such file or directory

Could you make that error out instead please?
rustybird added a commit that referenced this issue Jan 15, 2020
@rustybird
Fail corridor-data earlier on process_consensus() failure
e400a03 
Terminate the process group immediately if the consensus reader function
fails, instead of possibly a few hours later when the next consensus
arrives. Use SIGUSR1, which by default terminates without additional
actions and is not treated as a successful exit by systemd.

#46
@rustybird
Copy link
Owner

Thanks! And sorry for the long delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adrelanos @rustybird