Bug ID 945389: Audit Log Syslog Servers do not create successfully

Last Modified: Aug 09, 2021

Bug Tracker

Affected Product:  See more info
BIG-IQ 1UX Monitor - Logs(all modules)

Known Affected Versions:

Fixed In:

Opened: Sep 15, 2020
Severity: 3-Major


Audit Log Syslog Server entries do not create successfully and consequently do not send syslog events to remote syslog server, despite the entry appearing to have been created without issue. /var/log/restjavad.X.log will log Null Pointer Exceptions whenever an Audit Log Syslog Server entry is created like: [ERROR][06 May 2021 10:59:23 PDT][ RestServer] java.lang.NullPointerException at com.f5.rest.workers.configmgmtbase.auditLogger.syslogServer.SyslogClient.tryAndEstablishConnection(SyslogClient.java:263) at com.f5.rest.workers.configmgmtbase.auditLogger.syslogServer.SyslogClient.access$100(SyslogClient.java:39) at com.f5.rest.workers.configmgmtbase.auditLogger.syslogServer.SyslogClient$4.run(SyslogClient.java:283) at com.f5.rest.common.ScheduleTaskManager$2$1.run(ScheduleTaskManager.java:116) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)


Audit Log Syslog Server objects appear to be created successfully however they will not transmit syslog entries to remote server due to Null Point Exception during their creation.


Audit Log Syslog Server entries are created via GUI.



Fix Information

Audit Log Syslog Server objects can now be successfully created without raising a Null Pointer Exception. A subsequent issue now occurs which is documented in ID1017125 with a workaround of issuing "bigstart restart restjavad" once after the issue occurs.

Behavior Change