Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 20.0.2, Meridian-2016.1.6
-
Fix Version/s: 20.1.0, Meridian-2016.1.7, Meridian-2017.1.0
-
Component/s: Logging, Remote Polling
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Sprint:Horizon - September 13th, Horizon - September 20th
Description
While trying latest Snapshots of Meridian 2017, I found that the remote poller logs are not properly generated. Here is an example:
[root@meridian2017 ~]# ls -als /opt/opennms/bin/ | grep poller
69136 -rw-r--r--. 1 root root 70793938 Sep 5 10:31 remote-poller.jar
4 -rwxr-xr-x. 1 root root 3312 Sep 8 08:28 remote-poller.sh
128 -rw-r--r--. 1 root root 67437 Sep 8 13:11 ${sys:poller.logfile}
8 -rw-r--r--. 1 root root 5460 Sep 1 14:15 ${sys:poller.logfile}-08-31-2017.gz
160 -rw-r--r--. 1 root root 161929 Sep 5 15:00 ${sys:poller.logfile}-09-01-2017.gz
140 -rw-r--r--. 1 root root 142625 Sep 8 13:08 ${sys:poller.logfile}-09-05-2017.gz
I found that the problem seems to be inside one of the JARs embedded inside the remote-poller.jar, that leads to features/remote-poller/src/main/resources/log4j2.xml.
