[ixpmanager] Looking Glass 500 Server Error :: Syntax error

[Austin Davis]

I removed the redundant file and verified my entry in /etc/sudoers is exactly as you have it below.

I have a single BIRDC entry in my files. I have 2 .env files for ipv4 and ipv6 which have a corresponding DNS entry for each.

 /srv/birdseye/bin/birdc and  /usr/bin/sudo files exist, and I was able to invoke sudo -u www-data /usr/bin/sudo /srv/birdseye/bin/birdc -2 -s /var/run/bird/bird-rs1-lan1-ipv4.ctl "show status" with the same output as you have shown.

Thank you for the help,

Austin Davis

________________________________
From: ixpmanager <ixpmanager-bounces at inex.ie> on behalf of Barry O'Donovan (INEX) via ixpmanager <ixpmanager at inex.ie>
Sent: Friday, January 26, 2024 4:17 AM
To: INEX IXP Manager Users Mailing List <ixpmanager at inex.ie>
Cc: Barry O'Donovan (INEX) <barry.odonovan at inex.ie>
Subject: Re: [ixpmanager] Looking Glass 500 Server Error :: Syntax error

[You don't often get email from ixpmanager at inex.ie. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

Caution: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe


Austin Davis via ixpmanager wrote on 26/01/2024 06:17:
> journalctl -t lighttpd shows this error whenever I try to access from
> either api or direct:
> "sudo: a terminal is required to read the password; either use the -S
> option to read from standard input or configure an askpass helper"
>
> /var/log/lighttpd/error.log doesn't have any errors in it.
>
> I've added "www-data ALL=(ALL) NOPASSWD: /srv/birdseye/bin/birdc" to
> both /etc/sudoers and /etc/sudoers.d/birdseye

I would remove one of these to reduce the problem space. Either should
work but /etc/sudoers is the canonical file so would be a better choice
for resolving this for now.

Your entry should read exactly:

www-data        ALL=(ALL)       NOPASSWD: /srv/birdseye/bin/birdc

You should have a single BIRDC entry in your Birdseye configuration file
- e.g.:


BIRDC="/usr/bin/sudo /srv/birdseye/bin/birdc -2 -s
/var/run/bird/bird-rs1-lan1-ipv4.ctl"

All of these files should exist:

xxx at rs1:~# file /srv/birdseye/bin/birdc
/srv/birdseye/bin/birdc: Bourne-Again shell script, ASCII text executable

xxx at rs1:~# file /usr/bin/sudo
/usr/bin/sudo: setuid ELF 64-bit LSB pie executable, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=b4b1e0966fbda253405de02862b0e78b295f9e17, for GNU/Linux
3.2.0, stripped

If everything is working you should be able to invoke it as follows:

xxx at rs1:~# sudo -u www-data /usr/bin/sudo /srv/birdseye/bin/birdc -2 -s
/var/run/bird/bird-rs1-lan1-ipv4.ctl "show status"
BIRD 2.0.9 ready.
Access restricted
BIRD 2.0.9
Router ID is 192.0.2.4
Hostname is rs1
Current server time is 2024-01-26 09:16:51
Last reboot on 2023-06-10 12:06:06
Last reconfiguration on 2024-01-18 12:40:06
Daemon is up and running


And if not, that should allow you to diagnose the problem.

Hth,
  - Barry


> I am running Ubuntu 20.04 and Bird 2.0.7. Let me know any other
> information that is needed. I've confirmed my subdomains match the .env
> files, and the .env files have the appropriate birdc and socket paths.
>
> Thank you,
>
>
> Austin Davis
>
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager
>


--

Kind regards,
Barry O'Donovan
INEX Operations

https://www.inex.ie/support/
+353 1 531 3339


_______________________________________________
INEX IXP Manager mailing list
ixpmanager at inex.ie
Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20240126/cb21eedb/attachment.htm>