Just for the archives, setting up totally new VMs seems to have fixed it.
Looking at the difference between the old and new VMs, the only change
that caught my eye was that the old VMs were set to dynamically allocate
memory, where as the new ones have a fixed memory size.
Thanks,
Andrew Kester
e a panic or similar. The log files just stop
at that time, there are no entries that indicate issues.
I'm at a loss for what troubleshooting I should try short of a complete
re-install. Any help is greatly appreciated.
Thanks,
Andrew Kester
The Storehouse
https://sthse.co
On 12/01/2017 07:
/ service errors on applications running on the
network during the failures, I'm happy to send along whatever would be
helpful, I'm just not sure where to start looking :/
--
Thanks,
Andrew Kester
The Storehouse
https://sthse.co
___
pfSense mailing
Actually, it looks like Node B was indeed in maintenance mode. Setting
it back to normal seems to have resolved the problem.
(That always seems to happen: send mail to a mailing list and it's
something silly on my end)
---
Thanks!
Andrew Kester
The Storehouse
https://sthse.co
On 11/3/17
information or clarification, I'm not sure
the best way to illustrate / communicate my problem.
---
Thanks,
Andrew Kester
The Storehouse
https://sthse.co
On 11/1/17 3:30 PM, Andrew Kester wrote:
Hi List,
I'm having an issue with CARP preempt. I have two pfSense machines
running 2.4.1-RELEASE
output taken from the master firewall
during a failure is attached.
Any help is greatly appreciated!
---
Thanks,
Andrew Kester
The Storehouse
https://sthse.co
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=209b<RXCSUM,TXCSUM
