2017-05-30 12:55 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001735openmediavaultBugpublic2017-05-09 22:31
Reporterhyamamoto 
Assigned Tovotdev 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version 
Target VersionErasmus (3.x)Fixed in VersionErasmus (3.x) 
Summary0001735: smartd refuses to monitor devices due to exceeding maximum line length
DescriptionUsing the latest version of OMV (3.0.74) and extending the smart test scheduling for a HDD device results in the "/etc/smartd.conf" configuration file to be causing a startup-failure with smartd. smartd refuses to process configuration files with lines longer then 256 characters. See also this ancient Debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398054).

The by OMV auto-generated "/etc/smartd.conf" file does not use line escapes to shorten or wrap the configuration lines. This would be one solution to this issue. Another solution would be to change the smartd scheduling to occur less frequently, however a sub-optimal solution.

Requesting the possibility to fix this 'bug' by escaping lines in the auto-generated "/etc/smartd.conf".

Example problem line in "/etc/smartd.conf":
/dev/disk/by-id/ata-WDC_WD4003FZEX-00Z4SA0_WD-WCC5D0002873 -a -o on -S on -T permissive -W 0,0,0 -I 194 -I 231 -n never,q -s (S/../04/./06|S/../18/./06|S/../11/./06|S/../25/./06|L/../07/./07|L/../21/./07) -m smartd@domain.tld -M exec /usr/share/smartmontools/smartd-runner

Output systemd (systemctl status smartd):
Error: line 8 of file /etc/smartd.conf is more than MAXLINELEN=256 characters.
Configuration file /etc/smartd.conf has fatal syntax errors.
Monitoring 0 ATA and 0 SCSI devices
TagsNo tags attached.
Product build
Attached Files

-Relationships
+Relationships

-Notes

~0004735

votdev (administrator)

Fixed in openmediavault 3.0.75, see https://github.com/openmediavault/openmediavault/commit/9d4c3818e0b65a4e6d5892c64db4e0b465ea5bd3.
+Notes

-Issue History
Date Modified Username Field Change
2017-05-09 10:14 hyamamoto New Issue
2017-05-09 10:14 hyamamoto Status new => assigned
2017-05-09 10:14 hyamamoto Assigned To => votdev
2017-05-09 10:16 votdev Target Version => Erasmus (3.x)
2017-05-09 22:31 votdev Status assigned => resolved
2017-05-09 22:31 votdev Resolution open => fixed
2017-05-09 22:31 votdev Fixed in Version => Erasmus (3.x)
2017-05-09 22:31 votdev Note Added: 0004735
+Issue History