Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

One-X Portal on Server Edition --- Not Starting 2

Status
Not open for further replies.

twitchy087

Vendor
Dec 20, 2011
144
US
Hi Everyone,

We have a SE that was working completely fine. Out of the blue our One-X service stopped and refuses to start back up. I have surfed these forums and Avaya's site to find nothing of real significance in regards to a fix. A lot of people say to reimage the whole server, others say to upgrade, reinstall the One-X service and such.

I have just upgraded us to 9.1.12 from 9.110 to no success. Reloading the whole damn server seems a bit ridiculous unless it is absolutely needed. Finally, reinstalling the One-X service seems to be tedious as well given there are multiple dependencies on the service. Again, I dont want to do this unless it is absolutely needed because it is removed 5-6 items to reinstall this.

I have gone through every damn log file and the only thing solid lead that I could find was in the ipowatchdog.log file. That file is completely littered with the below Java errors. Is One-X dependent on Java? If so then does anyone have any solid info on how to go about troubleshooting this? I know Linux enough to be able to get in and do some damage but I am not fully familiar with the inner workings.


<11> 2017 Sep 21 20:01:42 pbx ipowatchdog[14642]: -04:00 2017 885 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:02:42 pbx ipowatchdog[14642]: -04:00 2017 891 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:06:12 pbx ipowatchdog[14642]: -04:00 2017 956 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:08:42 pbx ipowatchdog[14642]: -04:00 2017 998 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:10:43 pbx ipowatchdog[14642]: -04:00 2017 019 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:14:13 pbx ipowatchdog[14642]: -04:00 2017 074 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:18:43 pbx ipowatchdog[14642]: -04:00 2017 152 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:22:13 pbx ipowatchdog[14642]: -04:00 2017 223 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Sep 21 20:40:43 pbx ipowatchdog[14642]: -04:00 2017 357 1 .ipowatchdog | 0 java problem detected. Restarting.

When I hit the "Start" button for the One-X service, it seemingly does nothing. This led me to manually start the service in Linux but that brought me to the same place. There is something stopping the boot of the service but I cant find any One-X specific logs that are giving me anything at all..

Any assistance is greatly appreciated.
Thanks ahead of time.






 
twitchy087 said:
A lot of people say to reimage the whole server, others say to upgrade, reinstall the One-X service and such.
There is a reason why they give this advise, they have been through the same process as you experience right now.
Avaya will advise the same as they have no clue either....
 
Have you looked in the Tomcat logs?

But yeah, it's probably faster to just take a backup of IPO config and VM Pro and reinstall so I would probably do that.
Although you won't learn anything from it =)

"Trying is the first step to failure..." - Homer
 
Yea, I am close to just just rebuilding the machine but like you said, I wont learn anything that way!

I am not familiar with the Tomcat log location. Can you point me in the right direction?

Thanks!
 
Hi twitchy087, did you solve the problem?

We did a reinstall of the system twice. The call was opened four months and the lack of resolution.

<11> 2017 Nov 12 14:19:51 localhost ipowatchdog[2576]: -02:00 2017 466 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 13 07:11:28 localhost ipowatchdog[2576]: -02:00 2017 185 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 16 01:50:48 localhost ipowatchdog[2576]: -02:00 2017 205 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 18 06:19:01 localhost ipowatchdog[2576]: -02:00 2017 096 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 19 06:57:49 localhost ipowatchdog[2576]: -02:00 2017 269 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 21 07:02:17 localhost ipowatchdog[2576]: -02:00 2017 906 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 21 09:34:49 localhost ipowatchdog[2576]: -02:00 2017 835 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 21 14:44:52 localhost ipowatchdog[2576]: -02:00 2017 409 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 23 18:55:37 localhost ipowatchdog[2576]: -02:00 2017 415 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 26 10:15:59 localhost ipowatchdog[2576]: -02:00 2017 335 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Nov 30 12:43:44 localhost ipowatchdog[2576]: -02:00 2017 045 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Dec 1 16:10:25 localhost ipowatchdog[2576]: -02:00 2017 398 1 .ipowatchdog | 0 java problem detected. Restarting.
<11> 2017 Dec 5 01:20:50 localhost ipowatchdog[2576]: -02:00 2017 399 1 .ipowatchdog | 0 java problem detected. Restarting.
 
Are you using the cores one-X portal with IPO or a separate application server?
 
What version of ACW are you using. Get it upgraded to the latest released by Avaya.
 
Twitchy, did you ever fix this without re-installing the server? It just happened to me too on 10.1.2 Server Edition. Was working fine then out of the blue the OneX service will not start.
 
Unfortunately, I had to build a new server. I did all that I could then got Avaya involved. Avaya went through and did all that they could before saying that I needed to start with a clean server. The issue seems to have revolved around Java becoming corrupt on the server and it could not be fixed with ease.

Sorry for the bad news. I really tried quite hard to avoid building a new server.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top