Closed Angel0fDarkness closed 10 years ago
Ah, maybe there was a problem on my side. Due to the fact that the firstrun file has not been deleted, further starts of the container already have the pid file for postgres in place even though postgres is not completely started yet..
But still the first_run.sh stops right where the user account should be created and the setup stops :( When I ran the commands manually with psql, it seems to work..!
Startup looks like this: * Running /etc/rc.local... * Booting runit daemon... *\ Runit started as PID 8 POSTGRES_USER=super POSTGRES_PASS=test123 POSTGRES_DATA_DIR=/data POSTGRES_DB=owncloud Initializing PostgreSQL at /data Starting PostgreSQL... Creating the superuser: super
I just saw that there already exists (looks almost the same) issue here: #9 Although I tryed printing the pid of postgres directly before the psql calls which returns some IDs so there server should be up&running but still hangs in the psql command somehow..
Sorry that I am commenting so much ;) I just updated the used baseimage from phusion to 0.9.12 and everything works fine ..
Hi! When I boot up the postgresql container, the super user, password and DB are not set up. The script seems to terminate right where the super user is created, therefore firstrun wont be removed as well.
I tried some things inside the container and it looks like the commands to psql are performed before the postgres server is even running. When I check the PID of postgres (using pidof postgres) right after the post_start_action() is called and before the first psql command is executed, no PID is available. Is there a solution to wait until the postgres server is started correctly?
Best Regards, Tobias