[GH-ISSUE #262] Upgrading from 4.0 to latest - no module named core.management #210

Closed
opened 2026-02-27 16:38:24 +03:00 by kerem · 35 comments
Owner

Originally created by @ITBlogger on GitHub (Mar 13, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/262

Hi,

I'm trying to upgrade from webvirtmgr 4.0 to the latest and when I run ./manage.py syncdb I get the following:

Traceback (most recent call last):
File "./manage.py", line 8, in
from django.core.management import execute_from_command_line
ImportError: No module named core.management

Any ideas on how to fix this? I've completely uninstalled as much of the old install as I could think of.

Thanks,

Alex

Originally created by @ITBlogger on GitHub (Mar 13, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/262 Hi, I'm trying to upgrade from webvirtmgr 4.0 to the latest and when I run ./manage.py syncdb I get the following: Traceback (most recent call last): File "./manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named core.management Any ideas on how to fix this? I've completely uninstalled as much of the old install as I could think of. Thanks, Alex
kerem closed this issue 2026-02-27 16:38:25 +03:00
Author
Owner

@retspen commented on GitHub (Mar 14, 2014):

Django version?

<!-- gh-comment-id:37657296 --> @retspen commented on GitHub (Mar 14, 2014): Django version?
Author
Owner

@ITBlogger commented on GitHub (Mar 14, 2014):

1.5.5

<!-- gh-comment-id:37670008 --> @ITBlogger commented on GitHub (Mar 14, 2014): 1.5.5
Author
Owner

@ITBlogger commented on GitHub (Mar 14, 2014):

I've tried uninstalling and reinstalling django multiple times, still get same error

<!-- gh-comment-id:37670051 --> @ITBlogger commented on GitHub (Mar 14, 2014): I've tried uninstalling and reinstalling django multiple times, still get same error
Author
Owner

@ITBlogger commented on GitHub (Mar 17, 2014):

Any ideas?

Thanks,

Alex

<!-- gh-comment-id:37833180 --> @ITBlogger commented on GitHub (Mar 17, 2014): Any ideas? Thanks, Alex
Author
Owner

@retspen commented on GitHub (Mar 17, 2014):

What show this command?

$ echo $PYTHONPATH
$ python -c 'import django; print django.VERSION'

<!-- gh-comment-id:37857822 --> @retspen commented on GitHub (Mar 17, 2014): What show this command? $ echo $PYTHONPATH $ python -c 'import django; print django.VERSION'
Author
Owner

@ITBlogger commented on GitHub (Mar 17, 2014):

echo $PYTHONPATH returns a blank line
the 2nd command returns (1, 5, 5, 'final', 0)

<!-- gh-comment-id:37859000 --> @ITBlogger commented on GitHub (Mar 17, 2014): echo $PYTHONPATH returns a blank line the 2nd command returns (1, 5, 5, 'final', 0)
Author
Owner

@retspen commented on GitHub (Mar 17, 2014):

$ export PYTHONPATH=/usr/lib/python/site-packages # or path to site-package or dist-package
$ ./manage.py syncdb

<!-- gh-comment-id:37861018 --> @retspen commented on GitHub (Mar 17, 2014): $ export PYTHONPATH=/usr/lib/python/site-packages # or path to site-package or dist-package $ ./manage.py syncdb
Author
Owner

@ITBlogger commented on GitHub (Mar 17, 2014):

Ran

export PYTHONPATH=/usr/lib/python2.6/site-packages

./manage.py syncdb

Got same error:
Traceback (most recent call last):
File "./manage.py", line 8, in
from django.core.management import execute_from_command_line
ImportError: No module named core.management

echo $PYTHONPATH

(now returns)
/usr/lib/python2.6/site-packages

On Mon, Mar 17, 2014 at 12:43 PM, Anatoliy Guskov
notifications@github.comwrote:

$ export PYTHONPATH=/usr/lib/python/site-packages # or path to
site-package or dist-package
$ ./manage.py syncdb

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37861018
.

<!-- gh-comment-id:37861541 --> @ITBlogger commented on GitHub (Mar 17, 2014): Ran # export PYTHONPATH=/usr/lib/python2.6/site-packages # ./manage.py syncdb Got same error: Traceback (most recent call last): File "./manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named core.management # echo $PYTHONPATH (now returns) /usr/lib/python2.6/site-packages On Mon, Mar 17, 2014 at 12:43 PM, Anatoliy Guskov notifications@github.comwrote: > $ export PYTHONPATH=/usr/lib/python/site-packages # or path to > site-package or dist-package > $ ./manage.py syncdb > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37861018 > .
Author
Owner

@retspen commented on GitHub (Mar 17, 2014):

$ rm -Rf /usr/lib/python2.6/site-packages/django
$ pip install django==1.5.5

<!-- gh-comment-id:37866341 --> @retspen commented on GitHub (Mar 17, 2014): $ rm -Rf /usr/lib/python2.6/site-packages/django $ pip install django==1.5.5
Author
Owner

@ITBlogger commented on GitHub (Mar 17, 2014):

When I ran the pip install, I got:

Downloading/unpacking django==1.5.5
Running setup.py egg_info for package django
warning: no previously-included files matching 'pycache' found
under directory ''
warning: no previously-included files matching '
.py[co]' found under
directory ''
Installing collected packages: django
Running setup.py install for django
warning: no previously-included files matching 'pycache' found
under directory '
'
warning: no previously-included files matching '.py[co]' found under
directory '
'
changing mode of /usr/bin/django-admin.py to 755
Successfully installed django
Cleaning up...

Still get same error when I run ./manage.py syncdb

Thanks,

Alex

On Mon, Mar 17, 2014 at 1:32 PM, Anatoliy Guskov
notifications@github.comwrote:

$ rm -Rf /usr/lib/python2.6/site-packages/django
$ pip install django==1.5.5

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37866341
.

<!-- gh-comment-id:37869289 --> @ITBlogger commented on GitHub (Mar 17, 2014): When I ran the pip install, I got: Downloading/unpacking django==1.5.5 Running setup.py egg_info for package django warning: no previously-included files matching '**pycache**' found under directory '_' warning: no previously-included files matching '_.py[co]' found under directory '_' Installing collected packages: django Running setup.py install for django warning: no previously-included files matching '**pycache**' found under directory '_' warning: no previously-included files matching '_.py[co]' found under directory '_' changing mode of /usr/bin/django-admin.py to 755 Successfully installed django Cleaning up... Still get same error when I run ./manage.py syncdb Thanks, Alex On Mon, Mar 17, 2014 at 1:32 PM, Anatoliy Guskov notifications@github.comwrote: > $ rm -Rf /usr/lib/python2.6/site-packages/django > $ pip install django==1.5.5 > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37866341 > .
Author
Owner

@retspen commented on GitHub (Mar 18, 2014):

$ python

>>> import django
>>> from django.core.management import execute_from_command_line

It show errors?

<!-- gh-comment-id:37935010 --> @retspen commented on GitHub (Mar 18, 2014): $ python ``` >>> import django >>> from django.core.management import execute_from_command_line ``` It show errors?
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

Yep.

import django
from django.core.management import execute_from_command_line
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named core.management

--Alex

On Tue, Mar 18, 2014 at 6:58 AM, Anatoliy Guskov
notifications@github.comwrote:

$ python

import django
from django.core.management import execute_from_command_line

It show errors?

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37935010
.

<!-- gh-comment-id:37951255 --> @ITBlogger commented on GitHub (Mar 18, 2014): Yep. > > > import django > > > from django.core.management import execute_from_command_line > > > Traceback (most recent call last): > > > File "<stdin>", line 1, in <module> > > > ImportError: No module named core.management --Alex On Tue, Mar 18, 2014 at 6:58 AM, Anatoliy Guskov notifications@github.comwrote: > $ python > > import django > from django.core.management import execute_from_command_line > > It show errors? > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37935010 > .
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

In my research of this issue one thing that continually comes up is the
notion of activating an environment. We didn't need to do this with the
previous versions, but do we need to do this now?

Thanks,

Alex

On Tue, Mar 18, 2014 at 9:05 AM, Alex Scoble bloggingitguy@gmail.comwrote:

Yep.

import django
from django.core.management import execute_from_command_line
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named core.management

--Alex

On Tue, Mar 18, 2014 at 6:58 AM, Anatoliy Guskov <notifications@github.com

wrote:

$ python

import django
from django.core.management import execute_from_command_line

It show errors?

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37935010
.

<!-- gh-comment-id:37957211 --> @ITBlogger commented on GitHub (Mar 18, 2014): In my research of this issue one thing that continually comes up is the notion of activating an environment. We didn't need to do this with the previous versions, but do we need to do this now? Thanks, Alex On Tue, Mar 18, 2014 at 9:05 AM, Alex Scoble bloggingitguy@gmail.comwrote: > Yep. > > > > > import django > > > > from django.core.management import execute_from_command_line > > > > Traceback (most recent call last): > > > > File "<stdin>", line 1, in <module> > > > > ImportError: No module named core.management > > --Alex > > On Tue, Mar 18, 2014 at 6:58 AM, Anatoliy Guskov <notifications@github.com > > > wrote: > > > > $ python > > > > import django > > from django.core.management import execute_from_command_line > > > > It show errors? > > > > ## > > > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37935010 > > .
Author
Owner

@retspen commented on GitHub (Mar 18, 2014):

This need to do if you use virtualenv. Could you show django module:

$ ls -l /usr/lib/python2.6/site-package/django
$ ls -l /usr/lib/python2.6/site-package/django/core # if exist dirctory

<!-- gh-comment-id:37960113 --> @retspen commented on GitHub (Mar 18, 2014): This need to do if you use virtualenv. Could you show django module: $ ls -l /usr/lib/python2.6/site-package/django $ ls -l /usr/lib/python2.6/site-package/django/core # if exist dirctory
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

[root@dtlkvmts1 webvirtmgr]# ls -l /usr/lib/python2.6/site-packages/django/
total 68
drwxr-xr-x. 3 root root 4096 Mar 17 13:45 bin
drwxr-xr-x. 6 root root 4096 Mar 17 13:45 conf
drwxr-xr-x. 22 root root 4096 Mar 17 13:45 contrib
drwxr-xr-x. 9 root root 4096 Mar 17 13:45 core
drwxr-xr-x. 4 root root 4096 Mar 17 13:45 db
drwxr-xr-x. 2 root root 4096 Mar 17 13:45 dispatch
drwxr-xr-x. 3 root root 4096 Mar 17 13:45 forms
drwxr-xr-x. 2 root root 4096 Mar 17 13:45 http
-rwxr-xr-x. 1 root root 269 Oct 30 13:25 init.py
-rwxr-xr-x. 1 root root 464 Mar 17 13:45 init.pyc
drwxr-xr-x. 2 root root 4096 Mar 17 13:45 middleware
drwxr-xr-x. 2 root root 4096 Mar 17 13:45 shortcuts
drwxr-xr-x. 3 root root 4096 Mar 17 13:45 template
drwxr-xr-x. 2 root root 4096 Mar 17 13:45 templatetags
drwxr-xr-x. 2 root root 4096 Mar 17 13:45 test
drwxr-xr-x. 5 root root 4096 Mar 17 13:45 utils
drwxr-xr-x. 4 root root 4096 Mar 17 13:45 views

On Tue, Mar 18, 2014 at 10:12 AM, Anatoliy Guskov
notifications@github.comwrote:

This need to do if you use virtualenv. Could you show django module:

$ ls -l /usr/lib/python2.6/site-package/django

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37960113
.

<!-- gh-comment-id:37961389 --> @ITBlogger commented on GitHub (Mar 18, 2014): [root@dtlkvmts1 webvirtmgr]# ls -l /usr/lib/python2.6/site-packages/django/ total 68 drwxr-xr-x. 3 root root 4096 Mar 17 13:45 bin drwxr-xr-x. 6 root root 4096 Mar 17 13:45 conf drwxr-xr-x. 22 root root 4096 Mar 17 13:45 contrib drwxr-xr-x. 9 root root 4096 Mar 17 13:45 core drwxr-xr-x. 4 root root 4096 Mar 17 13:45 db drwxr-xr-x. 2 root root 4096 Mar 17 13:45 dispatch drwxr-xr-x. 3 root root 4096 Mar 17 13:45 forms drwxr-xr-x. 2 root root 4096 Mar 17 13:45 http -rwxr-xr-x. 1 root root 269 Oct 30 13:25 **init**.py -rwxr-xr-x. 1 root root 464 Mar 17 13:45 **init**.pyc drwxr-xr-x. 2 root root 4096 Mar 17 13:45 middleware drwxr-xr-x. 2 root root 4096 Mar 17 13:45 shortcuts drwxr-xr-x. 3 root root 4096 Mar 17 13:45 template drwxr-xr-x. 2 root root 4096 Mar 17 13:45 templatetags drwxr-xr-x. 2 root root 4096 Mar 17 13:45 test drwxr-xr-x. 5 root root 4096 Mar 17 13:45 utils drwxr-xr-x. 4 root root 4096 Mar 17 13:45 views On Tue, Mar 18, 2014 at 10:12 AM, Anatoliy Guskov notifications@github.comwrote: > This need to do if you use virtualenv. Could you show django module: > > $ ls -l /usr/lib/python2.6/site-package/django > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37960113 > .
Author
Owner

@retspen commented on GitHub (Mar 18, 2014):

Do you have installed any other python3 or django project? Selinux status?

<!-- gh-comment-id:37963974 --> @retspen commented on GitHub (Mar 18, 2014): Do you have installed any other python3 or django project? Selinux status?
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

No other Python is installed. No other django project is installed on the
box I'm using. selinux is set to permissive.

On Tue, Mar 18, 2014 at 10:41 AM, Anatoliy Guskov
notifications@github.comwrote:

Do you have installed any other python3 or django project? Selinux status?

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37963974
.

<!-- gh-comment-id:37966908 --> @ITBlogger commented on GitHub (Mar 18, 2014): No other Python is installed. No other django project is installed on the box I'm using. selinux is set to permissive. On Tue, Mar 18, 2014 at 10:41 AM, Anatoliy Guskov notifications@github.comwrote: > Do you have installed any other python3 or django project? Selinux status? > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37963974 > .
Author
Owner

@schmitch commented on GitHub (Mar 18, 2014):

Did you tried to run python manage.py syncdbinstead of the ./manage.pysometimes this could help against env problems.

<!-- gh-comment-id:37968824 --> @schmitch commented on GitHub (Mar 18, 2014): Did you tried to run `python manage.py syncdb`instead of the `./manage.py`sometimes this could help against env problems.
Author
Owner

@retspen commented on GitHub (Mar 18, 2014):

And you can try to change path in python in file manage.py:
#!/usr/bin/env python to #!/usr/bin/python

<!-- gh-comment-id:37976537 --> @retspen commented on GitHub (Mar 18, 2014): And you can try to change path in python in file manage.py: #!/usr/bin/env python to #!/usr/bin/python
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

Yeah, tried both of those and no change.

By the way, I can't even run django-admin.py I get similar error (No module
named core)

On Tue, Mar 18, 2014 at 12:23 PM, Anatoliy Guskov
notifications@github.comwrote:

And you can try to change path in python in file manage.py:
#!/usr/bin/env python to #!/usr/bin/python

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37976537
.

<!-- gh-comment-id:37977934 --> @ITBlogger commented on GitHub (Mar 18, 2014): Yeah, tried both of those and no change. By the way, I can't even run django-admin.py I get similar error (No module named core) On Tue, Mar 18, 2014 at 12:23 PM, Anatoliy Guskov notifications@github.comwrote: > And you can try to change path in python in file manage.py: > #!/usr/bin/env python to #!/usr/bin/python > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37976537 > .
Author
Owner

@retspen commented on GitHub (Mar 18, 2014):

You can try new trick with virtualenv:

  1. $ sudo pip uninstall django
  2. $ sudo yum install python-virtualenv
  3. $ cd /var/www/webvirtmgr
  4. $ virtualenv --system-site-packages venv
  5. $ source venv/bin/activate
  6. $ pip install django==1.5.5
  7. $ sudo ./manage.py syncdb # return to /usr/bin/env python in manage.py
<!-- gh-comment-id:37982252 --> @retspen commented on GitHub (Mar 18, 2014): You can try new trick with virtualenv: 1. $ sudo pip uninstall django 2. $ sudo yum install python-virtualenv 3. $ cd /var/www/webvirtmgr 4. $ virtualenv --system-site-packages venv 5. $ source venv/bin/activate 6. $ pip install django==1.5.5 7. $ sudo ./manage.py syncdb # return to /usr/bin/env python in manage.py
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

Thanks...that worked.

On Tue, Mar 18, 2014 at 1:17 PM, Anatoliy Guskov
notifications@github.comwrote:

You can try new trick with virtualenv:

  1. $ sudo pip uninstall django
  2. $ sudo yum install python-virtualenv
  3. $ cd /var/www/webvirtmgr
  4. $ virtualenv --system-site-packages vent
  5. $ source venv/bin/activate
  6. $ pip install django==1.5.5
  7. $ sudo ./manage.py syncdb # return to /usr/bin/env python in manage.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37982252
.

<!-- gh-comment-id:37983946 --> @ITBlogger commented on GitHub (Mar 18, 2014): Thanks...that worked. On Tue, Mar 18, 2014 at 1:17 PM, Anatoliy Guskov notifications@github.comwrote: > You can try new trick with virtualenv: > 1. $ sudo pip uninstall django > 2. $ sudo yum install python-virtualenv > 3. $ cd /var/www/webvirtmgr > 4. $ virtualenv --system-site-packages vent > 5. $ source venv/bin/activate > 6. $ pip install django==1.5.5 > 7. $ sudo ./manage.py syncdb # return to /usr/bin/env python in manage.py > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37982252 > .
Author
Owner

@retspen commented on GitHub (Mar 18, 2014):

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py
<!-- gh-comment-id:37985286 --> @retspen commented on GitHub (Mar 18, 2014): Good news! Change line in file supervisor.conf for run automatically: ``` command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py ``` to ``` command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py ```
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

Yeah, that seemed to happen automatically.

Now I'm getting the dreaded 502 bad gateway error when I try to access the
web site. On the server these errors are showing up:

2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: Connection
refused) while connecting to upstream, client: , server:
dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: "
http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org"

I can connect just fine when running ./manage.py runserver 0:8000

Ideas?

Thanks so much for your help so far.

On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov
notifications@github.comwrote:

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286
.

<!-- gh-comment-id:37990132 --> @ITBlogger commented on GitHub (Mar 18, 2014): Yeah, that seemed to happen automatically. Now I'm getting the dreaded 502 bad gateway error when I try to access the web site. On the server these errors are showing up: 2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: Connection refused) while connecting to upstream, client: <clientip>, server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: " http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org" I can connect just fine when running ./manage.py runserver 0:8000 Ideas? Thanks so much for your help so far. On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov notifications@github.comwrote: > Good news! Change line in file supervisor.conf for run automatically: > > command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > to > > command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286 > .
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c
/var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to server
just fine.

/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py
run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works

On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yeah, that seemed to happen automatically.

Now I'm getting the dreaded 502 bad gateway error when I try to access the
web site. On the server these errors are showing up:

2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: Connection
refused) while connecting to upstream, client: , server:
dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: "
http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org"

