Skip to content
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

Configuration is lost after restarting the stack #15

Open
AyoubHabra opened this issue Oct 25, 2021 · 2 comments
Open

Configuration is lost after restarting the stack #15

AyoubHabra opened this issue Oct 25, 2021 · 2 comments
Assignees

Comments

@AyoubHabra
Copy link

When restarting the stack, the configuration is lost and the portal redirects again to the registration form. We investigated this issue, and we have found that the configuration is lost because the hsql folder is not mapped to a persistent volume on the host like srv_data. With previous releases, we have been able to fix this by mapping the folder to a mount point, but with now we are receiving the following error on startup:
Caused by: org.hsqldb.HsqlException: Database lock acquisition failure: lockFile: org.hsqldb.persist.LockFile@d99bbf6b[file =/opt/meeds/gatein/data/hsql/exo-plf.lck, exists=false, locked=false, valid=false, ] method: openRAF reason: java.io.FileNotFoundException: /opt/meeds/gatein/data/hsql/exo-plf.lck (Permission denied)
Any help / ideas ?
Thank you.

@ahamdi
Copy link
Member

ahamdi commented Oct 25, 2021

Hi @AyoubHabra
You need to remove the file /opt/meeds/gatein/data/hsql/exo-plf.lck, which is the lock used by HSQL DB to make a single connection, to the database.
I would also recommend that you use a Production database MysqlDB or Postgres DB, to avoid losing data if HSQL files got corrupted
HTH
Ali

@ahamdi ahamdi self-assigned this Oct 25, 2021
@AyoubHabra
Copy link
Author

Thank you so much for your reply @ahamdi,
In fact, we're still testing Meeds, and we want to keep hsql for a few days.
In fact, It was a permissions issue, I changed the owner of files from root to meeds (exo-plf.lck included), and it worked.
I have another question, if you don't mind. When using a production dbms, is it required to change the environment variable called : MEEDS_DB_TYPE which is set to hsql by defualt ?
The problem, here, is that the setenv-docker-customize.sh script will stop the container at startup if this variable is not set to hsqldb.
case "${MEEDS_DB_TYPE}" in hsqldb) echo "################################################################################" echo "# WARNING: you are using HSQLDB which is not recommanded for production purpose." echo "################################################################################" sleep 2 ;; *) echo "ERROR: you must provide a supported database type with MEEDS_DB_TYPE environment variable (current value is '${MEEDS_DB_TYPE}')" echo "ERROR: supported database types are :" echo "ERROR: HSQLDB (MEEDS_DB_TYPE = hsqldb) (default)" exit 1;;
`
Best Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants