Snmp error generror a general failure occured

ITM Agent Insights: Debugging problems of an SNMP Agent you created with Agent Builder

Body

This blog will help you with your SNMP agent that you built with Agent Builder when it is not being able to retrieve data and, in the TEP GUI, you see the NO_INSTANCES_RETURNED error code.  Here is how you can debug this problem.

The first thing you should do is enable the trace level in the agent log. 

     For all new instances or productcode[_instance name].config
    -Edit the line that begins with KBB_RAS1= to set the following trace:  KBB_RAS1=ERROR (UNIT:snmp ALL)

Once the traces are enable, recreate the problem.  In the log file you will find some messages — generated by the snmpqueryclass module — showing the problem.

For example, you might find messages like the following:

     (4CD40703.0198-9:snmpqueryclass.cpp,1250,»handle_snmp_response_async») Error values: index=1, status=5                                         
     (4CD40703.0199-9:snmpqueryclass.cpp,106,»match_oid_prefix») Active RAS1 Classes: EVERYT EVERYE EVERYU                                           
     (4CD40703.019A-9:snmpqueryclass.cpp,106,»match_oid_prefix») Entry       
     (4CD40703.019B-9:snmpqueryclass.cpp,154,»match_oid_prefix») Error status 5 != SNMP_ERROR_noError                      

As you can see from the messages above, the root cause of the problem is the error code 5.  The status 5 error indicates that the SNMP agent on the remote system replied to our request with a «general error».  Once you get a clear idea of the error code that the ITM agent received from the SNMP agent, you will need to run the snmpgetnext and snmpwalk commands for the problematic OID.  In this case, if you run the snmpwalk command, then you will receive all the proper information but, at the end of the output, you might see an error like the following one:

     Error in packet.                                               
     Reason: (genError) A general failure occurred                   
     Failed object: SNMPv2-SMI::enterprises.x.x.x

This error message will reflect the error code 5 in the agent trace log.  It means that the problem is not related with the ITM agent but with the SNMP agent that provided the problematic outcome.

Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM Agent Insights: Introduction.

Tutorials Point

Subscribe and follow us for all the latest information directly on your social feeds:

image

[{«Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Product»:{«code»:»»,»label»:»»},»Component»:»»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»»,»label»:»»}}]

Источник

Log inSkip to main contentSkip to sidebar

Uploaded image for project: 'ZABBIX BUGS AND ISSUES'

  1. ZABBIX BUGS AND ISSUES
  2. ZBX-8062
    XMLWordPrintable

