Hi All,
I have installed CentraSite on Windows and Linux machine. I was able to boot up CentraSite Registry Repository on Windows machine without any issues.
But when I am trying to boot up the one installed on Linux machine it is showing Terminated with errors.
I am not seeing any errors and logs apart from the one mentioned below.
Attaching the screenshot in the thread. Any pointer to resolve this issue will be helpful.
INODST1781: Start of CentraSite server startup processing on Linux x86_64
INODSI2271: Start server 'CentraSite'
INODSE2274: Server died during startup
INODSF1436: Terminated with errors
Regards,
Syed Faraz Ahmed
Hi,
Is this issue still relevant?
Thanks,
Adhithya.
Hi Adhithya,
It was resolved long back. However, i dont remember the resolution now.
Are you facing same issue now?
Regards,
Syed Faraz Ahmed
Hi,
I am facing the same issue, could you please help.
Thanks
If the startup of CentraSite’s Registry Repository fails, then there should be a log file named AABinosrv*.txt at
/CentraSite/data
Hi Paul,
Appreciate your response on this topic.
PFB logs-
[eai@frmseaiwbmp02 data]$ more AABinosrv.17:17:24.txt
/opt/eai/Centrasite/CentraSite/data/AABinosrv.17:17:24.txt
18-JAN-2020 17:17:24 INODSA2278: CentraSite server 9.7(456) on Linux x86_64
18-JAN-2020 17:17:24 INODSS1712: Starting database server
18-JAN-2020 17:17:24 INODSR1687: Reading parameters
18-JAN-2020 17:17:24 INODSI2310: Licensed for TOTAL SA - DSIT / CGI Mme Messaouda BRAHIMI with ID 7307813
18-JAN-2020 17:17:24 INOXHI8151: Communication method: HTTPS
18-JAN-2020 17:17:25 INOSXI6723: JVM started with user options ’ -Xss2000k’
18-JAN-2020 17:17:25 INODSW1809: Error when opening data space 1 (at /opt/eai/Centrasite/CentraSite/data/AAB00001.2D0): size mismatch, expected 112167354368 byt
es
18-JAN-2020 17:17:25 INOXHR8245: Initializing XML processing
18-JAN-2020 17:17:25 INODSF1300: Open of Log file (/opt/eai/Centrasite/CentraSite/data/AAB000010000000494.2L0) has failed due to an invalid structure
18-JAN-2020 17:17:25 INODSW1840: Log space of server session 494 extent 1 not closed
18-JAN-2020 17:17:25 INODSA1000: Starting autorepair after abnormal termination
18-JAN-2020 17:17:25 INODSS1711: Recovering from abnormal termination
18-JAN-2020 17:17:25 INODSR1682: Analyzing journal information
18-JAN-2020 17:17:25 INODSR1684: Reconstructing consistent index structures. Processing journal block 3747.
18-JAN-2020 17:17:25 INODSR1684: Reconstructing consistent index structures. Processing journal block 3746.
18-JAN-2020 17:17:25 INODSR1684: Reconstructing consistent index structures. Processing journal block 3745.
18-JAN-2020 17:17:25 INODSR1684: Reconstructing consistent index structures. Processing journal block 3744.
18-JAN-2020 17:17:25 INODSR1684: Reconstructing consistent index structures. Processing journal block 3456.
18-JAN-2020 17:17:25 INODSR1684: Reconstructing consistent index structures. Processing journal block 3455.
18-JAN-2020 17:17:25 INODSW2073: Previous log file corrupted (reason: LOG file registration error). Please perform a database backup as soon as possible.
18-JAN-2020 17:17:25 INODSR1683: Re-applying changes. Processing journal block 3455.
18-JAN-2020 17:17:25 INODSR1683: Re-applying changes. Processing journal block 3456.
18-JAN-2020 17:17:25 INODSF1251: Internal error 17 occurred
18-JAN-2020 17:17:25 INODSF1454: Internal error occurred: location SRV-CMD-04 nds.c nds_add. Server stopped.
io_term: Stack Backtrace (C):
18-JAN-2020 17:17:25 INODSA1001: Start writing crash dump of database, writing to file /opt/eai/Centrasite/CentraSite/data/CentraSite.AAB.17:17:25.1M0
18-JAN-2020 17:17:25 INODSI1635: Crash dump of database finished
Start writing SAGSMP dump, writing to file /opt/eai/Centrasite/CentraSite/data/SAGSMP.AAB.17:17:25.0M0
Dump of SAGSMP finished
18-JAN-2020 17:17:25 INOXHA8259: Start writing XML dump of database, writing to file /opt/eai/Centrasite/CentraSite/data/CentraSite.AAB.17:17:25.xml
18-JAN-2020 17:17:25 INOXHI8260: XML crash dump of database finished
18-JAN-2020 17:17:28 INODSF1436: Terminated with errors
You have new mail in /var/spool/mail/eai
Please provide any solution for this.
Thanks,
Prateek
The CentraSite database consists of different types of database containers: index space (.2I0), data space (.2D0) and journal space (.2J0). The index space does not only contain index data, it also contains other meta data such as the sizes of the database containers. The error
INODSW1809: Error when opening data space 1 (at /opt/eai/Centrasite/CentraSite/data/AAB00001.2D0): size mismatch …
means that the database is inconsistent, the expected size in the message can be used to compare it with the actual size of /opt/eai/Centrasite/CentraSite/data/AAB00001.2D0 in the file system.
Such an inconsistency could be introduced by a file system restore. For example when a file system backup was done, the backup for the .2D0 file could have been completed at a different point of time than the .2I0 file. In between of these 2 points of time data may have been added and the active server might have increased the .2D0 file. When now a file system restore is done, the size of the data container within the .2I0 might not match with the real size of the .2D0 file.
If a file system restore with CentraSite container files is done, the CentraSite database will become consistent again with a CentraSite restore/recover using the latest restored backups and log spaces.
Hello Heinz,
This is a long pending issue occured in August which we have got in hereditary from previos partner. So the backup of this entire filesystem would not be available even with our storage team as they have 3 months retention policy only.
Please provide anyother solution for this issue.
Thanks in advance.
Prateek