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

    Ntopng Service is not running on pfsense 2.3.2-RELEASE ?

    Scheduled Pinned Locked Moved
    Traffic Monitoring
    7
    13
    7.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.
    • R
      rimfire
      last edited by

      This is a week or two old, but I will have a go at this since I had the same problem as well.
      The problem seems to stem from using a ramdisk for /var

      After digging around a bit I found this
      https://redmine.pfsense.org/issues/6443#note-15

      from the shell I was able to start redis with with no .config file, but it would not start from pfsense or from the shell using the redis.config file.

      When using redis.config, redis complained it was missing the folders
      /var/log/redis
      /var/db/redis

      After creating those, redis would start from the shell using redis.config.  But then ntopng would not start until I created
      /var/db/ntopng

      At this point I have ntop running.
      But the same problem will occur whenever I restart so this has me questioning running the /var ramdisk.
      Since pfblocker stores everything in /var as well, blocklists do not work until pfb can redownload the lists, and I also loose all my lightsquid and ntop reports.  Sure I can fix all that on restart, but do I really need to…

      So, my question
      I have a fully allocated 64G SSD (no explicit over provisioning), but its showing only 2% used. 
      Is running the /var ramdisk really buying you anything if running trim on the SSD?
      Does freeBSD use unused space as well for trim?  If so I then I really don't see the benefit of running a ramdisk for /var with all its associated side effects.

      Fair warning - I have been running pfsense for a year - so I am pretty new at this *nix stuff and spend about 98% of my time on WinX machines so YMMV.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        No, it doesn't buy you anything except for being a royal PITA. Hopefully the ramdisk nonsense will get removed from pfSense one day for /var now that nanobsd is dead. And WTH is that glued to /tmp goes beyond me. It's allegedly somehow persistent across reboots on recent 2.4 snapshots (as in tar up the stuff and restore on reboot.  ::))

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

          i tried installing on 2.1  the dashboard ses its running but. i cant access it :(  .

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            2.1? Huh? And why are you posting it here?

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

              ^_^ just a testing. i just test it on a generic computer  but it doesn't run anyways. can you  help me please doktornotor

              1 Reply Last reply Reply Quote 0
              • C
                chrcoluk
                last edited by

                A word of warning, tomshardware recently published some alarming news about ramless planar TLC ssd's where they are predicted by the vendors to reach flash rated endurance in a little over a year (planned obsolescence).  When there is no ram cache installed on the SSD, then a certain type of data gets written way more frequently to do with the drive mapping which is the cause of the problem alongside very cheap flash used in some budget low end drives.

                With pfsense the only issue I see is the rrd graphs, they generate about 5 gig of writes a day on my unit if I let it write to the ssd.  I think there is merit in moving /var/db/rrd to a ramdisk but is little need for the rest of /var. However on most modern ssd's 5 gig a day shouldnt be a problem, with 3d NAND, TRIM, write levelling etc.

                The vast majority of ssd's especially non OEM models do have a ram cache tho.

                Also if using zfs then the compression will mitigate the amount of writes (even with the copy on write system) as a lot of data written by pfsense if not all of it compresses well.

                pfSense CE 2.7.2

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  @nandattebayu:

                  ^_^ just a testing. i just test it on a generic computer  but it doesn't run anyways. can you  help me please doktornotor

                  No. Anything <2.3.x is totally unmaintained and unsupported. https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD

                  1 Reply Last reply Reply Quote 0
                  • jimpJ
                    jimp Rebel Alliance Developer Netgate
                    last edited by

                    @doktornotor:

                    No, it doesn't buy you anything except for being a royal PITA. Hopefully the ramdisk nonsense will get removed from pfSense one day for /var now that nanobsd is dead. And WTH is that glued to /tmp goes beyond me. It's allegedly somehow persistent across reboots on recent 2.4 snapshots (as in tar up the stuff and restore on reboot.  ::))

                    Actually it's more likely to stay now that NanoBSD is dead. Keeping those both in RAM drastically reduces disk writes. On modern SSDs it doesn't matter so much but if you're running off a thumb drive you probably don't want to be writing out several files every second of every day chewing through write cycles on dodgy media.

                    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
                    • D
                      doktornotor Banned
                      last edited by

                      Eh, whatever. I could live with that if /tmp was decoupled from /var. The /var thing is just a massive PITA. Certainly way better off getting at least a small SSD.

                      1 Reply Last reply Reply Quote 0
                      • V
                        VladimirM
                        last edited by

                        I have been using pfsense on 2.3.2-RELEASE (amd64) my problem is ntopng it worked until my router is reboted after lost light . Now ntopng doesn't start without redis-server . For starting service i have to activated it with config ,  i mean redis-server /usr/local/etc/redis.conf then i start ntopng .
                        If you want to see my logs :

                        ntopng : 27/Mar/2017 17:34:15 [Prefs.cpp:919] Logging into /var/tmp/ntopng/ntopng.log
                        27/Mar/2017 17:34:15 [Ntop.cpp:1121] Setting local networks to 127.0.0.0/8
                        27/Mar/2017 17:34:17 [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        27/Mar/2017 17:34:17 [Redis.cpp:80] ERROR: Please start it and try again or use -r
                        27/Mar/2017 17:34:17 [Redis.cpp:81] ERROR: to specify a redis server other than the default

                        syslog : Mar 27 11:02:48 pfSense php-fpm[280]: /rc.start_packages: [ntopng] Cannot set admin password - redis-server is not running.
                        Mar 27 11:02:50 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 11:02:50 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 11:03:10 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 11:03:10 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 11:06:42 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 11:06:42 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 11:12:30 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 11:12:30 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 11:14:24 pfSense admin: /usr/local/etc/rc.d/redis: WARNING: failed to start redis
                        Mar 27 11:18:52 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 11:18:52 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 11:20:33 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 11:20:33 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 11:20:48 pfSense admin: /usr/local/etc/rc.d/redis: WARNING: failed to start redis
                        Mar 27 12:22:30 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 12:22:30 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 12:24:27 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 12:24:27 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default
                        Mar 27 12:24:47 pfSense ntopng: [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
                        Mar 27 12:24:47 pfSense ntopng: [Redis.cpp:81] ERROR: to specify a redis server other than the default

                        Redis logs : /var/log/redis/redis.log
                        13771:M 27 Mar 16:06:34.087 * 10 changes in 300 seconds. Saving…
                        13771:M 27 Mar 16:06:34.087 * Background saving started by pid 73803
                        73803:C 27 Mar 16:06:34.092 * DB saved on disk
                        13771:M 27 Mar 16:06:34.194 * Background saving terminated with success
                        13771:M 27 Mar 16:11:35.077 * 10 changes in 300 seconds. Saving...
                        13771:M 27 Mar 16:11:35.078 * Background saving started by pid 89520
                        89520:C 27 Mar 16:11:35.083 * DB saved on disk
                        13771:M 27 Mar 16:11:35.181 * Background saving terminated with success
                        13771:M 27 Mar 16:16:36.083 * 10 changes in 300 seconds. Saving...
                        13771:M 27 Mar 16:16:36.083 * Background saving started by pid 11670
                        11670:C 27 Mar 16:16:36.088 * DB saved on disk
                        13771:M 27 Mar 16:16:36.190 * Background saving terminated with success
                        13771:M 27 Mar 16:21:37.029 * 10 changes in 300 seconds. Saving...
                        13771:M 27 Mar 16:21:37.030 * Background saving started by pid 32620
                        32620:C 27 Mar 16:21:37.035 * DB saved on disk
                        13771:M 27 Mar 16:21:37.137 * Background saving terminated with success
                        13771:M 27 Mar 16:26:38.083 * 10 changes in 300 seconds. Saving...
                        13771:M 27 Mar 16:26:38.084 * Background saving started by pid 81885
                        81885:C 27 Mar 16:26:38.089 * DB saved on disk
                        13771:M 27 Mar 16:26:38.191 * Background saving terminated with success
                        13771:M 27 Mar 16:31:39.071 * 10 changes in 300 seconds. Saving...
                        13771:M 27 Mar 16:31:39.072 * Background saving started by pid 24264
                        24264:C 27 Mar 16:31:39.077 * DB saved on disk
                        13771:M 27 Mar 16:31:39.173 * Background saving terminated with success
                        13771:signal-handler (1490632348) Received SIGTERM scheduling shutdown...
                        13771:M 27 Mar 16:32:28.955 # User requested shutdown...
                        13771:M 27 Mar 16:32:28.955 * Saving the final RDB snapshot before exiting.
                        13771:M 27 Mar 16:32:28.968 * DB saved on disk
                        13771:M 27 Mar 16:32:28.968 * Removing the pid file.
                        13771:M 27 Mar 16:32:28.968 # Redis is now ready to exit, bye bye...

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