Thought it would also be useful to quote some advise I’ve given to someone onto this thread.
To find out how to stop daemon.log filling up ramlog, exceeding it’s 20M limit and falling back to writing logs directly to the Linux system partition until a fix is available you need to call Western Digital and ask them for advise.
This seems to be a Apple MAC related problem. I use only Microsoft Windows OSes on my network and as such I don’t need the netatalk protocol and services so I’ve stopped them on my MyBook Live and, unfortunatly, I am not MAC expert.
Maybe there is something service on your MAC that you can stop that has got something to do with CNID (By the way, what is CNID and what does it do?) which should cure the MyBook Live logging these repeated errors within daemon.log.
I’ve been made aware that Western Digital is working towards the MBL’s Linux OS managing it’s log files a lot better than it is now and the CNID issue has been known for quite a while. I suspect that Western Digital is not rushing to get the next firmware released and may be trying to get things as robust as possible.
As you’ll see, between a few others and myself there has been a lot going on within the discussion forum that’ll have the development team at W.D. scratching their heads for a while.
If youy can get your MAC to use the SMB protocol to access files on the MyBook Live and not use AppleTalk and/or AFP then you can turn off the AppleTalk service on your MyBook Live until a re-boot or power-cycle event to which each time you will need to disable the netatalk service.
To turn off AppleTalk services on the MyBook Live . . .
/etc/init.d/netatalk stop
To start the service on the MyBook Live . . .
/etc/init.d/netatalk start
. . . or reboot the MyBook Live.
It’s the only workaround I know at this present moment. You should get file services. Other services like TimeMachine may stop working because AppleTalk services on the MyBook Live would be turned off.
Hope that helps.
henlihai wrote:
hi Myron,
I have removed both daemon.logs and reboot.
[Solved] No more blinking green
[Solved] Able to access UI normally
/var/www/Admin/webapp/config$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md1 1.9G 979M 846M 54% /
tmpfs 50M 0 50M 0% /lib/init/rw
udev 10M 6.7M 3.4M 67% /dev
tmpfs 50M 0 50M 0% /dev/shm
tmpfs 50M 2.9M 48M 6% /tmp
ramlog-tmpfs 20M 20M 0 100% /var/log
/dev/sda4 2.8T 164G 2.6T 6% /DataVolume
Yet, I realised that my ramlog-tmpfs under “df -h” is full (100% used of the 20MB), as another new sets of daemon.logs are created (just smaller in size).
Am I suppose to micro-manage the daemon.logs until a fix comes in?
I noticed under /dev/md1 used to be 100% used too. After removing the 2 old daemon.logs. Now it is 54%.
how can I get the ramlog-tmpfs % down to normal levels?
Henry