Home > munin error > munin error command /usr/sbin/smartctl

Munin Error Command /usr/sbin/smartctl

new enhancement hddtemp_smartctl problem with USB devices Reported by: dacer Owned by: nobody Priority: low Milestone: Component: design Version: 2.0.6 Severity: normal Keywords: Cc: Description Hi, I have some problems when reading USB Disk values with smartcl. These command (default) file for USB (not for internal) $sudo /usr/sbin/smartctl -A --nocheck=standby -d sat /dev/sdc smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.9-1-amd64] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net Device is in SLEEP mode, exit(2) But without --nocheck=standby works fine: $ sudo /usr/sbin/smartctl -A -d sat /dev/sdc smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.9-1-amd64] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 116 103 021 Pre-fail Always - 7191 4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3026 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 058 058 000 Old_age Always - 30961 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 139 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 104 193 Load_Cycle_Count 0x0032 056 056 000 Old_age Always - 432816 194 Temperature_Celsius 0x0022 095 086 000 Old_age Always - 52 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 I change some lines in hddtemp_smartctl plugin (I never write python before this time) foreach my $drive (@drives) { warn "[DEBUG] Processing $drive\n" if $DEBUG; my $fulldev = devic

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 /dev/hda. Auto configuration The plugin supports "autoconf", so when running munin-node-configure --suggest the plugin returns "yes" http://munin-monitoring.org/ticket/1365 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 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 http://munin-monitoring.org/wiki/PluginPortrait/smart_ 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 temperature) is also a normalized VALUE and does not really reflect the temperature of the disk (the RAW_VALUE). The behaviour of the plugin is not going to change regarding the returned value of the temperature. If you want to monitor the actual temperature of your disks, use a s

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 out http://articles.slicehost.com/2010/4/9/enabling-munin-node-plug-ins-on-debian 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 you by: munin error 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 needed to munin error command 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 Attachments: Message as HTML Hi gab

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 not found] apache_processes | no | [LWP::UserAgent not found] apache_volume | no | [LWP::UserAgent not found] courier_mta_mailqueue | no | [spooldir not found] courier_mta_mailstats | no | [could not find executable] courier_mta_mailvolume | no | [could not find executable] cupsys_pages | no | [could

 

Related content

munin error

Munin Error p The content of this page has been moved to the Munin Guide Troubleshooting This wiki page has therefore been set to Read only and later will be purged This page lists some general troubleshooting for Munin The examples show a munin-node agent running on replace with other IP adresses as Restart Munin Master you see fit Is the munin-node process running on the agent node Did munin graphs not updating you restart the munin-node process Does the munin-node agent allow your munin master to contact it Simple test telnet munin test plugin localhost Hint check the allow

munin error in node communication with

Munin Error In Node Communication With p at - - T Last modified at - - T closed defect fixed Socket read timeout confuses munin-update Reported by gombasg Owned by nobody Priority normal Milestone Munin Component master Version Severity normal Keywords Cc Description Hi Sometimes configuring fetching a plugin takes long and that seems to confuse munin-update Background querying LVM information can take long so I have set the timeout to seconds in munin-node conf That works since munin-node does not report any timeouts Both the client and master runs munin - from Debian Sid Sometimes I get these messages