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

    Corrupt Configs

    Scheduled Pinned Locked Moved General pfSense Questions
    25 Posts 3 Posters 1.6k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      That probably never made a 2.3.X package though....

      Make sure you set a total log directory size limit as well as the individual log sizes.

      Steve

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        Yeah, that fix was definitely for pfSense-2.4.x.

        1 Reply Last reply Reply Quote 0
        • S
          Stewart
          last edited by

          I've updated to 2.4.4-p3 but the available packages page is blank:

          d6580b3e-564b-426e-b83c-086cdb80a730-image.png

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Try running pkg update see what error it gives.

            Steve

            S 1 Reply Last reply Reply Quote 0
            • S
              Stewart @stephenw10
              last edited by Stewart

              @stephenw10

              Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/meta.txz: Network is unreachable
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/packagesite.txz: Network is unreachable
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/meta.txz: Network is unreachable
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/packagesite.txz: Network is unreachable
Unable to update repository pfSense
Error updating repositories!

              EDIT: WAN is up. I'm connecting out through the unit right now.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Can the firewall itself connect out? Ping? DNS lookup?

                If you're policy routing it may have lost it's default route coming from 2.3.X.

                Make sure you have a default gateway set in System > Routing > Gateways rather than set to 'automatic' there.

                Steve

                1 Reply Last reply Reply Quote 0
                • S
                  Stewart
                  last edited by

                  Using the force command fixed it, though.

                  /root: pkg update -f
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%    2 KiB   1.7kB/s    00:01
Processing entries: 100%
pfSense-core repository update completed. 7 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%  138 KiB 140.9kB/s    00:01
Processing entries: 100%
pfSense repository update completed. 518 packages processed.
All repositories are up to date.
                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Ah, interesting. And it sees packages now?

                    1 Reply Last reply Reply Quote 0
                    • S
                      Stewart
                      last edited by

                      Yes. So far so good. I don't know why it ran out of space while in service but after taking it offline suddenly there is 4.6GB free. Certainly need to clear it out but where did that other space run off to? I wonder...

                      1 Reply Last reply Reply Quote 0
                      • S
                        Stewart
                        last edited by

                        I've also found an oddity in /var/squid/logs:

                        /var/squid/logs: ls -lah | grep access
-rw-r-----  1 squid  proxy     0B Aug 13 00:00 access.log
-rw-r-----  1 squid  proxy   6.1G Jun  8 05:14 access.log.0
-rw-r-----  1 squid  proxy    52M May  5 00:00 access.log.1
-rw-r-----  1 squid  proxy     0B Apr 25 00:00 access.log.10
-rw-r-----  1 squid  proxy     0B Apr 24 00:00 access.log.11
-rw-r-----  1 squid  proxy     0B Apr 23 00:00 access.log.12
-rw-r-----  1 squid  proxy     0B Apr 22 00:00 access.log.13
-rw-r-----  1 squid  proxy     0B Apr 21 00:00 access.log.14
-rw-r-----  1 squid  proxy     0B Apr 20 00:00 access.log.15
-rw-r-----  1 squid  proxy     0B Apr 19 00:00 access.log.16
-rw-r-----  1 squid  proxy     0B Apr 18 00:00 access.log.17
-rw-r-----  1 squid  proxy     0B Apr 17 00:00 access.log.18
-rw-r-----  1 squid  proxy     0B Apr 16 00:00 access.log.19
-rw-r-----  1 squid  proxy    56M May  4 00:00 access.log.2
-rw-r-----  1 squid  proxy     0B Apr 15 00:00 access.log.20
-rw-r-----  1 squid  proxy     0B Apr 14 00:00 access.log.21
-rw-r-----  1 squid  proxy     0B Apr 13 00:00 access.log.22
-rw-r-----  1 squid  proxy     0B Apr 12 00:00 access.log.23
-rw-r-----  1 squid  proxy     0B Apr 11 00:00 access.log.24
-rw-r-----  1 squid  proxy     0B Apr 10 00:00 access.log.25
-rw-r-----  1 squid  proxy     0B Apr  9 00:00 access.log.26
-rw-r-----  1 squid  proxy     0B Apr  8 00:00 access.log.27
-rw-r-----  1 squid  proxy     0B Apr  7 00:00 access.log.28
-rw-r-----  1 squid  proxy     0B Apr  6 00:00 access.log.29
-rw-r-----  1 squid  proxy    35M May  3 00:00 access.log.3
-rw-r-----  1 squid  proxy   9.6M May  2 00:00 access.log.4
-rw-r-----  1 squid  proxy   1.9M May  1 00:00 access.log.5
-rw-r-----  1 squid  proxy     0B Apr 29 00:00 access.log.6
-rw-r-----  1 squid  proxy     0B Apr 28 00:00 access.log.7
-rw-r-----  1 squid  proxy     0B Apr 27 00:00 access.log.8
-rw-r-----  1 squid  proxy     0B Apr 26 00:00 access.log.9

                        with access.log.0 being 6.1GB in size, would that indicate that it isn't rotating?

                        bmeeksB 1 Reply Last reply Reply Quote 0
                        • bmeeksB
                          bmeeks @Stewart
                          last edited by

                          @Stewart said in Corrupt Configs:

                          I've also found an oddity in /var/squid/logs:

                          /var/squid/logs: ls -lah | grep access
