The problem looks to be with Tomcat, not YF itself, but after some googling and community searching I’ve yet to find a start point let alone anything meaningful…. And Tomcat is not something I’m familiar with, so searching from a knowledge base of zero.
When we attempt to start YF it bombs out immediately; putting some ‘pause’ commands in the startup script appear to show it crashing out within Catalina.bat, on the first command after the script has ‘echo’d the various pathnames.
Some Background info:
After some pointers from Support (Paul) we verified that JRE was a 32 bit version; that's now be upped to the 64bit version; and we amended the Catalina.bat file to allocate 4Gb of RAM (machine has 16Gb)
After all of that we are still (I suspect) getting a failure in starting Tomcat. Unfortunately my knowledge of Tomcat is not sufficient to help trouble shoot....
Should add... Tomcat didn't appear to write a logfile which suggest there may be a permission issue (in creating the file) or it's not finding something.
Thanks for reaching out with the issue you're facing. Please open a command prompt at <YellowfinInstall>/appserver/bin and execute the startup.bat file manually. This will open a tomcat console, which will likely close as you've been experiencing, but should provide some additional output in your original command prompt as to what's happening here. Please add that information here for review.
I wanted to reach out and offer a remote session to resolve the issue you're facing. I'm located in the North American office, so my times of availability range from 0800 - 1700 US MDT. If these times do not work with your schedule, please let me know your availability including time zone and I can reach out to another region.
Hello, I’m free now for the next 2 hours, would anytime fit? Thanks for your help, Ben.
From: Support Queue <support@Yellowfin.bi>
Sent: 13 March 2019 15:19
To: Ben Neesom <firstname.lastname@example.org>
Subject: Re: Tomcat not starting [#12807]
Sure thing! You can use the following link to join the meeting:
Thank you for taking the time to screen share with me today. As a quick summary of how we resolved this issue: we first had to identify the error at hand, which wasn't being logged anywhere. To overcome this, we opened a command prompt in the <YellowfinInstall>/appserver/bin folder and issued the following command:
This revealed that we were allocating 4GB of RAM to a 32-bit Java.
After updating the JAVA_HOME in the <YellowfinInstall>/appserver/bin/catalina.bat file, Yellowfin was able to start successfully.
We then updated your existing Yellowfin Windows service:
I'll mark this as answered since we were able to get you up and running, but please don't hesitate to let me know if you have further issues.
Great stuff thanks Ryan. Added the 'JAVA_HOME' bit to my 'trouble shooting' crib sheet.
Comments have been locked on this page!