RN214 Failing to Update Antivirus

---

Astra03 wrote:

 

I have been unable to find any of the three log files that you mentioned - I tried using the Linux "find" command, but got back "No such file or directory" for each of them. There is a folder /var/log/clamav , but "ls" does not return any contents.

 

---

The log is accessed via ssh with journalctl.  While I do sometimes do that, it generally works out better if you have a keyword to search for.  Then you can pipe it through grep.  For instance

# journalctl -r --no-pager | grep -i error 

will give you all journal entries that have the word "error" in them.

Adding -k to the journalctl command will limit the output to kernel entries.  Journalctl does have filters built into it (an alternative to grep), but mostly I just use grep.  https://manpages.debian.org/stretch/systemd/journalctl.1.en.html

I was suggesting that you download the log zip file from the NAS web ui - the files I suggested are in the zip.  

---

Astra03 wrote:

 

So, I think I know how to copy a folder to the /data partition to reduce space, (cp "copy" or mv "move" if I am trying to reduce space usage?), but what I do not know how to do is use ln to create symbolic links to the new folder locations. Can you help me with that please?

 

---

There is a lot of help for most linux commands out there if you just google the command name with "linux" (perhaps also adding "man").

Here are two:

• https://linux.die.net/man/1/ln
• https://www.howtoforge.com/linux-ln-command/

It's really best to look through the man pages and examples, and try them on your linux desktop.  Trying them directly on the NAS does have some risk - you can easily end up with an unbootable NAS, or with data loss.

Also, you want to ssh into the NAS as root (using the NAS admin password).

That said: what you want in this case is a "soft link".

ReadyNAS apps are supposed to put their data on the data volume.  If you use the default data volume name ("data"), then the app data is in a subfolder of /data/.apps 

Note that .apps is a hidden folder - so you won't see it with ls /data but you will see it with ls -a /data.

I suggest creating a relocation folder in .apps (perhaps /data/.apps/relocate) and then copy the folders into relocate.  Alternatively you can create a relocation folder for each app (e.g., /data/.apps/LMS, etc). 

But let's say the folder you want to relocate is /var/myfolder and that you've already moved it to /data/.apps/relocate/myfolder.  

Then you create the soft link with

ln -s /data/.apps/relocate/myfolder /var/myfolder  

Remember that you put the target first (which I find non-intuitive).  And it's important to create a soft link (-s) and not the default hard link.

You might want to try this sequence to get the hang of it:

# mkdir /data/.apps/relocate
# mkdir /data/.apps/relocate/myfolder
# mkdir /data/.apps/relocate/myfolder/temp
# ln -s /data/.apps/relocate/myfolder

Now if you look at /var you'll see the soft link

root@RN202:/var# ls -al /var/myfolder
lrwxrwxrwx 1 root root 29 Jul 26 06:26 /var/myfolder -> /data/.apps/relocate/myfolder

And if you navigate into /var/myfolder, you'll see that you appear to be in /var/myfolder but you are seeing the files and folders in the target /data/.apps/relocate/myfolder.  In this example, the temp folder you created above.

# root@RN202:/var# cd myfolder
# root@RN202:/var/myfolder# ls -al
total 0
drwxr-xr-x 1 root root  8 Jul 26 06:26 .
drwxr-xr-x 1 root root 16 Jul 26 06:24 ..
drwxr-xr-x 1 root root  0 Jul 26 06:26 temp
root@RN202:/var/myfolder#

Note that /var/myfolder is deleted as if it is an ordinary file - not a folder.  That's because a soft link is a file.

# root@RN202:/var# rm myfolder

To delete the relocated target you'd need to use -r (or rmdir if it is empty).

# rm -r /data/.apps/relocate/myfolder