Show your config file?

On Sunday 1 September 2024 at 18:45:19 UTC+1 Chinelo Ufondu wrote:

> I have been able to resolve the issue, the problem was my config file, it 
> wasn't properly indented and it had some syntax errors
>
> I tried running alertmanager again and i came across another issue, here 
> is the error
>
> ts=2024-09-01T17:35:52.421Z caller=main.go:181 level=info msg="Starting 
> Alertmanager" version="(version=0.27.0, branch=HEAD, 
> revision=0aa3c2aad14cff039931923ab16b26b7481783b5)"
> ts=2024-09-01T17:35:52.421Z caller=main.go:182 level=info 
> build_context="(go=go1.21.7, platform=linux/amd64, user=root@22cd11f671e9, 
> date=20240228-11:51:20, tags=netgo)"
> ts=2024-09-01T17:35:52.440Z caller=cluster.go:186 level=info 
> component=cluster msg="setting advertise address explicitly" 
> addr=192.168.101.2 port=9094
> ts=2024-09-01T17:35:52.441Z caller=main.go:221 level=error 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"
>
> I have tried all i can to stop the processes that is currently running  on 
> alert manager, but it didn't work out, i also tried adding an external 
> command to run *alertmanager --web.listen-address=localhost:9095 
> --config.file=alertmanager.yml, *but it still isn't picking the new port 
> number i would appreciate further assistance from you guys please, Thank 
> you.
>
>
> On Wed, 28 Aug 2024 at 18:28, chinelo Ufondu <[email protected]> wrote:
>
>> × alertmanager.service - AlertManager
>>      Loaded: loaded (/lib/systemd/system/alertmanager.service; enabled; 
>> vendor preset: enabled)
>>      Active: failed (Result: exit-code) since Wed 2024-08-28 15:43:10 
>> UTC; 2s ago
>>     Process: 1691244 ExecStart=/usr/bin/alertmanager --config.file 
>> /etc/alertmanager/alertmanager.yml (code=exited, status=1/FAIL>
>>    Main PID: 1691244 (code=exited, status=1/FAILURE)
>>         CPU: 29ms
>>
>> Aug 28 15:43:10 localhost systemd[1]: Started AlertManager.
>> Aug 28 15:43:10 localhost alertmanager[1691244]: 
>> ts=2024-08-28T15:43:10.392Z caller=main.go:181 level=info msg="Starting 
>> Alertman>
>> Aug 28 15:43:10 localhost alertmanager[1691244]: 
>> ts=2024-08-28T15:43:10.392Z caller=main.go:182 level=info 
>> build_context="(go=go1>
>> Aug 28 15:43:10 localhost alertmanager[1691244]: 
>> ts=2024-08-28T15:43:10.392Z caller=main.go:193 level=error msg="Unable to 
>> create>
>> Aug 28 15:43:10 localhost systemd[1]: alertmanager.service: Main process 
>> exited, code=exited, status=1/FAILURE
>> Aug 28 15:43:10 localhost systemd[1]: alertmanager.service: Failed with 
>> result 'exit-code'.
>> ~
>> ~
>>
>> -- 
>>
> 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/4010ba23-d4bb-4396-875b-13768c36eca3n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/prometheus-users/4010ba23-d4bb-4396-875b-13768c36eca3n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/12709b8a-ecb8-40ae-a9b7-2319fae3a1afn%40googlegroups.com.

Reply via email to