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

Unable to start Che 7 Workspace with latest Che Server #12631

Closed
sleshchenko opened this issue Feb 7, 2019 · 6 comments
Closed

Unable to start Che 7 Workspace with latest Che Server #12631

sleshchenko opened this issue Feb 7, 2019 · 6 comments
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.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Feb 7, 2019

Description

Unable to start Che 7 Workspace with latest Che Server.
Investigation shows that Theia container is started with 150mb memory limit while 1.5Gb is configured https://github.com/ws-skeleton/che-editor-theia/blob/master/etc/che-plugin.yaml#L43.

It may be related to ab82e73

Reproduction Steps

  1. Deploy latest Che Server.
  2. Try to create and start workspace from Che 7 Stack.

OS and version:
Che Server 6.19.0-SNAPSHOT, may be also actual for 6.18.0

Diagnostics:
@skabashnyuk guesses that it may be caused by outdated Che Plugin Registry where memory-limit field is present while memoryLimit is expected by Che Server.

Theia container Logs
Starting the master backend process with 5000 (ms) timeout.
Starting server worker...
Server worker has been started. [ID: 1 | PID: 24]
Failed to resolve module: @types/body-parser
Failed to resolve module: @types/bunyan
Failed to resolve module: @types/express
Failed to resolve module: @types/lodash.debounce
Failed to resolve module: @types/lodash.throttle
Failed to resolve module: @types/react
Failed to resolve module: @types/react-dom
Failed to resolve module: @types/react-virtualized
Failed to resolve module: @types/route-parser
Failed to resolve module: @types/ws
Failed to resolve module: @types/yargs
Failed to resolve module: electron
Failed to resolve module: font-awesome
Failed to resolve module: react
Failed to resolve module: react-dom
Failed to resolve module: react-virtualized
Failed to resolve module: @types/base64-js
Failed to resolve module: @types/fs-extra
Failed to resolve module: @types/mime-types
Failed to resolve module: @types/rimraf
Failed to resolve module: @types/tar-fs
Failed to resolve module: @types/touch
Failed to resolve module: @types/uuid
Failed to resolve module: @typefox/monaco-editor-core
Failed to resolve module: @types/base64-arraybuffer
Failed to resolve module: @theia/monaco
Failed to resolve module: @types/p-debounce
Failed to resolve module: @types/diff
Failed to resolve module: @types/p-queue
Failed to resolve module: @types/glob
Failed to resolve module: @types/tar
Failed to resolve module: @types/highlight.js
Failed to resolve module: @types/markdown-it
Failed to resolve module: @types/markdown-it-anchor
Server worker is ready to accept messages. [ID: 1 | PID: 24]
root INFO Plugins Remote Endpoints are  []
root INFO Plugins Remote Endpoints are  Map {}
root INFO unzipping the plugin ProxyPluginDeployerEntry {
  deployer: PluginTheiaFileHandler { unpackedFolder: '/tmp/theia-unpacked' },
  delegate:
   PluginDeployerEntryImpl {
     originId: 'local-dir:///default-theia-plugins',
     pluginId: 'eclipse_che_theia_containers_plugin.theia',
     map: Map {},
     changes: [],
     acceptedTypes: [],
     currentPath: '/default-theia-plugins/eclipse_che_theia_containers_plugin.theia',
     initPath: '/default-theia-plugins/eclipse_che_theia_containers_plugin.theia',
     resolved: true,
     resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
  deployerName: 'PluginTheiaFileHandler' }
root INFO unzipping the plugin ProxyPluginDeployerEntry {
  deployer: PluginTheiaFileHandler { unpackedFolder: '/tmp/theia-unpacked' },
  delegate:
   PluginDeployerEntryImpl {
     originId: 'local-dir:///default-theia-plugins',
     pluginId: 'eclipse_che_theia_factory_plugin.theia',
     map: Map {},
     changes: [],
     acceptedTypes: [],
     currentPath: '/default-theia-plugins/eclipse_che_theia_factory_plugin.theia',
     initPath: '/default-theia-plugins/eclipse_che_theia_factory_plugin.theia',
     resolved: true,
     resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
  deployerName: 'PluginTheiaFileHandler' }
root INFO unzipping the plugin ProxyPluginDeployerEntry {
  deployer: PluginTheiaFileHandler { unpackedFolder: '/tmp/theia-unpacked' },
  delegate:
   PluginDeployerEntryImpl {
     originId: 'local-dir:///default-theia-plugins',
     pluginId: 'theia_yeoman_plugin.theia',
     map: Map {},
     changes: [],
     acceptedTypes: [],
     currentPath: '/default-theia-plugins/theia_yeoman_plugin.theia',
     initPath: '/default-theia-plugins/theia_yeoman_plugin.theia',
     resolved: true,
     resolvedByName: 'LocalDirectoryPluginDeployerResolver' },
  deployerName: 'PluginTheiaFileHandler' }
root INFO Theia app listening on http://0.0.0.0:3100 .
Received message which is neither a response nor a notification message:
"3100"
/entrypoint.sh: line 93: syntax error: unexpected end of file
Server worker has been disconnected. [ID: 1 | PID: 24]
Server worker has been stopped. [ID: 1 | PID: 24]
@sleshchenko sleshchenko added kind/bug Outline of a bug - must adhere to the bug report template. team/platform severity/P1 Has a major impact to usage or development of the system. labels Feb 7, 2019
@ibuziuk
Copy link
Member

ibuziuk commented Feb 7, 2019

Update of plugin registry should fix the problem openshiftio/saas-openshiftio#1215

@l0rd
Copy link
Contributor

l0rd commented Feb 7, 2019

A workaround is setting the attribute "sidecar.theia-ide.memory_limit": "1500Mi" in the workspace.config

@ibuziuk
Copy link
Member

ibuziuk commented Feb 8, 2019

plugin registry has been updated to prod to the latest version on che.openshift.io and the issue should be fixed now

@garagatyi
Copy link

@sleshchenko could you check if this helped ?

@ibuziuk
Copy link
Member

ibuziuk commented Feb 8, 2019

verified locally on prod-preview - che 7 workspace startup seems to work just fine

@sleshchenko
Copy link
Member Author

Now it works fine for my local Che installation.

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.
Projects
None yet
Development

No branches or pull requests

4 participants