Comments
-
Bruce, the issue with Logserver application not connecting with its bultin PostgreSQL database was that the server had another PostgreSQL running instance for Veeam Backup & Replication that was using same TCP 5432 port, once respective service was stopped and Logserver was reinstalled, communication with database went up.
-
I see, the thing is, something on this given computer is malfunctioning regarding Logserver, the WSM and Logserver installs, but Logserver and bultin PostgreSQL doesn't connect, i don't know if it's third-party AV (ESET) - (i have tried disabling AV and reinstalling and adding WatchGuard folders as scan exceptions) or…
-
Bruce, i appreciate your reply, thank you. Even 'thou WSM Log Server is no longer supported from V12.9 and beyond, it doesn't the feature it doesn't work. The feature is still referenced in WatchGuard documentation.…
-
What about using External PostgreSQL DB? Logserver is unable to communicate with builtin DB, so i tried with External One, but it doesn't communicate with PostgreSQL DB neither, it gives messages likes PostgreSQL authentication method 10 not supported or PostgreSQL authentication method 8 not supported - depending on…
-
Hi James, i appreciate your reply. Cluster status seems fine to me. If issue arises again, i'll check this same status report again. Cluster Snapshot ------ Cluster Info ------ cluster is Enabled mode is Active/Passive ha1_if_num=eth3 ha2_if_num=eth4 mgmt_if_num=eth1 cluster_id=5 lb_algorithm=Least-Connections…
-
From the last event, on Feb, 25th 3pm - (firewalls went down at 3:18pm) until Feb, 26th 1pm, we have 34914 records with pattern '"UserMac" parameter' - firewalls were rejoined at Feb 26th 12:06pm. We have these annoying logs until 12:59:58pm - i'll check if we have some of these currently right now and i'll update this…
-
Thank you @Robert_Vilhelmsen