[ixpmanager] HANDLE: rs1-ix-ipv4: ABORTING: router not available for update ERROR

[Barry O'Donovan (INEX)]

Thanks for the follow-up, Deri.

You can monitor daemons that get stuck using an API endpoint. We have a 
practical example for Nagios here:

https://docs.ixpmanager.org/features/nagios/#birdseye-daemon-monitoring

  - Barry







------ Original Message ------
>From "Deri Yusep Apriyadi via ixpmanager" <ixpmanager at inex.ie>
To "INEX IXP Manager Users Mailing List" <ixpmanager at inex.ie>
Cc "Deri Yusep Apriyadi" <cartoen at gmail.com>
Date 23/08/2025 08:09:22
Subject Re: [ixpmanager] HANDLE: rs1-ix-ipv4: ABORTING: router not 
available for update ERROR

>Hi All,
>
>For this already solved after i try "Reset Update Timestamps" and 
>running reconfigure again.
>The Handle already ok and update synch.
>
>Thanks all.
>
>On Sat, Aug 23, 2025 at 8:30 AM Deri Yusep Apriyadi <cartoen at gmail.com> 
>wrote:
>>Hi,
>>I have 4 RS and some time ago I had a change in the IP subnet and 
>>changed the VLAN interface on the IXP manager. After making this 
>>change and reconfiguring (./api-reconfigure-all.sh), 3 RS had no 
>>issues, but on RS1, the results are as follows:
>>
>>--------------------------------------------------------------------------------
>>>root at IX-RS1-100-18:/usr/local/sbin# ./api-reconfigure-all.sh
>>>Reconfiguring all bird instances:
>>>HANDLE: rs1-ix-ipv4: ABORTING: router not available for update ERROR
>>>HANDLE: rs1-ix-ipv6: ABORTING: router not available for update ERROR
>>>
>>--------------------------------------------------------------------------------
>>I have ensured that the Handle and API are correct, but the result is 
>>always the same: ABORTING: router not available for update.
>>
>>I would appreciate your help in resolving this issue.
>>
>>Thank's,
>>
>>Deri
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20250823/b27b71e5/attachment.htm>