{"action":"closed","issue":{"url":"https://api.github.com/repos/cloudfoundry/cloud_controller_ng/issues/417","labels_url":"https://api.github.com/repos/cloudfoundry/cloud_controller_ng/issues/417/labels{/name}","comments_url":"https://api.github.com/repos/cloudfoundry/cloud_controller_ng/issues/417/comments","events_url":"https://api.github.com/repos/cloudfoundry/cloud_controller_ng/issues/417/events","html_url":"https://github.com/cloudfoundry/cloud_controller_ng/issues/417","id":102966959,"number":417,"title":"Broken cc.runner logger","user":{"login":"vlerenc","id":4974203,"avatar_url":"https://avatars.githubusercontent.com/u/4974203?v=3","gravatar_id":"","url":"https://api.github.com/users/vlerenc","html_url":"https://github.com/vlerenc","followers_url":"https://api.github.com/users/vlerenc/followers","following_url":"https://api.github.com/users/vlerenc/following{/other_user}","gists_url":"https://api.github.com/users/vlerenc/gists{/gist_id}","starred_url":"https://api.github.com/users/vlerenc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vlerenc/subscriptions","organizations_url":"https://api.github.com/users/vlerenc/orgs","repos_url":"https://api.github.com/users/vlerenc/repos","events_url":"https://api.github.com/users/vlerenc/events{/privacy}","received_events_url":"https://api.github.com/users/vlerenc/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-08-25T07:26:27Z","updated_at":"2015-12-02T22:48:53Z","closed_at":"2015-12-02T22:48:53Z","body":"Hi guys,\r\n\r\n@mandelsoft and I accidentally made a mistake when configuring our CF system. What we saw during analysis was that cc.runner wasn't logging anything (especially not during seeding). Line 87 in https://github.com/cloudfoundry/cloud_controller_ng/blob/master/lib/cloud_controller/runner.rb#L87 initializes the cc.runner logger implicitly while initializing the message bus. However, the actual configuration for the logger is not read until line 89 when the cloud controller initialization is triggered. So no cc.runner log gets written, especially not the logs made during CC seeding in line 91.\r\n\r\nWe could validate this by switching the initialization order. If the logging is initialized (call of setup_logging) before the message bus is initialized that implicitly initializes the logger, the cc.runner logger logs properly.\r\n\r\nYou can reproduce this by inserting logs after the CC initialization. They won't appear until you call setup_logging before the message bus implicitly initializes the logger:\r\n```ruby\r\nsetup_logging\r\nmessage_bus = MessageBus::Configurer.new(servers: @config[:message_bus_servers], logger: logger).go\r\nlogger.info(\"TEST INFO LOG\")\r\nlogger.error(\"TEST ERROR LOG\")\r\nstart_cloud_controller(message_bus)\r\n```\r\n\r\nCheers, Uwe and Vedran"}}