Page 1 of 1
Update Otms 2.1 to 2.1.1 failed
Posted: 17 Dec 2015 18:27
by Split
Hi
Today i try a update omts-v 2.1.0.101 to otms-v 2.1.1 i did not expect any problems because the minimal release jump but it is not working .....the chameleon service is Not starting i check "service chameleond status" and the result is the service stays at starting not started after a while the service is terminated and start again.
I check logs and it seems something with java. With top i can see a process 130% cpu usage for short time. I restore a Backup of the virtuell Maschine and try again but it happens again i have no idea whats the reason for that.
I will Check Logs tomorrow cause there are so many logs it takes a lot time but if i found something i will post ot here
Have somebody a idea whats the chameleon service starts or give mehr a hint how i solve this?
Thanks for Held
Split
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 19 Dec 2015 15:51
by tgn
i had no problems some. updated last week an ot from 2.1 to 2.1.1 physical installation. update was done with 2nd partition.
regards...
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 19 Dec 2015 17:47
by Split
Hi tgn
My otms is in a vmware esxi 5.5.
After the update the first i see is that the Service that restarting
Now i spent a lot of time ...in the logs iam unable to find something at the moment. But whats real strange is that 8770 unable to connect to EES ; the global synchronisation works only for oxe. I can connect to the WBM from 8770 but a connect to the Teamwork ACS Server fails with invalid authentification or expired message ....conference and mailbox are reachable but all 8082 cant connect to EES i update the 8082 to the new Binary Version x.12 like discribe in tc. A update on 2nd partiton not possible in virtualisation.
Im very confused

Re: Update Otms 2.1 to 2.1.1 failed
Posted: 20 Dec 2015 20:24
by oldboy
So a question i know they have had issues before, check the firewall on the OT server in redhat !!!! i think as part of an upgrade that is turned on turn it off and see how it goes
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 21 Dec 2015 09:14
by Split
Hi oldboy
I checked the firewall but this is disable.... before i start the update i run a systenCheckLinux.sh from the ot2.1.1 dvd and all was ok after the update i do this again and all seems ok but it isnt
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 21 Dec 2015 18:08
by oldboy
Have you updated the licence server as well??
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 21 Dec 2015 18:14
by Split
Yes to the new one wich supports esxi 5.5 and have the rasperry pi Image included ...checkLicencse.sh says all ok
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 21 Dec 2015 18:30
by tgn
what says the output of ifconfig?
regards...
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 21 Dec 2015 18:59
by Split
Hi thanks for Help
@tgn
[root@otms01 otuser]# ifconfig
br0 Link encap:Ethernet HWaddr 00:0C:29:70:8D:61
inet addr:192.168.99.18 Bcast:192.168.99.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe70:8d61/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:247800 errors:0 dropped:0 overruns:0 frame:0
TX packets:266796 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:58921599 (56.1 MiB) TX bytes:91491381 (87.2 MiB)
eth0 Link encap:Ethernet HWaddr 00:0C:29:70:8D:61
inet6 addr: fe80::20c:29ff:fe70:8d61/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:252278 errors:0 dropped:0 overruns:0 frame:0
TX packets:266805 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62643039 (59.7 MiB) TX bytes:91492339 (87.2 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:7746057 errors:0 dropped:0 overruns:0 frame:0
TX packets:7746057 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1420045525 (1.3 GiB) TX bytes:1420045525 (1.3 GiB)
did you mean this?
Re: Update Otms 2.1 to 2.1.1 failed
Posted: 12 Jan 2016 05:35
by Split
Hi
Late feedback. ..
I didnt find the reason so install R2.1.1 from scratch all service running restore backup and it happens again so i export user data from otms restore the backup which made at first start and Import User data and fill the other things like unified messaging so now ist working ..