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

    PFSense 2.4.4 not responding at console and web interface CRITICAL BUG! HELP!

    Scheduled Pinned Locked Moved Virtualization
    32 Posts 3 Posters 3.1k 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

      You mean shutdown and restart or actually suspend?

      john_wickJ 1 Reply Last reply Reply Quote 0
      • john_wickJ
        john_wick @stephenw10
        last edited by john_wick

        @stephenw10 Without reboot only suspend like pause/resume

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

          Hmm, not sure I've ever tried that. Does it only show that error when you resume it?

          john_wickJ 1 Reply Last reply Reply Quote 0
          • john_wickJ
            john_wick @stephenw10
            last edited by

            @stephenw10 said in PFSense 2.4.4 not responding at console and web interface CRITICAL BUG! HELP!:

            You might try switching to one of the other timecounters:
            sysctl kern.timecounter=ACPI-fast

            You can add that in System Tunables if it fixes it.

            Steve

            alt timecounter

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

              Sorry I missed a bit there, the sysctl should be kern.timecounter.hardware

              Did you try it at the command line first?

              Steve

              john_wickJ 1 Reply Last reply Reply Quote 0
              • john_wickJ
                john_wick @stephenw10
                last edited by

                @stephenw10
                Mostly yes. According to my observations, sometimes the calcru error enters the log not immediately, but at intervals after a pause. Basically, the console simply stops responding or responding via ssh and the web UI stops responding sometimes with a 502 bad gateway. Now I have installed sysctl kern.timecounter = ACPI-fast will reboot and look at the reaction. If I fail, I will try to improve performance and frequency.

                1 Reply Last reply Reply Quote 0
                • john_wickJ
                  john_wick @stephenw10
                  last edited by john_wick

                  @stephenw10 said in PFSense 2.4.4 not responding at console and web interface CRITICAL BUG! HELP!:

                  Sorry I missed a bit there, the sysctl should be kern.timecounter.hardware

                  Did you try it at the command line first?

                  Steve

                  Like this alt text Hase a diference with cli or with UI config edit?

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

                    That's correct. It will apply via the GUI like that but it's then permanent. If you test it from the CLI first and it does something unexpected you can just reboot.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • john_wickJ
                      john_wick
                      last edited by john_wick

                      Hi Stepen yesterday error is gone and server work stable access to cli and web UI was anytime when was small trafic but after night when trafic was zero error come back again. Need more time to watch on the actions and need to tweak to max performance or maybe I can add some cron jobs to prevent falling asleep webconfigurator or this is more fundamental timecounter problems?

                      Mar 25 15:08:27	kernel		calcru: runtime went backwards from 685818 usec to 353871 usec for pid 24 (syncer)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 685818 usec to 353871 usec for pid 24 (syncer)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 17 usec to 8 usec for pid 5 (sctp_iterator)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 18 usec to 9 usec for pid 5 (sctp_iterator)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 182 usec to 93 usec for pid 15 (usb)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 164420 usec to 83927 usec for pid 4 (cam)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 5 usec to 2 usec for pid 2 (crypto)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 19805 usec to 10109 usec for pid 14 (geom)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 21765 usec to 11109 usec for pid 14 (geom)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 1094 usec to 558 usec for pid 14 (geom)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 7510 usec to 3833 usec for pid 14 (geom)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 10 usec to 5 usec for pid 13 (ng_queue)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 15 usec to 8 usec for pid 13 (ng_queue)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 33 usec to 17 usec for pid 12 (intr)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 928 usec to 474 usec for pid 12 (intr)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 949204 usec to 490190 usec for pid 12 (intr)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 1790 usec to 1195 usec for pid 12 (intr)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 10823 usec to 5572 usec for pid 1 (init)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 20126323 usec to 10274286 usec for pid 1 (init)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 10823 usec to 5572 usec for pid 1 (init)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 10 usec to 5 usec for pid 10 (audit)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 42471156539 usec to 21679250280 usec for pid 0 (kernel)


                      Mar 25 15:08:27	kernel		calcru: runtime went backwards from 7 usec to 3 usec for pid 0 (kernel)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 13 usec to 6 usec for pid 0 (kernel)
Mar 25 15:08:27	kernel		calcru: runtime went backwards from 9 usec to 4 usec for pid 0 (kernel)
                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        kern.timecounter.hardware is still set to ACPI-fast?

                        john_wickJ 1 Reply Last reply Reply Quote 0
                        • john_wickJ
                          john_wick @stephenw10
                          last edited by john_wick

                          @stephenw10 Work stable last hours

                          [2.4.4-RELEASE][root@pfSense.localdomain]/root: sysctl kern.timecounter
kern.timecounter.tsc_shift: 1
kern.timecounter.smp_tsc_adjust: 0
kern.timecounter.smp_tsc: 0
kern.timecounter.invariant_tsc: 0
kern.timecounter.fast_gettime: 1
kern.timecounter.tick: 1
kern.timecounter.choice: i8254(0) ACPI-fast(900) HPET(950) TSC-low(800) dummy(-1000000)
kern.timecounter.hardware: ACPI-fast
kern.timecounter.alloweddeviation: 5
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.counter: 23746
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.ACPI-fast.quality: 900
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.counter: 12995060
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.HPET.quality: 950
kern.timecounter.tc.HPET.frequency: 100000000
kern.timecounter.tc.HPET.counter: 2672335151
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.TSC-low.quality: 800
kern.timecounter.tc.TSC-low.frequency: 1199698926
kern.timecounter.tc.TSC-low.counter: 2441661706
kern.timecounter.tc.TSC-low.mask: 4294967295
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            You could try the TSC-low timecounter also if you#re still seeing issues. That is lower quality though.

                            Steve

                            john_wickJ 1 Reply Last reply Reply Quote 0
                            • john_wickJ
                              john_wick @stephenw10
                              last edited by john_wick

                              @stephenw10 said in PFSense 2.4.4 not responding at console and web interface CRITICAL BUG! HELP!:

                              That is lower quality though.

                              Last hours work stable :) Thank you for the professional help from expert its helps for my case!
                              Fought this problem for several months, there was no desire to leave PfSense.
                              This is my first experience with BSD systems. Several years watched pfsense and not in vain awesome project

                              What you mean That is lower quality though?
                              I have enother qestion about VM cputime (units) what optimal recomended value for PFsense in KVM?

                              Does it make sense to increase the frequency or processor time for more stable operation

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

                                The quality value shown in brackets denotes the accuracy of the timecounter source which is why HPET was chosen by default. That can be a problem when all the hardware is virtual, some may be virtualised better than others for whatever reason.

                                I can't really advice you on KVM settings directly. I would think anything that is different to the host CPU is going to require more processing from the hypervisor. Passing CPU cores directly to the VM is probably better. But as I say I don't use KVM so that's speculation. I'm sure there are others here who can give better advice there.

                                Steve

                                john_wickJ 1 Reply Last reply Reply Quote 0
                                • john_wickJ
                                  john_wick @stephenw10
                                  last edited by

                                  @stephenw10 Hi Stephen. UI and console was resopnsive after 15 hours and stable work

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

                                    Cool. So which timecounter did you end up using for reference?

                                    Steve

                                    john_wickJ 1 Reply Last reply Reply Quote 0
                                    • john_wickJ
                                      john_wick @stephenw10
                                      last edited by john_wick

                                      @stephenw10 I just add kern.timecounter.hardware=ACPI-fast from web UI in tunables and reboot the PFsense VM :)

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