Ntopng Service is not running on pfsense 2.3.2-RELEASE ?



  • I was using pfsense 2.2 and install ntopng package but after it install successfully its service do not start in services. I've have made several tries after uninstalling and reinstalling it again and also by restarting server but ntopng server remain stopped in the services.
    In system logs I've found the following messages related to it.

    Dec 27 00:04:45 ntopng [Redis.cpp:79] ERROR: ntopng requires redis server to be up and running
    Dec 27 00:04:45 ntopng [Redis.cpp:80] ERROR: Please start it and try again or use -r
    Dec 27 00:04:45 ntopng [Redis.cpp:81] ERROR: to specify a redis server other than the default

    I have upgraded the pfsense version from 2.2 to 2.3 but still facing the same issue.

    PLease help if anyone have a solution regarding this issue.



  • Here is the full veiw when ntopng package is installed

    Installing pfSense-pkg-ntopng…
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up-to-date.
    Updating pfSense repository catalogue...
    pfSense repository is up-to-date.
    All repositories are up-to-date.
    The following 22 package(s) will be affected (of 0 checked):

    New packages to be INSTALLED:
    pfSense-pkg-ntopng: 0.8.5 [pfSense]
    webfonts: 0.30_11 [pfSense]
    mkfontdir: 1.0.7 [pfSense]
    mkfontscale: 1.1.2 [pfSense]
    xproto: 7.0.28 [pfSense]
    freetype2: 2.6.3 [pfSense]
    libfontenc: 1.1.3 [pfSense]
    fontconfig: 2.11.1_2,1 [pfSense]
    ntopng: 2.2.2016.05.28 [pfSense]
    ndpi: 1.8 [pfSense]
    json-c: 0.12_2 [pfSense]
    mysql56-client: 5.6.30 [pfSense]
    luajit: 2.0.4_1 [pfSense]
    GeoIP: 1.6.9 [pfSense]
    graphviz: 2.38.0_12 [pfSense]
    libgd: 2.1.0_7,1 [pfSense]
    png: 1.6.21 [pfSense]
    jpeg-turbo: 1.4.2 [pfSense]
    tiff: 4.0.6_2 [pfSense]
    jbigkit: 2.1_1 [pfSense]
    redis: 3.0.7 [pfSense]
    gdbm: 1.12 [pfSense]

    Number of packages to be installed: 22

    The process will require 137 MiB more space.
    12 MiB to be downloaded.
    Fetching pfSense-pkg-ntopng-0.8.5.txz: . done
    Fetching webfonts-0.30_11.txz: …....... done
    Fetching mkfontdir-1.0.7.txz: . done
    Fetching mkfontscale-1.1.2.txz: .. done
    Fetching xproto-7.0.28.txz: ...... done
    Fetching freetype2-2.6.3.txz: .......... done
    Fetching libfontenc-1.1.3.txz: .. done
    Fetching fontconfig-2.11.1_2,1.txz: .......... done
    Fetching ntopng-2.2.2016.05.28.txz: .......... done
    Fetching ndpi-1.8.txz: .......... done
    Fetching json-c-0.12_2.txz: .... done
    Fetching mysql56-client-5.6.30.txz: .......... done
    Fetching luajit-2.0.4_1.txz: .......... done
    Fetching GeoIP-1.6.9.txz: .......... done
    Fetching graphviz-2.38.0_12.txz: .......... done
    Fetching libgd-2.1.0_7,1.txz: .......... done
    Fetching png-1.6.21.txz: .......... done
    Fetching jpeg-turbo-1.4.2.txz: .......... done
    Fetching tiff-4.0.6_2.txz: .......... done
    Fetching jbigkit-2.1_1.txz: ...... done
    Fetching redis-3.0.7.txz: .......... done
    Fetching gdbm-1.12.txz: .......... done
    Checking integrity... done (0 conflicting)
    [1/22] Installing xproto-7.0.28…
    [1/22] Extracting xproto-7.0.28: …....... done
    [2/22] Installing freetype2-2.6.3…
    [2/22] Extracting freetype2-2.6.3: …....... done
    [3/22] Installing libfontenc-1.1.3…
    [3/22] Extracting libfontenc-1.1.3: …... done
    [4/22] Installing jpeg-turbo-1.4.2…
    [4/22] Extracting jpeg-turbo-1.4.2: …....... done
    [5/22] Installing jbigkit-2.1_1…
    [5/22] Extracting jbigkit-2.1_1: …....... done
    [6/22] Installing mkfontscale-1.1.2…
    [6/22] Extracting mkfontscale-1.1.2: .. done
    [7/22] Installing json-c-0.12_2…
    [7/22] Extracting json-c-0.12_2: …....... done
    [8/22] Installing png-1.6.21…
    [8/22] Extracting png-1.6.21: …....... done
    [9/22] Installing tiff-4.0.6_2…
    [9/22] Extracting tiff-4.0.6_2: …....... done
    [10/22] Installing mkfontdir-1.0.7…
    [10/22] Extracting mkfontdir-1.0.7: .. done
    [11/22] Installing fontconfig-2.11.1_2,1…
    [11/22] Extracting fontconfig-2.11.1_2,1: …....... done
    Running fc-cache to build fontconfig cache...
    /usr/local/share/fonts: skipping, no such directory
    /usr/local/lib/X11/fonts: skipping, no such directory
    /root/.local/share/fonts: skipping, no such directory
    /root/.fonts: skipping, no such directory
    /var/db/fontconfig: cleaning cache directory
    /root/.cache/fontconfig: not cleaning non-existent cache directory
    /root/.fontconfig: not cleaning non-existent cache directory
    fc-cache: succeeded
    [12/22] Installing ndpi-1.8…
    [12/22] Extracting ndpi-1.8: …....... done
    [13/22] Installing mysql56-client-5.6.30…
    [13/22] Extracting mysql56-client-5.6.30: …....... done
    [14/22] Installing luajit-2.0.4_1…
    [14/22] Extracting luajit-2.0.4_1: …....... done
    [15/22] Installing libgd-2.1.0_7,1…
    [15/22] Extracting libgd-2.1.0_7,1: …....... done
    [16/22] Installing webfonts-0.30_11…
    [16/22] Extracting webfonts-0.30_11: …....... done
    [17/22] Installing ntopng-2.2.2016.05.28…
    ===> Creating groups.
    Creating group 'ntopng' with gid '288'.
    ===> Creating users
    Creating user 'ntopng' with uid '288'.
    [17/22] Extracting ntopng-2.2.2016.05.28: …....... done
    [18/22] Installing GeoIP-1.6.9…
    [18/22] Extracting GeoIP-1.6.9: …....... done
    [19/22] Installing graphviz-2.38.0_12…
    [19/22] Extracting graphviz-2.38.0_12: …....... done
    [20/22] Installing redis-3.0.7…
    ===> Creating groups.
    Using existing group 'redis'.
    ===> Creating users
    Using existing user 'redis'.
    [20/22] Extracting redis-3.0.7: …...... done
    [21/22] Installing gdbm-1.12…
    [21/22] Extracting gdbm-1.12: …....... done
    [22/22] Installing pfSense-pkg-ntopng-0.8.5…
    [22/22] Extracting pfSense-pkg-ntopng-0.8.5: …...... done
    Saving updated package information...
    done.
    Loading package configuration... done.
    Configuring package components...
    Loading package instructions...
    Custom commands...
    Executing custom_php_install_command()...done.
    Executing custom_php_resync_config_command()...



  • same here. i tried re.installing but didn't work :(



  • 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.


  • Banned

    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.  ::))



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


  • Banned

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



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



  • 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.


  • Banned

    @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


  • Rebel Alliance Developer Netgate

    @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.


  • Banned

    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.



  • 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...