[j-nsp] MX-80 19.2R1.8 returns 500 Internal Server Error to REST API calls

[Rafael Ganascim]

Hi Juniper experts,

I've a Juniper MX-80 running Junos 19.2R1.8 and I'm trying to use the
REST-API calls.

It always returns a 500 Internal Server Error, even though the REST
calls seem to be processed, in response to curl or REST API Explorer
embedded calls.

Sending the RPC via Netconf interface of the same underlying XML API works fine.

I have enabled the set rest traceoptions flag all, but the
/var/chroot/rest-api/var/log/lighttpd log (available below [2]) does
not show much clues, at least for me. Since the Netconf way goes
through, I assume the mgd process is fine and the problem is somewhere
at lighttpd or mod_juise level.

I've found similar issues with vSRX [1], but I don't know if the
solution can follow the same path.

Did anyone encounter this or could point towards further debugging?

Regards,

Rafael

[1] 
https://community.juniper.net/communities/community-home/digestviewer/viewthread?MID=72012

[2]
# curl http://a.b.c.d:3000/rpc/get-software-information -u "xxx:"
-H "Content-Type: application/xml" -H "Accept: application/xml"

http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;>
http://www.w3.org/1999/xhtml; xml:lang="en" lang="en">

500 - Internal Server Error


500 - Internal Server Error



% tail -n 20 /var/chroot/rest-api/var/log/lighttpd
2021-04-27 15:26:15:
(../../../../../../src/dist/lighttpd/src/server.c.1412) server started
(lighttpd/1.4.48)
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.736)
mod_juise: connection_reset:
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.739)
mod_juise: connection_reset: done
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1841)
mod_juise: physical: fn /www/rpc/get-software-information
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1842)
mod_juise: physical: uri /rpc/get-software-information
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1753)
mod_juise: start: looking at /usr/sbin/juise
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: /usr/sbin/juise
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: --rpc-on-box
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: --auth-socket
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: /var/run/rest_api_mgmt_sock
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: --trace
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: /var/log/juise
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1072)
juise: argv: /usr/sbin/juise
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.1945)
mod_juise: handle:
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.736)
mod_juise: connection_reset:
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.739)
mod_juise: connection_reset: done
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.736)
mod_juise: connection_reset:
2021-04-27 15:26:31:
(../../../../../../../src/dist/juise/mod_juise/mod_juise.c.739)
mod_juise: connection_reset: done
2021-04-27 15:27:41:
(../../../../../../src/dist/lighttpd/src/server.c.936) [note] graceful
shutdown started
2021-04-27 15:27:41:
(../../../../../../src/dist/lighttpd/src/server.c.2011) server stopped

aph@JMX5T> show configuration system services rest | display set
set system services rest http port 3000
set system services rest control allowed-sources a.b.c.d
set system services rest enable-explorer
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] l2circuit down one side/up another

[Rafael Ganascim]

Just more checks:

How is the MPLS forwarding table for the negotiated Labels for loopback and
l2circuit?
Are you using label PHP? Can you switch It off?
Is the LDP adjacency up and exchanging labels?
Are the l2circuit neighbors configured between loopback interfaces?

Regards,




Em 20 de out de 2017 8:26 AM, "Caio"  escreveu:

> Hello people,
>
> There's a weird problem I would like to share with you.
> I have the following scenario:
>
> MX104 -> L2 SW (1) -> L2 SW (2) -> MX80
>
> Both L2 SW are Extreme X460 and they're doing nothing except forwarding
> frames at layer 2.
>
> In order to simplify our topology, we have changed the MX104 uplink to L2
> SW (2) so the topology went to MX104 -> L2 SW (2) -> MX80.
>
> After that, the BGP sessions went up and all the traffic has returned as
> expected, however I have three l2circuit connections (vlan-ccc mode) and
> they went to "Down (OL)" status at one side and Up at another. In order to
> reestablish them we had to do a rollback of the physical changes we did.
>
> As it just don't make any sense to me, I summon you experts to help me with
> that, so we can try to figure out what went wrong.
>
> Additional details: I'm using LDP signaling at both sides. It' a point to
> point L3 connection, so I have the loopback interfaces configured at both
> sides and a /30 between them, also I have static routes to reach their
> loopback interface's addresses.
>
> Any help will be appreciated.
>
> Cheers,
> Caio
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp