nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD Admin Server not able to start

Remo

Dear Friends,

I am not able to access OD Admin Server from the browser after installation.

Environment: TS 6.7.2, OD 6.2.0, Linux OS

As per instructions, I installed OD Admin server using the port 8082 and try start access using URL:http://phoenix.ges.com:8082/iw/opendeploy/login, but I am getting below message:

The connection has timed out

The server at phoenix.ges.com is taking too long to respond.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Logs:

2010-04-08 13:17:27 StandardContext[/iw/opendeploy]config path: /usr/AdminServer/odadmin/config/odreporting.cfg
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]deployAdmin path : /usr/AdminServer/odadmin/config/deployAdmin.cfg
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]DeployAdmin.rmiPort1 not specified in config file.
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]Using default value for DeployAdmin.rmiPort1: 25071
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]DeployAdmin.rmiPort2 not specified in config file.
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]Using default value for DeployAdmin.rmiPort2: 25071
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]starting reporting server
2010-04-08 13:17:29 StandardContext[/iw/opendeploy]reporting server started

Nothing erros in other log files.

Entries in deploy.cfg:

Deploy.bootStrapUserName: root
Deploy.allowDefaultBootStrapUser: yes

Could anyone share any information that could help resolving the issue.

Many thanks in advance.

Find more posts tagged with

Comments

Bhargav Coca

Dear Friends,

I am not able to access OD Admin Server from the browser after installation.

Environment: TS 6.7.2, OD 6.2.0, Linux OS

As per instructions, I installed OD Admin server using the port 8082 and try start access using URL:http://phoenix.ges.com:8082/iw/opendeploy/login, but I am getting below message:

The connection has timed out

The server at phoenix.ges.com is taking too long to respond.

* The site could be temporarily unavailable or too busy. Try again in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Logs:

2010-04-08 13:17:27 StandardContext[/iw/opendeploy]config path: /usr/AdminServer/odadmin/config/odreporting.cfg
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]deployAdmin path : /usr/AdminServer/odadmin/config/deployAdmin.cfg
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]DeployAdmin.rmiPort1 not specified in config file.
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]Using default value for DeployAdmin.rmiPort1: 25071
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]DeployAdmin.rmiPort2 not specified in config file.
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]Using default value for DeployAdmin.rmiPort2: 25071
2010-04-08 13:17:27 StandardContext[/iw/opendeploy]starting reporting server
2010-04-08 13:17:29 StandardContext[/iw/opendeploy]reporting server started

Nothing erros in other log files.

Entries in deploy.cfg:

Deploy.bootStrapUserName: root
Deploy.allowDefaultBootStrapUser: yes

Could anyone share any information that could help resolving the issue.

Many thanks in advance.

Are you sure your port is 8082. DId you try 8081? Check your port.

Thanks

Ramarao

Make sure that the port is available for running Admin server.

Adam Stoller

Hi lilleywhite,

Yeah, I am sure about the port. It is 8082.

I even tried with port 8081, but the issue is same.

Thanks

Are you sure that there isn't something else listening on port 8082 - that might be preventing the OD Admin UI from listening there and thus from responding to requests?

Have you tried running netstat -na | grep 8082 and whatever other tools are available to you for tracking down the actual process that's listening on that port?

Ramarao

Hi Remo,

Check whether the port is running for some other application.

Firewall may also cause access issue.

Remo

Hi Ghoti,

When I run netstat, below is the output.

[root]# netstat -na | grep 8082
tcp 0 0 :::8082 :::* LISTEN

Remo: The port is free for running Admin server and no firewall is running.

Thanks.

Adam Stoller

Hi Ghoti,

When I run netstat, below is the output.

[root]# netstat -na | grep 8082
tcp 0 0 :::8082 :::* LISTEN

Explicitly stop the OD Admin service and then try the netstat again. If you still see something listening on that port - that's the problem.
If you don't see something listening on that port - try restarting the OD Admin service and see if it works.

Remo

Hi Ghoti,

I Explicitly stop the OD Admin service and tried netstat, nothing is listening on that port.

And started server again and tried access the UI, but the issue is same.

I tried looking into all the logs, but didn't find any specific error that might cause the issue.

Exactly which log file do we need to look for debugging?

Thanks.

Adam Stoller

Hi Ghoti,

I Explicitly stop the OD Admin service and tried netstat, nothing is listening on that port.

And started server again and tried access the UI, but the issue is same.

I tried looking into all the logs, but didn't find any specific error that might cause the issue.

Exactly which log file do we need to look for debugging?

Thanks.

Okay - the good news is that you now know that the OD Admin Server is (attempting) to listen for connections on port 8082.

I'm not sure exactly which logs to look in, but I believe they may be found under the AdminServer and/or CSF installation ("home") directories.

If you cannot find the information there - I suggest you open a case with Support.