Dimension not receiving logs after reboot
Dimension was running slow so I rebooted the system. After the reboot my firewall cluster (M370) is listed in Dimension but logging shows as 'No'. This Dimension instance has been rebooted before without issue.
Dimension is sending warning messages:
No heartbeat detected from Log Collector since 2021-10......
We are under current maintenance
Under Status:
First log server Instance
Primary Server: 192.168.xx.xx
Primary server error: Network unavailable
Status: Not Connected
Active: None
Global Flags: (0x0000)
In Monitor the following are logged:
2021-10-20 08:13:43 Member2 Allow 192.168.xx.xx 192.168.xx.xx wg-logging/tcp 49129 4115 Firebox 1-Data Allowed 52 64 (Any From Firebox-00) proc_id="firewall" rc="100" msg_id="3000-0148" tcp_info="offset 8 S 3520457221 win 4210" Traffic
2021-10-20 08:14:08 Member2 Allow 192.168.xx.xx 192.168.xx.xx wg-logging/tcp 38804 4115 Firebox 1-Data Allowed 52 64 (Any From Firebox-00) proc_id="firewall" rc="100" msg_id="3000-0148" tcp_info="offset 8 S 3542376549 win 4210" Traffic
Steps Taken:
Rebooted Dimension 2nd time
Rebooted both Firewalls
Removed and added the Dimension server under Setup\Logging
Dimension 2.1.1 U1
Comments
Could be that Dimension is messed up.
Open a support incident to get help from a WG rep. They can often fix Dimension issues.
Issue was fixed after updating Dimension to a new version. Apparently the logging service was messed up, but the update corrected it.
I did open a case but was not getting responses so I thought I would try here. Finally did after 12 days and multiple calls.