I can connect just fine when running ./manage.py runserver 0:8000

Ideas?

Thanks so much for your help so far.

On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov <notifications@github.com

wrote:

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286
.

<!-- gh-comment-id:37991795 --> @ITBlogger commented on GitHub (Mar 18, 2014): gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to server just fine. /var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote: > Yeah, that seemed to happen automatically. > > Now I'm getting the dreaded 502 bad gateway error when I try to access the > web site. On the server these errors are showing up: > > 2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: Connection > refused) while connecting to upstream, client: <clientip>, server: > dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: " > http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org" > > I can connect just fine when running ./manage.py runserver 0:8000 > > Ideas? > > Thanks so much for your help so far. > > On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov <notifications@github.com > > > wrote: > > > > Good news! Change line in file supervisor.conf for run automatically: > > > > command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > to > > > > command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > ## > > > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286 > > .
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr
show up?

Also, your install says to put the lines in /etc/supervisor.conf shouldn't
it be added to /etc/supervisord.conf?

On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote:

gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c
/var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to server
just fine.

/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py
run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works

On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yeah, that seemed to happen automatically.

Now I'm getting the dreaded 502 bad gateway error when I try to access
the web site. On the server these errors are showing up:

2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: Connection
refused) while connecting to upstream, client: , server:
dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: "
http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org"

