question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Automatic worker update cause container to crash

See original GitHub issue

Description:

worker version: 2.169.1

Hi all, I’m running the worker as self-hosted. I have build my own container image with the binary etc.

After some time, I was not able to reproduce why container died ( since I run it as service in detached mode).

I found out that the worker try to update itself automatically and then it fails.

2020-05-17 20:23:37Z: Listening for Jobs
Runner update in progress, do not shutdown runner.
Downloading 2.262.1 runner
Waiting for current job finish running.
Generate and execute update script.
Runner will exit shortly for update, should back online within 10 seconds.
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found
/home/CI/_work/_update.sh: line 31: ping: command not found

I think automatic update the worker is not what user want generally by default.

I think it should be an option like to either enabling automatic updating if wanted but not the default behaviour.

thx! let me know

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
MalloZupcommented, May 18, 2020

@bryanmacfarlane

Runner update in progress, do not shutdown runner.
Downloading 2.262.1 runner
Waiting for current job finish running.
Generate and execute update script.
Runner will exit shortly for update, should back online within 10 seconds.
Runner listener exited with error code 3
Runner listener exit because of updating, re-launch runner in 5 seconds.
Starting Runner listener with startup type: service
Started listener process

That worked for me

1reaction
NPelletcommented, Sep 14, 2020

Works very nicely 😃 Quick note for those who end up here. runsvc.sh is in ./bin/

Read more comments on GitHub >

github_iconTop Results From Across the Web

Restart Docker Containers when they Crash Automatically
It looks ok to me, but the best way to test it is to intentionally make one of the containers fail and see...
Read more >
Kubernetes CrashLoopBackOff Error: What It Is and How to ...
It's a common error message that occurs when a Kubernetes container fails to start up properly for some reason, then repeatedly crashes.
Read more >
5 Reasons your Kubernetes Pod can crash
When the application crashes, Kubernetes will spin up another container. But since the pod was not the issue, the application will crash again....
Read more >
Find out Why Your Docker Container Keeps Crashing
Your Docker container is exiting without a useful error message? Here are a few ways to find out what's happening.
Read more >
An Ubuntu kernel bug causes container crashes
First, the bug was in a security branch. Second, it wasn't just the containers that crashed. If you booted containers on boot via...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found