-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
corefile uploader: Updates per review comments offline #3915
Changes from 4 commits
ddfe7d8
64257b6
eec4326
6f84d55
e4bab36
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,13 @@ | ||
[Unit] | ||
Description=Host core file uploader daemon | ||
Requires=updategraph.service | ||
After=updategraph.service | ||
Requires=syslog.service | ||
After=syslog.service | ||
|
||
[Service] | ||
Type=simple | ||
ExecStart=/usr/bin/core_uploader.py | ||
StandardOutput=null | ||
Restart=on-failure | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we need back off here? if core_uploader is constantly restarting? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No need. The only failure that crashes the service, is some fatal things like, sonic_version.yaml does not have expected attributes or some fatal system related failure (which should crash many more ...), and running out of disk space. The one thing, I would need to take care of "running out of disk space". This I can take care of inside the script. |
||
|
||
[Install] | ||
WantedBy=multi-user.target |
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can do retry in the big loop. if it fails, retry in the big loop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess no. The bigger loop is either scan/wait-for-core. In either case, the next one would suffer the same fate. So I rather spew log & retry, until either I succeed or service is restarted, by someone alerted by these log messages.