Error when updating VPS with the latest snapshot. about openmptcprouter

[Ysurac]

Please use the template.

What is the result of systemctl status [email protected] and journalctl -xeu [email protected] ?

[vempire-ghost]

vempire@instance-3:~$ systemctl status [email protected]
× [email protected] - Glorytun UDP on tun0
Loaded: loaded (/lib/systemd/system/[email protected]; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2024-02-23 13:42:54 UTC; 13s ago
Duration: 4ms
Process: 4026 ExecStart=/usr/local/bin/glorytun-udp-run /etc/glorytun-udp/tun0 (code=exited, status=2)
Process: 4027 ExecStartPost=/etc/glorytun-udp/post.sh /etc/glorytun-udp/tun0 (code=exited, status=2)
Main PID: 4026 (code=exited, status=2)
CPU: 8ms

Feb 23 13:42:53 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Failed with result 'exit-code'.
Feb 23 13:42:53 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Failed to start [email protected] - Glorytun UDP on tun0.
Feb 23 13:42:54 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
Feb 23 13:42:54 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Stopped [email protected] - Glorytun UDP on tun0.
Feb 23 13:42:54 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Start request repeated too quickly.
Feb 23 13:42:54 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Failed with result 'exit-code'.
Feb 23 13:42:54 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Failed to start [email protected] - Glorytun UDP on tun0.

vempire@instance-3:~$ journalctl -xeu [email protected]
░░ Automatic restarting of the unit [email protected] has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Stopped [email protected] - Glorytun UDP on tun0.
░░ Subject: A stop job for unit [email protected] has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit [email protected] has finished.
░░
░░ The job identifier is 5163 and the job result is done.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Starting [email protected] - Glorytun UDP on tun0...
░░ Subject: A start job for unit [email protected] has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit [email protected] has begun execution.
░░
░░ The job identifier is 5163.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal glorytun-udp-run[4818]: /usr/local/bin/glorytun-udp-run: 10: .: cannot open /etc/glorytun-udp/tun0: Permission denied
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit [email protected] has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal post.sh[4819]: /etc/glorytun-udp/post.sh: 3: .: cannot open /etc/glorytun-udp/tun0: Permission denied
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Failed to start [email protected] - Glorytun UDP on tun0.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 5163 and the job result is failed.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit [email protected] has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Stopped [email protected] - Glorytun UDP on tun0.
░░ Subject: A stop job for unit [email protected] has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit [email protected] has finished.
░░
░░ The job identifier is 5239 and the job result is done.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Start request repeated too quickly.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Feb 23 13:43:35 instance-3.southamerica-east1-a.c.helical-fin-392321.internal systemd[1]: Failed to start [email protected] - Glorytun UDP on tun0.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 5239 and the job result is failed.

[Ysurac]

What is the result of ls -la /etc/glorytun-udp/ ?

[vempire-ghost]

vempire@instance-3:~$ ls -la /etc/glorytun-udp/
total 24
drwxr-xr-x 2 vempire vempire 4096 Feb 23 13:30 .
drwxr-xr-x 97 root root 4096 Feb 23 14:35 ..
-rwxr-xr-x 1 vempire vempire 641 Jun 14 2021 post.sh
-rw------- 1 vempire vempire 76 Feb 1 23:34 tun0
-rw------- 1 vempire vempire 86 Sep 2 2021 tun0.dpkg-dist
-rw------- 1 vempire vempire 65 Nov 27 23:49 tun0.key

[Ysurac]

Why files belong to user vempire ? Should belong to user root and group root

[vempire-ghost]

A while ago, I tried to copy the files via SFTP, and as I didn't have the necessary permissions, I took them for my user and forgot to return them to root. Thank you, returning them to root, the update was successful.