-rw-r-----  1 squid  proxy     0B Aug 13 00:00 access.log
-rw-r-----  1 squid  proxy   6.1G Jun  8 05:14 access.log.0
-rw-r-----  1 squid  proxy    52M May  5 00:00 access.log.1
-rw-r-----  1 squid  proxy     0B Apr 25 00:00 access.log.10
-rw-r-----  1 squid  proxy     0B Apr 24 00:00 access.log.11
-rw-r-----  1 squid  proxy     0B Apr 23 00:00 access.log.12
-rw-r-----  1 squid  proxy     0B Apr 22 00:00 access.log.13
-rw-r-----  1 squid  proxy     0B Apr 21 00:00 access.log.14
-rw-r-----  1 squid  proxy     0B Apr 20 00:00 access.log.15
-rw-r-----  1 squid  proxy     0B Apr 19 00:00 access.log.16
-rw-r-----  1 squid  proxy     0B Apr 18 00:00 access.log.17
-rw-r-----  1 squid  proxy     0B Apr 17 00:00 access.log.18
-rw-r-----  1 squid  proxy     0B Apr 16 00:00 access.log.19
-rw-r-----  1 squid  proxy    56M May  4 00:00 access.log.2
-rw-r-----  1 squid  proxy     0B Apr 15 00:00 access.log.20
-rw-r-----  1 squid  proxy     0B Apr 14 00:00 access.log.21
-rw-r-----  1 squid  proxy     0B Apr 13 00:00 access.log.22
-rw-r-----  1 squid  proxy     0B Apr 12 00:00 access.log.23
-rw-r-----  1 squid  proxy     0B Apr 11 00:00 access.log.24
-rw-r-----  1 squid  proxy     0B Apr 10 00:00 access.log.25
-rw-r-----  1 squid  proxy     0B Apr  9 00:00 access.log.26
-rw-r-----  1 squid  proxy     0B Apr  8 00:00 access.log.27
-rw-r-----  1 squid  proxy     0B Apr  7 00:00 access.log.28
-rw-r-----  1 squid  proxy     0B Apr  6 00:00 access.log.29
-rw-r-----  1 squid  proxy    35M May  3 00:00 access.log.3
-rw-r-----  1 squid  proxy   9.6M May  2 00:00 access.log.4
-rw-r-----  1 squid  proxy   1.9M May  1 00:00 access.log.5
-rw-r-----  1 squid  proxy     0B Apr 29 00:00 access.log.6
-rw-r-----  1 squid  proxy     0B Apr 28 00:00 access.log.7
-rw-r-----  1 squid  proxy     0B Apr 27 00:00 access.log.8
-rw-r-----  1 squid  proxy     0B Apr 26 00:00 access.log.9

                          with access.log.0 being 6.1GB in size, would that indicate that it isn't rotating?

                          It would look that way to me at first glance.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.