Antwort: Re: Changing the oserv port number of a MN

Hallo Venkat,

thanks for the answer, yes I had already done all these steps you describe
but the oserv remained hard and did not start on port 95.

The problem was actually that the ManagedNode was installed under the usage
of
port 94 for this oserv and the start using port 95 got rejected although
I'd modified the
local environment/start files. I was thinking about a way to inform the TMR
server about the new
port ( odadmin odlist should list the new port number for this oserv), but
found no way how to do it.

So I changed back and started it using port 94 and changed the port for the
Test TMR servers oserv port
to 95. Now all looks and works fine.

Anyway it would be appreciated if anyone in the list knows about a way to
tell the TMR Server
that the oserv port number for a specific object dispatcher has changed.


Mit freundlichen Gruessen / best regards

Yusuf Demir
IDG mbH / PS-SYS2-SM

Tel: 0221/308-29838
Mobil: 0160-4757963
E-Mail: Yusuf_Demir@xxxxxx




Venkatesan Saranathan <sa.venkatesan@xxxxxxxxx>@lists.us.ibm.com on
22.02.2005 20:14:42

Bitte antworten an tme10@xxxxxxxxxxxxxxxx

Gesendet von:     owner-tme10@xxxxxxxxxxxxxxxx


An:    tme10@xxxxxxxxxxxxxxxx
Kopie:
Thema: Re: [tme10] Changing the oserv port number of a MN

Hi Yusuf,

Greetings. I changed the port number in our test tmr using the following
steps.

1) Stopped oserv. (/etc/Tivoli/oserv.rc stop)
2) Edited the oserv.rc script and changed the o_dispatch variable
3) Edited the setup_env.sh and setup_env.csh and changed o_dispatch
variable
4) Edited the /etc/services file and changed the lines defining
objcall udp and tcp services.

It worked correctly in my linux tmr.  not sure if you have done all
these and the implications of running multiple oservs.

with warm regards,
Venkat Saranathan
Tivoli Certified Consultant.


On Tue, 22 Feb 2005 14:34:35 +0100, yusuf_demir@xxxxxx
<yusuf_demir@xxxxxx> wrote:
>
>
> Hallo List,
>
> I had a ManagedNode running fine on port 94 but had to
> change it to someother number (95) because of another oserv
> that should run on 94.
>
> 1. I know the whole scenario is unsupported.
>
> 2. I have installed both MN's on different directories, each one having
> its own environment scripts. (under /etc/Tivoli/ and /etc/Tivoli-95).
>
> 3. The scripts in both /etc/Tivoli and /etc/Tivoli-95 are adapted having
> set o_dispatch either to 94 or 95.
>
> Problem: The first oserv (running on port 94) always starts, but the
second
> does not:
>
>
##########################################################################################

> :/etc/Tivoli-95 # grep o_dispatch *
> oserv.rc:o_dispatch=95
> oserv.rc:      exec $BINDIR/bin/oserv -p $o_dispatch -I -k $DBDIR
> >/dev/null 2>&1
> oserv.rc:      if [ $o_dispatch -ne 94 ]; then
> oserv.rc:         portstr=" (port $o_dispatch)"
> oserv.rc:      $BINDIR/bin/oserv -p $o_dispatch -k $DBDIR
> oserv.rc:      odadmin -p $o_dispatch reexec
> oserv.rc:      odadmin -p $o_dispatch shutdown
> setup_env.csh:setenv o_dispatch 95
> setup_env.sh:o_dispatch=95
> setup_env.sh:export o_dispatch
> :/etc/Tivoli-95 # . ./setup_env.sh
> :/etc/Tivoli-95 # ./oserv.rc start
> !/usr/local/Tivoli-95/bin/linux-ix86/bin/oserv: odlist init failed.
> FRWOG0010E requested resource not found. (30)
> :/etc/Tivoli-95 #
>
###########################################################################################

>
> Anyone having an idea ?
>
> Mit freundlichen Gruessen / best regards
>
> Yusuf Demir
> IDG mbH / PS-SYS2-SM
>
> Tel: 0221/308-29838
> Mobil: 0160-4757963
> E-Mail: Yusuf_Demir@xxxxxx
>
>