On 2020-02-13 21:03:48 -0800, Adrian Klaver wrote:
> On 2/13/20 9:02 PM, Adrian Klaver wrote:
> > On 2/13/20 7:54 PM, Jason Swails wrote:
> > > The problem is that after my machine boots, I'm unable to connect to
> > > the server from anywhere except localhost. Running a simple
> > > "systemctl restart postgresql" fixes the problem and allows me to
> > > connect from anywhere on my LAN. Here is an example of this
> > > behavior:
[...]
> > >
> > > So the first connection attempt fails. But when I restart the
> > > service and try again (doing nothing else in between), the
> > > connection attempt succeeds. My workaround has been to simply
> > > restart the service every time my machine reboots, but I'd really
> > > like to have a more reliable startup.
> > >
> > > Any ideas how to start hunting down the root cause? I think this
> > > started happening after I moved the data directory to another drive.
> >
> > I would start by looking in the system log to see what it records when
> > the service tries to start on reboot.
>
> Hit send to soon. At a guess the Postgres service is starting before the
> drive is mounted.
I don't think this has anything to do with the drive. If the drive
wasn't mounted he couldn't connect from localhost either.
What is probably happening is that postgresql is configured to listen on
localhost and the IP address of the ethernet interface and is starting
before the etherned interface is ready. So it is listening only on
localhost (there should be an error message regarding the other address
in the log). When he restarts postgresql some time later, the interface
is ready.
It should be possible to solve this by adding the right dependencies to systemd.
hp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@xxxxxx | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
Attachment:
signature.asc
Description: PGP signature
