Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

java.io.FileNotFoundException: ..\..\bundles\agent-4.2.0.3-EE-1274\pdk\mibs when starting agent in platform neutral agent (tcserver licensed restricted bundle)

Details

  • Case Links:
    none
  • Regression:
    No

Description

installed and configured agent using http://download.hyperic.com/dl/tcs/shimmer-m4/hyperic-hq-agent-4.2.0.4-EE-1278-tcs-shimmer-2010-01-26.zip (tc server shimmer M4 bundle)

on startup of the HQ platform-neutral agent, I see the following stacktrace in the agent log file:
2010-01-28 17:57:24,843 ERROR [Thread-1] [MIBTree] ..\..\bundles\agent-4.2.0.3-EE-1274\pdk\mibs (The sy
stem cannot find the file specified)
java.io.FileNotFoundException: ..\..\bundles\agent-4.2.0.3-EE-1274\pdk\mibs (The system cannot find the
file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at org.hyperic.snmp.MIBTree.parseFile(MIBTree.java:585)
at org.hyperic.snmp.MIBTree.parse(MIBTree.java:683
at org.hyperic.snmp.MIBTree.parse(MIBTree.java:645)
at org.hyperic.snmp.MIBTree.init(MIBTree.java:237)
at org.hyperic.snmp.MIBTree.getInstance(MIBTree.java:247)
at org.hyperic.snmp.SNMPClient.init(SNMPClient.java:198)
at org.hyperic.hq.product.SNMPMeasurementPlugin.init(SNMPMeasurementPlugin.java:144)
at org.hyperic.hq.product.PluginManager.registerPlugin(PluginManager.java:366)
at org.hyperic.hq.product.PluginManager.registerPlugin(PluginManager.java:331)
at org.hyperic.hq.product.PluginManager.registerPlugin(PluginManager.java:338)
at org.hyperic.hq.product.MeasurementPluginManager.registerProxy(MeasurementPluginManager.java:57)
at org.hyperic.hq.product.MeasurementPluginManager.init(MeasurementPluginManager.java:71)
at org.hyperic.hq.product.ProductPluginManager.initPluginManagers(ProductPluginManager.java:461
)
at org.hyperic.hq.product.ProductPluginManager.init(ProductPluginManager.java:436) at org.hyperic.hq.agent.server.AgentDaemon.startPluginManagers(AgentDaemon.java:683)
at org.hyperic.hq.agent.server.AgentDaemon.start(AgentDaemon.java:828)
at org.hyperic.hq.agent.server.AgentDaemon$RunnableAgent.run(AgentDaemon.java:926)
at java.lang.Thread.run(Unknown Source)

...

The agent does start up. will attach agent log file

Activity

Hide
Ellen Johansen added a comment -

adding in email reply from Chip:
The mibs directory is present in the tcs agent bundle, but like the noJRE standard agent, contains no files. I'm not sure why we aren't seeing this with the standard agent, but I am fairly confident it has nothing to do with my re-rolling of the bundles. The only things removed were the following plugins and the examples directory:

alfresco-plugin.jar \
bind-plugin.jar \
coldfusion-plugin.jar \
db2-plugin.jar \
dotnet-plugin.jar \
exchange-plugin.jar \
geronimo-plugin.xml \
glassfish-plugin.xml \
iis-plugin.jar \
informix-plugin.jar \
iplanet-plugin.jar \
jboss-plugin.jar \
jetty-plugin.xml \
memcached-plugin.jar \
mqseries-plugin.jar \
mssql-plugin.jar \
mysql-plugin.jar \
mysql_stats-plugin.jar \
nagios-plugin.jar \
netdevice-plugin.jar \
netservices-plugin.jar \
ntds-plugin.jar \
ntp-plugin.jar \
oc4j-plugin.jar \
openldap-plugin.jar \
oracle-plugin.jar \
perlbal-plugin.jar \
postfix-plugin.jar \
postgresql-plugin.jar \
resin-plugin.xml \
samba-plugin.jar \
sendmail-plugin.xml \
sqlquery-plugin.jar \
sybase-plugin.jar \
vim-plugin.jar \
vmware-plugin.jar \
weblogic-plugin.jar \
websphere-plugin.jar \
xen-plugin.jar \
zimbra-plugin.jar;

Aside from adding the tcs plugin (and the license in the case of the server), nothing else was changed.

CW

Show
Ellen Johansen added a comment - adding in email reply from Chip: The mibs directory is present in the tcs agent bundle, but like the noJRE standard agent, contains no files. I'm not sure why we aren't seeing this with the standard agent, but I am fairly confident it has nothing to do with my re-rolling of the bundles. The only things removed were the following plugins and the examples directory: alfresco-plugin.jar \ bind-plugin.jar \ coldfusion-plugin.jar \ db2-plugin.jar \ dotnet-plugin.jar \ exchange-plugin.jar \ geronimo-plugin.xml \ glassfish-plugin.xml \ iis-plugin.jar \ informix-plugin.jar \ iplanet-plugin.jar \ jboss-plugin.jar \ jetty-plugin.xml \ memcached-plugin.jar \ mqseries-plugin.jar \ mssql-plugin.jar \ mysql-plugin.jar \ mysql_stats-plugin.jar \ nagios-plugin.jar \ netdevice-plugin.jar \ netservices-plugin.jar \ ntds-plugin.jar \ ntp-plugin.jar \ oc4j-plugin.jar \ openldap-plugin.jar \ oracle-plugin.jar \ perlbal-plugin.jar \ postfix-plugin.jar \ postgresql-plugin.jar \ resin-plugin.xml \ samba-plugin.jar \ sendmail-plugin.xml \ sqlquery-plugin.jar \ sybase-plugin.jar \ vim-plugin.jar \ vmware-plugin.jar \ weblogic-plugin.jar \ websphere-plugin.jar \ xen-plugin.jar \ zimbra-plugin.jar; Aside from adding the tcs plugin (and the license in the case of the server), nothing else was changed. CW
Hide
Jason Konicki added a comment -

First off, this will not cause any problems, except the error in the log.

Second, this issue is due to the tar utility that was used when tarring up the package. Some older tar utilities remove the empty directories by default.

When the hq agent was repackaged, the mibs directory was eliminated from the tar bundle.

Chip, what tar utility were you using? What OS?

Show
Jason Konicki added a comment - First off, this will not cause any problems, except the error in the log. Second, this issue is due to the tar utility that was used when tarring up the package. Some older tar utilities remove the empty directories by default. When the hq agent was repackaged, the mibs directory was eliminated from the tar bundle. Chip, what tar utility were you using? What OS?
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks ago