Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error when I try to add new server in Vom (Veritas Operation Manager)

Created: 27 Jan 2014 | 13 comments
marcelogigliotti's picture

Hi,

I've been had some problems when I try to add many clients into Vom Server. I receive the message below.

"

[root@webserver01 ~]# ./vom.dms.local.pl

Veritas Operations Manager Managed Host Deployment

Initializing

Attempting to configure host using hostname webserver01.dms.local.

Verifying if it is reachable from the CMS vom.dms.local...

Extracting credential

Configuring managed host

Can't locate object method "Internal Error: Could not determine hostid" via package "VRTS::SFMHCAT" at ./vom.dms.local.pl line 246, <DATA> line 92.

"

The release vom server is 6.

Any sugestions about this problem? I can't find any information in log.

Regards

Operating Systems:

Comments 13 CommentsJump to latest comment

Michael Auria's picture

What is the OS of the Central Managment Server (where you connect the browser too) ?

What is the OS of the Managed Host (where youn are running the vom.dms.local.pl script) ?

Are both machines VOM versions the same (VRTSsfmcs aznd VRTSsfmh on Unix/Linux platforms ?

marcelogigliotti's picture

What is the OS of the Central Managment Server

  • RHEL 6.5

What is the OS of the Managed Host (where youn are running the vom.dms.local.pl script) ?

  • RHEL 6.2
  • RHEL 5.7

Are both machines VOM versions the same (VRTSsfmcs aznd VRTSsfmh on Unix/Linux platforms ?

  • For all machines we are using VRTSsfmh 6.0.0 
  • The version of VRTSsfmcs 

Look the log file

Add Host Log

------------

Started [01/27/2014 15:44:53]

[01/27/2014 15:44:53] type  rh nbserver03 cms 

[01/27/2014 15:44:53] Check if MH is pingable from MS and get vital information from MH

[01/27/2014 15:44:53] Output: {

"XPRTLD_VERSION" :  "6.0.0.0",

"LOCAL_NAME" : "UNKNOWN",

"LOCAL_ADDR" : "192.168.10.23",

"PEER_NAME" : "vom.dms.local",

"PEER_ADDR" : "192.168.11.47",

"LOCAL_TIME" : "1390844694",

"LOCALE" : "en_US.UTF-8",

"DOMAIN_MODE" : "FALSE",

"QUIESCE_MODE" : "RUNNING",

"OSNAME" : "Linux",

"OSRELEASE" : "2.6.18-194.el5",

"CPUTYPE" : "x86_64",

"OSUUID" : "{0001f4ce-46ba-c934-0000-000000000000}",

"DOMAINS" : {

    }

}

Michael Auria's picture

The CONNECT website is not a forum for a formal support case.  While I look into this matter, if you have a support contract and require a more urgent responce, I can assist you with opening a formal support case.

Ireyes's picture

Hi Marcelo, 

The query you have will require a bit more research on Symantec end. I suggest you please open a support case as Michael suggested , so we may assit you on identifying this problem.

Regards,

Ivette

Michael Auria's picture

Also, are these virtual machines ?  If so, what type ?

I'm thinking it may be more effective and efficient to handle this via a formal support case if possible.

Michael Auria's picture

Can you check on the following file please ?

  /var/opt/VRTSsfmh/.hostguid
 

Please post an "ls -l" and a "cat" of this file from the Managed Host (MH).

This issue is requiring additional research.  It is suggested that a suppport case be opened.

jsilvestriOIT's picture

I am having a similar issue on a Managed Host for VOM

The managed host is running Solaris 10 10/09 s10s_u8wos_08a SPARC and I installed the VOM 6.0 managed host for Solaris SPARC (VRTSsfmh_6.0.0.0_SunOS_arch_sparc.pkg)

The file /var/opt/VRTSsfmh/.hostguid has the following information in it:

total 38
drwxr-xr-x   8 root     other        512 Mar 12 10:55 .
drwxr-xr-x   5 root     sys          512 Mar 12 10:51 ..
-rw-r--r--   1 root     other          8 Mar 12 10:55 .hostguid
-rw-r--r--   1 root     other         16 Mar 12 10:51 .hostid
-rw-r-----   1 root     root           0 Mar 12 10:54 configure_mh.lock
drwxr-xr-x   2 root     other        512 Mar 12 10:51 etc
drwxr-xr-x   2 root     other        512 Mar 12 10:53 logs
-rw-r--r--   1 root     other          7 Mar 12 10:52 mh_config.ver
-rw-r-----   1 root     root        4.9K Mar 12 10:54 mh_cred.xml
-rw-r-----   1 root     root           0 Mar 12 10:55 scheduler.lock
drwxr-xr-x   6 root     other        512 Mar 12 10:51 sec
-rw-r-----   1 root     root           0 Mar 12 10:55 tasks.lock
drwxr-xr-x   2 root     other        512 Mar 12 10:51 tmp
drwx------   2 root     root         512 Mar 12 10:55 trusted
-rw-r--r--   1 root     other          0 Mar 12 10:52 upgrade_mh.lock
drwxr-xr-x   2 root     other        512 Mar 12 10:52 vea
-rw-r-----   1 root     root        1.2K Mar 12 10:52 whitelist.json
-rw-r-----   1 root     other          5 Mar 12 10:51 xprtld.pid
 

and .hostguid

OS_UUID:
 

This is all.  Any ideas?

jsilvestriOIT's picture

Additional log info from /var/opt/VRTSsfmh/logs/mhrun.log

Note that the server does have a hostname and ip address other than localhost...

2014-03-12 13:14:45 [debug] 11862 MHRUN: Executing
2014-03-12 13:14:45 [debug] 11862 get_vitals: Getvitals for this host shows {
"XPRTLD_VERSION" :  "6.0.0.0",
"LOCAL_NAME" : "localhost",
"LOCAL_ADDR" : "127.0.0.1",
"PEER_NAME" : "localhost",
"PEER_ADDR" : "127.0.0.1",
"LOCAL_TIME" : "1394644485",
"LOCALE" : "en_US.ISO8859-1",
"DOMAIN_MODE" : "FALSE",
"QUIESCE_MODE" : "RUNNING",
"OSNAME" : "SunOS",
"OSRELEASE" : "5.10",
"CPUTYPE" : "sparc",
"OSUUID" : "UNKNOWN",
"DOMAINS" : {
    }
}
 

Also further down

2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: Getting hostname
2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: Writing sfm_resolv.conf
2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: Written sfm_resolv.conf
2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: Stamping hostid
2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: Old hostguid not defined
2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: Getting hostid
2014-03-12 13:15:03 [error] 11862 create_sfm_conf: Internal Error: Could not determine hostid
2014-03-12 13:15:03 [debug] 11862 create_sfm_conf: json = {"JOB":{"ERROR":"Internal Error: Could not determine hostid","ISHIDDEN":0
,"RETURNCODE":100,"NAME":"create_sfm_conf","OUTPUT":"","STATE":"FAILED","PROGRESS":50}}
2014-03-12 13:15:03 [debug] 11862 setup_cron: json = {"JOB":{"ERROR":null,"ISHIDDEN":0,"RETURNCODE":-9999,"NAME":"setup_cron","OUTP
UT":null,"STATE":"SKIPPED","PROGRESS":62.5}}
2014-03-12 13:15:03 [debug] 11862 setup_addons: json = {"JOB":{"ERROR":null,"ISHIDDEN":0,"RETURNCODE":-9999,"NAME":"setup_addons","
OUTPUT":null,"STATE":"SKIPPED","PROGRESS":75}}
2014-03-12 13:15:03 [debug] 11862 setup_metering: json = {"JOB":{"ERROR":null,"ISHIDDEN":0,"RETURNCODE":-9999,"NAME":"setup_meterin
g","OUTPUT":null,"STATE":"SKIPPED","PROGRESS":87.5}}
2014-03-12 13:15:04 [debug] 11862 run_discovery: json = {"JOB":{"ERROR":null,"ISHIDDEN":0,"RETURNCODE":-9999,"NAME":"run_discovery"
,"OUTPUT":null,"STATE":"SKIPPED","PROGRESS":100}}
2014-03-12 13:15:04 [error] 11862 run_discovery: Rolling back job jobs::create_sfm_conf
 

This is when I try to run the gendeploy.pl script I have set up to have VOM MH talk to the VOM MS

Michael Auria's picture

Can you show me what hostid returns at the Unix prompt of the host you are adding to the VOM domain ?

This is what it looks like in the lab here.

# hostid
8340ad4b
 

Michael Auria's picture

Also, what is the error when running the Auto Configure script (referred to as gendeploy).  Please cut and paste the command/output from the screen.

jsilvestriOIT's picture

Error from the autoconfigure script

# ./gendeploy.pl

Veritas Operations Manager Managed Host Deployment
Initializing
Attempting to configure host using hostname example.whatever.com.
Verifying if it is reachable from the CMS ManagementServer...
Extracting credential
Configuring managed host
Can't locate object method "Internal Error: Could not determine hostid" via package "VRTS::SFMHCAT" at ./gendeploy.pl line 246, <DATA> line 91.
 

output of the hostid command

# hostid
846b54d0

Edited the hostname and CMS server name for general principles