Hi,
I’m using 1.1.0-dev4 and I keep seeing this kind of activity, at something like 12 hour intervals, sometimes less:
time="2016-06-12T23:48:48Z" level=info msg="Exiting rancher-compose-executor" version=v0.8.3
time="2016-06-12T23:48:50Z" level=info msg="Starting rancher-compose-executor" version=v0.8.3
time="2016-06-12T23:48:50Z" level=info msg="Initializing event router" workerCount=10
time="2016-06-12T23:48:51Z" level=info msg="Connection established"
time="2016-06-12T23:48:58Z" level=info msg="Exiting go-machine-service"
time="2016-06-12T23:49:00Z" level=info msg="Setting log level" logLevel=info
time="2016-06-12T23:49:00Z" level=info msg="Starting go-machine-service..." gitcommit=v0.31.4
time="2016-06-12T23:49:00Z" level=info msg="Waiting for handler registration (1/2)"
time="2016-06-12T23:49:02Z" level=info msg="Initializing event router" workerCount=10
time="2016-06-12T23:49:02Z" level=info msg="Connection established"
time="2016-06-12T23:49:02Z" level=info msg="Waiting for handler registration (2/2)"
time="2016-06-12T23:49:02Z" level=info msg="Initializing event router" workerCount=10
time="2016-06-12T23:49:02Z" level=info msg="Connection established"
time="2016-06-12T23:49:02Z" level=info msg="Installing builtin drivers"
time="2016-06-12T23:49:02Z" level=info msg="Downloading all drivers"
time="2016-06-12T23:49:03Z" level=info msg="Copying /var/lib/cattle/machine-drivers/1f7058341420e2f525168052818c3f819ff78e9ca5f57d5a650a049bcd5945e9-docker-machine-driver-packet => /usr/local/bin/docker-machine-driver-packet"
time="2016-06-12T23:49:03Z" level=info msg="Copying /var/lib/cattle/machine-drivers/56b60d32caac27345f4f55c4c91ed8adcfe7b3d5abcadd29d0551812f222f37e-docker-machine-driver-ubiquity => /usr/local/bin/docker-machine-driver-ubiquity"
time="2016-06-12T23:49:03Z" level=info msg="Done downloading all drivers"
time="2016-06-12T23:50:10Z" level=info msg="Registering backend for host [073e24f6-d6bf-4552-8631-4a31f8d7db48]"
time="2016-06-12T23:50:15Z" level=info msg="Registering backend for host [9aed6c94-36de-4d1e-9049-09dad2169419]"
time="2016-06-12T23:50:18Z" level=info msg="Registering backend for host [6e1a068f-79a4-44d6-b6c7-37c3799b3ccb]"
time="2016-06-12T23:50:26Z" level=info msg="Registering backend for host [6fb1608d-5fb4-4854-b300-54aa0d205cec]"
time="2016-06-13T00:44:26Z" level=info msg="Registering backend for host [68932a02-98a8-4d81-b069-cf648d6f6bc2]"
time="2016-06-13T00:44:27Z" level=info msg="Registering backend for host [66ac7563-623f-41c2-8326-e24e122ffc07]"
time="2016-06-13T02:04:42Z" level=info msg="Registering backend for host [2a1f9adc-d719-4f7f-8f31-9e01473f69ff]"
time="2016-06-13T02:04:50Z" level=info msg="Registering backend for host [fe26dbae-ba72-425e-a281-cb4d4a42e485]"
time="2016-06-13T02:04:56Z" level=info msg="Registering backend for host [5faf70bc-13dd-4f90-8fb2-01953a04264e]"
time="2016-06-13T03:04:22Z" level=info msg="Registering backend for host [04b10482-8893-4033-a6e0-c7a4abbffa65]"
time="2016-06-13T03:04:41Z" level=info msg="Registering backend for host [dd0ed418-cb8d-444e-8e88-8a33e8a2f95d]"
time="2016-06-13T03:04:43Z" level=info msg="Registering backend for host [9b85bde3-cadc-4fa3-a50b-3bfa811a71eb]"
time="2016-06-13T03:05:27Z" level=info msg="Registering backend for host [4cda845f-3d71-4197-a4e2-b9d25e29c0c3]"
time="2016-06-13T03:05:37Z" level=info msg="Registering backend for host [8da0b9ec-e253-465e-a12d-49336474ef23]"
time="2016-06-13T03:05:42Z" level=info msg="Registering backend for host [9fd12c8c-605d-4caf-8995-e1cf24d9fe27]"
time="2016-06-13T03:38:14Z" level=info msg="Registering backend for host [5e53a8f4-f689-45fb-b7d0-d6b70d1e0399]"
time="2016-06-13T03:38:14Z" level=info msg="Registering backend for host [7c34d2c8-7863-4232-8f93-c784224ec936]"
time="2016-06-13T03:38:35Z" level=info msg="Registering backend for host [a970e214-387c-4ac1-8857-c6386a7f7e0f]"
Is this expected behaviour? Can you explain what’s happening and why please? I also saw yesterday a lot (i.e. > 100) of these just before the ‘Registering backend…’ messages, not sure if this indicative of an issue of some sort?
2016/06/12 11:34:26 http: TLS handshake error from <IP>:4780: tls: first record does not look like a TLS handshake
Thanks,
John