AD controller not starting

[CommunityUser]

I have an issue at customer. After installation of new 3.9.0.2 release on Windows server 2008 32 bit, controller are not starting.

I've attached screenshots and logs below.

Controller runs as administrator.

Please help us to solve this issue.

[Arun_Dasetty]

Hi,

Can you see if updating hosts file (usually under C:\Windows\System32\drivers\etc) 

with following hosts/ip details added helps here and see how it goes after restart, we assume this are the hosts used by controller to ping controller appserver status as per server.log:
INFAP , 127.0.0.1, localhost

Example:

127.0.0.1       localhost

Regards,

Arun

[CommunityUser]

Hi, thank you for the answer, but

this parameter in hosts file has been already added, before installation.

May this problem appear, when agent still 3.8.x  version and conroller reinstalled with 3.9 version?

Before this upgrade controller works and communicated with agents.

[Arun_Dasetty]

Hi,

We could confirm that agent version used or agent registered will not affect controller installation Or startup of controller.

Can you please re-run the installer with following args:

-Vad-timeout-in-min=60 -Vstartup-timeout-in-min=60

Also please provide the snippet of hosts file Or try running the installer after OS restart suspect that changes to hosts file are either not updated as expected or not take affect.

Regards.

Arun

[CommunityUser]

Hi, 

Launching with these parameters are the same result. I've attacheched scrshot and hosts file. 

Restarting of server and intallation of controller made repeatedly. 

But version 3.8.4 installed and works.

[Arun_Dasetty]

Hi,

Unfortunately the provided logs arhive seems corrupted and we could not able to open please reattach the server.log , startAs.log and latst install.log in addition to hosts file as requested earlier

Regards,

Arun

[CommunityUser]

Yes, of course.

[Arun_Dasetty]

Hi,

We see errors around mysql db connecion and other errors in previous server.log , but the main issue seems to port conflict issue as per startAs.log content, make sure 4848 port is not use, by default controller runs on Glassfish server instance:

There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server.
Command start-domain failed.

Regards,

Arun