2.5 with many tunnels - Apply Changes fails
-
It was stuck on this screen for about 4 minutes.
Please let me know if you need anything else.
-
That
g_vfs_doneline implies it's having problems communicating with its storage.You may have some other problem in your hypervisor/guest config which is causing it to perform slower than it should, leading to your timerout.
-
Only post 2.5 upgrade and only for IpSec tunnels?
-
Yes, it's common for hypervisors to need adjustments when moving from one FreeBSD version to another, depending on your settings.
It may not be related to IPsec at all, just that it's something that is time consuming and provokes the general slowness.
-
Thank you.
What is your recommendation to correct this?
-
That depends on your hypervisor and guest settings, I don't have any general recommendations there other than to check what your hypervisor recommends for use with FreeBSD 12.2 (or at least 12.x).
-
This is an AWS instance with your approved image and size. This is a c5n.large.
-
Then I suggest you redeploy it instead of upgrading in-place to see if the problem happens that way.
-
When I load the XML file into a new instance, your software produces the same timeout issue and the XML never loads.
Any other ideas?
-
Also, after a few attempts it loaded. It continues to hang in the same spot during boot up, and actually does not boot up at all. I don't think that its hardware or disk related.
Please let me know how you would like to proceed.
-
Is there any way you can try at least loading the IPsec portion of that configuration in a non-AWS system?
It's difficult to tell if it's related to IPsec or if there is a general problem with AWS.
The only other potentially-related report I've seen is a report of a kernel panic on AWS with someone that has even more IPsec tunnels than you, but as far as I'm aware they were not experiencing any slowness or boot delays.
