I have been having problem with the electricity going off often for 3 hours and more at a time and the UPS i have is not enough. When the UPS runs out then the servers switch off. When the electricity goes back on things boot up and all servers and VM's go on automatically (running XenServer with a few VM's). The issue I am having is that when the servers switch back on all the VM's go on as normal but there is two webservers that rely on the database and the other 5 don't. The ones that are relying on the database (all the content housed on a FreeNas) both have this error on the live site.


**Fatal error: Uncaught exception 'PDOException' with message
'SQLSTATE[08006] [7] could not connect to server: Connection refused
Is the server running on host "192.168.xx.xx" and accepting TCP/IP connections on port 5432?'**


The first and second time i saw this error i just restarted the freeNas and then it worked as normal however now this error is back because the server switched off again because of electricity going off (and yes got better UPS so wont go off again unless the electricity is off for 5 hours).

My question is where do i start to try to fix the problem. I restarted everything one by one and then searched the error that comes up and saw a post off someone saying i should try this with no reason at all setsebool -P httpd_can_network_connect on

First, connection refused means that you can connect (not a typo ) to this IP address, i.e. the kernel is running, it's attached to the network and no firewall blocks port 5432. However, no process listens for connection requests at port 5432, and the kernel actively rejects the connection by sending the client an ICMP packet.

This could be a temporary condition. Perhaps the processes on the FreeNAS take a bit longer to start up. Perhaps the FreeNAS is in the middle of a monstrous filesystem check. If so, you should be able to connect in a few minutes.

Or it's a permanent problem, and your power failure has caused a problem that prevents the server processes on the FreeNAS to start up and wait for connection requests.

You should start troubleshooting this on the FreeNAS. I believe it's essentially a FreeBSD box with special software on it, so that you should be able to log on and look around, either using its web interface or the command line. There might be a console showing that the FreeNAS can't complete its boot process, or log files that indicate why processes aren't running.