-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Traefik shuts down when SystemD watchdog run #1353
Comments
@yuav can you paste log outputs please? |
@timoreimann I have the very same problem with v1.2.3. Which log do you need?
It works without |
@guilhem any idea on what's going on here ? 🤔 |
It seems to work for me if I set the WatchdogSec to 10s. |
Same issue for me with 1.2.3. @philiplb's suggestion doesn't work for me. Only disabling the Watchdog timer completely (i.e. removing the line |
I will look at it this week-end |
Commit coreos/go-systemd@0c088e introduce cleaning environment. First usage of sdnotify (for type=notify) was clearing NOTIFY_SOCKET environment variable. sdnotify in watchdog was unable to ping back. Fix traefik#1353
Hi there, Just had the issue with 1.5.2 whereas I didn't have it before. New thing in my context is that I use ubuntu 16.04 LTS at my client whereas I used to used Debian on servers or HypriotOS on arm boards. I add to remove the
|
@nsteinmetz do you have a log (journald) to provides? |
Oh yes, I posted them on slack:
|
@nsteinmetz watchdog is sharing code with |
@nsteinmetz could you open a new issue. |
@ldez ok I will. |
Following issue now on : #2851 |
What version of Traefik are you using (
traefik version
)?1.2.1
What did you do?
Install service file from: https://github.com/containous/traefik/blob/master/contrib/systemd/traefik.service
What did you expect to see?
Running service
What did you see instead?
Crashing service every 2s, with SystemD starting it again. Adjusting watchdog timings correlate with time between crashes
The text was updated successfully, but these errors were encountered: