Skip to main content

I rebooted Application VM from working TEST environment.

After reboot, I checked status of unix mws-svr.sh and here I see all components in status RUNNING, but starting IFS EE gives time-out after entering logon info.

Database VM has no problems, since I can query using PLSQL.

IFS System Monitoring shows normal

IFS Middleware Server Admin Console opens, but shows no running servers

When you ask details, you need to wait some time and get an error
Does anyone has a solution for this behavior?

 

Hi ​@mesjd0061 

Could you please share the screen shot of the Common → Database. windows.


Hi ​@mesjd0061 

 

Could you please share the screen shot of the Common → Database. window and Main Cluster → Deployments


@mesjd0061 

If the Middleware console is not showing the running MWS services means there is an issue with connection between MWS and Database. This could be network/configuration

1). Please check that the DB connection string in the Common → Database is correctly updated. Then click on “Validate Connection” to validate the DB connection from MWS server

2). Please check the Main Cluster → Deployments are active and Data Sources are running

3). Please analyze the database alert log and listener log for TNS Errors.

4). Please analyze the MainServer logs for the errors reported with login timeout. (You can tail the log and try to login for the recent login entries)

5). Verify the network connectivity between Middleware server and database.


Hi, thanks for suggestions, we finally found a solution.

We are using some wildcard-certificate (*.company.com) to access the different application servers for the different IFS-environments (ifsprod, ifstest, ifsdev). 

Solution was to add an entry like below in etc/hosts

ipaddres-server   ifstest.company.com

after saving, Middleware console and IFS EE immediately worked

Greetings,

Jos

 


Reply