Yellowfin Logging Stopped

Melissa Baldwin shared this question 5 months ago
Answered

Q. I upgraded a tomcat from an earlier 9 (1.2.2.0 delivered with YF9.3 ) to tomcat 9.0.48(1.2.4.0) (like I've done at ~15 of our other customer sites).

AFTERWARDS (after launching the site to make sure it was OK) I upgraded from Yellowfin 9.3 to 9.6. Now I'm having serval strange issues in YF9.6. BUT i noticed it is no longer logging most of the standard Yellowfin logs.

I'm only getting

  • commons-daemon.2021-08-17.log (which does show every time i use the service.bat to install or remove the Yellowfin Service)
  • empty (0KB) yellowfin.stderr.202-08017.log and yellowfin.stdout.202-08017.log

Any idea what could be the issue with the Tomcat? I need the logging to try to troubleshoot the rest of the crud that seems to have come with the YF upgrade.

When I rolled back Tomcat to the original tomcat folder (1.2.2.0) I get logging back but I cant seem to start the Yellowfin service with YF9.6.: in yellowfin_stderr

/ea2ef779724276154605025663f381f4

I'm sort of stuck...

Comments (4)

photo
1

Hi Melissa,

That is some odd behaviour, what is your customer's setup in terms of infrastructure? I assume Yellowfin is running on Windows as you've said you're running a service. What version of Java is installed?


If you open a cmd prompt at the Yellowfin folder and run

tomcat9w.exe //ES/Yellowfin

could you please send screenshots of the Logging and Java tabs? If the Java Options box has more lines than can be shown, would you please copy the text out to this ticket.

I've included some examples below:

/1bfef3a7e34395cf95f795778858d11e

/817adf6569ce05345ab738b2d4c36316


/a7789da7d5d601b468ddf63adbb099f6

Thanks!

Kind regards,

Chris

photo
1

nothing out of the ordinary. Did no touch the Java between the two tomcat versions.

Using the standard 9.0.84 bin/service.bat with this customer's local java folder... This morning, I'm not even able to start the new 9.0.84 env. The saga continues still looking for some weird permissions issue that is probably causing this.


/59e840b31ad2146cc24d093769d3b4cd

/034a9fbc54648f1d9bb86d0c218d0ce2

photo
1

you can close this ticket.

I was able to upgrade to Java JRE to the 301 release and then use the original service.bat with that new JRE_Home path.

photo
1

Hi Melissa,

That's great to hear. I'll close this off. Thanks also for letting me know how you solved it, such answers might be helpful to people in future!

Enjoy the rest of your week :)

Kind regards,

Chris