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

"Text file is busy" with Node on querybook_web container #1341

Open
PaulMatthieu opened this issue Sep 28, 2023 · 0 comments
Open

"Text file is busy" with Node on querybook_web container #1341

PaulMatthieu opened this issue Sep 28, 2023 · 0 comments

Comments

@PaulMatthieu
Copy link

Hello
I'm trying to run Querybook locally to test it before deploying in a bigger environment, I'm currently using the latest commit on (bac499c)
I can't seem to be able to boot the querybook_web container, I get the following error log when I run the make command

web_1            | [2023-09-28 Thu 12:24:48] - /opt/querybook/querybook/server/lib/utils/import_helper.py - DEBUG   "Cannot import stats_logger_plugin.ALL_PLUGIN_STATS_LOGGERS due to: No module named 'stats_logger_plugin'"
web_1            | INFO  [alembic.runtime.migration] Context impl MySQLImpl.
web_1            | INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
web_1            | [2023-09-28 Thu 12:24:49] - /opt/querybook/querybook/server/lib/utils/import_helper.py - DEBUG   "Cannot import stats_logger_plugin.ALL_PLUGIN_STATS_LOGGERS due to: No module named 'stats_logger_plugin'"
web_1            | /opt/querybook
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 0.66s.
web_1            | Running: python3 querybook/server/runweb.py --debug 3000
yarn run v1.22.19
$ /opt/querybook/node_modules/.bin/webpack serve --host 0.0.0.0 --port 10001 --mode=development --open --hot --env QUERYBOOK_UPSTREAM=http://0.0.0.0:3000
web_1            | /usr/bin/env: ‘node’: Text file busy
error Command failed with exit code 126.

I tried running the v3.28.0 tag but I ran in an other bug services.elasticsearch.environment.plugins.security.disabled contains true, which is an invalid type, it should be a string, number, or a null, which is fixed on master

Any idea what to do ? I've seen similar issues but on much older Node containers (nodejs/docker-node#1912 for instance)

Thanks

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

1 participant