-
Notifications
You must be signed in to change notification settings - Fork 9
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
dbptk enterprise - validation problems #464
Comments
in DBTPK Enterprise, when exactly is this error shown? Is it mid validation, or right as you press the button, for example? EDIT: Additionally, what versions of DBPTK are you using in both cases? |
It is right after I click the button that starts the validation. I can not reproduce it very easily as the validation process just keeps going after I click the error away... So for example this picture has been present for a week now. I will try to get you the logs, where are they exactly in the docker installation? |
I found /containers/7b8e80cf557822a8947b31a323daf6be082c52b66668d9be21cdaccdfb2ea1b3/7b8e80cf557822a8947b31a323daf6be082c52b66668d9be21cdaccdfb2ea1b3-json.log file that is 119GB, is it normal? |
I took last 10000 rows from it and uploaded here: https://www.eha.ee/pilvi/index.php/s/3FnAQ9ZZDRiLYCq |
The logs for DBPTK Enterprise can be found in |
root@b6055639ee06:/dbvtk/log# tail -4000 dbvtk.log |
There seems to be a Java version mismatch issue in the mapdb extension that I can't replicate on my side. How was this instance of DBPTK Enterprise setup? Are you using the docker compose file from https://github.com/keeps/dbptk-enterprise/archive/master.zip ? |
Yes I am using the docker compose file. I have not specified any additional java versions for this installation. I just took the dbptk-enterprise from your site and then inserted docker command "docker compose up" |
I have siard file that can be validated successfully in DBPTK Desktop.
When I try the same file in the DBPTK Enterprise then i get
No errors in the logs just this message on my screen.
The text was updated successfully, but these errors were encountered: