Error Description Table Integer Length Too Long 5 Bytes

You have to register before you can post. / Vous devez vous inscrire avant de pouvoir nagios check_snmp_storage créer un sujet. Announcement Collapse No announcement yet. ERROR when check_snmp_storage example getting CPU percentage use values : ProcessorLoad Table : INTEGER length t Collapse X Collapse Posts check_snmp_storage.pl example Latest Activity Search Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only nagios interface monitoring Filtered by: Clear All new posts Previous Next s3ri4l Junior Member Oreonistes Join Date: Jul 2010 Posts: 8 #1 ERROR when getting CPU percentage use values : ProcessorLoad Table : INTEGER length t 13th July 2010, 20:43 Hello everybody, I'm having trouble with Centreon check_centreon_snmp_cpu command when using the web interface it displays

Check_snmp_storage.pl Exclude

the following message "ERROR when getting CPU percentage use values : ProcessorLoad Table : INTEGER length too long (5 bytes)." already on the command line manual it the same mistake. ja he brings with snmpwalk mibs normally. see: [root@monitor libexec]# snmpwalk -On -v 2c -c pr0j3ctSnMP 10.11.133.192 | more .1.3.6.1.2.1.1.1.0 = STRING: Linux projint-bd01.project.intra.net 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64 .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.8072.3.2.10 .1.3.6.1.2.1.1.3.0 = Timeticks: (10490) 0:01:44.90 .1.3.6.1.2.1.1.4.0 = STRING: monitor@project.intra.net .1.3.6.1.2.1.1.5.0 = STRING: projint-bd01.project.intra.net .1.3.6.1.2.1.1.6.0 = STRING: projectnms .1.3.6.1.2.1.1.8.0 = Timeticks: (2) 0:00:00.02 Can help me? Thz. Tags: None dimka Junior Member Oreonistes Join Date: Jun 2010 Posts: 6 #2 26th July 2010, 11:19 Hej - I am having the same problem both on disks and RAM checks - any solutions ? Comment Post Cancel surcouf Senior Member Gourou Join Date: Dec 2004 Posts: 1128 #3 26th July 2010, 20:58 Originally posted by s3ri4l View Post Hello everybody, I'm

Script : check_snmp_storage.pl Last update : Jun 09 2007 Description : This scripts checks by snmp (V1 and v3) disks, memory, swap, everthing in hrStorage table. Storages selection can be done : - by

Nagios Check Interface

perl regexp on description or index (-m) - and (optional) by storage type nagios snmp disk check (-q) : Other, Ram, VirtualMemory, FixedDisk, RemovableDisk, FloppyDisk, CompactDisk, RamDisk, FlashMemory, NetworkDisk One or multiple storages can be selected. It is unable to write file /tmp/tmp_nagios_int also possible to sum all selected storages (-s) Warning and critical levels can be checked based on : - Percent of disk used - Percent of disk left - MB left - MB used Output https://forum.centreon.com/forum/centreon-use/centreon-project/10586-error-when-getting-cpu-percentage-use-values-processorload-table-integer-length-t options (-S): -S can have 3 options : [,,] : Make the output shorter : 0 : only print the global result except the disk in warning or critical 1 : Don't print all info for every disk : (optional) if = 1, put the OK/WARN/CRIT at the beginning : take the first caracters or last if n<0 With the following disks : /home : http://nagios.manubulon.com/snmp_storage.html 51% used and / : 90% used Option used Warning Output 99% /home: 51%used(1012MB/1969MB) /: 90%used(5781MB/6390MB) (<99%) : OK 90% /home: 51%used(1012MB/1969MB) /: 90%used(5781MB/6390MB) (>90%) : WARNING -S0 90% All selected storages (<99%) : OK -S0 99% /: 90%used(5781MB/6390MB) (>90%) : WARNING -S1 90% /home: 51% /: 90% (<99%) : OK -S1 99% /home: 51% /: 90%used(5781MB/6390MB) (>90%) : WARNING -S0,1 90% OK : (<99%) All selected storages -S0,1 90% WARNING : (>90%) /: 90%used(5781MB/6390MB) -S1,,2 99% /h: 51% /: 90% (<99%) : OK -S1,,-2 99% me: 51% /: 90% (<99%) : OK -S0,1,-2 30% WARNING : (>30%) me: 51%used(1012MB/1969MB) /: 90%used(5781MB/6390MB) Performance output (-f option) The performance will remove any weird caracters ( `~!$%^&*'"<>|?,(= ) ) from the drive name. Msg size option (-o option) In case you get a "ERROR: running table : Message size exceeded maxMsgSize" error, you may need to adjust the maxMsgSize, i.e. the maximum size of snmp message with the -o option. Try a value with the -o AND the -v option : the script will output the actual value so you can add some octets to it with the -o option. SNMP Login See snmp info page --- Vérifie par snmp v1 ou v3 l'occupation des disques, ma

Accueil Aide Identifiez-vous Inscrivez-vous Forums monitoring-fr.org » Support Eco-Système Nagios » Addons » Check_snmp_storage http://forums.monitoring-fr.org/index.php?topic=142.0 (ERROR: Description/Type table: Request) « précédent suivant » Imprimer Pages: [1] En bas Auteur Sujet: Check_snmp_storage (ERROR: Description/Type table: Request) (Lu 7522 fois) ne0ca62 BoyScout http://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes Froggy Messages: 51 Karma: 0 Check_snmp_storage (ERROR: Description/Type table: Request) « le: 05 Mai, 2009, 16:11:38 pm » Bonjour,Je travaille sous Redhat 5 EL et nagios check avec Nagios 3.0.6.Je rencontre des difficultés avec le plugin check_snmp_storage pour vérifier l'espace disque sur les machines linux.Pour certains serveurs Linux ça fonctionne :Code: [Sélectionner]./check_snmp_storage.pl -H 127.0.0.1 -C public -m "^/$" -w 80 -c 90
/: 48%used(9553MB/19840MB) (<80%) : OKCode: [Sélectionner]./check_snmp_storage.pl -H IP_SERVEUR -C public -m /dba/ -w 70 -c 80 error description table -r -f
/dba/arch: 17%used(13490MB/80635MB) (<70%) : OK | '/dba/'=13490MB;56444;64508;0;80635Mais pour d'autres serveurs Linux ça ne marche pas et j'ai l'erreur suivante :Code: [Sélectionner]./check_snmp_storage.pl -H IP_SERVEUR -C public -m /dba/arch -w 70 -c 80 -r -f
ERROR: Description/Type table : Requested table is empty or does not exist.Voici les modifications que j'ai fait dans mon fichier snmpd.conf :Code: [Sélectionner]# sec.name source community
com2sec notConfigUser default publicCode: [Sélectionner]view all included .1
view systemview included .1.3.6.1.2.1.1
view systemview included .1.3.6.1.2.1.25.1.1
view systemview included .1.3.6.1.2.1.2.2
view systemview included .1.3.6.1.4.1.2021
view systemview included .1.3.6.1.2.1.25.2.3
Code: [Sélectionner]# group context sec.model sec.level prefix read write notif
# access notConfigGroup "" any noauth exact systemview none none
access notConfigGroup "" any no

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up #1071 - Specified key was too long; max key length is 767 bytes up vote 194 down vote favorite 43 When I executed the following command: ALTER TABLE `mytable` ADD UNIQUE ( `column1` , `column2` ); I got this error message: #1071 - Specified key was too long; max key length is 767 bytes Information about column1 and column2: column1 varchar(20) utf8_general_ci column2 varchar(500) utf8_general_ci I think varchar(20) only requires 21 bytes while varchar(500) only requires 501 bytes. So the total bytes are 522, less than 767. So why did I get the error message? #1071 - Specified key was too long; max key length is 767 bytes mysql byte varchar mysql-error-1071 share|improve this question edited May 23 '11 at 21:32 OMG Ponies 198k36356415 asked Nov 29 '09 at 3:18 Steven 5,2743480112 Because its not 520 bytes, but rather, 2080 bytes, which far exceeds 767 bytes, you could do column1 varchar(20) and column2 varchar(170). if you want a character/byte equiv, use latin1 –Rahly Dec 18 '15 at 0:21 add a comment| 17 Answers 17 active oldest votes up vote 137 down vote accepted 767 bytes is the stated prefix limitation for InnoDB tables - its 1,000 bytes long for MyISAM tables. According to the response to this issue, you can get the key to apply by specifying a subset of the column rather than the entire amount. IE: ALTER TABLE `mytable` ADD UNIQUE ( column1(15), column2(200) ); Tweak as you need to get the key to apply, but I wonder if it would be worth it to review your data model regarding this entity to see if there's improvements that would allow you to implement the intended business rules without hitting the MySQL limitation. share|improve this answer edited Oct 15 '14 at 20:20 The Alchemist 2,6901017 answered Nov 29 '09 at 3:52 OMG Ponies 198k36356415 To apply by specifying a subset of the column rather than the entire amount. A good solution. –Steven Nov 29 '09 at 4:14 @OMGPonies: Do you happen to know, if DB2/MSSQL/Oracle have the same limitation on index size? For example HSQL does