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.

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

Failed with error when : sudo systemctl enable --now zrok-share.service #700

Closed
sircsaba opened this issue Jul 15, 2024 · 4 comments
Closed
Assignees

Comments

@sircsaba
Copy link

sircsaba commented Jul 15, 2024

When I tried to enable the systemctl I got the following errors:

Job for zrok-share.service failed because the control process exited with error code.
See "systemctl status zrok-share.service" and "journalctl -xeu zrok-share.service" for details.

How can I see what exactly went wrong ?

My reserve share works perfectly with zrok ... Its for sharing a url

I'm running on a Raspberry PI4 ARM64 at 64bits raspian OS
I used the Ubuntu and Debian install of Front end.

This is what I get when I check the status:

● zrok-share.service - zrok reserved public share service
     Loaded: loaded (/lib/systemd/system/zrok-share.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/zrok-share.service.d
             └─override.conf
     Active: activating (auto-restart) (Result: exit-code) since Mon 2024-07-15 20:13:18 BST; 2s ago
    Process: 54011 ExecStartPre=/opt/openziti/bin/zrok-enable.bash /opt/openziti/etc/zrok/zrok-share.env (code=exited, s>
        CPU: 441ms
lines 1-7/7 (END)
● zrok-share.service - zrok reserved public share service
     Loaded: loaded (/lib/systemd/system/zrok-share.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/zrok-share.service.d
             └─override.conf
     Active: activating (auto-restart) (Result: exit-code) since Mon 2024-07-15 20:13:18 BST; 2s ago
    Process: 54011 ExecStartPre=/opt/openziti/bin/zrok-enable.bash /opt/openziti/etc/zrok/zrok-share.env (code=exited, status=1/FAI>
        CPU: 441ms
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-7/7 (END)...skipping...
● zrok-share.service - zrok reserved public share service
     Loaded: loaded (/lib/systemd/system/zrok-share.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/zrok-share.service.d
             └─override.conf
     Active: activating (auto-restart) (Result: exit-code) since Mon 2024-07-15 20:13:18 BST; 2s ago
    Process: 54011 ExecStartPre=/opt/openziti/bin/zrok-enable.bash /opt/openziti/etc/zrok/zrok-share.env (code=exited, status=1/FAILURE)
        CPU: 441ms

And the second log:

Jul 15 20:16:28 nightscout zrok-enable.bash[55406]: (where newEndpoint is something like: https://some.zrok.io)
Jul 15 20:16:28 nightscout systemd[1]: zrok-share.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStartPre= process belonging to unit zrok-share.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 15 20:16:28 nightscout systemd[1]: zrok-share.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit zrok-share.service has entered the 'failed' state with result 'exit-code'.
Jul 15 20:16:28 nightscout systemd[1]: Failed to start zrok-share.service - zrok reserved public share service.
░░ Subject: A start job for unit zrok-share.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit zrok-share.service has finished with a failure.
░░
░░ The job identifier is 23629 and the job result is failed.
Jul 15 20:16:31 nightscout systemd[1]: zrok-share.service: Scheduled restart job, restart counter is at 255.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit zrok-share.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 15 20:16:31 nightscout systemd[1]: Stopped zrok-share.service - zrok reserved public share service.
░░ Subject: A stop job for unit zrok-share.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit zrok-share.service has finished.
░░
░░ The job identifier is 23703 and the job result is done.
Jul 15 20:16:32 nightscout systemd[1]: Starting zrok-share.service - zrok reserved public share service...
░░ Subject: A start job for unit zrok-share.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit zrok-share.service has begun execution.
░░
░░ The job identifier is 23703.
Jul 15 20:16:32 nightscout zrok-enable.bash[55443]: INFO: reading enable parameters from /opt/openziti/etc/zrok/zrok-share.env
Jul 15 20:16:32 nightscout zrok-enable.bash[55447]: zrok configuration updated
Jul 15 20:16:32 nightscout zrok-enable.bash[55443]: INFO: running: zrok enable ...
Jul 15 20:16:32 nightscout zrok-enable.bash[55443]: {"file":"/home/runner/work/zrok/zrok/cmd/zrok/enable.go:102","func":"main.(*enableCommand).run","level":"info","msg":"contacting the zrok servic>
Jul 15 20:16:32 nightscout zrok-enable.bash[55443]: {"file":"/home/runner/work/zrok/zrok/cmd/zrok/enable.go:113","func":"main.(*enableCommand).run","level":"error","msg":"the zrok service returned>
l
@qrkourier
Copy link
Member

The second log looks like it has the info, but it's cut off in the copy/paste. Can you run it like this instead?

journalctl -xeu zrok-share.service --no-pager

The enable command failed for some reason. The token or API endpoint might be incorrect, there could be an illegal character in the environment description.

@sircsaba
Copy link
Author

I just tried it again because I always copy and paste the values from the dashboard etc. I then noticed that there was actually a space inserted for some reason ... This seems to have been the problem !!
In the mean time I did a cron job to actually achieve the same thing !!! Thanks for the thought of a space !!

@dovholuknf
Copy link
Member

sounds like we can close this then. reopen if needed. cheers

@sircsaba
Copy link
Author

Yes !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants