Created
March 11, 2015 16:15
-
-
Save tleyden/289ad588ec7dff4444f5 to your computer and use it in GitHub Desktop.
fleet_logs_post_restart_machine_35.text
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| -- Logs begin at Wed 2015-03-11 15:35:52 UTC, end at Wed 2015-03-11 16:12:07 UTC. -- | |
| Mar 11 15:36:15 ip-10-239-174-35.ec2.internal systemd[1]: Starting fleet daemon... | |
| Mar 11 15:36:15 ip-10-239-174-35.ec2.internal systemd[1]: Started fleet daemon. | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: INFO fleet.go:58: Starting fleetd version 0.9.1 | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: INFO fleet.go:162: No provided or default config file found - proceeding without | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: INFO server.go:153: Establishing etcd connectivity | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 100ms | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:19 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 200ms | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 400ms | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 800ms | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 100ms | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:20 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 200ms | |
| Mar 11 15:36:21 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:21 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 400ms | |
| Mar 11 15:36:21 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused | |
| Mar 11 15:36:21 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Create /_coreos.com/fleet/machines/ad8cb97d6e5a49c6a2ceefaaae22ec6e/object}, retrying in 800ms | |
| Mar 11 15:36:22 ip-10-239-174-35.ec2.internal fleetd[590]: INFO server.go:164: Starting server components | |
| Mar 11 15:36:22 ip-10-239-174-35.ec2.internal fleetd[590]: INFO engine.go:80: Engine leader is cc2b61a5ab3f4d7992a8098154b2b906 | |
| Mar 11 15:39:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:40:38 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:41:08 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:41:09 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:41:13 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:41:22 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: unexpected end of JSON input | |
| Mar 11 15:41:22 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: unexpected EOF | |
| Mar 11 15:41:22 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Watch /_coreos.com/fleet/job}, retrying in 100ms | |
| Mar 11 15:41:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:41:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: too many redirects | |
| Mar 11 15:41:25 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/lease/engine-leader}, retrying in 100ms | |
| Mar 11 15:41:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_node@2.service (863b) | |
| Mar 11 15:41:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_node@2.service start: job=1195 | |
| Mar 11 15:41:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@2.service reason="unit scheduled here but not loaded" | |
| Mar 11 15:41:53 ip-10-239-174-35.ec2.internal fleetd[590]: 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 15:41:54 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@2.service (780b) | |
| Mar 11 15:41:54 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@2.service start: job=1278 | |
| Mar 11 15:41:54 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@2.service reason="unit scheduled here but not loaded" | |
| Mar 11 15:41:54 ip-10-239-174-35.ec2.internal fleetd[590]: 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 15:42:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:54 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:42:54 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:09 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:09 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:28 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:29 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:38 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:38 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:38 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:39 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:39 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:43 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:44 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:47 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR server.go:185: Server monitor triggered: Monitor timed out before successful heartbeat | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: INFO server.go:153: Establishing etcd connectivity | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:43:48 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled | |
| Mar 11 15:43:49 ip-10-239-174-35.ec2.internal fleetd[590]: INFO server.go:164: Starting server components | |
| Mar 11 15:44:05 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:05 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:05 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:05 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:05 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:06 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:07 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:07 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:09 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:10 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:14 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR server.go:185: Server monitor triggered: Monitor timed out before successful heartbeat | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO server.go:153: Establishing etcd connectivity | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR event.go:107: etcd watcher {Watch /_coreos.com/fleet/job} returned error: cancelled | |
| Mar 11 15:44:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:17 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:19 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:20 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:22 ip-10-239-174-35.ec2.internal fleetd[590]: INFO server.go:164: Starting server components | |
| Mar 11 15:44:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:44:53 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:08 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:08 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:08 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:08 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:08 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:19 ip-10-239-174-35.ec2.internal fleetd[590]: ERROR engine.go:150: Unable to determine cluster engine version | |
| Mar 11 15:45:20 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:23 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:45:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO client.go:291: Failed getting response from http://localhost:4001/: cancelled | |
| Mar 11 15:59:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:145: Triggered systemd unit couchbase_node@2.service stop: job=2805 | |
| Mar 11 15:59:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:275: Removing systemd unit couchbase_node@2.service | |
| Mar 11 15:59:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:145: Triggered systemd unit couchbase_sidekick@2.service stop: job=2807 | |
| Mar 11 15:59:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:275: Removing systemd unit couchbase_sidekick@2.service | |
| Mar 11 15:59:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_node@2.service reason="unit loaded but not scheduled here" | |
| Mar 11 15:59:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_sidekick@2.service reason="unit loaded but not scheduled here" | |
| Mar 11 16:03:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@2.service (780b) | |
| Mar 11 16:03:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_node@2.service (863b) | |
| Mar 11 16:03:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:198: Instructing systemd to reload units | |
| Mar 11 16:03:24 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@2.service start: job=3208 | |
| Mar 11 16:03:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_node@2.service start: job=3292 | |
| Mar 11 16:03:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@2.service reason="unit scheduled here but not loaded" | |
| Mar 11 16:03:25 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@2.service reason="unit scheduled here but not loaded" | |
| Mar 11 16:03:25 ip-10-239-174-35.ec2.internal fleetd[590]: 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:03:25 ip-10-239-174-35.ec2.internal fleetd[590]: 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:06:28 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:145: Triggered systemd unit couchbase_node@2.service stop: job=3700 | |
| Mar 11 16:06:28 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:275: Removing systemd unit couchbase_node@2.service | |
| Mar 11 16:06:29 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:145: Triggered systemd unit couchbase_sidekick@2.service stop: job=3702 | |
| Mar 11 16:06:29 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:275: Removing systemd unit couchbase_sidekick@2.service | |
| Mar 11 16:06:29 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_node@2.service reason="unit loaded but not scheduled here" | |
| Mar 11 16:06:29 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_sidekick@2.service reason="unit loaded but not scheduled here" | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_node@3.service (863b) | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@3.service (780b) | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_node@3.service start: job=3706 | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@3.service start: job=3789 | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@3.service reason="unit scheduled here but not loaded" | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@3.service reason="unit scheduled here but not loaded" | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_node@3.service reason="unit currently loaded but desired state is launched" | |
| Mar 11 16:07:15 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_sidekick@3.service reason="unit currently loaded but desired state is launched" | |
| Mar 11 16:08:34 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:145: Triggered systemd unit couchbase_sidekick@3.service stop: job=4040 | |
| Mar 11 16:08:34 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:275: Removing systemd unit couchbase_sidekick@3.service | |
| Mar 11 16:08:34 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:145: Triggered systemd unit couchbase_node@3.service stop: job=4041 | |
| Mar 11 16:08:34 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:275: Removing systemd unit couchbase_node@3.service | |
| Mar 11 16:08:34 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_sidekick@3.service reason="unit loaded but not scheduled here" | |
| Mar 11 16:08:34 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=UnloadUnit job=couchbase_node@3.service reason="unit loaded but not scheduled here" | |
| Mar 11 16:09:13 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_node@2.service (863b) | |
| Mar 11 16:09:13 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:198: Instructing systemd to reload units | |
| Mar 11 16:09:13 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_node@2.service start: job=4046 | |
| Mar 11 16:09:13 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_node@2.service reason="unit scheduled here but not loaded" | |
| Mar 11 16:09:13 ip-10-239-174-35.ec2.internal fleetd[590]: 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:09:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:262: Writing systemd unit couchbase_sidekick@2.service (780b) | |
| Mar 11 16:09:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO manager.go:134: Triggered systemd unit couchbase_sidekick@2.service start: job=4132 | |
| Mar 11 16:09:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=couchbase_sidekick@2.service reason="unit scheduled here but not loaded" | |
| Mar 11 16:09:16 ip-10-239-174-35.ec2.internal fleetd[590]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=couchbase_sidekick@2.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