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

Can't load the job having 2627 images #5898

Closed
spt3009 opened this issue Mar 22, 2023 · 11 comments
Closed

Can't load the job having 2627 images #5898

spt3009 opened this issue Mar 22, 2023 · 11 comments
Labels
need info Need more information to investigate the issue

Comments

@spt3009
Copy link

spt3009 commented Mar 22, 2023

My actions before raising this issue

I had annotated approximately 1300 images, then I did control+S and closed the window. I am trying to open the job but just keeps loading.....

frames = 0-2625
segment size = 2626
image quality = 70

@spt3009 spt3009 changed the title Can't load the job having more 2626 images Can't load the job having 2627 images Mar 22, 2023
@nmanovic nmanovic added the need info Need more information to investigate the issue label Mar 22, 2023
@nmanovic
Copy link
Contributor

@spt3009 , could you please provide more information? Which version of CVAT do you use (CVAT.ai cloud or on-prem)? If you use self-hosted version is it the latest release CVAT v2.4.0?

We just need steps to reproduce the issue on our side.

@spt3009
Copy link
Author

spt3009 commented Mar 22, 2023 via email

@spt3009
Copy link
Author

spt3009 commented Mar 22, 2023 via email

@spt3009
Copy link
Author

spt3009 commented Mar 22, 2023 via email

@jhaux-askui
Copy link

jhaux-askui commented Apr 4, 2023

I have a similar problem. After having annotated 1500 images I cannot open the job anymore. In the console I get only a timeout error.

If I want to export the annotations from jobs page I get the following error:

Could not export dataset for the job xxx

Error: Request failed with status code 500. "django.db.utils.OperationalError: could not resize shared memory segment "/PostgreSQL.1284416766" to 33554432 bytes: No space left on device\nCONTEXT: parallel worker\n\n".

It looks like there is no space left on the servers?

Is there any way I can debug what is going wrong? I would really like to not lose those annotations.

@zhiltsov-max
Copy link
Contributor

@jhaux-askui, it seems like a different problem with the space left on the server. If the server is under your control, please check if there is enough disk space, and it is allowed for use by the containers.

@spt3009, #5974 may fix the problem once merged. It addresses long responses from the server on the job loading, leading to timeout errors.

@jhaux-askui
Copy link

Thanks for the quick answer @zhiltsov-max!

I'll check out if the servers are managed by us.

Today when I tried to load the job I got this error:

Error: Request failed with status code 500. "\n<!doctype html>\n<html lang="en">\n<head>\n <title>Server Error (500)</title>\n</head>\n<body>\n <h1>Server Error (500)</h1><p></p>\n</body>\n</html>\n".

Then after refreshing it actually worked and loaded everything! It might be because I have a better internet connection today.

I hope that helps 🙂

@azhavoro
Copy link
Contributor

I have a similar problem. After having annotated 1500 images I cannot open the job anymore. In the console I get only a timeout error.

If I want to export the annotations from jobs page I get the following error:

Could not export dataset for the job xxx

Error: Request failed with status code 500. "django.db.utils.OperationalError: could not resize shared memory segment "/PostgreSQL.1284416766" to 33554432 bytes: No space left on device\nCONTEXT: parallel worker\n\n".

It looks like there is no space left on the servers?

Is there any way I can debug what is going wrong? I would really like to not lose those annotations.

Try to increase shared memory size for cvat_db container https://docs.docker.com/compose/compose-file/compose-file-v3/#domainname-hostname-ipc-mac_address-privileged-read_only-shm_size-stdin_open-tty-user-working_dir

@bsekachev
Copy link
Member

I hope the issue was solved. Do not hesitate to reopen in any case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need info Need more information to investigate the issue
Projects
None yet
Development

No branches or pull requests

7 participants
@zhiltsov-max @bsekachev @nmanovic @azhavoro @spt3009 @jhaux-askui and others