Maybe, some component is Down.

Did you check that all components are running?

Process 'etcd' initializing
Process 'hm9000_listener' initializing
Process 'hm9000_fetcher' initializing
Process 'hm9000_analyzer' initializing
Process 'hm9000_sender' initializing
Process 'hm9000_metrics_server' initializing
Process 'hm9000_api_server' initializing
Process 'hm9000_evacuator' initializing
Process 'hm9000_shredder' initializing
Process 'cloud_controller_ng' initializing
Process 'cloud_controller_worker_local_1' initializing
Process 'cloud_controller_worker_local_2' initializing
Process 'nginx_cc' initializing
Process 'cloud_controller_worker_1' initializing
Process 'cloud_controller_clock' initializing
Process 'uaa' initializing
Process 'uaa_cf-registrar' initializing
Process 'haproxy' initializing
Process 'gorouter' initializing
Process 'warden' initializing
Process 'dea_next' initializing
Process 'dir_server' initializing
Process 'loggregator_trafficcontroller' initializing
Process 'doppler' initializing
Process 'metron_agent' not monitored - start pending
Process 'dea_logging_agent' not monitored - start pending
Process 'etcd_metrics_server' not monitored - start pending
Process 'postgres' running - start pending
System 'system_XXX' running - start pending

Another alternative could be if you had some network problem. You run GO Cli in local so if the client system has some network problem to connect with some component in CF is normal in some cases. When you deploy, the action is for Cloud Controller but Log system is for another component. Take a look this document:
https://docs.pivotal.io/pivotalcf/concepts/architecture/

timeout connecting to log server, no log will be shown

Juan Antonio