[ixpmanager] Fwd: Looking Glass Server Error :: content is not defined.

[Jose Gonzalez]

Hi Nick, I just sent you. I made some tests with rs2 and now is working
fine, I mean, if I get access to the route server, but still have the same
error from the ixpmanager. the url is reachable from the ixp console but
not from the gui.
[image: image.png]
[image: image.png]

El mar., 27 de oct. de 2020 a la(s) 08:35, Nick Hilliard (INEX) (
nick at inex.ie) escribió:

> Hi Jose,
>
> Sorry, I can't find the output from the curl command.  can you upload it
> again to pastebin.ibn.ie?
>
> Nick
>
> Jose Gonzalez wrote on 22/10/2020 20:01:
>
> Hi Nick, I already sent you the output. As I mentioned before, I'm working
> with rs4-pit-ipv6-lan10.pitperu.net, because is not in service yet. let
> me know if you need anything else.
> Best regards
>
> El mié., 21 de oct. de 2020 a la(s) 10:40, Nick Hilliard (INEX) (
> nick at inex.ie) escribió:
>
>> The diagnosis process here is the same as with Basil's email: the aim is
>> to see if the route server http microserver is reachable.
>>
>> Can you post the output of the following command to
>> https://pastebin.ibn.ie/ ?
>>
>> bash$ curl -v http://rs1-amt-ipv4-lan10.pitperu.net/api/status
>>
>> Nick
>>
>> Jose Gonzalez wrote on 20/10/2020 21:48:
>> >
>> > Dear support,
>> >
>> > Hi Nick, sorry for not answering before, but I followed your
>> > recommendation. I just modified the /etc/hosts to match the url and the
>> > IP address, also certified the lighttpd are running , but still doesn't
>> > work.
>> > I just note from the live RS status the following error:
>> > image.png
>> > but when I just run ./artisan up from /srv/birdseye-v1.2.2/ i did not
>> > receive the error message and I was able to see the version but it goes
>> > down 2 min later.
>> > I already installed a new RS server from scratch (rs4), I will let you
>> > know the results, but I will appreciate any suggestion.
>> >
>> > ---------- Forwarded message ---------
>> > De: *Jose Gonzalez* <josegonzalez at pitperu.net
>> > <mailto:josegonzalez at pitperu.net>>
>> > Date: lun., 19 de oct. de 2020 a la(s) 12:37
>> > Subject: Re: [ixpmanager] Looking Glass Server Error :: content is not
>> > defined.
>> > To: Nick Hilliard <nick at foobar.org <mailto:nick at foobar.org>>
>> >
>> >
>> > Hi Nick, sorry for not answering before, but I followed your
>> > recommendation. I just modified the /etc/hosts to match the url and the
>> > IP address, also certified the lighttpd are running , but still doesn't
>> > work.
>> > I just note from the live RS status the following error:
>> > image.png
>> > but when I just run ./artisan up from /srv/birdseye-v1.2.2/ i did not
>> > receive the error message and I was able to see the version but it goes
>> > down 2 min later.
>> > I already installed a new RS server from scratch (rs4), I will let you
>> > know the results, but I will appreciate any suggestion.
>> >
>> > El mié., 14 de oct. de 2020 a la(s) 05:57, Nick Hilliard
>> > (nick at foobar.org <mailto:nick at foobar.org>) escribió:
>> >
>> >     Jose Gonzalez wrote on 13/10/2020 16:16:
>> >      > Dear support,
>> >      >
>> >      > I sent you this report, because I was unable to get information
>> >     from the
>> >      > looking glass functionality. This is what I have done so far:
>> >      > - Installed the birdv2 server according to
>> >      > https://bird.network.cz/?get_doc&v=20&f=bird-1.html#ss1.2
>> >      > - Installed birseyev1.2.2 according to
>> >     https://github.com/inex/birdseye
>> >      > After that, when we select the looking glass option from the
>> >     ixpmanager,
>> >      > always shown the error message 500 | Server Error :: content is
>> >     not defined.
>> >      > I collected all the info required by the debugging item, but
>> >     everything
>> >      > responded as the document said.
>> >      > Hopefully you can help me with this issue.
>> >
>> >     Hi Jose,
>> >
>> >     You should start out by checking the following things:
>> >
>> >     1. lighttpd should be running on all of the route servers
>> >
>> >     2. you should have DNS configured to point
>> >     rs1-pit-ipv4-lan10.pitperu.net
>> >     <http://rs1-pit-ipv4-lan10.pitperu.net> and
>> >     rs2-pit-ipv4-lan10.pitperu.net
>> >     <http://rs2-pit-ipv4-lan10.pitperu.net> to the
>> >     management IP addresses of the route servers
>> >
>> >     3. You should get json output if you browse the RS web server at:
>> >     http://rs1-pit-ipv4-lan10.pitperu.net/api
>> >
>> >     4. you should set the "API Endpoint" field in the Router section in
>> IXP
>> >     Manager to be "http://rs1-pit-ipv4-lan10.pitperu.net/api" and
>> >     "http://rs2-pit-ipv4-lan10.pitperu.net/api"
>> >
>> >     Nick
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20201028/89e881a4/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 67731 bytes
Desc: not available
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20201028/89e881a4/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 29671 bytes
Desc: not available
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20201028/89e881a4/attachment-0003.png>