Minio Service does not start from UI

During the remote support session, we were able to get the unit update from U7 to U8.

On failover, S3 was not running.

Packet filtering seemed to be enabled so services were all showing active but no traffic (data) was being passed. We were able to ping throughout the process.

S3 service would not start. This was also the case when they were running 12.0-U7.

I am including debugs from before the update (jan 31) and after the update (Feb 8th).

Also including the databse file for the unit in question.

M50-HA.

data points gathered

pfctl -sr (passes through things being blocked by packet filtering? )

pfctl -d

workgroup = MANINVESTMENTS

idmap config *: range = 90000001-100000000

idmap config maninvestments: unix_primary_group = Yes

idmap config maninvestments: unix_nss_info = Yes

idmap config maninvestments: schema_mode = rfc2307

idmap config maninvestments: range = 20-90000000

idmap config maninvestments: backend = ad

idmap config * : backend = tdb

directory name cache size = 0

dos filemode = Yes

[provider]

ea support = No

level2 oplocks = No

oplocks = No

path = /mnt/tank/provider

read only = No

strict locking = Yes

vfs objects = streams_xattr shadow_copy_zfs ixnas aio_fbsd

nfs4:chown = true

root@dloninalps01-c2[~]# id minio

uid=473(minio) gid=473(minio) groups=473(minio)

Failover logs seemed to have stopped after "importing tank"

Starting the S3 service in the UI seemed to have "undid" packet filtering issue and looked to have increased the python3.9 output from 1000M to 3800M

LLDP service is running

SMB is running and is configured for the same dataset as an NFS export (CVE message alert is displaying in the UI)