More Detailed logging please

rogard wrote:
It would be really useful to access the nfs and smb logs, for trying to troubleshoot permission issues.

You can access the smb logs -- smbd.log and nmbd.log. Use the Download All Logs link from the Status/Log page. NFS logs can be seen in the kernel.log.

yoh-dah wrote:
rogard wrote: It would be really useful to access the nfs and smb logs, for trying to troubleshoot permission issues. You can access the smb logs -- smbd.log and nmbd.log. Use the Download All Logs link from the Status/Log page. NFS logs can be seen in the kernel.log.

Please add syslog and/or syslog-ng and audit functionality. All businesses with any regulations like HIPAA, SOX, GBL or any other require audit loging. Without syslog NAS devices will not be allowed to be used offices that must comply with regulations.

Is syslog and audit functionality on the future feature list?

Thanks,

Troy

tas wrote:

yoh-dah wrote: rogard wrote: It would be really useful to access the nfs and smb logs, for trying to troubleshoot permission issues. You can access the smb logs -- smbd.log and nmbd.log. Use the Download All Logs link from the Status/Log page. NFS logs can be seen in the kernel.log. Please add syslog and/or syslog-ng and audit functionality. All businesses with any regulations like HIPAA, SOX, GBL or any other require audit loging. Without syslog NAS devices will not be allowed to be used offices that must comply with regulations. Is syslog and audit functionality on the future feature list? Thanks, Troy

We can add syslog support in a future update. 8)

When is SysLog going to be available. Need it NOW PLEASE!!

I'll 3rd the syslog request.

It's interesting that this request for a logical, well reasoned addition to the software was made in early/mid 2006 and here it is mid 2008 and I'm still requesting the same thing. :shock:

Having never really played around with syslog before, as well as not knowing exactly what you're trying do (i.e. use the ReadyNAS to be the main syslog server or have the logs forwarded to a syslog server).

I did a quick search of the repositories and found this:

nas-01-4C-1B:~# apt-cache show sysklogd
Package: sysklogd
Priority: important
Section: base
Installed-Size: 204
Maintainer: Martin Schulze <joey@debian.org>
Architecture: sparc
Version: 1.4.1-17
Replaces: syslogd
Provides: syslogd, system-log-daemon
Depends: libc6 (>= 2.3.2.ds1-21), klogd | linux-kernel-log-daemon
Conflicts: syslogd
Filename: pool/main/s/sysklogd/sysklogd_1.4.1-17_sparc.deb
Size: 56666
MD5sum: 363e58af58a7def5c6fe4b683c917e0b
SHA1: 936b5135b714e9326915184fada0d60575ca89bc
SHA256: 8e9e7a65667a9a2b2d8adea617109e9fbfd0e75ba4dbe1bb536f8007c3c4e889
Description: System Logging Daemon
 This package implements the system log daemon, which is an enhanced
 version of the standard Berkeley utility program. It is responsible
 for providing logging of messages received from programs and facilities
 on the local host as well as from remote hosts.

Package: sysklogd
Status: install ok installed
Priority: important
Section: base
Installed-Size: 200
Maintainer: Martin Schulze <joey@debian.org>
Version: 1.4.1-10
Replaces: syslogd
Provides: syslogd, system-log-daemon
Depends: libc6 (>= 2.2.4-4), klogd | linux-kernel-log-daemon
Conflicts: syslogd
Conffiles:
 /etc/syslog.conf 3882195aa34cd97b8a57120bc8b47f3b
 /etc/init.d/sysklogd cfe9ee910fb41db683f298e7accd74fe
 /etc/cron.daily/sysklogd 05c1e431b98caa3f1277ad74fcf9185d
 /etc/cron.weekly/sysklogd 62066ad440b58a954e68132610b3c347
Description: System Logging Daemon
 This package implements the system log daemon, which is an enhanced
 version of the standard Berkeley utility program. It is responsible
 for providing logging of messages received from programs and facilities
 on the local host as well as from remote hosts.

So, it appears as though sysklogd is installed, but I don't know if this will do what you're looking for. There's also an uninstalled package called 'syslog-ng' in the repos:

nas-01-4C-1B:~# apt-cache show syslog-ng
Package: syslog-ng
Priority: extra
Section: admin
Installed-Size: 564
Maintainer: SZALAY Attila <sasa@debian.org>
Architecture: sparc
Version: 1.6.5-2.2
Provides: system-log-daemon, linux-kernel-log-daemon
Depends: libc6 (>= 2.3.2.ds1-21), util-linux (>= 2.12-10)
Recommends: logrotate
Conflicts: system-log-daemon, sysklogd, linux-kernel-log-daemon
Filename: pool/main/s/syslog-ng/syslog-ng_1.6.5-2.2_sparc.deb
Size: 216720
MD5sum: 8a94f75ae25bff8799ec754a1bc01ea7
SHA1: ff038208d5128748081be793b346434d40233af1
SHA256: 72b752db4a0cc8d642c136cd2e8283946986c752944197bc1edf1812fffb751a
Description: Next generation logging daemon
 Syslog-ng tries to fill the gaps original syslogd's were lacking:
   * powerful configurability
   * filtering based on message content
   * portability
   * better network forwarding

Again, I don't know if any of this helps you, but perhaps it might be useful.

-Dave

I would like to add my voice to those requesting syslog support, but I would very much like for the Readynas to be able to both be a syslog server AND a client. The server capability has obvious utility as already described, while the client, or sending, capability is necessary in certain regulated environments, as already mentioned by another poster.

The requests in this thread date back several years by now, so I'm wondering why these capabilities, which are already supported in the underlying Readynas OS and could be fairly easily exposed via Frontview, have been left to languish?

I'm not expert here but I have managed to get syslog running thanks to the previous posts. I followed these steps:
1. Download APT Add-on from http://www.readynas.com/?page_id=617
2. Enable ssh root access
3. Run apt-get update.
4. Run apt-get install syslog-ng
5. Edit /etc/default/syslog-ng to remove hash before CONSOLE_LOG_LEVEL=0 and KERNEL_RINGBUF_SIZE
6. Run /etc/init.d/syslog-ng start
7. Edit /etc/syslog-ng/syslog-ng.conf removing hash before udp(); and changing use_dns(no); to use_dns(yes);
8. run /etc/init.d/syslog-ng restart

That's it it should be working now. To test

1. Run tail -f /var/log/syslog
2. On a second machine run nc -w0 -u 192.168.7.254 514 <<< "testing again from my home machine" replacing the ip address for you nas device's

Good luck. Remember if your not sure then I wouldn't recommend it. Also please keep in mind that NETGEAR may deny support if you’ve enabled root access

Hi everyone

It's been a long time that this thread was opened. I just wanted to add another (very easy) way to enable logging to a remote host on the ReadyNAS NVX Pioneer Edition. The point is: syslog is already there!

As always: Use this mini howto and the links on your own risk!!!

Just follow these steps to enable remote logging:

1. Install EnableRootSSH Addon from netgear site: http://www.readynas.com/?p=4203
2. Stop syslogd

/etc/init.d/syslogd stop

3. Edit /etc/default/syslogd as follows to enable remote logging:
Replace

SYSLOGD=""

with

SYSLOGD="-r -m 0"

4. Edit /etc/syslog.conf to send all logs to vsyslog syslog collector (FDQN of remote host)

 *.*                             @yourhost.example.com

5. Start syslogd

/etc/init.d/syslogd start

For more info of how to configure syslog: see http://linux.die.net/man/8/sysklogd and http://linux.die.net/man/5/sysklogd