Details


    • Type:


      Incident report

    • Status:

      Closed


    • Priority:


      Major

    • Resolution:

      Incomplete


    • Affects Version/s:



      2.2.3

    • Fix Version/s:



      None

    Description

      After upgrade to 2.2.3 ( previous 2.2.1)
      In server log i receive :
      item [xxxxxxxxxxxx] became not supported: SNMP error: (genError) A general failure occured
      Items change state from supported to unsupported and so in circle.
      Before upgrade everything works well.

      Attachments

        Activity

          People

            Votes:
            0

            Vote for this issue

            Watchers:

            1

            Start watching this issue

            Dates

              Created:

              2014 Apr 10 14:38
              Updated:

              2017 May 30 18:14
              Resolved:

              2014 May 13 09:32

              Источник

              New issue

              Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

              By clicking “Sign up for GitHub”, you agree to our terms of service and
              privacy statement. We’ll occasionally send you account related emails.

              Already on GitHub?
              Sign in
              to your account


              Closed

              MikeW83 opened this issue

              Sep 11, 2019

              · 12 comments

              Comments

              @MikeW83

              Hey guys,

              another problem occured. When I try to check some services I receive following error:

              UNKNOWN: SNMP Table Request : (genError) A general failure occured

              On other machines there is no problem to check servies. The only difference is that this one server is not a domain member. All other checks for cpu, memory etc. is working perfect.
              This is the command for checking the services:
              /usr/lib/centreon/plugins/centreon_windows_snmp.pl --plugin=os::windows::snmp::plugin --mode=service --hostname=xxx.xxx.xxx.xxx --snmp-version='2c' --snmp-community='public' --service='Sap' --warning= --critical=1:1 --state='' --regexp

              Thanks, Michael

              @garnier-quentin

              It’s an issue of windows snmp agent. I could optimize the check. And maybe i could avoid that error.

              @MikeW83

              The mysterious thing is, that this only happens with one server. All other server don’t have such an issue.

              @joschi99

              This is a Microsoft bug. We have seen this issue on different OS version, from W2K12 until W2K19. We do not have any solution how to fix this issue.
              You need to monitor through WMI or using a client like nsclient++ as workaround.

              @MikeW83

              It’s the first server I’ve ever seen with this bug.

              @garnier-quentin

              I have done a patch. Could you test with last version ? Maybe it solved the genError

              @MikeW83

              There is no change… I have updated Centreon via
              yum upgrade -y
              to receive all updates. Or do I need to do update files manually? When I check the status of my plugins there are only versions from July 2019

              drwxr-xr-x. 2 root root 4096 Jul 8 11:37 .
              drwxr-xr-x. 3 root root 21 Feb 11 2019 ..
              -rwxrwxr-x 1 root root 255079 Jul 4 14:38 centreon_centreon_central.pl
              -rwxrwxr-x 1 root root 421093 Jul 4 14:38 centreon_centreon_database.pl
              -rwxrwxr-x 1 root root 238272 Jul 4 14:38 centreon_centreon_map.pl
              -rwxrwxr-x 1 root root 255079 Jul 4 14:38 centreon_centreon_poller.pl
              -rwxrwxr-x 1 root root 259061 Jul 4 14:38 centreon_cisco_meraki_snmp.pl
              -rwxrwxr-x 1 root root 566335 Jul 4 14:38 centreon_cisco_standard_snmp.pl
              -rwxrwxr-x 1 root root 456098 Jul 4 14:38 centreon_fortinet_fortigate.pl
              -rwxrwxr-x 1 root root 194341 Jul 4 14:38 centreon_hp_3par_7000.pl
              -rwxrwxr-x 1 root root 307395 Jul 4 14:38 centreon_hp_ilo_xmlapi.pl
              -rwxrwxr-x 1 root root 294294 Jul 4 14:38 centreon_hp_lefthand.pl
              -rwxrwxr-x 1 root root 351969 Jul 4 14:38 centreon_hp_procurve.pl
              -rwxrwxr-x 1 root root 362542 Jul 4 14:38 centreon_hp_proliant.pl
              -rwxrwxr-x 1 root root 284841 Jul 4 14:38 centreon_hp_storeonce_restapi.pl
              -rwxrwxr-x 1 root root 216267 Jul 4 14:38 centreon_hp_storeonce_ssh.pl
              -rwxrwxr-x 1 root root 515331 Jul 4 14:38 centreon_linux_snmp.pl
              -rwxrwxr-x 1 root root 297071 Jul 4 14:38 centreon_mssql.pl
              -rwxrwxr-x 1 root root 338374 Jul 4 14:38 centreon_mysql.pl
              -rwxrwxr-x 1 root root 280992 Jul 4 14:38 centreon_office365_teams_api.pl
              -rwxrwxr-x 1 root root 273496 Jul 4 14:38 centreon_printers_generic_snmp.pl
              -rwxrwxr-x 1 root root 206849 Jul 4 14:38 centreon_protocol_dns.pl
              -rwxrwxr-x 1 root root 229575 Jul 4 14:38 centreon_protocol_ftp.pl
              -rwxrwxr-x 1 root root 299268 Jul 4 14:38 centreon_protocol_http.pl
              -rwxrwxr-x 1 root root 215386 Jul 4 14:38 centreon_protocol_ldap.pl
              -rwxrwxr-x 1 root root 203408 Jul 4 14:38 centreon_protocol_telnet.pl
              -rwxrwxr-x 1 root root 387218 Jul 4 14:38 centreon_synology.pl
              -rwxrwxr-x 1 root root 261311 Jul 4 14:38 centreon_ups_standard_rfc1628_snmp.pl
              -rwxrwxr-x 1 root root 522681 Jul 4 14:38 centreon_vmware_connector_client.pl
              -rwxrwxr-x 1 root root 430066 Jul 4 14:38 centreon_windows_snmp.pl

              Best regards, Michael

              @garnier-quentin

              You need to use unstable repository.

              yum --enablerepo=centreon-unstable-noarch update centreon-plugin-Operatingsystems-Windows-Snmp

              @MikeW83

              Perfect, thank you. Now it’s working. I get correct information from the plugin.

              Best regards, Michael

              @garnier-quentin

              @buchetiglia

              Hello i’ve got the same problem on Windows Server 2019.

              I’ve update plugin with the unstable-repository (date 24/12/2019) but i allways have the same error :

              UNKNOWN: SNMP Table Request : (genError) A general failure occured

              There is someone wich can help me ?

              @garnier-quentin

              I have done my best. You should use nsclient.

              @buchetiglia

              ok thanks, il will going to try to use nsclient.

              Источник

              • Summary

              • Files

              • Reviews

              • Support

              • News

              • Mailing Lists

              • Bugs

              • Feature Requests

              • Patches

              • Official Patches

              • Htdocs

              • Code

              Menu
              ▾
              ▴

              net-snmp-users


              From: jack n <mailb…@gm…> — 2010-11-24 20:42:43

              		 
              Hi All,

