To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Restoring an nvhotbackup to another system |
From: | Mike Pearson <pearsom@us.ibm.com> |
Date: | Fri, 2 Jun 2006 11:51:51 -0400 |
Delivery-date: | Fri, 02 Jun 2006 16:52:50 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <060220061539.18510.44805BB50002DE3C0000484E2205886360CFCFCFCD020107040407030A050703@comcast.net> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Mike: The 255 error message for ovtopmd is because of the env not being properly sourced. Did you start netview with either /etc/netnmrc or netview? The sourcing should be in netnmrc. Regards, Michael Pearson Tivoli NetView for UNIX and NT Support Building 660, Office CC105B; HWY. 54 & 600 PARK OFFICES DR Research Triangle Park, N.C. 27709 (919) 254-2270 pearsom@us.ibm.com ****************************************************************** ****************************************************************** Need help with Tivoli Software Products? Ask Tivoli! http://www.tivoli.com/asktivoli
Frank- Yes, the 7.1.4 system was operational before I restored the databases. However, you may have something here: root@connm10:/usr/OV/bin>./ovtopmd exec(): 0509-036 Cannot load program ./ovtopmd because of the following errors: 0509-150 Dependent module librim.a(shr.o) could not be loaded. 0509-022 Cannot load module librim.a(shr.o). 0509-026 System error: A file or directory in the path name does not exist. root@connm10:/usr/OV/bin> -------------- Original message -------------- From: George deSocio <desocio@us.ibm.com> Mike, did your 7.1.4 system ever work? Did ovtopmd ever start? Run ovtopmd in the foreground. That is, from the command line: /usr/OV/bin/ovtopmd Post the resulting messages. Regards, Geo. George deSocio IBM Americas Support - Distributed Network Management E-Mail: desocio@us.ibm.com
Noted that I did not revise the subject header, so I'm just re-posting this, as I would appreciate any suggestions/help. Thanx. Mikemillion -------------- Original message -------------- From: mikemillion2000@comcast.net Working on recoving an nvhotbackup from one server (7.1.3) to another server (7.1.4). Here is what I ran into when I ran the reset_ci: root@connm10:/usr/OV/service>./reset_ci Start of reset_ci, after successful completion you will receive a reset_ci finished message. Reregistering /u! sr/OV/l rf/ovesmd.lrf... ovaddobj - Static Registration Utility Successful Completion Reregistering /usr/OV/lrf/ovelmd.lrf... ovaddobj - Static Registration Utility Successful Completion ./reset_ci[253]: objcall: not found. Unable to update the label for the NetView server icon. reset_ci finished Then when I tried to start the daemons, here is what resulted: root@connm10:/usr/OV/service>/etc/netnmrc portmap is already running Starting IBM Tivoli NetView daemons : WARNING: Daemon startup error. See /usr/OV/tmp/netnmrc.ovstart root@connm10:/usr/OV/service> root@connm10:/usr/OV/service>cat /usr/OV/tmp/netnmrc.ovstart object manager name: OVsPMD behavior: OVs_PMD state: RUNNING PID: 50550 exit status: - object mana! ! ger n am e: nvsecd behavior: OVs_WELL_BEHAVED state: RUNNING PID: 45610 last message: Initialization complete. exit status: - object manager name: pmd behavior: OVs_WELL_BEHAVED state: ! ; ; RUNNING PID: 22990 last message: pmd completed initialization exit status:&nb! sp;! &n bsp;& nbsp; - object manager name: nvpagerd behavior: OVs_WELL_BEHAVED state: RUNNING PID: 5702 last message: PMD initialization complete exit status: - object manager name: nvlockd behavior: OVs_WELL_BEHAVED state: RUNNING PID: 20318 last message: ! & amp;nbs! p; ; Init: Success exit status: - obje ct manager name: nvlockd behavior: OVs_WELL_BEHAVED state: RUNNING PID: 20318 last message: Initialization complete. exit status: - object manager name: OVORS_M behavior: OVs_WELL_BEHAVED state: RUNNING PID: &nbs! p; ; &nbs! p; ; 17292 last message: orsd completed initialization exit status: - object manager name: mgragentd behavior: OVs_NON_WELL_BEHAVED state: RUNNING PID: 66798 exi! t statu s: - object manager name: trapgend behavior: OVs_NON_WELL_BEHAVED state: RUNNING PID: ! & nbsp; &n! bsp;&nb sp; 42102 exit status: - object manager name: snmpserver behavior: OVs_WELL_BEHAVED state: RUNNING PID: 66264 last message: Initialization complete exit status: - object manager name: trapd behavior: OVs_WELL_BEHAVED state: RUNNING PID: &nb! sp;&nbs p; &nbs! p; ; 11394last message: Initialization complete. exit status: - object manager name: nvcorrd behavior: OVs_WELL_BEHAVED state: RUNNING PID: 19436 last message: Initialization complete exit status: - object manager name: actionsvr behavior: OVs_WELL_BEHAVED state: ! & nbsp; RUNNING PID: ! ; 37946 last message: Initialization complete exit status: - object manager name: ovwdb behavior: OVs_WELL_BEHAVED state: ! RUNNING PID: 25212 last message: Initialization complete. exit status: - object manager name: nvserverd behavior: OVs_WELL_BEHAVED ! ;state: ! & nbsp; RUNNING PID: 38302 last message: Initialization complete. exit status: - object manager name: nvcold behavior: OVs_WELL_BEHAVED state: RUNNING PID: 73470 last message: Initialization complete. exit status: - object manager name: servmon beh! avior: &nbs! p; ; ! OVs_WE LL_BEHAVED state: RUNNING PID: 29530 last message: Initialization complete exit status: - object manager name: webserver behavior: OVs_WELL_BEHAVED state: RUNNING PID: 17662 last message: Initialization complete exit status: ! - &n bsp; object manager name: ovactiond &nb! sp;beha vior: OVs_WELL_BEHAVED state: RUNNING PID: 58782 last message: ! I nitialization complete. exit status: - object manager name: ovtopmd behavior: OVs_WELL_BEHAVED state: NOT_RUNNING PID: 68860 last message: &n! bsp;&nb sp; exit status: &n! bsp;&nb sp; exit(255) object manager name: snmpCollect behavior: OVs_WELL_BEHAVED state: UNSTARTABLE PID: (never run) last message: exit status: - object manager name: itsl2 behavior: OVs_WELL_BEHAVED state: UNSTARTABLE PID: &n! bsp; &n bsp; &nbs! p; (nev er run) last message: &nb! sp; exit status: - object manager name: netmon behavior: OVs_WELL_BEHAVED state: UNSTARTABLE PID: (never run) last message: exit status: - object manager name: ems_sieve_agent behavior: OVs_WELL_BEHAVED state: UNSTARTABLE PID: &nb! sp;&nbs p; (never run) &nb! sp;last message: exit status: - object manager name: ems_log_agent behavior: OVs_W! ELL_BEH AVED state: UNSTARTABLE PID: (never run) last message: exit status: - As you can see, I'm having daemon startup issues. Any suggestions/takers? Thanx. Mikemillion |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] Restoring an nvhotbackup to another system, mikemillion2000 |
---|---|
Next by Date: | Re: [nv-l] Restoring an nvhotbackup to another system, mikemillion2000 |
Previous by Thread: | Re: [nv-l] Restoring an nvhotbackup to another system, mikemillion2000 |
Next by Thread: | Re: [nv-l] Restoring an nvhotbackup to another system, George deSocio |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web