New question #290719 on Graphite: https://answers.launchpad.net/graphite/+question/290719
I have graphite running in a docker container. If there is something done on the host machine(e.g. updates that require reboot) and the docker containers restart(containers set to --restart=always) sometimes carbon-cache fails to start. See log file from supervisor(which is what I see people using in docker hub) 2016-04-08 13:32:44,313 INFO exited: carbon-cache (exit status 1; not expected) 2016-04-08 13:32:44,510 INFO spawned: 'carbon-cache' with pid 28 2016-04-08 13:32:44,649 INFO exited: carbon-cache (exit status 1; not expected) 2016-04-08 13:32:46,230 INFO spawned: 'carbon-cache' with pid 35 2016-04-08 13:32:46,374 INFO exited: carbon-cache (exit status 1; not expected) 2016-04-08 13:32:48,380 INFO spawned: 'carbon-cache' with pid 38 2016-04-08 13:32:48,509 INFO exited: carbon-cache (exit status 1; not expected) 2016-04-08 13:32:51,513 INFO spawned: 'carbon-cache' with pid 41 2016-04-08 13:32:51,680 INFO exited: carbon-cache (exit status 1; not expected) 2016-04-08 13:32:52,681 INFO gave up: carbon-cache entered FATAL state, too many start retries too quickly Also looked at the carbon-cache log file, but found no entries related to this. I have looked to see if others have had this problem and came across a few, however there has been no answer to why this occurs and a solution. Any ideas on why this occurs and if there is a solution to stop it happening? -- You received this question notification because your team graphite-dev is an answer contact for Graphite. _______________________________________________ Mailing list: https://launchpad.net/~graphite-dev Post to : graphite-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
