Munin Error Command /usr/sbin/smartctl

Sign in Pricing Blog Support Search GitHub This repository Watch 103 Star 861 Fork 279 munin-monitoring/munin Code Issues 102 Pull requests 21 Projects 0 Wiki Pulse Graphs New issue hddtemp_smartctl fails on a drive in standby #690 Closed covex opened this Issue Mar 11, 2016 · 4 comments Projects None yet Labels [affects] devel [component] plugins [type] bug Milestone No milestone Assignees No one assigned 3 participants covex commented Mar 11, 2016 This what the plugin resports: UNKNOWNs: sdb is unknown: Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdb on drive sdb failed: 512. The plugin needs to have read permission on all monitored devices., sdd is unknown: Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdd on drive sdd failed: 512. The plugin needs to have read permission on all monitored devices.. OKs: sda is 32.00, sdc is 33.00. Both sbb and sdd are in standby. The plugin correctly uses "--nocheck=standby" however smartctl returns non zero exit code upon this on drive that is in standby.The plugin threats this as error: my $output = $cmd; if ($? ne 0) { ... and prints this "incorrect" message. ssm added [type] bug [component] plugins [affects] devel labels Mar 14, 2016 dipohl commented May 22, 2016 Both sbb and sdd are in standby. The plugin correctly uses "--nocheck=standby" however smartctl returns non zero exit code upon this on drive that is in standby.The plugin threats this as error I could reproduce it: [root@niva smartmontools]# munin-run hddtemp_smartctl sda.value 31 sdf.value U sdf.extinfo Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdf on drive sdf failed: 512. The plugin needs to have read permission on all monitored devices. [ERROR] Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdf on drive sdf failed: 512. The plugin n

is a wildcard plugin to monitor all SMART attributes of a specified hard drive. Languagepython Known working OSesLinux2.4 Linux 2.6 SunOS *BSD written byNicolas STRANSKY Configuration You need to install python in order to run the plugin. You also need a valid ​smartmontools installation. This plugin needs the following minimal configuration in plugin-conf.d/munin-node [smart_*] user root group disk To monitor a S.M.A.R.T device, link smart_ to the smart_ plugin file. E.g. ln -s /usr/share/munin/plugins/smart_ /etc/munin/plugins/smart_hda ...will monitor https://github.com/munin-monitoring/munin/issues/690 /dev/hda. Auto configuration The plugin supports "autoconf", so when running munin-node-configure --suggest the plugin returns "yes" if all required programs are found. On Linux2.4 Linux 2.6 SunOS *BSD, the following command should list the autoprobed disks where the SMART informations are readable. Be aware that this http://munin-monitoring.org/wiki/PluginPortrait/smart_ command will actually try to get SMART informations from all the detected drives on the system. When running munin-node-configure --suggest or munin-node-configure --shell, the plugin will suggest which disk drives to monitor. Additional parameters smartpath - Specify path to smartctl program (Default: /usr/sbin/smartctl) smartargs - Override '-a' argument passed to smartctl with '-A -i'+smartargs Parameters can be specified on a per-drive basis, eg: [smart_hda] user root env.smartargs -H -c -l error -l selftest -l selective -d ata env.smartpath /usr/local/sbin/smartctl Use this to monitor drives pluged in a 3Ware RAID card: [smart_twa0-1] user root env.smartargs -H -l error -d 3ware,1 [smart_twa0-2] user root env.smartargs -H -l error -d 3ware,2 # And so on... SATA drives: [smart_sda] env.smartargs -d ata -a Remarks The smart_ plugin displays normalized VALUES for all SMART attributes. Subsequently, the value #194 (the

instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our https://sourceforge.net/p/munin/mailman/message/31646217/ ad policies X You seem to have CSS turned off. Please don't fill http://articles.slicehost.com/2010/4/9/enabling-munin-node-plug-ins-on-debian out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Munin Mailing Lists Munin Brought to munin error you by: bjornruberg, janl, snide Summary Files Reviews Support Mailing Lists News Code munin-users munin-users-de munin-users-jp Re: [munin-users] SELinux blocks plugin hddtemp_smartctl (but strangely not smart_ ) Re: [munin-users] SELinux blocks plugin hddtemp_smartctl (but strangely not smart_ ) From: Gabriele Pohl - 2013-11-16 18:50:29 Attachments: signature.asc On 11/14/2013 12:24 AM, Gabriele Pohl wrote: > On 11/13/2013 05:50 PM, Nicolai Langfeldt wrote: >> > A write is munin error command needed to send the command that >> > returns the temperature. > the commands send to the plugins have set similar flags: > > # hddtemp_smartctl > /usr/sbin/smartctl -A --nocheck=standby -a -d cciss,0 /dev/cciss/c0d0 > # smart_ > /usr/sbin/smartctl -a -n standby -A -i /dev/sda > > But they are accessing different types of disks. > > My assumption is that access to the SCSI disk requires > write access because here using a different command set. > I will ask the smartmontools developers and report back here. My assumption was right. Reason for the difference between the two are different open modes for the two devices. READ access for the ATA disk http://sourceforge.net/p/smartmontools/code/HEAD/tree/trunk/smartmontools/os_linux.cpp#l224 WRITE acess for the CCISS RAID http://sourceforge.net/p/smartmontools/code/HEAD/tree/trunk/smartmontools/os_linux.cpp#l1204 So SELinux policy of munin-node needs additional rules for plugins labeled with munin_disk_plugin_t to grant WRITE access to the block device. @drjohnson1: Will you please add these: ---------------------------------- module my_munin-node 1.0; require { type munin_disk_plugin_t; type fixed_disk_device_t; class blk_file write; } #============= munin_disk_plugin_t ============== allow munin_disk_plugin_t fixed_disk_device_t:blk_file write; ---------------------------------- Thanks and all the best ~ Gabriele Thread view Re: [munin-users] SELinux blocks plugin hddtemp_smartctl (but strangely not smart_ ) From: Nicolai Langfeldt - 2013-11-13 16:50:36 Attachment

Fedora Arch SERVERS Apache Nginx Email FRAMEWORKS Ruby on Rails Capistrano Django SLICE ADMIN SliceManager Slice Admin Backup Security OTHER MySQL PostgreSQL Email Subversion SSH Windows Enabling munin node plug-ins on Debian Munin uses plug-ins to determine what data is gathered and reported. It includes several plug-ins for the types of data most people would be interested in, but not all of those plug-ins are enabled on a fresh installation. What are plug-ins? When a munin node gathers data about a slice so it can be graphed, the node reads instructions from files called "plug-ins" to determine what information to collect. Several plug-ins are installed with munin but not all of them are used by default. Fortunately a munin node installation includes a command that lets you see what plug-ins are active and can help you decide which others to enable. The munin-node-configure command The "munin-node-configure" command can list the status of installed munin plug-ins, suggest which to enable, and provide a shell script that will automate enabling the appropriate plug-ins. Using this command isn't the only way to perform these tasks, but it's convenient and easy to use. Easy is good. Listing installed plug-ins To see which plug-ins are installed on a munin node, log into it and run the "munin-node-configure" command by itself: $ sudo /usr/sbin/munin-node-configure Plugin | Used | Extra information ------ | ---- | ----------------- acpi | no | apache_accesses | no | apache_processes | no | apache_volume | no | apt | no | apt_all | no | courier_mta_mailqueue | no | courier_mta_mailstats | no | courier_mta_mailvolume | no | cps_ | no | cpu | yes | cupsys_pages | no | df | yes | df_abs | no | df_inode | yes | entropy | yes | exim_mailqueue | yes | exim_mailstats | yes | forks | yes | fw_conntrack | no | ... The output is longer than that, but that's generally what you'll see — the plug-ins with "yes" next to them are enabled, the ones with "no" next to them are installed but disabled. Deciding what to enable To help you decide whether you want to enable any other munin plug-ins, run munin-node-configure with the "--suggest" option: $ sudo /usr/sbin/munin-node-configure --suggest Plugin | Used | Suggestions ------ | ---- | ----------- acpi | no | [ACPI program not found] apache_accesses | no | [LWP::UserAgent n