-
Notifications
You must be signed in to change notification settings - Fork 50
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
Weird issue with Omero #2219
Comments
Hi, |
thanks @will-moore. Please see the chart below: |
Hi @Hamedhm. How long has this been happening? Did anything change at about the time it began? (e.g. a move to a new server, a configuration change, a new file type) The error you're getting looks to me like a system resource issue. Without knowing more, I'd guess a file descriptor limit ( |
Hi @joshmoore Thank you for your reply. No nothing changed as far as I know. I guess the issue is that Omero eats up all memory. For example, I restarted the Omero a few hours ago and it is using 17.6GB of virtual memory already. Yesterday, it was around 80GB. for the command |
How much memory does this system have, @Hamedhm?
This is a reasonable setting, so 👍
Interesting. Can you show the rest of that output? What python process is running under the java process with 1500m of memory. |
Thanks @joshmoore The machine has 32GB of memory. The screenshot below is for when the machine is idle (like when I restart the machine). There is one task running on the machine but really nothing much. and |
Hi @Hamedhm, Historically, the Java virtual memory consumption can be taken with a grain of salt, but 80GB definitely sounds like an issue. Also noting the Java version (1.6) I must make the plea for an upgrade. As a sidenote: I don't recognize this |
Hi,
We have an Omero server V5.3.1 (I know it is old!) to upload 100K+ images, and have recently encountered some issues with it.
Before I start, the config file looks like below:
The issue is that the server quickly becomes unavailable.
The log below is produced by the process that may have some signals to specify the issue:
Please have you seen the same issue before?
The text was updated successfully, but these errors were encountered: