Forum Discussion
/var/log/ has only 0% free | Big-IP PEM
Hi all,
Unit: Big-IP Policy Enforcement Manager (PEM) Software: BIG-IP 13.1.1 Build 0.76.4 Engineering Hotfix Issue: /var/log/ has reached full capacity. We have started receiving Broadcast messages when connected via SSH, stating that Disk partition /var/log (slot 1) has only 0% free. As our regular F5 administrators are away I am unsure how to proceed.Broadcast message from root@hostname (Wed Jan 9 13:01:02 2019):
011d0004:3: Disk partition /var/log (slot 1) has only 0% free
Here is the disk usage from /var/log/ and the culprit looks to be wr_urldbd.out. As shown below it's at a staggering 34G. We have another identical unit at another site which has this file @ 8.4M.
[user@hostname:/S1-green-P::Active:Standalone] log ls -Slh | head -10
total 6.8G
-rw-r--r--. 1 root root 34G 2019-01-09 13:04 wr_urldbd.out
-rw-r--r--. 1 root root 4.7G 2019-01-09 13:01 wr_urldbd.out.1
-rw-------. 1 root root 2.1G 2018-10-27 21:45 zebos.log
-rw-r--r--. 1 root root 1.1M 2018-10-24 14:37 restjavad-gc.log.0
-rw-r--r--. 1 root root 978K 2018-10-27 21:45 restjavad.1.log
-rw-r--r--. 1 root root 688K 2019-01-09 12:53 restjavad-gc.log.0.current
-rw-------. 1 root root 680K 2019-01-09 03:26 hitless_upgrade.log
-rw-------. 1 root root 672K 2019-01-09 13:03 ltm
-rw-r--r--. 1 root root 496K 2019-01-09 12:48 restjavad.0.log
Tailing wr_urldbd.out yields -
`[user@hostname:/S1-green-P::Active:Standalone] log tail wr_urldbd.out
nGetRtuUpdateInfo: failed sConnectSocket to service.brightcloud.com failed connect to 570354308 on 8888, err = -1
nGetRtuUpdateInfo: failed sConnectSocket to service.brightcloud.com failed connect to 570354308 on 8888, err = -1
nGetRtuUpdateInfo: failed sConnectSocket to service.brightcloud.com failed connect to 570354308 on 8888, err = -1
nGetRtuUpdateInfo: failed sConnectSocket to service.brightcloud.com failed connect to 570354308 on 8888, err = -1
nGetRtuUpdateInfo: failed sConnectSocket to service.brightcloud.com failed connect to 570354308 on 8888, err = -1
As this unit is relatively new to our network, I suspect that configuration is yet to be finalised which is why it's being blocked - and I'm not too worried about that. What'd I'd like to know is the purpose of this file and if it would be safe to delete it? Thanks in advance. First time poster so please let me know if any additional information is required.
- Samir_Jha_52506Noctilucent
Open Support case for more information.
- John_Huttley_23Historic F5 Account
Agreed, you shouldn't delete it, but you could download to your workstation then
cp /dev/null /var/log/wr_urldbd.out
For relief.
If its a new implementation, please check the obvious. Is the device able to lookup DNS and access that fqdn through your firewall??
Then get on the phone to us. --John
- Damon_380891Nimbostratus
Hi guys,
Thanks for the comments, I am in the process of logging a support case.
Regards, Damon
- SurgeonRet. Employee
This file is logging activity of webroot database: connection and updates. It can be safely deleted and will be recreated with next database restart. However I would make it zero rather the delete it: > /var/log/wr_urldbd.out
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com