Advertisement
Guest User

Untitled

a guest
Apr 1st, 2015
228
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.05 KB | None | 0 0
  1. -- Reboot --
  2. Apr 01 22:09:15 corb1.c.inductive-actor-543.internal systemd[1]: Starting fleet daemon...
  3. Apr 01 22:09:15 corb1.c.inductive-actor-543.internal systemd[1]: Started fleet daemon.
  4. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO fleet.go:58: Starting fleetd version 0.9.1
  5. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO fleet.go:162: No provided or default config file found - proceeding without
  6. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO server.go:153: Establishing etcd connectivity
  7. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
  8. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/383f91c3c6c9e7d7974758febc914427/object}, retrying in 100ms
  9. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
  10. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/383f91c3c6c9e7d7974758febc914427/object}, retrying in 200ms
  11. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO client.go:291: Failed getting response from http://localhost:4001/: dial tcp 127.0.0.1:4001: connection refused
  12. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR client.go:213: Unable to get result for {Update /_coreos.com/fleet/machines/383f91c3c6c9e7d7974758febc914427/object}, retrying in 400ms
  13. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO server.go:164: Starting server components
  14. Apr 01 22:09:16 corb1.c.inductive-actor-543.internal fleetd[595]: INFO engine.go:80: Engine leader is 4b51b24061a7c80747ed12eab14e4691
  15. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:262: Writing systemd unit mysql-wordpress.service (849b)
  16. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:262: Writing systemd unit spaera-login@.service (626b)
  17. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:262: Writing systemd unit spaera-restapi@1.service (620b)
  18. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:262: Writing systemd unit bo-wordpress.service (1098b)
  19. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:134: Triggered systemd unit bo-wordpress.service start: job=1321
  20. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:134: Triggered systemd unit mysql-wordpress.service start: job=1322
  21. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO manager.go:134: Triggered systemd unit spaera-restapi@1.service start: job=1490
  22. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR manager.go:136: Failed to trigger systemd unit spaera-login@.service start: Unit name spaera-login@.service is not valid.
  23. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=mysql-wordpress.service reason="unit scheduled here but not loaded"
  24. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=spaera-login@.service reason="unit scheduled here but not loaded"
  25. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=spaera-restapi@1.service reason="unit scheduled here but not loaded"
  26. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=LoadUnit job=bo-wordpress.service reason="unit scheduled here but not loaded"
  27. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=bo-wordpress.service reason="unit currently loaded but desired state is launched"
  28. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=mysql-wordpress.service reason="unit currently loaded but desired state is launched"
  29. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=spaera-restapi@1.service reason="unit currently loaded but desired state is launched"
  30. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: INFO reconcile.go:311: AgentReconciler completed task: type=StartUnit job=spaera-login@.service reason="unit currently loaded but desired state is launched"
  31. Apr 01 22:09:18 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR generator.go:67: Failed fetching current unit states: Unit name spaera-login@.service is not valid.
  32. Apr 01 22:09:19 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR generator.go:67: Failed fetching current unit states: Unit name spaera-login@.service is not valid.
  33. Apr 01 22:09:20 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR generator.go:67: Failed fetching current unit states: Unit name spaera-login@.service is not valid.
  34. Apr 01 22:09:21 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR generator.go:67: Failed fetching current unit states: Unit name spaera-login@.service is not valid.
  35. Apr 01 22:09:22 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR generator.go:67: Failed fetching current unit states: Unit name spaera-login@.service is not valid.
  36. Apr 01 22:09:23 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR reconcile.go:81: Unable to determine agent's current state: failed fetching unit states from UnitManager: Unit name spaera-login@.service is not valid.
  37. Apr 01 22:09:23 corb1.c.inductive-actor-543.internal fleetd[595]: ERROR generator.go:67: Failed fetching current unit states: Unit name spaera-login@.service is not valid.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement