-
Notifications
You must be signed in to change notification settings - Fork 79
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 to launch runner: jobberrunner exited prematurely #307
Comments
After running
So yes, it was just a bad config. A more accessable log would go a long way in these situations, maybe the daemon can log to |
Yeah...
… On Jun 23, 2020, at 4:56 AM, MCOfficer ***@***.***> wrote:
After running sudo /usr/lib/x86_64-linux-gnu/jobbermaster, the issue is apparently
Restarting runner for mcofficer
Runner for mcofficer exited with error: exit status 2
Error loading jobfile. Reloading previous one. Invalid 'hour' value: cannot be greater than 23.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x7dd81a]
goroutine 34 [running]:
main.(*JobManager).replaceCurrJobfile(0xc000228090, 0xc0001a80f0)
/home/runner/work/jobber/jobber/jobberrunner/job_manager.go:104 +0x15a
main.(*JobManager).loadJobfile(0xc000228090, 0x4, 0xc000036780)
/home/runner/work/jobber/jobber/jobberrunner/job_manager.go:184 +0xa4
main.(*JobManager).runMainThread.func1(0xc000228090)
/home/runner/work/jobber/jobber/jobberrunner/job_manager.go:243 +0x9b
created by main.(*JobManager).runMainThread
/home/runner/work/jobber/jobber/jobberrunner/job_manager.go:235 +0xe7
Failed to launch runner for mcofficer: jobberrunner for mcofficer exited prematurely.
So yes, it was just a bad config. A more accessable log would go a long way in these situations, maybe the daemon can log to /var/log/?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I also have this issue. Found this solution: to delete all files in /var/log/jobber and restart the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, since a couple days after updating to v1.4.4 i have the following issue:
This happens whenever i try to launch jobber. Consequentially, none of my cron jobs are currently running.
This is jobber v1.4.4 on ubuntu 18.04, installed via the .deb. I already tried to purge and reinstall jobber, no dice. If you need any other information, just ask.
The text was updated successfully, but these errors were encountered: