GUI console messages + system dataset

[Norleif]

On a fresh install, clicking the messages in the GUI footer pops up a window containing what seems to be most of the syslog.
When importing/creating the first volume, the "System dataset pool" is automatically set to this pool with "Syslog" checked.
I also get this in the console popup:

Code:

Nov 11 00:16:15 Red notifier: ls: /var/db/system: No such file or directory
Nov 11 00:16:15 Red notifier: ls: /var/db/system: No such file or directory
Nov 11 00:16:15 Red notifier: ls: /var/db/system: No such file or directory
Nov 11 00:16:15 Red notifier: Stopping collectd.
Nov 11 00:16:17 Red notifier: Waiting for PIDS: 2624.
Nov 11 00:16:17 Red notifier: Starting collectd.
Nov 11 00:16:30 Red GEOM_ELI: Device ada2p1.eli created.
Nov 11 00:16:30 Red GEOM_ELI: Encryption: AES-XTS 256
Nov 11 00:16:30 Red GEOM_ELI:  Crypto: hardware
Nov 11 00:16:30 Red notifier: geli: Cannot access ada2p1 (error=1).
Nov 11 00:16:30 Red notifier: ls: /var/db/system: No such file or directory
Nov 11 00:16:30 Red notifier: ls: /var/db/system: No such file or directory
Nov 11 00:16:30 Red notifier: ls: /var/db/system: No such file or directory
Nov 11 00:16:30 Red notifier: Stopping collectd.
Nov 11 00:16:37 Red notifier: Waiting for PIDS: 3597.
Nov 11 00:16:37 Red notifier: Starting collectd.
Nov 11 00:16:39 Red notifier: kern.corefile: %N.core -> /var/db/system/cores/%N.core
Nov 11 00:16:43 Red syslog-ng[4373]: syslog-ng starting up; version='3.5.6'

Next time I reboot, the console log popup is stuck on "Loading..."

Disabling "Syslog" in System dataset" generates a lot of messages before leaving the following single line in the console log:

Code:

Nov 11 00:28:48 Red syslog-ng[3768]: syslog-ng starting up; version='3.5.6'

The GUI log works normally after this, but I think it kind of defeat the purpose of the "System dataset" not to have the "Syslog" on it...

Is this a known issue, or am I the only one struggling with this?

Btw.. I'm running 9.3-BETA 2014-11-08 00:21:30 GMT on real hardware:
Xeon E3-1225 V2 + 32GB ECC RAM on Asus P8C-WS
1x Seagate 320GB through onboard AHCI (System dataset pool)
8x WD RED 3TB through IBM M1015 (IT fw P16)
2x WD RED 3TB through onboard Intel AHCI

 

[jkh]

I don't see any bugs for this - please file one. It could be that the switch to syslog-ng was not entirely seamless in its interaction with the .system dataset.

 

[Norleif]

I'm leaning towards GUI problems, as the little box at the bottom of the screen is updating normally.
/var/db/system is a zfs mount on the selected "System Dataset pool" and looking into "/var/db/system/syslog-xxx/log/messages" everything is in working order.

 

[mjws00]

I was hitting stuck at Loading... yesterday as well. But couldn't produce the error consistently. I was creating/deleting datasets and pools, and testing detach/replace etc. Perhaps I was messing with the dataset holding .system a little too hard. I was trying to figure out if it was just a rendering glitch, but kind of makes sense that something wasn't responding with data as anticipated.