Re: docker container fails to start after stopping

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Mark Deneen <mdeneen(at)gmail(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: docker container fails to start after stopping
Date: 2018-01-03 12:56:30
Message-ID: CA+OCxox1+HMdgQrFE_WgdqyB0OofaA_=1CD1t2PvQ8Cc5yNWSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Tue, Jan 2, 2018 at 6:42 PM, Mark Deneen <mdeneen(at)gmail(dot)com> wrote:

> I submitted a pull request on github, but it appears that you prefer
> to use a mailing list for such things.
>
> Attached is a patch to correct the behavior in the Docker container.
>
> The problem is that apache generates httpd.pid at startup and it is
> never removed. When the container is stopped, the file remains. At
> startup httpd fails to start because it believes that httpd is already
> running.
>
> The patch simply deletes this file before starting httpd.

Thanks - patch applied (with the addition of "-f" to quieten any errors).

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Ashesh Vashi 2018-01-03 13:02:12 pgAdmin 4 commit: Remove any Apache HTTPD PID file before starting the
Previous Message Dave Page 2018-01-03 12:54:56 pgAdmin 4 commit: Remove any Apache HTTPD PID file before starting the