crash report after update

kiokoman

@jimp
i have this after upgrading to the latest development snapshot

Crash report begins.  Anonymous machine information:

amd64
12.0-RELEASE-p9
FreeBSD 12.0-RELEASE-p9 e23c75c4280(RELENG_2_5) pfSense

Crash report details:

PHP Errors:

Fatal error: Uncaught Error: Call to undefined function sort_related_log_files() in /usr/local/sbin/prefixes.php:112
Stack trace:
#0 {main}
  thrown in /usr/local/sbin/prefixes.php on line 112

No FreeBSD crash data found.

content of line 112
if (file_exists($dhcpdlogfile)) {
$fd = popen('/usr/bin/bzcat -f ' . sort_related_log_files($dhcpdlogfile, true, true), 'r');

it seem to be a new entry
-rw-r--r-- 1 root wheel 4356 Aug 31 01:21 prefixes.php

kiokoman

https://redmine.pfsense.org/issues/9715
if anyone else have the same problem
solution is to add

require_once("functions.inc");

to the file

like this

* Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
require_once("functions.inc");
$leases_file = "/var/dhcpd/var/db/dhcpd6.leases";
if (!file_exists($leases_file)) {

after this a reboot is needed,
also i found out that a route to one of my interface was not working and i was unable to reach that interface via IPv6 without this

bimmerdriver

I'm seeing a similar problem:

Crash report begins.  Anonymous machine information:

amd64
12.0-RELEASE-p9
FreeBSD 12.0-RELEASE-p9 e23c75c4280(RELENG_2_5) pfSense

Crash report details:

PHP Errors:
[01-Sep-2019 14:29:15 America/Vancouver] PHP Fatal error:  Uncaught Error: Call to undefined function sort_related_log_files() in /usr/local/sbin/prefixes.php:112
Stack trace:
#0 {main}
  thrown in /usr/local/sbin/prefixes.php on line 112



No FreeBSD crash data found.

kiokoman

@bimmerdriver
It's the same. Apply my patch and reboot

stephenw10

There are likely to be some logging errors after clog was removed. Keep reporting them.

https://forum.netgate.com/topic/146169/heads-up-logging-changes-clog-deprecated-plain-text-logs-newsyslog-rotation-in-next-snapshots

Steve