Birt iHub suddenly stopped working

Hi Everyone,
 
We have been using birt iHub and its was working fine until yesterday, It suddenly stopped working.
 
I have no idea what has happened. I restarted the i-hub server and the restart messages tells successful restart but i am stil not able to access http://[hostname]:8700/iportal.
 Getting following messages on server start up:-
 
<div>
<pre class="_prettyXprint">
The AC_JAVA_HOME property is set to be /home/actuate/BIRTiHubVisualization/modules/JDK64
Path to iHub is /home/actuate/BIRTiHubVisualization/modules/BIRTiHub/iHub
Path to Java Development Kit is /home/actuate/BIRTiHubVisualization/modules/JDK64
Starting PostgreSQL for Actuate ...
pg_ctl: another server might be running; trying to start server anyway

pg_ctl: this data directory appears to be running a pre-existing postmaster
pg_ctl: could not start server
Examine the log output.
Starting Actuate BIRT iHub 3 ...
Calling CheckJavaVersion to validate required java version
Checking java version: Required minimum java version is 1.6.0
Checking java version: Current java version is 1.7.0_45, 64-bit
Checking java version: 1.7.0_45 is okay to run BIRT iHub.
AC_JRE32_HOME is
Start iHub complete.
nohup: redirecting stderr to stdout
setup complete.</pre>
</div>
<div> </div>
 
I also checked startsrvr.out but it is empty.
 
We have been using Linux Cent OS 7.5 version for iHub. Can anyone help . Its really urgent as we have release tomorrow.
 
Thanks Nikhil

Find more posts tagged with

Comments

micajblock

If this is urgent, I would suggest contacting customer support.

JFreeman

Regarding the console output while starting the iHub, this output is normal for a situation where the PostgreSQL metadata database is already running. If the PostgreSQL was not stopped when the iHub was stopped this could be expected.
 
Did you experience any errors attempting to stop PostgreSQL when you were restarting the iHub?
 
Do you see the ihubservletcontainer process running?
 
Please zip or tar your iHub's log files and attach them to this thread. The diagnostic log files can be found within the ./iHub/data/server/log directory.

RSiegler

To provide more clarity on this issue, this was due to the license file being expired.
After obtaining the replacement license file and applying to the configuration home, the issue is resolved.
 
For anyone experiencing a similar issue, my suggestion is to go to the server log folder (Defaulted to $Visualization_Home$/iHub/data/server/log) and look for the most recent "ihubd " log file.
 
This will start off with a large amount of data concerning the system (OS, CPUs, RAM), the iHub version (build number, etc), and then some information on the license file, and any errors when trying to start the service.
 
If a parameter is listed as a date in the failure, please check it against the current date. If it is the same as today's date or previous to today's date, then the server has shut down due to the licence having expired.