I can connect just fine when running ./manage.py runserver 0:8000

Ideas?

Thanks so much for your help so far.

On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov <
notifications@github.com> wrote:

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286
.

<!-- gh-comment-id:37992515 --> @ITBlogger commented on GitHub (Mar 18, 2014): When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr show up? Also, your install says to put the lines in /etc/supervisor.conf shouldn't it be added to /etc/supervisord.conf? On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote: > gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c > /var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to server > just fine. > > /var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py > run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works > > On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > Yeah, that seemed to happen automatically. > > > > Now I'm getting the dreaded 502 bad gateway error when I try to access > > the web site. On the server these errors are showing up: > > > > 2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: Connection > > refused) while connecting to upstream, client: <clientip>, server: > > dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: " > > http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org" > > > > I can connect just fine when running ./manage.py runserver 0:8000 > > > > Ideas? > > > > Thanks so much for your help so far. > > > > On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov < > > notifications@github.com> wrote: > > > > > Good news! Change line in file supervisor.conf for run automatically: > > > > > > command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > to > > > > > > command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > ## > > > > > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286 > > > .
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

Yep, when I moved the stuff from /etc/supervisor.conf to
/etc/supervisord.conf and restarted supervisord service, I can now access
web server.

Looks like the docs may need to be updated for CentOS/RHEL.

On Tue, Mar 18, 2014 at 2:43 PM, Alex Scoble bloggingitguy@gmail.comwrote:

When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr
show up?

Also, your install says to put the lines in /etc/supervisor.conf shouldn't
it be added to /etc/supervisord.conf?

On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote:

gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c
/var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to server
just fine.

/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py
run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works

On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yeah, that seemed to happen automatically.

Now I'm getting the dreaded 502 bad gateway error when I try to access
the web site. On the server these errors are showing up:

2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111:
Connection refused) while connecting to upstream, client: ,
server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: "
http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org"

I can connect just fine when running ./manage.py runserver 0:8000

Ideas?

Thanks so much for your help so far.

On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov <
notifications@github.com> wrote:

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286
.

<!-- gh-comment-id:37992755 --> @ITBlogger commented on GitHub (Mar 18, 2014): Yep, when I moved the stuff from /etc/supervisor.conf to /etc/supervisord.conf and restarted supervisord service, I can now access web server. Looks like the docs may need to be updated for CentOS/RHEL. On Tue, Mar 18, 2014 at 2:43 PM, Alex Scoble bloggingitguy@gmail.comwrote: > When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr > show up? > > Also, your install says to put the lines in /etc/supervisor.conf shouldn't > it be added to /etc/supervisord.conf? > > On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c > > /var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to server > > just fine. > > > > /var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py > > run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works > > > > On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > > > Yeah, that seemed to happen automatically. > > > > > > Now I'm getting the dreaded 502 bad gateway error when I try to access > > > the web site. On the server these errors are showing up: > > > > > > 2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: > > > Connection refused) while connecting to upstream, client: <clientip>, > > > server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: " > > > http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org" > > > > > > I can connect just fine when running ./manage.py runserver 0:8000 > > > > > > Ideas? > > > > > > Thanks so much for your help so far. > > > > > > On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov < > > > notifications@github.com> wrote: > > > > > > > Good news! Change line in file supervisor.conf for run automatically: > > > > > > > > command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > > > to > > > > > > > > command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > > > ## > > > > > > > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286 > > > > .
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

