snap.microk8s.daemon-apiserver-kicker.service: Start request repeated too quickly.

[groner]

I had microk8s networking stop working today.

Aug 12 10:57:03 dipper microk8s.daemon-apiserver-kicker[1621]: /snap/microk8s/743/apiservice-kicker: line 21: /snap/microk8s/743/bin/sleep: No such file or directory
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Main process exited, code=exited, status=127/n/a
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Service RestartSec=100ms expired, scheduling restart.
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Scheduled restart job, restart counter is at 1.
Aug 12 10:57:03 dipper systemd[1]: Stopped Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:03 dipper systemd[1]: Started Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:03 dipper microk8s.daemon-apiserver-kicker[16514]: /snap/microk8s/743/apiservice-kicker: line 21: /snap/microk8s/743/bin/sleep: No such file or directory
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Main process exited, code=exited, status=127/n/a
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Service RestartSec=100ms expired, scheduling restart.
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Scheduled restart job, restart counter is at 2.
Aug 12 10:57:03 dipper systemd[1]: Stopped Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:03 dipper systemd[1]: Started Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:03 dipper microk8s.daemon-apiserver-kicker[16535]: /snap/microk8s/743/apiservice-kicker: line 21: /snap/microk8s/743/bin/sleep: No such file or directory
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Main process exited, code=exited, status=127/n/a
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Service RestartSec=100ms expired, scheduling restart.
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Scheduled restart job, restart counter is at 3.
Aug 12 10:57:03 dipper systemd[1]: Stopped Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:03 dipper systemd[1]: Started Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:03 dipper microk8s.daemon-apiserver-kicker[16558]: /snap/microk8s/743/apiservice-kicker: line 21: /snap/microk8s/743/bin/sleep: No such file or directory
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Main process exited, code=exited, status=127/n/a
Aug 12 10:57:03 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Service RestartSec=100ms expired, scheduling restart.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Scheduled restart job, restart counter is at 4.
Aug 12 10:57:04 dipper systemd[1]: Stopped Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:04 dipper systemd[1]: Started Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:04 dipper microk8s.daemon-apiserver-kicker[16582]: /snap/microk8s/743/apiservice-kicker: line 21: /snap/microk8s/743/bin/sleep: No such file or directory
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Main process exited, code=exited, status=127/n/a
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Service RestartSec=100ms expired, scheduling restart.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Scheduled restart job, restart counter is at 5.
Aug 12 10:57:04 dipper systemd[1]: Stopped Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:04 dipper systemd[1]: Started Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:04 dipper microk8s.daemon-apiserver-kicker[16610]: /snap/microk8s/743/apiservice-kicker: line 21: /snap/microk8s/743/bin/sleep: No such file or directory
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Main process exited, code=exited, status=127/n/a
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Service RestartSec=100ms expired, scheduling restart.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Scheduled restart job, restart counter is at 6.
Aug 12 10:57:04 dipper systemd[1]: Stopped Service for snap application microk8s.daemon-apiserver-kicker.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Start request repeated too quickly.
Aug 12 10:57:04 dipper systemd[1]: snap.microk8s.daemon-apiserver-kicker.service: Failed with result 'exit-code'.
Aug 12 10:57:04 dipper systemd[1]: Failed to start Service for snap application microk8s.daemon-apiserver-kicker.

Running systemctl start snap.microk8s.daemon-apiserver-kicker restored functionality.

The path /snap/microk8s/743/bin/sleep exists, and according to snap info microk8s this didn't coincide with an update.

This was a bit of an ordeal to investigate (started with ingress controller failing with no errors), is this something microk8s.status could/should check for?

inspection-report-20190813_183218.tar.gz

[ktsakalozos]

Hi @groner thank you for reporting this. I cannot think of a way this may happen. The sleep binary is in the snap, why would the daemon not see it? Lets see if the snapcraft folks have a good explanation why/when this may happen https://forum.snapcraft.io/t/daemon-not-seeing-binary-under-snap/12778.

Thank you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.