Re: docker container fails to start after stopping

From: Mark Deneen <mdeneen(at)gmail(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: docker container fails to start after stopping
Date: 2018-01-03 14:42:20
Message-ID: CAP6JJ88K6gv_fY0XJeipmpvqqDEBSxGijahz7Wxt38p61sHkFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Thanks, Dave!

On Wed, Jan 3, 2018 at 7:56 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>
> 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

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2018-01-03 14:49:11 pgAdmin 4 commit: Prevent multiple connections to new slow-to-respond s
Previous Message Dave Page 2018-01-03 14:34:50 Re: [pgAdmin4][Patch]: RM #2945 - [Web based] Message "can't execute an empty query" displayed if user Click Yes on constrains trigger for view trigger