Bug #8528
closedIPsec does not start at boot
0%
Description
Hi,
I setup reboot pfSense everynight to avoid memory leak. I understand that this is not really good idea, but before I disable it I found that IPSec service does not start 1-3 times per 5 reboots. After system boot I see that service is marked as stopped with vmwareguestd and vmware-kmod. When I press start button is started without any problem all the time. I tried to grep by 'ipsec|fail|error' in /var/log but found only:
dmesg.boot:module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80682e80, 0) error 1
dmesg.boot:module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff8065c1c0, 0) error 1
dmesg.boot:module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff8065c270, 0) error 1
dmesg.boot:module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff8065c320, 0) error 1
dmesg.boot:module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff80682d20, 0) error 1
dmesg.boot:module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80682dd0, 0) error 1
Could you please help with this issue? At least how to collect more data. I increase the log size, but it still not catch any issues.
BR,
Dmitriy
Updated by Jim Pingle almost 7 years ago
- Category deleted (
IPsec) - Status changed from New to Not a Bug
- Priority changed from High to Normal
- Affected Version deleted (
2.4.3)
You appear to have something unrelated happening on your system causing some startup tasks to fail. There is no confirmed bug here. Please post to the forum, pfSense subreddit, or mailing list for assistance in diagnosing your underlying issue.
Updated by Dmitriy Stark almost 7 years ago
Hi,
But there is no any logs in system. 2 times ipsec starts ok, and third fail. How to at least track it? There is only node_exporter in startup list from external programs.
Updated by Jim Pingle almost 7 years ago
That is a topic for a discussion platform (forum, reddit, list) not a bug tracking system.