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

    Sustained Unbound write I/O

    pfBlockerNG
    7
    44
    3.5k
    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.
    • S
      slu @keyser
      last edited by

      @keyser
      not easy to debug.

      @NOCling you use python mode as well, right?
      Do you see this as well?

      pfSense Gold subscription

      1 Reply Last reply Reply Quote 0
      • N
        NOCling
        last edited by

        Yes, i use it.
        But i run a RAM Disk to prevent Unbound killing my SSD.
        I use a UPS and NUT on the pfsense, so no unexpected Power loss and the RAM Disk is safely written to the SSD.

        Netgate 6100 & Netgate 2100

        S w0wW 2 Replies Last reply Reply Quote 0
        • S
          slu @NOCling
          last edited by

          @NOCling said in Sustained Unbound write I/O:

          Yes, i use it.
          But i run a RAM Disk to prevent Unbound killing my SSD.

          ah ok, I can't use RAM Disk in my setup.
          So you know about the Unbound write problem?

          pfSense Gold subscription

          1 Reply Last reply Reply Quote 0
          • w0wW
            w0w @NOCling
            last edited by

            @NOCling
            ะกould you please suggest the correct configuration for a RAM disk? Every time I've tried to set it up, it ended with messages about running out of space or other issues. I have 16GB of memory; is that generally enough?

            1 Reply Last reply Reply Quote 0
            • N
              NOCling
              last edited by

              I use this settings on my 6100, but it depends on the list if its ok or not:
              edcaf417-6d4e-434a-af0b-0a81eeb3ff0b-image.png

              Netgate 6100 & Netgate 2100

              Bob.DigB 2 Replies Last reply Reply Quote 1
              • Bob.DigB
                Bob.Dig LAYER 8 @NOCling
                last edited by

                @NOCling I lose my pfBlocker aliases if I try the RAM-disk. Any hints?

                M 1 Reply Last reply Reply Quote 0
                • Bob.DigB
                  Bob.Dig LAYER 8 @NOCling
                  last edited by

                  @NOCling Do I have to wait til Friday to get an answer? ๐Ÿ˜

                  1 Reply Last reply Reply Quote 0
                  • M
                    mcury @Bob.Dig
                    last edited by

                    @Bob-Dig said in Sustained Unbound write I/O:

                    @NOCling I lose my pfBlocker aliases if I try the RAM-disk. Any hints?

                    force update in pfblockerNG and you will get your aliases back.

                    dead on arrival, nowhere to be found.

                    Bob.DigB 1 Reply Last reply Reply Quote 1
                    • Bob.DigB
                      Bob.Dig LAYER 8 @mcury
                      last edited by Bob.Dig

                      @mcury Yes, but after the next reboot is was gone again. So maybe I have to tick a box to save something? But saving will not be good for the health...
                      I do reboot daily. "Reboot does good" they say around my place.

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        mcury @Bob.Dig
                        last edited by

                        @Bob-Dig said in Sustained Unbound write I/O:

                        @mcury Yes but after the next reboot is was gone. So maybe I have to tick a box to save something? But saving will not be good for the health...
                        I do reboot daily. "Reboot does good" they say around my place.

                        you can install cron and shellcmd packages.
                        check cron and get the command used to update pfblockerNG, them add it to shellcmd package to run after boot.

                        dead on arrival, nowhere to be found.

                        Bob.DigB 1 Reply Last reply Reply Quote 1
                        • Bob.DigB
                          Bob.Dig LAYER 8 @mcury
                          last edited by Bob.Dig

                          @mcury said in Sustained Unbound write I/O:

                          check cron and get the command used to update pfblockerNG, them add it to shellcmd package to run after boot.

                          Thanks. Have you edited the command? It doesn't seem to work for me. No files are shown when looking in logs in pfB. Only running "reload" manually will bring them back.

                          Screenshot 2024-08-20 191758.png

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            mcury @Bob.Dig
                            last edited by

                            @Bob-Dig said in Sustained Unbound write I/O:

                            @mcury said in Sustained Unbound write I/O:

                            check cron and get the command used to update pfblockerNG, them add it to shellcmd package to run after boot.

                            Thanks. Have you edited the command? It doesn't seem to work for me. No files are shown when looking in logs in pfB. Only running "reload" manually will bring them back.

                            Screenshot 2024-08-20 191758.png

                            this one works for me, but I'm not using DNSBL, so I don't know the DNSBL entry, but should be something similar.

                            /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron
                            

                            dead on arrival, nowhere to be found.

                            Bob.DigB 1 Reply Last reply Reply Quote 1
                            • Bob.DigB
                              Bob.Dig LAYER 8 @mcury
                              last edited by Bob.Dig

                              @mcury Looking in the firewall rules, the aliases do work. But I can't see any files in the log-section of pfB. After I run reload manually, I see those files... Don't know what to think about it. Shellcmd doesn't seem to make any difference about that.

                              M 1 Reply Last reply Reply Quote 0
                              • M
                                mcury @Bob.Dig
                                last edited by mcury

                                @Bob-Dig according to this link:

                                https://forum.netgate.com/topic/111940/quickest-way-to-reload-pfblockerng-rules/2

                                BBcan177 stated that the command above may be dangerous in case the cron job is already running.
                                So, take that in consideration.

                                In that link, he also explains the logs missing.

                                dead on arrival, nowhere to be found.

                                Bob.DigB 2 Replies Last reply Reply Quote 1
                                • Bob.DigB
                                  Bob.Dig LAYER 8 @mcury
                                  last edited by Bob.Dig

                                  @mcury said in Sustained Unbound write I/O:

                                  In that link, he also explains the logs missing.

                                  I am not sure if this is what I meant. Anyway, if the aliases themselves are saved to the disk anyways, then I don't need Shellcmd I guess. Will have to reboot yet again. ๐Ÿ˜
                                  Yep, aliases are there in any case, now I will watch what regular cron update will do to the "logs" (not reloading).

                                  1 Reply Last reply Reply Quote 1
                                  • Bob.DigB
                                    Bob.Dig LAYER 8 @mcury
                                    last edited by

                                    @mcury Much Ado About Nothing from me, I should have looked in the rules before, everything works right away. Regular cron is rebuilding the files in "log". So Shellcmd does nothing in this regard and is not needed anyways. ๐Ÿ™‚

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