-
Notifications
You must be signed in to change notification settings - Fork 81
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
nscd, unscd, cron and crond fail to restart #139
Comments
I experience this same issue with COS version 93:
|
When lots of servers start or restart at once, we get 100s of these errors that end up triggering server alerts. Could someone please let us know if this is the same as #134 and thus being worked on? (Should I open a GCP Support case?) |
The background for these log messages: on startup, the guest agent makes configuration changes, then restarts services for the changes to take effect. It logs a warning message when a service isn't found, but it is benign. We actually already reduced this extraneous logging in #122 so if you use an updated version of the guest agent, these logs should go away. I think some of our partner distributions have not yet received this change, i.e. Ubuntu or COS. |
Thanks @hopkiw. Indeed the latest version available from/for Ubuntu is 20210629.00. Do you know if there's a way to accelerate the release of a new version? (Is that done by Canonical or Google?) |
Canonical takes updates on a regular cadence, except for critical vulnerabilities, where we will ask them to prioritize an update or patch. I don't know if end users can influence the process, but I imagine you might try filing them a bug. |
* add image test task in pipeline fix bug * add other image-test job * make iamge test as task * using full image name instead family * add image test task in pipeline fix bug * fix centos-7 * fix missing image-test * add almalinux rocky-linux
When google-guest-agent tries to start, it seems to try to start nscd, unscd, cron and crond, but those units are not present on our servers.
Are these benign? If so, can they be downgraded from Errors?
These same error lines appear in #134, but in my case, the service is active/running, not dead.
The text was updated successfully, but these errors were encountered: