[ixpmanager] IRRDB error handling

[Pete Ashdown]

I ran across this problem in UpdatePrefixDb.php as well, and made a 
similar patch.  I hope I didn't assume too much:

*** UpdatePrefixDb.php-orig    2021-05-04 17:16:41.247198103 -0600
--- UpdatePrefixDb.php    2021-05-04 15:58:40.512741630 -0600
***************
*** 49,55 ****
       public function update(): array {

           foreach( $this->protocols() as $protocol ) {
!             if( $this->customer()->isRouteServerClient( $protocol ) && 
$this->customer()->isIrrdbFiltered() && ) {
                   $this->bgpq3()->setSources( 
$this->customer()->getIRRDB()->getSource() );

                   $this->startTimer();
--- 49,55 ----
       public function update(): array {

           foreach( $this->protocols() as $protocol ) {
!             if( $this->customer()->isRouteServerClient( $protocol ) && 
$this->customer()->isIrrdbFiltered() && $this->customer()->getIRRDB() ) {
                   $this->bgpq3()->setSources( 
$this->customer()->getIRRDB()->getSource() );

                   $this->startTimer();


On 3/14/21 1:11 PM, Nick Hilliard wrote:
> Pete Ashdown wrote on 14/03/2021 18:53:
>> Had a customer who entered their AS macros wrong, and as a result, 
>> they blocked everyone below them alphabetically from receiving IRRDB 
>> updates.  It would be good if the update would continue over these 
>> kind of errors.  Here is the output from the crash:
>
> Hi Pete,
>
> This should already be fixed in master:
>
>> https://github.com/inex/IXP-Manager/commit/d67b493d30c6483ded4d265d7d51c30924a26739 
>>
>
> Nick
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20210504/b1399793/attachment.htm>