Skip to content

Instantly share code, notes, and snippets.

@tleyden
Created March 11, 2015 16:18
Show Gist options
  • Save tleyden/76c267fc3f8d05f778a7 to your computer and use it in GitHub Desktop.
Save tleyden/76c267fc3f8d05f778a7 to your computer and use it in GitHub Desktop.
fleet_logs_post_restart_machine_12.text
-- Logs begin at Wed 2015-03-11 15:36:54 UTC, end at Wed 2015-03-11 16:12:31 UTC. --
Mar 11 15:37:18 ip-10-156-7-12.ec2.internal systemd[1]: Starting fleet daemon...
Mar 11 15:37:18 ip-10-156-7-12.ec2.internal systemd[1]: Started fleet daemon.
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO fleet.go:58: Starting fleetd version 0.9.1
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO fleet.go:162: No provided or default config file found - proceeding without
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:153: Establishing etcd connectivity
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 100ms
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:23 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 200ms
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 400ms
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 800ms
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 100ms
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:24 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 200ms
Mar 11 15:37:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:25 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 400ms
Mar 11 15:37:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
Mar 11 15:37:25 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 800ms
Mar 11 15:37:26 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: too many redirects
Mar 11 15:37:26 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 100ms
Mar 11 15:37:26 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: too many redirects
Mar 11 15:37:26 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/8995d6d7c1f14cfdbf278987f28968be/object}, retrying in 200ms
Mar 11 15:37:27 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:164: Starting server components
Mar 11 15:37:27 ip-10-156-7-12.ec2.internal fleetd[601]: INFO engine.go:80: Engine leader is cc2b61a5ab3f4d7992a8098154b2b906
Mar 11 15:41:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@1.service (780b)
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_node@1.service (863b)
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@1.service start: job=1116
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_node@1.service start: job=1200
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@1.service reason="unit scheduled here but not loaded"
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@1.service reason="unit scheduled here but not loaded"
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_sidekick@1.service reason="unit currently loaded but desired state is launched"
Mar 11 15:41:54 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_node@1.service reason="unit currently loaded but desired state is launched"
Mar 11 15:42:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:14 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:14 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:14 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:28 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:28 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:28 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:28 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:28 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:31 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:32 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:36 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:37 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR server.go:185: Server monitor triggered: Monitor timed out before successful heartbeat
Mar 11 15:42:37 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:153: Establishing etcd connectivity
Mar 11 15:42:37 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:164: Starting server components
Mar 11 15:42:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:42:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:09 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:09 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:28 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:38 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:39 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:39 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:39 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:39 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:43 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:44 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:47 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR server.go:185: Server monitor triggered: Monitor timed out before successful heartbeat
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:153: Establishing etcd connectivity
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:43:48 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled
Mar 11 15:43:49 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:164: Starting server components
Mar 11 15:44:05 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:05 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:05 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:05 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:05 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:06 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:06 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:06 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:09 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:10 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:14 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR server.go:185: Server monitor triggered: Monitor timed out before successful heartbeat
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:153: Establishing etcd connectivity
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:15 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled
Mar 11 15:44:16 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:17 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:19 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:20 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:22 ip-10-156-7-12.ec2.internal fleetd[601]: INFO server.go:164: Starting server components
Mar 11 15:44:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:44:53 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:08 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:08 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:08 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:08 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:08 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:19 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR engine.go:150: Unable to determine cluster engine version
Mar 11 15:45:19 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:23 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:45:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled
Mar 11 15:59:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:145: Triggered systemd unit couchbase_sidekick@1.service stop: job=2720
Mar 11 15:59:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:275: Removing systemd unit couchbase_sidekick@1.service
Mar 11 15:59:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:145: Triggered systemd unit couchbase_node@1.service stop: job=2721
Mar 11 15:59:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:275: Removing systemd unit couchbase_node@1.service
Mar 11 15:59:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_sidekick@1.service reason="unit loaded but not scheduled here"
Mar 11 15:59:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_node@1.service reason="unit loaded but not scheduled here"
Mar 11 16:03:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_node@1.service (863b)
Mar 11 16:03:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:198: Instructing systemd to reload units
Mar 11 16:03:24 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@1.service (780b)
Mar 11 16:03:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_node@1.service start: job=3041
Mar 11 16:03:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@1.service start: job=3124
Mar 11 16:03:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@1.service reason="unit scheduled here but not loaded"
Mar 11 16:03:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@1.service reason="unit scheduled here but not loaded"
Mar 11 16:03:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_node@1.service reason="unit currently loaded but desired state is launched"
Mar 11 16:03:25 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_sidekick@1.service reason="unit currently loaded but desired state is launched"
Mar 11 16:06:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:145: Triggered systemd unit couchbase_sidekick@1.service stop: job=3614
Mar 11 16:06:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:275: Removing systemd unit couchbase_sidekick@1.service
Mar 11 16:06:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:145: Triggered systemd unit couchbase_node@1.service stop: job=3615
Mar 11 16:06:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:275: Removing systemd unit couchbase_node@1.service
Mar 11 16:06:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_sidekick@1.service reason="unit loaded but not scheduled here"
Mar 11 16:06:29 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_node@1.service reason="unit loaded but not scheduled here"
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_node@2.service (863b)
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@2.service (780b)
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_node@2.service start: job=3620
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@2.service start: job=3703
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@2.service reason="unit scheduled here but not loaded"
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@2.service reason="unit scheduled here but not loaded"
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_node@2.service reason="unit currently loaded but desired state is launched"
Mar 11 16:07:15 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_sidekick@2.service reason="unit currently loaded but desired state is launched"
Mar 11 16:08:34 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:145: Triggered systemd unit couchbase_sidekick@2.service stop: job=4035
Mar 11 16:08:34 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:275: Removing systemd unit couchbase_sidekick@2.service
Mar 11 16:08:34 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:145: Triggered systemd unit couchbase_node@2.service stop: job=4036
Mar 11 16:08:34 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:275: Removing systemd unit couchbase_node@2.service
Mar 11 16:08:34 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_sidekick@2.service reason="unit loaded but not scheduled here"
Mar 11 16:08:34 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_node@2.service reason="unit loaded but not scheduled here"
Mar 11 16:09:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_node@1.service (863b)
Mar 11 16:09:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:198: Instructing systemd to reload units
Mar 11 16:09:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:134: Triggered systemd unit couchbase_node@1.service start: job=4041
Mar 11 16:09:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@1.service reason="unit scheduled here but not loaded"
Mar 11 16:09:13 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_node@1.service reason="unit currently loaded but desired state is launched"
Mar 11 16:09:16 ip-10-156-7-12.ec2.internal fleetd[601]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@1.service (780b)
Mar 11 16:09:16 ip-10-156-7-12.ec2.internal fleetd[601]: ERROR manager.go:136: Failed to trigger systemd unit couchbase_sidekick@1.service start: Unit couchbase_sidekick@1.service failed to load: No such file or directory.
Mar 11 16:09:16 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@1.service reason="unit scheduled here but not loaded"
Mar 11 16:09:16 ip-10-156-7-12.ec2.internal fleetd[601]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_sidekick@1.service reason="unit currently loaded but desired state is launched"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment