Am 23.11.22 um 16:12 schrieb Darren Ankney:
I just noticed your date/time pattern: %d{%j %H:%M:%S.%q} %c %m You
might want to change to %D{%Y-%m-%d %H:%M:%S.%q %Z} %-5p [%c/%i.%t]
%m (or at least capitalize the %D as I think the content in {} is a
description of the output you want from %D).
I just noticed your date/time pattern: %d{%j %H:%M:%S.%q} %c %m You
might want to change to %D{%Y-%m-%d %H:%M:%S.%q %Z} %-5p [%c/%i.%t]
%m (or at least capitalize the %D as I think the content in {} is a
description of the output you want from %D). You can also add a %Z in
the format message to
Am 23.11.22 um 14:34 schrieb Darren Ankney:
Suggestions for debuglevel? full 99? (yes, I'd have to set severity "DEBUG")
We run INFO as the severity. If you expect more trouble, you might
increase the severity to DEBUG to capture more.
Currently things run fine, as it seems.
I see allocati
> Yes, about that. I copied that block from the docs, I assume:
>
> https://kea.readthedocs.io/en/kea-2.3.2/arm/logging.html#example-logger-configurations
>
> Currently I have logs until around 1am back. But only with severity "INFO"
>
> I increase "maxsize" to its default of 10 MB and "maxver" to
Am 23.11.22 um 13:41 schrieb Darren Ankney:
It may be that your logs are rotating too quickly after seeing your
logging configuration. There may be a large amount of logs in a short
period of time during trouble events. depending how many clients you
have. According to
https://kea.readthedocs.i
It may be that your logs are rotating too quickly after seeing your
logging configuration. There may be a large amount of logs in a short
period of time during trouble events. depending how many clients you
have. According to
https://kea.readthedocs.io/en/kea-2.3.2/arm/logging.html maxsize is in
Am 23.11.22 um 12:43 schrieb Darren Ankney:
If clients were attempting to get addresses at what should have been
an elevated pace, there should have been elevated logs in the minutes
leading up to the unplug. There are many nuanced logging options with
Kea. Do you normally see detailed logs of
Am 23.11.22 um 12:20 schrieb Kevin P. Fleming:
On Wed, Nov 23, 2022, at 06:08, Stefan G. Weichinger wrote:
I browsed the logs etc (could it be that kea logs in UTC and not in my
local timezone?). Everything quiet in there until the boxes were
unplugged, so no error visible until that manual inte
On Wed, Nov 23, 2022 at 6:09 AM Stefan G. Weichinger wrote:
>
>
> Greetings, I subscribed to this list 5 minutes ago because this morning
> we had a event I can't yet fully explain.
>
> A few weeks ago I set up a kea-HA-cluster of 2 Debian-11 nodes using the
> 2.3.2 packages from the isc-repos.
>
On Wed, Nov 23, 2022, at 06:08, Stefan G. Weichinger wrote:
> I browsed the logs etc (could it be that kea logs in UTC and not in my
> local timezone?). Everything quiet in there until the boxes were
> unplugged, so no error visible until that manual intervention.
Also consider that your network
Greetings, I subscribed to this list 5 minutes ago because this morning
we had a event I can't yet fully explain.
A few weeks ago I set up a kea-HA-cluster of 2 Debian-11 nodes using the
2.3.2 packages from the isc-repos.
I run kea-dhcp4 only on the 2 nodes, no DHCPv6 or DDNS. For sure I
11 matches
Mail list logo
