Project

General

Profile

Actions
Copy link

Bug #8914

closed

Gateway switch events cause a huge amount of log spew

Added by → luckman212 over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Logging
Target version:
2.4.4-p1
Start date:
09/18/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
Affected Architecture:

Description

When a gateway failure/defgw switch event occurs, there seem to be some code paths that get iterated over dozens of times in a very short span of time. This floods system.log making it hard to read. Specifically, these 2 phrases are repeated over and over:

Gateways status could not be determined, considering all as up/active
Keep current gateway, its already part of the group members

This is part of an effort to try to make the logs readable again, while still allowing verbose logging if needed via a new hidden config option from the developer shell:

$config['system']['gw-debug'] = true;
write_config("Enable Developer Spew");
exec
exit
Actions
Copy link

Also available in: Atom PDF