Postgresql wont run with fatal error about quickstart HOT 14 CLOSED

hey guys, if I remembered it had something to do conf file not in the right place or wasn't getting the path the specified..I dont have the setup anymore sorry know that's not very helpful

from quickstart.

just connect your docker container with the command below

1. docker exec -it [container name] /bin/bash
2. tail /var/log/supervisor/postgresql-stderr---supervisor-*.log

it will shows exact problem that you faced.

my problem is below, so i think same as yours.
"FATAL: could not create lock file "postmaster.pid": No space left on device"

from quickstart.

Please update to the latest version (if you're building it from source: git pull origin master).

from quickstart.

that didnt do it..still exactly same error

from quickstart.

Can you copy the postgres log here?

1. Login to your docker container: docker exec -it [container name] /bin/bash
2. supervisorctl
3. tail postgresql

from quickstart.

log is blank..this is strange
horizon RUNNING pid 20, uptime 0:19:37
postgresql FATAL Exited too quickly (process log may have details)
stellar-core RUNNING pid 19, uptime 0:19:37
supervisor> tail postgresql

supervisor>

from quickstart.

having similar issues. did something change in stellar/base:latest that would break new builds?

from quickstart.

I have the same issue. Stellar was working for some time, now I try to run the container shows the same errors discussed above. Getting absolutely the same behaviour.
I thought the issue could be with docker container stopped and postgres database getting corrupted.

from quickstart.

@bartekn why did you close the issue if it's not solved? Could you please reopen it as many people are getting the same error. I am using last docker image call stellar/quickstart

from quickstart.

I have the exact same issue after trying to restart my testnet node after the network reset. Cannot run a node as I get

INFO exited: postgresql (exit status 2; not expected)
INFO spawned: 'postgresql' with pid 44
INFO success: stellar-core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO success: horizon entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO exited: postgresql (exit status 2; not expected)
INFO spawned: 'postgresql' with pid 82
INFO exited: postgresql (exit status 2; not expected)
INFO spawned: 'postgresql' with pid 136
INFO exited: postgresql (exit status 2; not expected)
INFO gave up: postgresql entered FATAL state, too many start retries too quickly
terminated - TODO: send SIGTERM to children

running tail postgresql shows an empty log.

from quickstart.

Same story after updating to the latest version....

 supervisorctl
horizon                          RUNNING   pid 22, uptime 0:01:50
postgresql                       FATAL     Exited too quickly (process log may have details)
stellar-core                     RUNNING   pid 21, uptime 0:01:50

supervisor> tail postgresql

supervisor> 

@bartekn

from quickstart.

hi @matricore i tried to did the same thing to view logs but it gives me permission denied error when i try to open supervisor, any idea how to fix that ?

from quickstart.

same problem was after copying the stellar data directory.
You need to fix the owner of the postgres data directory:
root@b5ee7ed62aab:/# ls -l /opt/stellar/postgresql
total 8
drwx------ 19 postgres postgres 4096 Sep 27 09:53 data
drwxr-xr-x 2 root root 4096 Sep 27 08:54 etc

I have had:

root@b5ee7ed62aab:/# ls -l /opt/stellar/postgresql total 8
drwx------ 19 root root 4096 Sep 27 09:53 data
drwxr-xr-x 2 root root 4096 Sep 27 08:54 etc

solution, in container enter:
chown -R postgres:postgres /opt/stellar/postgresql/data

from quickstart.

This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed.

from quickstart.