Обсуждение: Odd problem in 7.4.2?
I have an odd problem where PostgreSQL 7.4.2 will fail to run if the machine it's installed on is moved to another network. The configuration is stock (i.e. no modifications to the configuration) running on Linux (Red Hat ????, it's a 2.4 kernel). I set up the machine with PostgreSQL and create the database on one network, and connections made to it are fine. If I move the machine to another network and bring it up, PostgreSQL fails to run.
Since PostgreSQL is configured by default to run only on Unix sockets, moving the machine shouldn't cause the server to fail to run, right? What am I missing?
Sorry for the lack of specific info. I'm getting most of my information second hand and after the fact. Any help you can give would be appreciated. Thanks!
Xerox Disclaimer: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient(s) please contact the sender by reply e-mail and destroy all copies of the original message. Finally, the recipient should check that this email is authentic and examine it for the presence of viruses. Xerox does perform virus checks but cannot accept liability for any damage caused by any virus transmitted by this email. Thank you.
On Thu, 2 Sep 2004, Owens, Steve wrote: > Since PostgreSQL is configured by default to run only on Unix sockets, > moving the machine shouldn't cause the server to fail to run, right? > What am I missing? You don't specify how it is failing to start up (hang, crash, etc.), but I have seen before when "localhost" was not in hosts file that postgresql hung for 5 minutes during startup while DNS resolution timed out. This was due to the way one of the local sockets was bound. After waiting for the timeout (30 second timeout with 6 retries) then postgres would come up. It may have been the stats collector socket (UDP) that was the culprit IIRC.