You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
When I fleetctl start auth-radius-1, both units start. When I fleet stop auth-radius-1, the cache process continues running. This is all expected.
When I then fleetctl stop auth-cache-1, fleet refuses to cooperate. Here's what I see:
$ fleetctl --debug stop auth-cache-1
2015/10/28 08:00:00 DEBUG http.go:28: HTTP GET http://domain-sock/fleet/v1/units?alt=json
2015/10/28 08:00:00 DEBUG http.go:31: HTTP GET http://domain-sock/fleet/v1/units?alt=json 200 OK
2015/10/28 08:00:00 DEBUG stop.go:68: Unit(auth-cache-1.service) already loaded, skipping.
The stop command seems to think that auth-cache-1.service is already in loaded state. But running fleetctl list-units confirms the container is still running:
$ fleetctl list-units
UNIT MACHINE ACTIVE SUB
auth-cache-1.service ef72cebf.../172.16.4.10 active running
auth-radius-1.service ef72cebf.../172.16.4.10 failed failed
This is on CoreOS 845.0.0, Fleet 0.11.5
The text was updated successfully, but these errors were encountered:
I've got two unit files loaded into fleet:
auth-radius-1.service
auth-cache-1.service
When I
fleetctl start auth-radius-1
, both units start. When Ifleet stop auth-radius-1
, the cache process continues running. This is all expected.When I then
fleetctl stop auth-cache-1
, fleet refuses to cooperate. Here's what I see:The stop command seems to think that auth-cache-1.service is already in loaded state. But running
fleetctl list-units
confirms the container is still running:This is on CoreOS 845.0.0, Fleet 0.11.5
The text was updated successfully, but these errors were encountered: