You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Yann Ylavic <yl...@gmail.com> on 2018/03/14 22:07:36 UTC
Re: A hang with mod_md renew
Hi Steffen,
On Wed, Mar 14, 2018 at 6:55 PM, Steffen <in...@apachelounge.com> wrote:
>
> See : https://www.apachelounge.com/viewtopic.php?p=36588#36588
Could we have the log messages at LogLevel trace1?
Regards,
Yann.
Re: A hang with mod_md renew
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Mar 15, 2018 at 3:20 PM, Steffen <in...@apachelounge.com> wrote:
> Ok, my fault. I shall stop reporting here.
>
> Btw.. official is 32 not announced and in the vote thread I said: When there some pop's up from the AL community, I let it know.
Bug reports are always very welcome, at any time!
Bugzilla is simply easier for tracing (relevant) discussions and
follow successive patches.
It also provides a reference for CHANGES entries...
Re: A hang with mod_md renew
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Mar 15, 2018 at 4:45 PM, Steffen <in...@apachelounge.com> wrote:
> Thinking.
>
> Because an issue can be a configuration fault and not a bug. I think
> best is post it to the user list first or dev can reply in the AL
> forum. Bugzilla is not so suited for discussions.
Yes, technical discussions and (possible) configuration issues are not
nice/appropriate for bz.
Qualified bugs are, and we can always (usually do) continue related
technical discussions on dev@, if needed.
There remain the description of the issue, final patches and where
they are committed/backported to in bz, which is nice for those who
didn't upgrade (for instance).
So once qualified it's always worth creating a bz for the record.
> Experience learns that AL users not always willing to be directed to
> bugzilla or to lists.
>
> Yep, hard for a non coder to understand what to do to report issues
> from my own test frame work, reported to me by mail, reported in the
> forum.
It's hard to get a fix without reporting appropriately, the less time
spent by the committer, the faster the issue gets resolved.
>
> For years I and others report issues on the dev list, but suddenly it
> seems not be the way anymore.
>
> What is changed lately ?
Well, it sometimes works on the one or the other, the preferred way is
(and has always been AFAICT) to fill a bz and ping on dev@ if it lacks
attention...
Re: A hang with mod_md renew
Posted by Steffen <in...@apachelounge.com>.
Thinking.
Because an issue can be a configuration fault and not a bug. I think best is post it to the user list first or dev can reply in the AL forum. Bugzilla is not so suited for discussions.
Experience learns that AL users not always willing to be directed to bugzilla or to lists.
Yep, hard for a non coder to understand what to do to report issues from my own test frame work, reported to me by mail, reported in the forum.
For years I and others report issues on the dev list, but suddenly it seems not be the way anymore.
What is changed lately ?
Btw.
Stefan want also issues reported in Git issues thread: “I want to use 'Issues' for support”.
> Op 15 mrt. 2018 om 15:20 heeft Steffen <in...@apachelounge.com> het volgende geschreven:
>
> Ok, my fault. I shall stop reporting here.
>
> Btw.. official is 32 not announced and in the vote thread I said: When there some pop's up from the AL community, I let it know.
>
>
>
>>>> Op 15 mrt. 2018 om 15:07 heeft Yann Ylavic <yl...@gmail.com> het volgende geschreven:
>>>>
>>>> On Thu, Mar 15, 2018 at 3:05 PM, Eric Covener <co...@gmail.com> wrote:
>>>> On Thu, Mar 15, 2018 at 10:04 AM, Steffen <in...@apachelounge.com> wrote:
>>>>
>>>> I am just passing the issues to list. I hope the reporter follows this list, the link I posted in the forum.
>>>
>>> The best thing for everyone would be to direct users to bugzilla to
>>> report bugs, when they're not in the packaging of course.
>>
>> +1
>
Re: A hang with mod_md renew
Posted by Steffen <in...@apachelounge.com>.
Ok, my fault. I shall stop reporting here.
Btw.. official is 32 not announced and in the vote thread I said: When there some pop's up from the AL community, I let it know.
>>> Op 15 mrt. 2018 om 15:07 heeft Yann Ylavic <yl...@gmail.com> het volgende geschreven:
>>>
>>> On Thu, Mar 15, 2018 at 3:05 PM, Eric Covener <co...@gmail.com> wrote:
>>> On Thu, Mar 15, 2018 at 10:04 AM, Steffen <in...@apachelounge.com> wrote:
>>>
>>> I am just passing the issues to list. I hope the reporter follows this list, the link I posted in the forum.
>>
>> The best thing for everyone would be to direct users to bugzilla to
>> report bugs, when they're not in the packaging of course.
>
> +1
Re: A hang with mod_md renew
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Mar 15, 2018 at 3:05 PM, Eric Covener <co...@gmail.com> wrote:
> On Thu, Mar 15, 2018 at 10:04 AM, Steffen <in...@apachelounge.com> wrote:
>>
>> I am just passing the issues to list. I hope the reporter follows this list, the link I posted in the forum.
>
> The best thing for everyone would be to direct users to bugzilla to
> report bugs, when they're not in the packaging of course.
+1
Re: A hang with mod_md renew
Posted by Eric Covener <co...@gmail.com>.
On Thu, Mar 15, 2018 at 10:04 AM, Steffen <in...@apachelounge.com> wrote:
>
> I am just passing the issues to list. I hope the reporter follows this list, the link I posted in the forum.
The best thing for everyone would be to direct users to bugzilla to
report bugs, when they're not in the packaging of course.
Re: A hang with mod_md renew
Posted by Steffen <in...@apachelounge.com>.
I am just passing the issues to list. I hope the reporter follows this list, the link I posted in the forum.
> Op 15 mrt. 2018 om 09:58 heeft Stefan Eissing <st...@greenbytes.de> het volgende geschreven:
>
> My bet would be on mod_md.c, line 701 that could place the job->next_run in
> the past. That would cause then the watchdog to run immediately again.
>
> Since the log shows the expiry date to be ok, the md->renew_window seems
> to be wrong. It would also be interesting to see the content of
>
> $SERVERROOT/md/domains/ftp.pbhq.com/md.json
>
> Cheers, Stefan
>
>> Am 14.03.2018 um 23:21 schrieb Yann Ylavic <yl...@gmail.com>:
>>
>> On Wed, Mar 14, 2018 at 11:07 PM, Yann Ylavic <yl...@gmail.com> wrote:
>>> Hi Steffen,
>>>
>>>> On Wed, Mar 14, 2018 at 6:55 PM, Steffen <in...@apachelounge.com> wrote:
>>>>
>>>> See : https://www.apachelounge.com/viewtopic.php?p=36588#36588
>>>
>>> Could we have the log messages at LogLevel trace1?
>>
>> Also, what's the configuration for MDRenewWindow there?
>>
>>>
>>> Regards,
>>> Yann.
>
Re: A hang with mod_md renew
Posted by Stefan Eissing <st...@greenbytes.de>.
My bet would be on mod_md.c, line 701 that could place the job->next_run in
the past. That would cause then the watchdog to run immediately again.
Since the log shows the expiry date to be ok, the md->renew_window seems
to be wrong. It would also be interesting to see the content of
$SERVERROOT/md/domains/ftp.pbhq.com/md.json
Cheers, Stefan
> Am 14.03.2018 um 23:21 schrieb Yann Ylavic <yl...@gmail.com>:
>
> On Wed, Mar 14, 2018 at 11:07 PM, Yann Ylavic <yl...@gmail.com> wrote:
>> Hi Steffen,
>>
>> On Wed, Mar 14, 2018 at 6:55 PM, Steffen <in...@apachelounge.com> wrote:
>>>
>>> See : https://www.apachelounge.com/viewtopic.php?p=36588#36588
>>
>> Could we have the log messages at LogLevel trace1?
>
> Also, what's the configuration for MDRenewWindow there?
>
>>
>> Regards,
>> Yann.
Re: A hang with mod_md renew
Posted by Yann Ylavic <yl...@gmail.com>.
On Wed, Mar 14, 2018 at 11:07 PM, Yann Ylavic <yl...@gmail.com> wrote:
> Hi Steffen,
>
> On Wed, Mar 14, 2018 at 6:55 PM, Steffen <in...@apachelounge.com> wrote:
>>
>> See : https://www.apachelounge.com/viewtopic.php?p=36588#36588
>
> Could we have the log messages at LogLevel trace1?
Also, what's the configuration for MDRenewWindow there?
>
> Regards,
> Yann.