Freenas 8.3.0 - A lot less info in system messages log

[kamil6x]

After running of this script Freenas 8.3.0 displays a lot less messages in the messages log file and in the console window through the web interface. The point of using this script was to store the log file data after a crash; but now the log contains almost no information.
eg. the only entries in the messages log now are (there is no record of the boot sequence at all as previously in the messages file):

Feb 11 01:06:58 shuttle syslogd: kernel boot file is /boot/kernel/kernel
Feb 11 01:14:20 shuttle kernel: ugen4.3: at usbus4
Feb 11 01:14:20 shuttle kernel: ukbd0: <Logitech USB Receiver, class 0/0, rev 1.10/38.10, addr 3> on usbus4
Feb 11 01:14:20 shuttle kernel: kbd2 at ukbd0
Feb 11 01:14:20 shuttle kernel: ums0: <Logitech USB Receiver, class 0/0, rev 1.10/38.10, addr 3> on usbus4
Feb 11 01:14:20 shuttle kernel: ums0: 10 buttons and [XYZT] coordinates ID=2
Feb 11 01:14:23 shuttle kernel: ugen4.3: at usbus4 (disconnected)
Feb 11 01:14:23 shuttle kernel: ukbd0: at uhub4, port 2, addr 3 (disconnected)
Feb 11 01:14:23 shuttle kernel: ums0: at uhub4, port 2, addr 3 (disconnected)
Feb 11 01:14:25 shuttle kernel: ugen4.3: at usbus4
Feb 11 01:14:25 shuttle kernel: ukbd0: <Logitech USB Receiver, class 0/0, rev 1.10/38.10, addr 3> on usbus4
Feb 11 01:14:25 shuttle kernel: kbd2 at ukbd0
Feb 11 01:14:25 shuttle kernel: ums0: <Logitech USB Receiver, class 0/0, rev 1.10/38.10, addr 3> on usbus4
Feb 11 01:14:25 shuttle kernel: ums0: 10 buttons and [XYZT] coordinates ID=2
Feb 11 01:14:26 shuttle kernel: ugen4.3: at usbus4 (disconnected)
Feb 11 01:14:26 shuttle kernel: ukbd0: at uhub4, port 2, addr 3 (disconnected)
Feb 11 01:14:26 shuttle kernel: ums0: at uhub4, port 2, addr 3 (disconnected)
Feb 11 01:15:01 shuttle syslogd: exiting on signal 15
Feb 11 01:15:13 shuttle syslogd: kernel boot file is /boot/kernel/kernel
Feb 11 01:15:23 shuttle kernel: ugen4.3: at usbus4
Feb 11 01:15:23 shuttle kernel: ukbd0: <Logitech USB Receiver, class 0/0, rev 1.10/38.10, addr 3> on usbus4
Feb 11 01:15:23 shuttle kernel: kbd2 at ukbd0
Feb 11 01:15:23 shuttle kernel: ums0: <Logitech USB Receiver, class 0/0, rev 1.10/38.10, addr 3> on usbus4
Feb 11 01:15:23 shuttle kernel: ums0: 10 buttons and [XYZT] coordinates ID=2
Feb 11 01:15:26 shuttle kernel: ugen4.3: at usbus4 (disconnected)
Feb 11 01:15:26 shuttle kernel: ukbd0: at uhub4, port 2, addr 3 (disconnected)
Feb 11 01:15:26 shuttle kernel: ums0: at uhub4, port 2, addr 3 (disconnected)
Feb 11 06:00:00 shuttle shutdown: power-down by root:
Feb 11 06:00:03 shuttle afpd[3173]: AFP Server shutting down on SIGTERM
Feb 11 06:00:04 shuttle rsyncd[2953]: rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(560) [Receiver=3.0.9]
Feb 11 06:00:04 shuttle upsmon[2756]: upsmon parent: read
Feb 11 06:00:05 shuttle upsd[2750]: mainloop: Interrupted system call
Feb 11 06:00:06 shuttle ntpd[2683]: ntpd exiting on signal 15
Feb 11 06:00:20 shuttle syslogd: exiting on signal 15

[Jesse Griffin]

I assume that you restarted the system? Are the messages persistent after restarting the system?

Note that I have not tested this on a 8.3 system yet, so any additional information would be helpful.

Messages in the log will most likely not show up until your persistent filesystem is mounted, which is likely to be toward the end of the boot process. If you need to see boot message while the system is running you can always run the dmesg command. I'll add a note to the README concerning this.

Are you trying to troubleshoot a crash that you have seen? I notice in the log you posted that the system was powered down by root, so it doesn't look like there is any crash there.

[alphakamp]

I had and issue with syslog.conf, however the logical link worked fine. I had to manually edit /etc/syslog.conf to include my desired log path. IE messages's path was just /messages, I changed to /mnt/tank/logdir/messages