Reply
Honored Contributor
Myron
Posts: 1,486
Registered: ‎05-01-2011

REST_API.LOG seems to be growing rapidly.

Now I seem to have discovered an issue . . .

 

The /var/log/rest_api.log file seems to rapidly grow.

Dec 31 13:01:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:01:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:01:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:01:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:01:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:01:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:01:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:01:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:01:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:01:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:01:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:01:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:01:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:01:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:01:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:01:55 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:01:55 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:01:55 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:01:55 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:02:05 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:02:05 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:02:05 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:02:05 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:02:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:02:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:02:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:02:15 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:02:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:02:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:02:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:02:25 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:02:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:02:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:02:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:02:35 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)
Dec 31 13:02:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT Storage_usage GET SUCCESS
Dec 31 13:02:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT System_state GET SUCCESS
Dec 31 13:02:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT Firmware_info GET SUCCESS
Dec 31 13:02:45 localhost REST_API[6655]: 172.16.0.1 OUTPUT Alerts GET PARAMS: (queryParams=Array)

The solution is to disable WD's QuickView application.  Seems every times QuickView queries the status of the MyBook Live, the procedure gets relentlessly logged within /var/log/rest_api.log.  The issue is not as cronic as the the other issue with CNID.

 

If you leave your computer logged in 24/7, which I don't, then you could end up with ramlog getting filled up, ramlog getting disabled and then all logs getting written directly to the MBL's disc which will prevent the MBL from going to sleep/standby (aka. blue LED status.)

Honored Contributor
ThePizzaMatrix
Posts: 4,010
Registered: ‎10-13-2010

Re: REST_API.LOG seems to be growing rapidly.

Tested and confirmed, thanks Myron!

You are reading a ghost long gone.
Honored Contributor
Myron
Posts: 1,486
Registered: ‎05-01-2011
0

Re: REST_API.LOG seems to be growing rapidly.

This will give an idea how quickly this log file can grow.  I've not been affected because I don't have my computer on 24/7 with WD Quickview running.  I guess this is something that may not brick the NAS or cause a malfunction of the Dashboard UI, but has the potential to push the log file usage above 20Mb, ehich disabled ramlog and then the MBL will not go to sleep.  W.D's log rotation routines will still work as normal.

 

I wonder if I've discovered a reason why some people are having issues with their MBL not going into standby?

Forums | Ideas | News and Announcements | Register | Sign in | Help | Forum Guidelines
Copyright © 2001 - 2014 Western Digital Technologies, Inc. All rights reserved. | Trademarks | Privacy | Community Terms of Service | Site Terms of Use | Copyright | Contact WD