I fixed the docs. :D Thanks!

On Tue, Mar 18, 2014 at 2:45 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yep, when I moved the stuff from /etc/supervisor.conf to
/etc/supervisord.conf and restarted supervisord service, I can now access
web server.

Looks like the docs may need to be updated for CentOS/RHEL.

On Tue, Mar 18, 2014 at 2:43 PM, Alex Scoble bloggingitguy@gmail.comwrote:

When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr
show up?

Also, your install says to put the lines in /etc/supervisor.conf
shouldn't it be added to /etc/supervisord.conf?

On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote:

gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c
/var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to
server just fine.

/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py
run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works

On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yeah, that seemed to happen automatically.

Now I'm getting the dreaded 502 bad gateway error when I try to access
the web site. On the server these errors are showing up:

2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111:
Connection refused) while connecting to upstream, client: ,
server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: "
http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org"

I can connect just fine when running ./manage.py runserver 0:8000

Ideas?

Thanks so much for your help so far.

On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov <
notifications@github.com> wrote:

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286
.

<!-- gh-comment-id:37993215 --> @ITBlogger commented on GitHub (Mar 18, 2014): I fixed the docs. :D Thanks! On Tue, Mar 18, 2014 at 2:45 PM, Alex Scoble bloggingitguy@gmail.comwrote: > Yep, when I moved the stuff from /etc/supervisor.conf to > /etc/supervisord.conf and restarted supervisord service, I can now access > web server. > > Looks like the docs may need to be updated for CentOS/RHEL. > > On Tue, Mar 18, 2014 at 2:43 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr > > show up? > > > > Also, your install says to put the lines in /etc/supervisor.conf > > shouldn't it be added to /etc/supervisord.conf? > > > > On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > > > gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c > > > /var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to > > > server just fine. > > > > > > /var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py > > > run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works > > > > > > On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > > > > > Yeah, that seemed to happen automatically. > > > > > > > > Now I'm getting the dreaded 502 bad gateway error when I try to access > > > > the web site. On the server these errors are showing up: > > > > > > > > 2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: > > > > Connection refused) while connecting to upstream, client: <clientip>, > > > > server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: " > > > > http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org" > > > > > > > > I can connect just fine when running ./manage.py runserver 0:8000 > > > > > > > > Ideas? > > > > > > > > Thanks so much for your help so far. > > > > > > > > On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov < > > > > notifications@github.com> wrote: > > > > > > > > > Good news! Change line in file supervisor.conf for run automatically: > > > > > > > > > > command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > > > > > to > > > > > > > > > > command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > > > > > ## > > > > > > > > > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286 > > > > > .
Author
Owner

@ITBlogger commented on GitHub (Mar 18, 2014):

For using SSH keys for authentication, I'm guessing that the key should be
created without a password, is that correct?

On Tue, Mar 18, 2014 at 2:49 PM, Alex Scoble bloggingitguy@gmail.comwrote:

I fixed the docs. :D Thanks!

On Tue, Mar 18, 2014 at 2:45 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yep, when I moved the stuff from /etc/supervisor.conf to
/etc/supervisord.conf and restarted supervisord service, I can now access
web server.

Looks like the docs may need to be updated for CentOS/RHEL.

On Tue, Mar 18, 2014 at 2:43 PM, Alex Scoble bloggingitguy@gmail.comwrote:

When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr
show up?

Also, your install says to put the lines in /etc/supervisor.conf
shouldn't it be added to /etc/supervisord.conf?

On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote:

gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c
/var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to
server just fine.

/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py
run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works

On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote:

Yeah, that seemed to happen automatically.

Now I'm getting the dreaded 502 bad gateway error when I try to access
the web site. On the server these errors are showing up:

2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111:
Connection refused) while connecting to upstream, client: ,
server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream:
"http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org"

I can connect just fine when running ./manage.py runserver 0:8000

Ideas?

Thanks so much for your help so far.

On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov <
notifications@github.com> wrote:

Good news! Change line in file supervisor.conf for run automatically:

command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

to

command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286
.

<!-- gh-comment-id:37996014 --> @ITBlogger commented on GitHub (Mar 18, 2014): For using SSH keys for authentication, I'm guessing that the key should be created without a password, is that correct? On Tue, Mar 18, 2014 at 2:49 PM, Alex Scoble bloggingitguy@gmail.comwrote: > I fixed the docs. :D Thanks! > > On Tue, Mar 18, 2014 at 2:45 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > Yep, when I moved the stuff from /etc/supervisor.conf to > > /etc/supervisord.conf and restarted supervisord service, I can now access > > web server. > > > > Looks like the docs may need to be updated for CentOS/RHEL. > > > > On Tue, Mar 18, 2014 at 2:43 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > > > When I do 'supervisorctl status' nothing shows up. Shouldn't webvirtmgr > > > show up? > > > > > > Also, your install says to put the lines in /etc/supervisor.conf > > > shouldn't it be added to /etc/supervisord.conf? > > > > > > On Tue, Mar 18, 2014 at 2:36 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > > > > > gunicorn wasn't started. When I manually do ./manage.py run_gunicorn -c > > > > /var/www/webvirtmgr/conf/gunicorn.conf.py I am able to connect to > > > > server just fine. > > > > > > > > /var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py > > > > run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py also works > > > > > > > > On Tue, Mar 18, 2014 at 2:22 PM, Alex Scoble bloggingitguy@gmail.comwrote: > > > > > > > > > Yeah, that seemed to happen automatically. > > > > > > > > > > Now I'm getting the dreaded 502 bad gateway error when I try to access > > > > > the web site. On the server these errors are showing up: > > > > > > > > > > 2014/03/18 14:05:13 [error] 10673#0: *5 connect() failed (111: > > > > > Connection refused) while connecting to upstream, client: <clientip>, > > > > > server: dtlkvmts1.xxxx.xxxx.org, request: "GET / HTTP/1.1", upstream: > > > > > "http://127.0.0.1:8000/", host: "dtlkvmts1.xxxx.xxxx.org" > > > > > > > > > > I can connect just fine when running ./manage.py runserver 0:8000 > > > > > > > > > > Ideas? > > > > > > > > > > Thanks so much for your help so far. > > > > > > > > > > On Tue, Mar 18, 2014 at 1:45 PM, Anatoliy Guskov < > > > > > notifications@github.com> wrote: > > > > > > > > > > > Good news! Change line in file supervisor.conf for run automatically: > > > > > > > > > > > > command=/usr/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > > > > > > > to > > > > > > > > > > > > command=/var/www/webvirtmgr/venv/bin/python /var/www/webvirtmgr/manage.py run_gunicorn -c /var/www/webvirtmgr/conf/gunicorn.conf.py > > > > > > > > > > > > ## > > > > > > > > > > > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-37985286 > > > > > > .
Author
Owner

@retspen commented on GitHub (Mar 19, 2014):

