Forum Discussion
Interesting... So we know restjavad is at least scheduled and not throwing errors.
By default the logging for that process is sparse and won't log much about success operations. It does log information about Apply at "FINE" logging level. It can be adjusted by editing the file /etc/restjavad.log.conf. The logging configuration line should be added at the end so it’s not overridden by a later setting.
1- SSH to the BIG-IP.
2- Edit /etc/restjavad.log.conf
3- Add the line at the end, for FINE level verbosity:
com.f5.rest.tmos.bigip.access.openid.OIDCDiscoverTaskCollectionWorker.level=FINE
4- bigstart restart restjavad.
These logging levels are available:
- SEVERE (highest value)
- WARNING
- INFO (this is default)
- CONFIG
- FINE
- FINER
- FINEST (lowest value)
There are also some other evidence that Apply has been performed:
1- /var/log/apm will have information about updating the "snapshot" version, which is APMd's data-structure of the access policy and its config objects.
2- /var/log/audit will have traces of a command "generation-action increment" and should have some detailed info.
I'm not sure we can get this all resolved with forum posts, but it's good information to understand the issue and symptoms more fully.