1-I couldn't find the other instance sir ! when i stop alertmanager.service
i don't receive any alert
2-how can i edit file the file ? oO
3-i added --log.level=debug than
: level=debug ts=2020-10-01T14:15:19.477Z caller=cluster.go:233
component=cluster msg="joined cluster" peers=0
alertmanager[1430]: level=info ts=2020-10-01T14:15:19.510Z
caller=cluster.go:623 component=cluster msg="Waiting for gossip to
settle..." interval=2s
alertmanager[1430]: level=info ts=2020-10-01T14:15:19.550Z
caller=coordinator.go:119 component=configuration msg="Loading
configuration file" file=/etc/alertmanager/alert
alertmanager[1430]: level=info ts=2020-10-01T14:15:19.551Z
caller=coordinator.go:131 component=configuration msg="Completed loading of
configuration file" file=/etc/alert
alertmanager[1430]: level=info ts=2020-10-01T14:15:19.553Z
caller=main.go:429 msg=Listening address=:9093
llevel=info ts=2020-10-01T14:15:21.510Z caller=cluster.go:648
component=cluster msg="gossip not settled" polls=0 before=0 now=1
elapsed=2.000135331s
level=debug ts=2020-10-01T14:15:23.510Z caller=cluster.go:645
component=cluster msg="gossip looks settled" elapsed=4.000586485s
level=debug ts=2020-10-01T14:15:25.510Z caller=cluster.go:645
component=cluster msg="gossip looks settled" elapsed=6.000806992s
level=debug ts=2020-10-01T14:15:27.511Z caller=cluster.go:645
component=cluster msg="gossip looks settled" elapsed=8.001014456s
level=info ts=2020-10-01T14:15:29.515Z caller=cluster.go:640
component=cluster msg="gossip settled; proceeding" elapsed=10.005216728s
level=debug ts=2020-10-01T14:16:15.562Z caller=dispatch.go:104
component=dispatcher msg="Received alert"
alert=SSLCertExpiringSoon[a5cda38][active]
level=debug ts=2020-10-01T14:16:15.563Z caller=dispatch.go:430
component=dispatcher aggrGroup="{}:{instance=\"https://lacompagnie.com\"}"
msg=fl
level=debug ts=2020-10-01T14:18:15.561Z caller=dispatch.go:104
component=dispatcher msg="Received alert"
alert=SSLCertExpiringSoon[a5cda38][active]
Le jeudi 1 octobre 2020 12:37:16 UTC+1, Brian Candler a écrit :
>
> On Thursday, 1 October 2020 12:16:31 UTC+1, Annonyme1 wrote:
>>
>> level=debug ts=2020-10-01T11:10:14.873Z caller=cluster.go:306
>> component=cluster memberlist="2020/10/01 12:10:14 [DEBUG] memberlist: Got
>> bind error: Failed to start TCP listener on \"0.0.0.0\" port 9094: listen
>> tcp 0.0.0.0:9094: bind: address already in use\n"
>> level=error ts=2020-10-01T11:10:14.873Z caller=main.go:222 msg="unable to
>> initialize gossip mesh" err="create memberlist: Could not set up network
>> transport: failed to obtain an address: Failed to start TCP listener on
>> \"0.0.0.0\" port 9094: listen tcp 0.0.0.0:9094: bind: address already in
>> use"
>>
>
> You have another instance of alertmanager running. You need to stop that
> one (e.g. "systemctl stop alertmanager"), before running alertmanager at
> the command line.
>
> Alternatively, if you want to run your systemd instance of alertmanager
> with --log.level=debug, then you need to edit the unit file.
>
>
>> but i still have the same alert duplicated problem
>>
>>
> Let's see logs from alertmanager, with --log.level=debug enabled, at the
> time the alerts are sent out.
>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/01cd4843-049f-473d-bc98-682d081f7639o%40googlegroups.com.