I had placed my private MIBs under /usr/share/snmp/mibs and compiled them
using mib2c.

I got .c and .h files, added my code in the .c file and placed them under
/agent/mibgroup.

Now when I try to run snmpwalk and SNMPGET request they work succesfully,
but when I run SNMPSET for the same OID, it fails and returns an error.

*# snmpwalk -v 1 localhost -c public 1.3.6.1.8.1.1.2321.79.2.1.5.4*
*.1.3.6.1.8.1.1.2321.79.2.1.5.4.0 = INTEGER: 123

**# snmpget -v 1 localhost -c public 1.3.6.1.8.1.1.2321.79.2.1.5.4.0
.1.3.6.1.8.1.1.2321.79.2.1.5.4.0 = INTEGER: 123*

But when I run *snmpset* ,

*snmpset -v 1 -c public localhost .1.3.6.1.8.1.1.2321.79.2.1.5.4.0 i 12345*
*Error in packet *
**
*Reason:(genError) A general failure occured*


My snmpd.conf file contains the following entries:

#       sec.name  source        community
com2sec Anyone    127.0.0.1/32  public
# create some groups
#     group name  security model  security name
group Group       v1              Anyone
group Group       v2c             Anyone
#view  all   included   xx.xx.xx.xx.xx.xx.xx
view  wview included   .1.3.6.1.8.1.1.2321.79.2.1.5.4.0
master agentx
#agentxPerms 0660 0550 nobody snmp
agentxPerms 600
agentxSocket /tmp/agentx
agentxTimeout 60
agentxRetries 1

rwcommunity  public

Is there anything else that I need to do?
Am i missing something? Please let me know.

Thanks and Regard,
Jack.

              From: jack n <mailb…@gm…> — 2010-11-29 09:35:22

              		 
              Can someone help me with this?
Thanks in advance.

Regards,
Jack.

On Thu, Nov 25, 2010 at 2:12 AM, jack n <mailb...@gm...> wrote:

> Hi All,
>
> I had placed my private MIBs under /usr/share/snmp/mibs and compiled them
> using mib2c.
>
> I got .c and .h files, added my code in the .c file and placed them under
> /agent/mibgroup.
>
> Now when I try to run snmpwalk and SNMPGET request they work succesfully,
> but when I run SNMPSET for the same OID, it fails and returns an error.
>
> *# snmpwalk -v 1 localhost -c public 1.3.6.1.8.1.1.2321.79.2.1.5.4*
> *.1.3.6.1.8.1.1.2321.79.2.1.5.4.0 = INTEGER: 123
>
> **# snmpget -v 1 localhost -c public 1.3.6.1.8.1.1.2321.79.2.1.5.4.0
> .1.3.6.1.8.1.1.2321.79.2.1.5.4.0 = INTEGER: 123*
>
> But when I run *snmpset* ,
>
> *snmpset -v 1 -c public localhost .1.3.6.1.8.1.1.2321.79.2.1.5.4.0 i 12345
> *
> *Error in packet *
> **
> *Reason:(genError) A general failure occured*
>
>
> My snmpd.conf file contains the following entries:
>
> #       sec.name  source        community
> com2sec Anyone    127.0.0.1/32  public
> # create some groups
> #     group name  security model  security name
> group Group       v1              Anyone
> group Group       v2c             Anyone
> #view  all   included   xx.xx.xx.xx.xx.xx.xx
> view  wview included   .1.3.6.1.8.1.1.2321.79.2.1.5.4.0
> master agentx
> #agentxPerms 0660 0550 nobody snmp
> agentxPerms 600
> agentxSocket /tmp/agentx
> agentxTimeout 60
> agentxRetries 1
>
> rwcommunity  public
>
> Is there anything else that I need to do?
> Am i missing something? Please let me know.
>
> Thanks and Regard,
> Jack.
>
>

              From: Connie Chan <conni…@ho…> — 2010-11-29 23:39:26

              		 
              Hi,
I'm using netsnmp 5.4.2.1.

I made a v2c request to server but got error "send response: Too long"

Turned on debug msgand got 
sess_async_send: 2010-11-29 15:00:16,716 - length of packet (8379) exceeds session maximum (4096)

We cannot specify maxMsgSize in snmpv2c PDU. 

Does netsnmp default it to 4096?

Why we limit the max response size in v2c? Should we only check the msgMaxSize if it is v3 or v2u?

Is there any way to increase the default size or skip the checking?

Thanks & Regards,
Connie
              Источник

              Понравилась статья? Поделить с друзьями:
            • Snmp error 2003
            • Smtp error from remote mail server after pipelined end of data
            • Smbios 0x16 error supermicro
            • Smbios 0x01 error supermicro
            • Slime rancher ошибка unity