Confluence on reboot has occasional Network Unreachable to Postgres problems

[Jiri Pik]

Sometimes on reboot, the Confluence has problems connecting to the Postgres server - see the log. 

On another reboot it always works.

What to do? 

There have never been similar problems with JIRA using the same server. 

Is it a connection string issue?

[Nic Brough -Adaptavist-]

That's a deeper error than a connection to the database.

That error is thrown by a java process when the network on the machine is dead.  Not just network unreachable or routing or connection errors, but the network cable is pulled out, or the operating system has shut down all network connections (ifdown eth0).  Bit like turning the wifi off on a mobile 'phone - there is literally no network.

You'll need to look at the networking on your machine.

[Jiri Pik]

Thanks for this, but it's an AWS machine which is always on and the Postgres is also an AWS RDS server, so the connectivity is virtually guaranteed. 

Could it be some timeout issue or so?

[Nic Brough -Adaptavist-]

I'm afraid that error really is "the network is not there when I need it".

[Jiri Pik]

Yeah, I understand that.

I have done some research and possible leads are these:

1. the database connection port is for unknown reasons used by other app -> unreachable

2. Some solutions recommend adding this -Djava.net.preferIPv4Stack=true

I will try and let's see.