Seems like if you wait 16 minutes, it finally listens to your requests again. There is a 16 minutes hole in the cloud-output.log:
14:37:38 INFO ClusterUtil | -> [ vcloud ] Node certificate valid= 14:37:38 INFO ClusterUtil | ------------------------------------- -------------------------- 14:53:13 WARN JDBCExceptionReporter | SQL Error: -3, SQLState: 08003 14:53:13 ERROR JDBCExceptionReporter | Connection is broken: java.net.Socket Exception: Connection timed out
Seems like if you wait 16 minutes, it finally listens to your requests again. There is a 16 minutes hole in the cloud-output.log:
14:37:38 INFO ClusterUtil | -> [ vcloud ] Node certificate valid= ------- ------- ------- ------- -- ------- ------- ----- porter | SQL Error: -3, SQLState: 08003 porter | Connection is broken: java.net.Socket
14:37:38 INFO ClusterUtil | -------
-------
14:53:13 WARN JDBCExceptionRe
14:53:13 ERROR JDBCExceptionRe
Exception: Connection timed out