search

reportportal / migrations

Apache License 2.0
1 stars 15 forks source link

timeout: unrecognized option: t #111

Open arrase opened 4 years ago

arrase commented 4 years ago

timeout: unrecognized option: t BusyBox v1.30.1 (2019-06-12 17:51:55 UTC) multi-call binary.

Usage: timeout [-s SIG] SECS PROG ARGS

Runs PROG. Sends SIG to it if it is not gone in SECS seconds. Default SIG: TERM. wait-for-it.sh: timeout occurred after waiting 15 seconds for 35.222.48.152:5432 no change

h4wkmoon commented 4 years ago

I'm this issue as well. For fresh install, it is a bit anoying as the db is not intialized at all !

digaetan commented 4 years ago

I´m facing same issue...any idea how to fix it?

inluxc commented 4 years ago

Me too.. in AWS ECS component

DzmitryHumianiuk commented 4 years ago

@pbortnik ^

pbortnik commented 4 years ago

Hi colleagues, I suppose, that it need to be clarify about these services. The service 'db-scripts' (older name 'migration') is responsible for database schema changes. So, it makes some changes only while first running. It executes default scripts. All next executions of the service show 'no changes' until the new script will be released. So, if database is up and running, please check if it has any tables inside 'reportportal' such as 'project', 'launch' etc. If not, try to redeploy reportportal from the scratch. The guide how to do it here

dagansandler commented 4 years ago

@pbortnik The issue isn't "no changes" output. It's the "timeout: unrecognized option: t" which is printed regardless. There's some issue in one of the scripts, not sure where.

dagansandler commented 4 years ago

relates to this I believe: https://github.com/vishnubob/wait-for-it/issues/71

This exists on docker tag 5.0.0, not sure what's the base image for later tags and if the issue is there too.

seems like the migrations are running properly but it spams the log and makes you wonder if it isn't missing anything in the migrations.

miracle8484 commented 1 year ago

Hello, in case if issue reproduced on the latest version of migration, could you provide please detailed information (version of migration, basic state of db, and logs)?