Sudo problema

Help
1

I have installed stable version for i686 platform (debian)

If i press "enable" from web interface the state remain unknown (orange) and in error.log i read:

sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted
sudo: unable to initialize policy plugin
sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted
sudo: unable to initialize policy plugin
sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted
sudo: unable to initialize policy plugin
[Sun Feb 23 11:02:44.078313 2020] [php7:warn] [pid 26472] [client 172.16.1.239:61729] PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/admin/api.php on line 47, referer: http://172.16.1.1/admin/settings.php?tab=blocklists

2

Please send us the token generated by

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

3

How i can upload the debug log?

Would you like to upload the log? [y/N] y
* Using curl for transmission.
[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log
4

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run pihole -d and upload the debug log

5

nothing....

[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log

root@apu:/var/www/admin# cat /etc/resolv.conf

Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

127.0.0.53 is the systemd-resolved stub resolver.

run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 9.9.9.9

6

PM the log to me.

7

pm sended

10x

9

You are running an unsupported OS (Bullseye) and there are configuration problems with the connectivity on the device.

*** [ DIAGNOSING ]:e[0m Networking [✓] IPv4 address(es) bound to the vlan2 interface: 169.254.105.110/16e[0m does not match the IP found in /etc/pihole/setupVars.conf Use IPv6 ULA addresses for Pi-hole

[i] Default IPv4 gateway: ppp0 192.168.1.1 *
Pinging ppp0 192.168.1.1...

Gateway did not respond https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546e[0m)

10

vlan2+wlan0 are in bridge
The used interface is br0

192.168.1.1 is not a real gw
ppp0 is wan interface

DNS work but i have sudo error with web interface

11

You are running on an unsupported OS, so there may be dependency or other problems.

12

why sudo fail?
Your answer is too generic

13

That's an OS level error, not anything related to Pi-hole.

14

Edit: A google search of that error leads to LDAP issues.

Edit2: Check the permissions on /etc/sudoers and /etc/sudoers.d they are likely wrong.

15

it's the first time I've seen such an uncontrolled use of sudo in php pages.
It is surely an unsafe solution :frowning:

I don't use ldap modules for apache and the installed php libraries are 7.3

16

It's not uncontrolled. There is a pihole user that is granted ability to run a very specific and limited number of functions.

The code has been reviewed and checked for vulnerabilities and all issues have been addressed.

Check the permissions of the /etc/sudoers and the sudoers.d directory to see what they are set to.

17

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.