@2chemlud:
Hi!
No, I had an eye on the RAM on the Dashboard, nothing went out of control. And the problem is apparently at the end of the procedure (snort is there and running, only not included in the GUI), while reinstalling the rules sets for the interfaces.
It worked fine during the update from 2.1.5 to 2.2 and from 2.2 to 2.2.1 on all three boxes. But this time…
Kind regards
I don't mean necessarily RAM as in free system memory, but rather free space on the RAM disks used for the various system partitions. These can be filled during the package download and unpacking process. You would really have no way of seeing them run out unless you were monitoring them in a shell session while the package installation happened in the GUI. After Snort starts up during the installation process, it returns control to pfSense where the package manager code of pfSense completes the installation. This last step, done by pfSense itself and not the Snort package, is where the menu entry is created under SERVICES. That step frequently dies for some reason on Nano installs. I think it is because of RAM disk exhaustion. Some other users have been able to get successful installs by manually increasing their RAM disk partition sizes. For example, increasing /tmp to 300 MB (or at least 100 MB) in size. That is the directory partition where the package downloading, unpacking, and other temp file creation happens. By default it is somewhat small on Nano installs.
Bill