Kevin Benton wrote:
There is no side effect other than log noise and a delayed reload? I
don't see why a revert would be appropriate.
I looked at the logs and the issue seems to be that the process isn't
tracked correctly the first time it starts.
grep for the
There is no side effect other than log noise and a delayed reload? I don't
see why a revert would be appropriate.
I looked at the logs and the issue seems to be that the process isn't
tracked correctly the first time it starts.
grep for the following:
ea141299-ce07-4ff7-9a03-7a1b7a75a371',
Ack, and thanks for the summary Ihar,
I will have a look on it tomorrow morning, please update this thread
with any progress.
On Tue, Sep 27, 2016 at 8:22 PM, Ihar Hrachyshka wrote:
> Hi all,
>
> so we started getting ‘Address already in use’ when trying to start dnsmasq
On 27 September 2016 at 11:29, Miguel Angel Ajo Pelayo
wrote:
> Ack, and thanks for the summary Ihar,
>
> I will have a look on it tomorrow morning, please update this thread
> with any progress.
>
>
>
> On Tue, Sep 27, 2016 at 8:22 PM, Ihar Hrachyshka
Hi all,
so we started getting ‘Address already in use’ when trying to start dnsmasq
after the previous instance of the process is killed with kill -9. Armando
spotted it today in logs for: https://review.openstack.org/#/c/377626/ but
as per logstash it seems like an error we saw before