Project

General

Profile

Actions

Bug #14277

closed

Fatal error while restarting Unbound through SSH

Added by Ketul Patel over 1 year ago. Updated over 1 year ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

High CPU usage and issues with DNS resolver.

Applied - c5faa351c1ef6d4555478a7f50b3a16ece7e0b2a BUG #14061

SSH - pfSsh.php playback svc restart unbound start receiving fatal error

Error log file attached


Files

PHP_errors.log (1.64 KB) PHP_errors.log Fatal error Ketul Patel, 04/15/2023 02:12 AM

Related issues

Related to Bug #14061: PHP error if a non-privileged shell user attempts an operation which needs to write ``config.cache``ResolvedJim Pingle

Actions
Actions #1

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Duplicate

The top couple lines there are the same PHP error from the other issue, so let's keep the discussion over there since it's still in a feedback state. What was happening in Unbound specifically is unrelated, the error was from you running that command.

Also when you do post a reply there make sure to include how you ran that command. Was it as root/admin or a different user? You have to be root to run that sort of command or use sudo, otherwise your user will lack privileges to perform all the tasks needed there.

Actions #2

Updated by Jim Pingle over 1 year ago

  • Project changed from pfSense Plus to pfSense
  • Category changed from DNS Resolver to DNS Resolver
  • Affected Plus Version deleted (23.01)
Actions #3

Updated by Jim Pingle over 1 year ago

  • Related to Bug #14061: PHP error if a non-privileged shell user attempts an operation which needs to write ``config.cache`` added
Actions #4

Updated by Jim Pingle over 1 year ago

A little follow-up here. The only way I can induce an error is to try running that command as a user without sufficient privileges. There isn't much we can do about that, lots of things are intended to only be run as admin/root or through sudo, and trying to safety belt all of them isn't viable in the current codebase.

We tried to fix the other one because it was easy for it to happen in an automated manner without manual intervention by the user, but this particular error path can only happen by a deliberate user action so it's not the same situation.

Actions

Also available in: Atom PDF