Category
Administration
Product Version
9.0
WARN - liquibase.resource.null .. too many open files
Defect Logged
Hi,
we see in catalina.yyyy-mm-dd.logs more often quite a lot of exceptions for liquibase - too many open file. Our server side limit for "open files" is 63536, so this should not be a problem.
You can find many of these messages on the internet and almost always it is related to the used liquibase version. In which version it was actually fixed, I could not find out so fast.
Do you know this problem and are you looking for a solution? We use v9.8.0.1
Log extract
WARN [main] liquibase.resource.null Cannot create filesystem for url file:/opt/tc/yellowfin/webapps/yellowfin/WEB-INF/lib/xmlgraphics-commons-2.6. /opt/tc/yellowfin/webapps/yellowfin/WEB-INF/lib/xmlgraphics-commons-2.6. too many open files java.nio.file.FileSystemException: /opt/tc/yellowfin/webapps/yellowfin/WEB-INF/lib/xmlgraphics-commons-2.6. too many open files
;) Stefan
The same problem 
This does seem to be an issue with the Liquibase version currently shipping with Yellowfin and was identified and subsequently fixed in Liquibase 4.5.0: https://github.com/liquibase/liquibase/issues/1815
The Liquibase library is due to be updated to 4.8 in Yellowfin 9.9, so that should put an end to these messages.
Kind regards,
Chris
This does seem to be an issue with the Liquibase version currently shipping with Yellowfin and was identified and subsequently fixed in Liquibase 4.5.0: https://github.com/liquibase/liquibase/issues/1815
The Liquibase library is due to be updated to 4.8 in Yellowfin 9.9, so that should put an end to these messages.
Kind regards,
Chris
In our case, we also got these liquibase errors but were able to fix them by setting the hard and soft limits in /etc/security/limits.conf for the <user> under which the server runs:
worked with us.By checking
we found out that the limit was too low.In our case, we also got these liquibase errors but were able to fix them by setting the hard and soft limits in /etc/security/limits.conf for the <user> under which the server runs:
worked with us.By checking
we found out that the limit was too low.Hi Stefan,
It does seem to be Linux related. I see you've set a limit for open files, does your limits.conf file have entries for both the hard nofile and soft, as mentioned in Gerhard's solution?
Kind regards,
Chris
Hi Stefan,
It does seem to be Linux related. I see you've set a limit for open files, does your limits.conf file have entries for both the hard nofile and soft, as mentioned in Gerhard's solution?
Kind regards,
Chris
Replies have been locked on this page!