Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Postgresql is not correctly initialzed after install
Date: Tue, 30 Jul 2019 21:30:26 +0200	[thread overview]
Message-ID: <20190730193026.K9tTQnEkHQtoUhbkb5DflIt73chrYFzAY-l2xjlGyn0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13377@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2592 bytes --]

New comment by knusbaum on void-packages repository

https://github.com/void-linux/void-packages/issues/13377#issuecomment-516560471
Comment:
Hmm. I wasn't able to reproduce this from a clean postgres install.
`Void 4.19.59_1 x86_64 GenuineIntel uptodate rmFFFFFFFFFFFF`
`postgresql-9.6.14_1`

After install:
```
$ sudo ln -s /etc/sv/postgresql /var/service/
...
$ sudo sv status postgresql
run: postgresql: (pid 4052) 289s; run: log: (pid 4051) 289s
$ sudo su postgres -c psql  
psql (9.6.14)
Type "help" for help.

postgres=#
```
Before installing `/var/lib/postgresql` did not exist. After linking the service, `/var/lib/postgresql/data` exists and is populated properly.


## Reproducing
If I start with an existing `/var/lib/postgresql/data` directory that's empty, then link the service, I get errors:
```
$ sudo ls -alh /var/lib/postgresql/data
total 0
drwx------ 2 postgres postgres  6 Jul 30 14:25 .
drwxr-x--- 3 postgres postgres 39 Jul 30 14:24 ..
$ sudo ln -s /etc/sv/postgresql /var/service/
$ sudo sv status postgresql                  
down: postgresql: 1s, normally up, want up; run: log: (pid 12664) 12s
$ sudo svlogtail | grep postgres
2019-07-30T19:27:41.29180 daemon.info: Jul 30 14:27:41 postgres: postgres: could not access the server configuration file "/var/lib/postgresql/data/postgresql.conf": No such file or directory
2019-07-30T19:27:42.29694 daemon.info: Jul 30 14:27:42 postgres: postgres: could not access the server configuration file "/var/lib/postgresql/data/postgresql.conf": No such file or directory
2019-07-30T19:27:43.30463 daemon.info: Jul 30 14:27:43 postgres: postgres: could not access the server configuration file "/var/lib/postgresql/data/postgresql.conf": No such file or directory
2019-07-30T19:27:44.31350 daemon.info: Jul 30 14:27:44 postgres: postgres: could not access the server configuration file "/var/lib/postgresql/data/postgresql.conf": No such file or directory
2019-07-30T19:27:45.32417 daemon.info: Jul 30 14:27:45 postgres: postgres: could not access the server configuration file "/var/lib/postgresql/data/postgresql.conf": No such file or directory
2019-07-30T19:27:46.33308 daemon.info: Jul 30 14:27:46 postgres: postgres: could not access the server configuration file "/var/lib/postgresql/data/postgresql.conf": No such file or directory
```

While these aren't the same errors you reported, could it be that you have a dirty `/var/lib/postgresql/data` directory on your machine? Maybe we want to check the directory in the startup script rather than assuming it's good if it exists?


      parent reply	other threads:[~2019-07-30 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 20:21 [ISSUE] Postgresql errors out voidlinux-github
2019-07-28  8:32 ` Postgresql is not correctly initialzed after install voidlinux-github
2019-07-30 19:30 ` voidlinux-github [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190730193026.K9tTQnEkHQtoUhbkb5DflIt73chrYFzAY-l2xjlGyn0@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).