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

Eclipse Che no longer responding, message "Updating File" #3396

Closed
didier1969 opened this issue Dec 15, 2016 · 10 comments
Closed

Eclipse Che no longer responding, message "Updating File" #3396

didier1969 opened this issue Dec 15, 2016 · 10 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@didier1969
Copy link

didier1969 commented Dec 15, 2016

Hello,
I installed Che on a KVM Ubuntu 16.04 machine, inside docker container. No problem at the beginning, but after a few days, Che becomes slow and even does not respond anymore. A message "Updating File" is shown.

The container contains one Workspace with Meteor, with one meteor project running inside. The biggest files are CSS files of 3-4 Mb

Reproduction Steps:

  1. Create Meteor Workspace according to procedure described here : https://eclipse-che.readme.io/docs/get-started-with-meteor
  2. Run meteor project
  3. Change any file
  4. Let system sit for a couple days

Observed behavior:
Freezes and browser no longer responding

Che version: 5.0.0. Latest
OS and version: Ubuntu 16.04 on KVM
Docker version: Docker version 1.12.3, build 6b644ec
Che install: Docker Container

Additional information:
KVM Machine has GB RAM, 6 GB used. CPU is between 1-2% only.

@TylerJewell TylerJewell added the kind/bug Outline of a bug - must adhere to the bug report template. label Dec 15, 2016
@TylerJewell TylerJewell added this to the 5.0.0-M9 milestone Dec 15, 2016
@TylerJewell TylerJewell added team/ide severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Dec 15, 2016
@TylerJewell
Copy link

  1. Does rebooting Che resolve the issues?
  2. Are there any logs in the chrome browser developer console?

@didier1969
Copy link
Author

Hello and thank you for your quick reply.
I restarted the server and after 25 minutes, the problem came again.

  1. The KVM machine under Proxmox
    proxmox_kvm

  2. The Google Chrome Dev console. I first thought that an extension diigolet could bring the issue. So Pic_1 is before disabling diigolet, Pic_2 after disabling it.

chrome_dev_1
chrome_dev_2

Many thanks for your help.
Didier

@vparfonov vparfonov self-assigned this Dec 15, 2016
@TylerJewell
Copy link

Thanks for the additional diagnostics. We are going to treat this as a possible blocker / outage related issue. We do not have any sort of timing or commitment we can offer, but it will get scheduled into our dev flow.

@bmicklea
Copy link

@didier1969 are you able to reproduce this issue running Che in Docker native on Linux (outside the KVM)?

@JamesDrummond JamesDrummond added the status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach label Dec 16, 2016
@JamesDrummond
Copy link
Contributor

We are currently having issues reproducing this issue. @didier1969 We need additional information to reproduce.

@JamesDrummond JamesDrummond modified the milestones: 5.1.0, 5.0.0-M9 Dec 20, 2016
@JamesDrummond JamesDrummond added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels Dec 20, 2016
@TylerJewell
Copy link

  1. We have seen some inconsistency with this issue. We have heard reports of this happening on native hosts, but it disappears before we can get a diagnostic log.

  2. This may be issue related to natively running in a VM - but want to see if original poster can reliably reproduce in their VM.

@TylerJewell
Copy link

@didier1969 - can you reconfirm that this issue is happening on our nightly release? We are effectively GA ready with 5.0.0 release (1300 commits). And we are trying to plan around 5.1.0 - and we need some more info on the state of this issue. There is a chance that the newly merged file system watchers solve your problem, so let's verify.

@didier1969
Copy link
Author

didier1969 commented Dec 30, 2016 via email

@TylerJewell
Copy link

@didier1969 - ok, thank you for doing another test with our nightly package. @vparfonov - let's budget investigation time for this in the next sprint starting Thursday.

@bmicklea bmicklea added severity/P1 Has a major impact to usage or development of the system. and removed severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Jan 10, 2017
@bmicklea bmicklea removed this from the 5.1.0 milestone Jan 10, 2017
@svor
Copy link
Contributor

svor commented Jan 17, 2017

Can't reproduce

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

6 participants