[ixpmanager] Birdseye documentation

[Kyle Spencer]

Sorry; I just realized that this error is identical to the second
error in my previous e-mail.

On Sat, Jan 20, 2018 at 5:01 PM, Kyle Spencer <kyle at stormzero.com> wrote:
> Just for the sake of testing, I built a fresh route server from
> scratch, strictly following the instructions, and swapped it in place
> of the other one. Now I get a different error:
>
> [2018-01-20 16:57:02] production.ERROR:
> Symfony\Component\Debug\Exception\FatalThrowableError: Call to a
> member function hasApi() on null in
> /srv/ixpmanager/app/Http/Middleware/Services/LookingGlass.php:72
>
> On Sat, Jan 20, 2018 at 4:48 PM, Kyle Spencer <kyle at stormzero.com> wrote:
>> 1) Yes the handle is correct.
>>
>> 2) CNAME resolves on the IXP Manager box.
>>
>> 3) Two errors are readily visible:
>>
>> [2018-01-20 16:47:06] production.ERROR: ErrorException:
>> file_get_contents(http://rs1.uixp.co.ug/api/protocols/bgp): failed to
>> open stream: HTTP request failed! HTTP/1.0 500 Internal Server Error
>>  in /srv/ixpmanager/app/Services/LookingGlass/BirdsEye.php:104
>>
>> [2018-01-20 16:47:18] production.ERROR:
>> Symfony\Component\Debug\Exception\FatalThrowableError: Call to a
>> member function hasApi() on null in
>> /srv/ixpmanager/app/Http/Middleware/Services/LookingGlass.php:72
>>
>>
>>
>> On Sat, Jan 20, 2018 at 4:42 PM, Barry O'Donovan <barry.odonovan at inex.ie> wrote:
>>>
>>>
>>> Kyle Spencer wrote:
>>>> I have now renamed the /srv/birdseye/.env file to
>>>> /srv/birdseye/birdseye-rs1-kla1-ipv4.env as instructed by the docs and
>>>> ensured the following line was set appropriately: BIRDC="/usr/bin/sudo
>>>> /srv/birdseye/bin/birdc -4 -s /var/run/bird/rs1-kla1-ipv4.ctl"
>>>
>>> Is IXP Manager generating the route server config file? And if so, have
>>> you set it up in the Routers table with the handle rs1-kla1-ipv4 ?
>>>
>>>> I created two CNAME entries in our DNS system as suggested by the
>>>> docs. Both return seemingly correct results on the RS1 box when
>>>> queried with dig:
>>>
>>> It's the box running IXP Manager that need to resolve these - do they
>>> work there?
>>>
>>>> However, attempts to view the LG from IXP Manager return a "Whoops,
>>>> looks like something went wrong." error with the big red banner on top
>>>> :(
>>>
>>> This means the issue is on the IXP Manager server rather than the route
>>> server.
>>>
>>> What's in the log file (under storage/logs/...) ?
>>> _______________________________________________
>>> INEX IXP Manager mailing list
>>> ixpmanager at inex.ie
>>> https://www.inex.ie/mailman/listinfo/ixpmanager
>>
>>
>>
>> --
>> Cell/WhatsApp/Signal: +256790884905
>
>
>
> --
> Cell/WhatsApp/Signal: +256790884905



-- 
Cell/WhatsApp/Signal: +256790884905