SC 3.5.0 VIBE error

by on ‎2012-01-26 10:24 AM

Not sure where to go from here, when I see this in the logs....

########## Application Auto Discovery ##########

[Thu Jan 26 11:20:41 2012] ERROR: 500 read timeout at /</usr/local/scServer3.5.0/snapcreator>SnapCreator/Agent/Remote.pm                 line 474

[Thu Jan 26 11:20:41 2012] [127.0.0.1:9090(3.5.0.1)] ERROR: [scf-00049] Auto Discovery for plugin vibe failed with exit code 1, Exiting!

Can someone point in the right direction?

Thanks,

Jim

Comments
Extraordinary Contributor

Hi Jim,

It is easier if you open a discussion not a document in future.

As for error read timeout is simply that the scServer waited for the scAgent and the timeout expired.

The timeout is controlled by the SC_AGENT_TIMEOUT setting in the config file.

I would set it to

SCX_AGENT_TIMEOUT=900

Also if it still times out you can with SC 3.5 set this option

SC_AGENT_LOG_ENABLE=Y

This will force logging on agent so you can actually see what it is doing, the logs are similar to those on server under the scAgent/logs directory.

Regards,

Keith

Extraordinary Contributor

Another thing

If you are using 127.0.0.1 which is localhost, why are you even using an agent?

Comment out SC_AGENT

The scServer can communicate directly with vCenter, you only need scAgent if scServer has no access to vCenter.

Keith

Read this in the 3.5 document...

You should be aware of the following considerations when using VMware plug-in:

• The VMware plug-in is supported only on Windows and Linux. If the user is using a non-Windows or non-Linux Snap Creator Server, they need a Snap Creator Windows/Linux agent to run the VMware plug-in.

Seemed that the agent would be required.

Frequent Contributor

Jim,

I believe that the point of the section you are referring to is the fact that the VMware plug-in only works with Windows and Linux.

If you are running a Snap Creator server on a different OS, say Solaris, then you would need a Windows or Linux agent to run the plug-in.

Snap Creator Server contains all of the same calls as the agent, so if you are running only on one system then you do not need the agent piece at all.

Hope this helps to clarify.

John

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.