-
Notifications
You must be signed in to change notification settings - Fork 40
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
FDP in the latest (develop) docker image cannot start #581
Comments
@mirzov Thanks for the detailed report. I'm trying to pick up some of the slack while familiarizing myself with the FDP codebase, so let's see if we can figure this out. On my system the mvn spring-boot:run -Dspring-boot.run.profiles=development (with postgres in a docker container) Tests also pass, so it looks like this case slipped through the cracks of the test suite. Looking more closely, the FAIRDataPoint/src/main/java/org/fairdatapoint/config/RepositoryMigrationConfig.java Lines 37 to 38 in d0ca93f
Sure enough, the error can be reproduced on a local system, running the FDP from source, by activating the mvn spring-boot:run -Dspring-boot.run.profiles=production At least this indicates that the issue is not limited to the Docker image. While I'm looking for a solution or workaround, perhaps @MarekSuchanek could tell us whether this part is still under development? |
Just for reference: FAIRDataPoint/.github/workflows/build.yml Line 173 in d0ca93f
FAIRDataPoint/Dockerfile.build Line 42 in d0ca93f
|
It turns out the public interface RdfMigrationRepository extends MongoRepository<RdfMigration, String> {
} |
Hi Dennis, Nice that there is someone working on the codebase now! I later found that just deleting the file with RdfMigrationRepository class did not prevent the project from building, and the server could start then. However, after packaging and "dockerizing" it, attempts to use the resulting container together with matching Postgres and latest published FDP client were not successful (login with the default credentials was rejected, front page was showing 404 message from a REST call). |
By removing the config file, the server will indeed start. However, this causes the rdf migration steps to be skipped, so the triple store will not be populated with initial data.
Setting up the postgres db, FDP, and FDP client, with the proper ports, I can get the login to work (user data are stored in postgres).
I suppose the status 404 is expected, because there is no data in the triple store, since the migrations have not been executed.
Apparently, the The first priority would then be to adapt the In addition, if we look at the production rdf migrations for the develop branch, it looks like those have not been fully adapted to postgres yet. Compare, e.g. with the production migrations for v1.17.2. It would be great if @MarekSuchanek could shed some light on this. |
@mirzov Although I'm working on the current issue, the For this reason it is probably safer to stick to one of the supported releases for now. |
What components are related to the issue?
Other (specify in text)
Which FDP are you using?
My local instance
Version
What happened?
Trying to get the latest development docker image working, prepared the following docker-compose setup:
https://github.com/ICOS-Carbon-Portal/meta/tree/28c90bcd2e7a417302b559f125758d6a5c98ac79/src/main/docker/fdp
FDP server startup failed, the logs complain about lack of Spring Bean definition for type
org.fairdatateam.rdf.migration.database.RdfMigrationRepository
. The culprit seems to be this method argument.In addition, the fdp docker log contains many messages about Spring Data MongoDB. Should it not have been removed when moving to Postgres? The output from
docker logs fdp
is included.Relevant log output
click to see full logs
The text was updated successfully, but these errors were encountered: