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

Log file export content out-of-order

Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
4 Posts 2 Posters 816 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.
  • H
    hda
    last edited by Jan 14, 2016, 9:22 AM Jan 13, 2016, 1:21 PM

    built on Tue Jan 12 02:01:13 CST 2016  Diagnostics > Execute command > Download file:
    After a line reset from outside and restart of PPPoE.

    I see the exported file (arrived downstream /UltraEdit) of system.log is out-of-order in records and not exact at starting (1 char off). Same behaviour from the nginx.log.

    Can someone verify this ?

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Jan 13, 2016, 7:27 PM

      It's a binary clog file, not plain text.

      https://doc.pfsense.org/index.php/Why_can't_I_view_view_log_files_with_cat/grep/etc%3F_%28clog%29

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • H
        hda
        last edited by Jan 13, 2016, 7:41 PM

        @jimp:

        It's a binary clog file, not plain text.

        Yes, well my point is, what changed from 2.2.6 to 2.3 ;) Because downloading (not conCATinating) this binary logfile was recognized as such from 2.2.6 and could be properly converted/toggled to txt. Notably the 2.3 ppp.log is OK with such procedure, but not the system.log or nginx.log…

        1 Reply Last reply Reply Quote 0
        • J
          jimp Rebel Alliance Developer Netgate
          last edited by Jan 13, 2016, 7:43 PM

          Nothing changed there. It was clog before, clog now.

          Maybe nginx is sending it as some other mime type but even so, it's the same content before and after.

          If you think a file is "OK" it's likely only because it hasn't had enough data inside to roll over.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received