For some reason recently syslog is getting quite clogged with....
collectd[4068]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
rrdcached plugin: rrdc_update (/var/lib/rrdcached/db/localhost/df-root/df_complex-used.rrd, [1421188065:7727468544.000000], 1) failed with status -1.Can anyone tell me what's going on here all of a sudden?
You don't have a data drive plugged in, I'm guessing?
Data drive plugged in? Squeeze/OMV is installed on an internal SATA drive. There's a USB drive plugged in that I use that in case debian doesn't wanna' boot, or if I need to flash firmware(s)/BIOS etc... Not sure what you're asking of me here?
I'll be able to tell from the output in your other thread.
bump.....
Try:
omv-mkconf collectd
service collectd restart
no change after those commands. the only way i can get those errors to stop is to comment out the df section in collectd.conf
ZitatAlles anzeigen
#LoadPlugin df
#<Plugin df>
# MountPoint "/"
# IgnoreSelected false
#</Plugin>
this of course breaks rrd collection for the disk space display in the web UI. i must do this after some upgrades which probably run those commands as well, otherwise my logs become quite big in a hurry.
What is the output of: cat /etc/collectd/collectd.conf
ZitatAlles anzeigen
root@dvrstorage:/etc/collectd# cat collectd.conf
Hostname "localhost"
FQDNLookup true
LoadPlugin syslog
<Plugin syslog>
LogLevel info
</Plugin>
LoadPlugin rrdcached
<Plugin rrdcached>
DaemonAddress "unix:/var/run/rrdcached.sock"
DataDir "/var/lib/rrdcached/db/"
CreateFiles true
CollectStatistics true
</Plugin>
LoadPlugin unixsock
<Plugin unixsock>
SocketFile "/var/run/collectd.socket"
SocketGroup "root"
SocketPerms "0660"
</Plugin>
LoadPlugin cpu
#LoadPlugin df
#<Plugin df>
# MountPoint "/"
# IgnoreSelected false
#</Plugin>
LoadPlugin interface
<Plugin interface>
Interface "eth0"
Interface "eth1"
IgnoreSelected false
</Plugin>
LoadPlugin load
LoadPlugin memory
Include "/etc/collectd/thresholds.conf"
You have at least one line in there like:
MountPoint "/media/ceb4e5a5-df2b-48db-9dab-570bb875f216"
I assume the output of: cat /etc/openmediavault/config.xml | awk '/<mntent>/,/<\/mntent>/' is still the same as the other thread?
Zitat
You have at least one line in there like:
? No. There's no lines in there like that.
ZitatAlles anzeigen
root@dvrstorage:/etc/collectd# cat collectd.conf
Hostname "localhost"
FQDNLookup true
LoadPlugin syslog
<Plugin syslog>
LogLevel info
</Plugin>
LoadPlugin rrdcached
<Plugin rrdcached>
DaemonAddress "unix:/var/run/rrdcached.sock"
DataDir "/var/lib/rrdcached/db/"
CreateFiles true
CollectStatistics true
</Plugin>
LoadPlugin unixsock
<Plugin unixsock>
SocketFile "/var/run/collectd.socket"
SocketGroup "root"
SocketPerms "0660"
</Plugin>
LoadPlugin cpu
#LoadPlugin df
#<Plugin df>
# MountPoint "/"
# IgnoreSelected false
#</Plugin>
LoadPlugin interface
<Plugin interface>
Interface "eth0"
Interface "eth1"
IgnoreSelected false
</Plugin>
LoadPlugin load
LoadPlugin memory
Include "/etc/collectd/thresholds.conf"
root@dvrstorage:/etc/collectd#
ZitatAlles anzeigen
root@dvrstorage:/etc/collectd# cat /etc/openmediavault/config.xml | awk '/<mntent>/,/<\/mntent>/'
<mntent>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
<fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
<dir>/xxx/yyy/zzz</dir>
<type>ext2|ext3|ext4|xfs|jfs|iso9660|udf</type>
<opts></opts>
<freq>0</freq>
<passno>0|1|2</passno>
</mntent>
root@dvrstorage:/etc/collectd#
You didn't mount your raid array in the omv web interface, did you? That is the only way filesystems (disk or array) get added to mntent which is where the collectd list is generated.
So if nothing is added/mounted, these errors are normal behavior?
It is normal behavior with no data data disks mounted via the OMV web interface (empty mntent section) due to a bug in Wheezy's df command. Volker worked on this quite a bit a few months back and couldn't come up with a workaround. It really didn't seem like that big of an issue because most people don't run a NAS without storage and you can't use the OS drive for storage. Even plugging a usb stick in and mounting it in the web interface would fix it. I realize you have storage but you need the mntent entry to add an entry to the collectd config to stop the error.
Zitat
It really didn't seem like that big of an issue because most people don't run a NAS without storage and you can't use the OS drive for storage.
I guess I am in the minority using OMV as a SAN rather than a NAS. I think my only other option instead of a USB stick, would be to ensure that the "df" section in collectd.conf stays commented out even after upgrades. Different strokes; different folks. Thanks for your help.
You could repartition the OS drive to include a additional, very small partition that you mount in the web interface.
Just out of curiosity, why are you using OMV? If you don't mount anything in the web interface, you can't create a shared folder. If you can't create a shared folder, you pretty much can't use any of the plugins.
The only plugins that I use are lvm2 and iscsitarget. Probably the only one's that don't need it.
I use the RAID section in the UI to create a md device. I use the LVM section to create a VG/LV on the md. I then use the iSCSi section to serve out the LV over iSCSI. I do not use any of the NAS capabilities at all.
Couldn't you make an additional very small lv (1gb) and create/mount a filesystem on it? That is all you would have to do.
There's another idea too. I suppose I'll give that a shot. Thanks again.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!