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

    Telegraf error after update PFSense to 23.01

    Scheduled Pinned Locked Moved
    pfSense Packages
    2
    4
    1.0k
    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.
    • KrumXK
      KrumX
      last edited by

      Telegraf craches after update to 23.01
      Hardware: Netgate 6100
      Telegraf Version: 0.9_6
      pfSense-pkg-Telegraf

      Crash report details:

      PHP Errors:
      [19-Feb-2023 10:00:54 Europe/Zurich] PHP Fatal error: Uncaught TypeError: implode(): Argument #1 ($pieces) must be of type array, string given in /usr/local/pkg/telegraf.inc:132
      Stack trace:
      #0 /usr/local/pkg/telegraf.inc(132): implode(',', NULL)
      #1 /etc/inc/pkg-utils.inc(781) : eval()'d code(1): telegraf_resync_config()
      #2 /etc/inc/pkg-utils.inc(781): eval()
      #3 /etc/inc/pkg-utils.inc(906): eval_once(' telegra...')
      #4 /etc/rc.packages(76): install_package_xml('Telegraf')
      #5 {main}
      thrown in /usr/local/pkg/telegraf.inc on line 132
      [19-Feb-2023 10:01:02 Europe/Zurich] PHP Fatal error: Uncaught TypeError: implode(): Argument #1 ($pieces) must be of type array, string given in /usr/local/pkg/telegraf.inc:132
      Stack trace:
      #0 /usr/local/pkg/telegraf.inc(132): implode(',', NULL)
      #1 /etc/inc/pkg-utils.inc(715) : eval()'d code(1): telegraf_resync_config()
      #2 /etc/inc/pkg-utils.inc(715): eval()
      #3 /etc/rc.start_packages(66): sync_package('Telegraf')
      #4 {main}
      thrown in /usr/local/pkg/telegraf.inc on line 132
      
      H 1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • H
        hovnetworks @KrumX
        last edited by

        @krumx I'm having the same issue at this time with the same version of PFSense. Did you ever find the fix for this error?

        KrumXK 1 Reply Last reply Reply Quote 0
        • KrumXK
          KrumX @hovnetworks
          last edited by

          @hovnetworks, Unfortunately no

          H 1 Reply Last reply Reply Quote 0
          • H
            hovnetworks @KrumX
            last edited by

            @krumx Hello,

            This doesn't help much at the moment however, they do have an open ticket for this issue. Just not sure when it will be fixed but at least we can track it here and update as soon as possible:

            https://redmine.pfsense.org/issues/13985

            1 Reply Last reply Reply Quote 0
            • First post
              Last post