Hi
could you attach the front end server log please (frontendserver.0.0.log)?
You can use the system information dashlet and check under yourServerName/support information/Logs files.
Regards
Flo
Answer by Juergen K. ·
What I found in the logfile was: Wed Sep 02 13:59:42 CEST 2015 WARNING [DefaultRepositoryExceptionHandler] An element does not exist perhaps the schema is corrupted: com.dynatrace.diagnostics.repository.exceptiontranslators.DefaultRepositoryExceptionHandler a:92
From this and couple of other log messages it seems that your Data Warehouse is corrupt.
If you do not have important information in it, I suggest to just recreate the schema (This will delete all the data)
(server settings -> data warehouse -> rebuild schema)
Answer by Ray B. ·
Here's some history, we had 7GB of memory and stage the server as medium size and the system took all memory and left 757M left for the OS so we added another 3 GB memory on yesterday and restarted the server and after that the frontend server start and stop. So we are learning the application. Anyway I check the server.config.xml and see the frontend port is 2031 and 2030 and not 2021 and 2020, so is there a offset by 10 for it?
<frontend frontendsslport="2031" frontendaddress="localhost" frontendrequiressl="true" frontendport="2030" />
no that's correct. The clients connect to the front-end server via 2021 but the front-end server connects to the back-end server via 2031. The Dynatrace server comprises of 2 processes that's why (front-end and server).
It might be worth checking that the 2nd process is running ok after the reboot.
Are you on Windows or Linux? On windows, there will be 2 services which should auto-restart but on Linux, unless you have registered our startup script via update-rc.d it won't restart automatically after the reboot.
For a medium size deployment, both processes will use a combined 6GB of RAM so it is behaving as expected.
Answer by Florent D. ·
I'm seeing a lot of connection errors especially with the backend server but nothing obvious jumps out.
I would suggest creating a support ticket.
sorry I couldn't help you more.
JANUARY 15, 3:00 PM GMT / 10:00 AM ET