Last Modified: Jun 19, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2
Opened: Mar 12, 2024 Severity: 3-Major
The find command in rest_logintegrity script fails and returns "No such file or directory" when no matching file is found if there are no newly rotated restnoded, restjavad log files whenever the rest_logintegrity script runs as part of the cron job.
Overload of emails with message similar to: find: '/var/log/restnoded/restnoded[1-9]*.log': No such file or directory
When there are no files which matches the below patterns in the script: "/var/log/restjavad.[1-9]*.log", "/var/log/restnoded/restnoded[1-9]*.log".
Creating the files as below mitigates the error touch /var/log/restnoded/restnoded1.log touch /var/log/restjavad.1.log
None