question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Installation fails due to not enough memory on host

See original GitHub issue

Hi! I have problems installing on a fresh Ubuntu Server 18.04 LTS VM following this tutorial. Seems that the conda install gets aborted? Output is:

Checking if TLJH is already installed...
TLJH already installed, upgrading...
Upgrading TLJH installer...
Setup tljh package
Starting TLJH installer...
Setting up admin users
Granting passwordless sudo to JupyterHub admins...
Setting up user environment...
Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/opt/tljh/hub/lib/python3.6/site-packages/tljh/installer.py", line 448, in <module>
    main()
  File "/opt/tljh/hub/lib/python3.6/site-packages/tljh/installer.py", line 430, in main
    ensure_user_environment(args.user_requirements_txt_url)
  File "/opt/tljh/hub/lib/python3.6/site-packages/tljh/installer.py", line 234, in ensure_user_environment
    'conda==4.5.8'
  File "/opt/tljh/hub/lib/python3.6/site-packages/tljh/conda.py", line 95, in ensure_conda_packages
    ] + packages).decode()
  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/opt/tljh/user/bin/python', '-m', 'conda', 'install', '-c', 'conda-forge', '--json', '--prefix', '/opt/tljh/user', 'conda==4.5.8']' died with <Signals.SIGKILL: 9>.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7

github_iconTop GitHub Comments

3reactions
hoellercommented, Jan 22, 2019

Process got killed by kernel due to low memory (VM had 512 MB). Tried with 1 GB and it worked. Should be mentioned somewhere.

1reaction
yuvipandacommented, May 19, 2019

ok, so #335 does the following:

  1. Make all integration tests run with 768MB of RAM, so we know if we’re using too much
  2. Document this requirement everywhere.

I think this should solve this issue, @hoeller.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Not enough memory in the system to start the virtual machine
Close the error window. · Click on the red power button to shut it down. · Select the virtual machine and click the...
Read more >
Not enough memory in the system to start virtual machine in ...
For that, right-click on the virtual machine and select the Settings option. Then, switch to the Memory tab and enter a lower amount...
Read more >
How To Fix "Not Enough Physical Memory" Error On VMWare?
Launch VMware and select Edit > Preferences. In the Memory tab, select Allow most virtual machine memory to be swapped and press OK....
Read more >
Not enough memory resources are available to process this ...
Fixes for "Not enough memory resources are available to process this command" in Windows 11/10, particularly when you run commands on CMD.
Read more >
How to Fix Not Enough Physical Memory Error in VMware
Fix 5. Modify the Config.ini File (Host Parameters) ... Step 1: Shut down your virtual machines and close the VMware Workstation. Step 2:...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found