Steve Yates wrote on Tue, Jan 12 2016 at 1:25 am:
> 6) I started on pfSense 2.2.5 and upgraded both routers to 2.2.6 since it
> said it
> fixed some sync issues. On at least two occasions, with 2.2.6, I start
> getting
> "unread notice" alerts for sync errors, and can't connect to the web GUI on
> router2. Connecting to its console and choosing "Restart webConfigurator"
> (option 11) fixes both issues, as if the web browser crashed.
It happened just now and the General log on router2 shows:
Jan 15 18:37:23 kernel: pid 17318 (lighttpd), uid 0: exited on signal
11 (core dumped)
...however that usually doesn't get logged, and I just see my restart
("lighttpd[33922]: (log.c.194) server started").
At this point, if I open the Suricata Sync tab, click Save, and within
a minute or so router2's web GUI crashes again. Interestingly, the last few
times if I restart webConfigurator I still can't connect but if I restart
PHP-FPM I instantly get a 500 - Internal Server Error page. Does that imply a
PHP problem?
I am thinking it can't handle having most of the rules in
emerging-web_specific_apps.rules disabled...too many things to update? A
memory limit somewhere? (PHP's is 256 MB)
Does anyone know if "Enable all rules in the current Category" will
reset the rule state back to default, or mark them all enabled (which won't
help any, if my theory is correct)? Is there a way to set "Disable all rules
in the current Category" back to the default but keep any changes? " Remove
Enable/Disable changes in the current Category" sounds like it will undo all my
changes. :-/
--
Steve Yates
ITS, Inc.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
