• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Logs not updating on 23.01

Scheduled Pinned Locked Moved Plus 23.01 Development Snapshots (Retired)
7 Posts 2 Posters 1.0k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    jjstecchino
    last edited by Feb 6, 2023, 11:21 PM

    Logs are not getting logged after update from 22.05 to 23.01

    I have a syslog instance running

    ps -ax | grep syslogd
    85310  -  Ss     0:00.10 /usr/sbin/syslogd -s -c -c -l /var/dhcpd/var/run/log -
    55116  0  S+     0:00.00 grep syslogd
    

    if I click settings on the log screen I get a php error:

    Crash report begins.  Anonymous machine information:
    
    amd64
    14.0-CURRENT
    FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256014-9cf2a68c5e5: Thu Feb  2 17:13:21 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/ItAd8BGz/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBS
    
    Crash report details:
    
    PHP Errors:
    [06-Feb-2023 17:11:58 America/New_York] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/status_logs_settings.php:72
    Stack trace:
    #0 {main}
      thrown in /usr/local/www/status_logs_settings.php on line 72
    [06-Feb-2023 17:23:12 America/New_York] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/status_logs_settings.php:72
    Stack trace:
    #0 {main}
      thrown in /usr/local/www/status_logs_settings.php on line 72
    [06-Feb-2023 18:19:00 America/New_York] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/status_logs_settings.php:72
    Stack trace:
    #0 {main}
      thrown in /usr/local/www/status_logs_settings.php on line 72
    
    
    
    No FreeBSD crash data found.
    			
    
    1 Reply Last reply Reply Quote 0
    • M
      marcosm Netgate
      last edited by Feb 6, 2023, 11:56 PM

      Would you post the config.xml section <syslog>?

      J 4 Replies Last reply Feb 7, 2023, 12:08 AM Reply Quote 0
      • J
        jjstecchino @marcosm
        last edited by Feb 7, 2023, 12:08 AM

        @marcosm
        The syslog section of my config.xml is empty:
        <syslog></syslog>

        1 Reply Last reply Reply Quote 0
        • J
          jjstecchino @marcosm
          last edited by Feb 7, 2023, 12:09 AM

          @marcosm

          And it shouldn't be as my other firewall has this:
          <syslog>
          <filterdescriptions>1</filterdescriptions>
          <nentries>500</nentries>
          <logcompressiontype>bzip2</logcompressiontype>
          <format>rfc3164</format>
          <rotatecount></rotatecount>
          <sourceip>lan</sourceip>
          <ipproto>ipv4</ipproto>
          <logall></logall>
          <logconfigchanges>enabled</logconfigchanges>
          </syslog>

          1 Reply Last reply Reply Quote 0
          • J
            jjstecchino @marcosm
            last edited by jjstecchino Feb 7, 2023, 12:12 AM Feb 7, 2023, 12:11 AM

            @marcosm

            This firewall was a straight upgrade from new install 2.6 -> plus 22.01 -> plus 22.05 -> plus 23.01.

            Logs were working up to 22.05

            1 Reply Last reply Reply Quote 0
            • J
              jjstecchino @marcosm
              last edited by Feb 7, 2023, 12:24 AM

              @marcosm

              Ok, I restored the syslog section from the working firewall to the non workin one and now all is ok.

              I wonder why the syslog session was lost during upgrade.

              1 Reply Last reply Reply Quote 1
              • M
                marcosm Netgate
                last edited by Feb 7, 2023, 1:58 AM

                Thank you - I submitted a fix for it:
                https://redmine.pfsense.org/issues/13942

                1 Reply Last reply Reply Quote 0
                • M mcury referenced this topic on Mar 17, 2023, 2:16 PM
                • M mcury referenced this topic on Mar 17, 2023, 2:16 PM
                7 out of 7
                • First post
                  7/7
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received