Yes, it is.

<!-- gh-comment-id:38018151 --> @retspen commented on GitHub (Mar 19, 2014): Yes, it is.
Author
Owner

@ITBlogger commented on GitHub (Apr 11, 2014):

I'm having similar problems getting webvirtmgr-novnc to run. When I start the service it crashes and when I cat the reason file in the python dump it says "webvirtmgr-novnc:22::ImportError: No module named django"

/var/www/webvirtmgr/console/webvirtmgr-novnc is not set up to use the venv python environment that we set up.

How do I do that?

Thanks,

Alex

<!-- gh-comment-id:40227672 --> @ITBlogger commented on GitHub (Apr 11, 2014): I'm having similar problems getting webvirtmgr-novnc to run. When I start the service it crashes and when I cat the reason file in the python dump it says "webvirtmgr-novnc:22:<module>:ImportError: No module named django" /var/www/webvirtmgr/console/webvirtmgr-novnc is not set up to use the venv python environment that we set up. How do I do that? Thanks, Alex
Author
Owner

@retspen commented on GitHub (Apr 11, 2014):

You need to change in file webvirtmgr-novnc:

#!/usr/bin/env python TO #!/var/www/webvirtmgr/venv/bin/python

<!-- gh-comment-id:40239606 --> @retspen commented on GitHub (Apr 11, 2014): You need to change in file webvirtmgr-novnc: #!/usr/bin/env python TO #!/var/www/webvirtmgr/venv/bin/python
Author
Owner

@ITBlogger commented on GitHub (Apr 11, 2014):

Thanks, I should have caught that.

Now it is returning "webvirtmgr-novnc:26::ImportError: No module
named novnc"

--Alex

On Fri, Apr 11, 2014 at 11:40 AM, Anatoliy Guskov
notifications@github.comwrote:

You need to change in file webvirtmgr-novnc:

#!/usr/bin/env python TO #!/var/www/webvirtmgr/venv/bin/python

Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-40239606
.

<!-- gh-comment-id:40241177 --> @ITBlogger commented on GitHub (Apr 11, 2014): Thanks, I should have caught that. Now it is returning "webvirtmgr-novnc:26:<module>:ImportError: No module named novnc" --Alex On Fri, Apr 11, 2014 at 11:40 AM, Anatoliy Guskov notifications@github.comwrote: > You need to change in file webvirtmgr-novnc: > > #!/usr/bin/env python TO #!/var/www/webvirtmgr/venv/bin/python > > ## > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-40239606 > .
Author
Owner

@ITBlogger commented on GitHub (Apr 14, 2014):

Any ideas on why the novnc module can't be found?

Thanks,

Alex

On Fri, Apr 11, 2014 at 11:56 AM, Alex Scoble bloggingitguy@gmail.comwrote:

Thanks, I should have caught that.

Now it is returning "webvirtmgr-novnc:26::ImportError: No module
named novnc"

--Alex

On Fri, Apr 11, 2014 at 11:40 AM, Anatoliy Guskov <
notifications@github.com> wrote:

You need to change in file webvirtmgr-novnc:

#!/usr/bin/env python TO #!/var/www/webvirtmgr/venv/bin/python


Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-40239606
.

<!-- gh-comment-id:40411859 --> @ITBlogger commented on GitHub (Apr 14, 2014): Any ideas on why the novnc module can't be found? Thanks, Alex On Fri, Apr 11, 2014 at 11:56 AM, Alex Scoble bloggingitguy@gmail.comwrote: > Thanks, I should have caught that. > > Now it is returning "webvirtmgr-novnc:26:<module>:ImportError: No module > named novnc" > > --Alex > > On Fri, Apr 11, 2014 at 11:40 AM, Anatoliy Guskov < > notifications@github.com> wrote: > > > You need to change in file webvirtmgr-novnc: > > > > #!/usr/bin/env python TO #!/var/www/webvirtmgr/venv/bin/python > > > > — > > Reply to this email directly or view it on GitHubhttps://github.com/retspen/webvirtmgr/issues/262#issuecomment-40239606 > > .
Author
Owner

@retspen commented on GitHub (Apr 15, 2014):

$ sudo yum install gcc
$ source /var/www/webvirtmgr/venv/bin/activate
$ pip install websockify

<!-- gh-comment-id:40467661 --> @retspen commented on GitHub (Apr 15, 2014): $ sudo yum install gcc $ source /var/www/webvirtmgr/venv/bin/activate $ pip install websockify
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#210
No description provided.