-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running fits.sh throws "Failed to instantiate SLF4J LoggerFactory" in 1.5.2 release #316
Comments
Running into this issue as well. Adding |
Will have an update for this shortly. The exception was being thrown when running FITS in Java 8 but not Java 11. |
Really appreciate the update and your work, thanks @daveneiman. |
Hello - please check out this 1.5.3 release. I should resolve the above problems when running under Java 8. |
The new release (1.5.3) is working great in our environment. Tested with a manual run and from our Hyrax based IR stack. Thanks again @daveneiman! |
@cudevmaxwell Turns out we've identified that this release, which upgraded to log4j2, still contains log4j (1) jar files within Tika and Droid. Will be trying to sort out the implications. |
The release(1.5.3) is working on my end now too(both via terminal and my through my rails app). Thanks for the quick fix @daveneiman! |
@daveneiman Why did you remove the log4j2 dependencies in this commit: 519a4ab Those are required for the logging to work. The main branch does not currently work. |
This has been fixed in in the main branch. |
I just updated to the recent 1.5.2 release locally and tried testing it using a bash shell (ie:
/path/to/fits/fits.sh -i /path/to/file.tif
) and it it now throwing the error in the title. I verified my$FITS_HOME
environment variable is still pointing to the correct folder and all the jars get appended to the$APPCLASSPATH
infits-env.sh
. Here is the full stack trace I captured.My machine/environment specs are
The text was updated successfully, but these errors were encountered: