<html><head><style id="css_styles" type="text/css"><!--blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: center; '], li[style='text-align: right;'], li[style='text-align: right; '] { list-style-position: inside;}
body { font-family: 'Avenir Next'; font-size: 10.5pt; }
.quote { margin-left: 1em; margin-right: 1em; border-left: 5px #ebebeb solid; padding-left: 0.3em; }
a.em-mention[href] { text-decoration: none; color: inherit; border-radius: 3px; padding-left: 2px; padding-right: 2px; background-color: #e2e2e2; }
._em_placeholder {color: gray; border-bottom: 1px dotted lightblue;} ._em_placeholder:before{color:gray; content: '{{ ';} ._em_placeholder:after{color:gray; content: ' }}';}
--></style></head><body style="color: rgb(0, 0, 0); overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br /></div><div>Thanks for the follow-up, Deri.</div><div><br /></div><div>You can monitor daemons that get stuck using an API endpoint. We have a practical example for Nagios here:</div><div><br /></div><div><a href="https://docs.ixpmanager.org/features/nagios/#birdseye-daemon-monitoring">https://docs.ixpmanager.org/features/nagios/#birdseye-daemon-monitoring</a></div><div><br /></div><div> - Barry</div><div><br /></div>
<div><br /></div><div id="signature_old" style="clear:both">
<br /><br />
<br />
</div><div><br /></div>
<div x-em-replyforwardheader=""><br /></div>
<div>
<div>------ Original Message ------</div>
<div>From "Deri Yusep Apriyadi via ixpmanager" <<a href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a>></div>
<div>To "INEX IXP Manager Users Mailing List" <<a href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a>></div>
<div>Cc "Deri Yusep Apriyadi" <<a href="mailto:cartoen@gmail.com">cartoen@gmail.com</a>></div>
<div>Date 23/08/2025 08:09:22</div>
<div>Subject Re: [ixpmanager] HANDLE: rs1-ix-ipv4: ABORTING: router not available for update ERROR</div></div><div x-em-quote=""><br /></div>
<div id="x1fe6de306ab6409"><blockquote cite="CACirtV1BdkBE+5YLQiHvQB-AatjENX8anfa38G6qQsL8Mu9vWQ@mail.gmail.com" type="cite" class="cite2">
<div dir="ltr"><div>Hi All,</div><div><br /></div><div>For this already solved after i try "Reset Update Timestamps" and running reconfigure again.</div><div>The Handle already ok and update synch.</div><div><br /></div><div>Thanks all.</div></div><br /><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Aug 23, 2025 at 8:30 AM Deri Yusep Apriyadi <<a href="mailto:cartoen@gmail.com">cartoen@gmail.com</a>> wrote:<br /></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">
<div><div><p dir="auto">Hi,<br />
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:
</p>
<hr />
<blockquote>
<p dir="auto">root@IX-RS1-100-18:/usr/local/sbin# ./api-reconfigure-all.sh<br />
Reconfiguring all bird instances:<br />
HANDLE: rs1-ix-ipv4: ABORTING: router not available for update ERROR<br />
HANDLE: rs1-ix-ipv6: ABORTING: router not available for update ERROR</p>
</blockquote>
<hr />
<p dir="auto">I have ensured that the Handle and API are correct, but the result is always the same: <em>ABORTING: router not available for update</em>.</p>
<p dir="auto">I would appreciate your help in resolving this issue.</p>
<p dir="auto">Thank's,</p>
<p dir="auto">Deri</p></div></div>
<br /></div>
</blockquote></div>
</blockquote></div>
</body></html>