Forum Discussion

Lance_53367's avatar
Lance_53367
Icon for Nimbostratus rankNimbostratus
Mar 19, 2011

PyControl install with no direct Internet Connection

I have a server in a secure network that has no direct Internet connection which I'm trying to deploy pycontrol. I do have access to a proxy. Is there a way to do this?

 

 

suds was installed fine but when I do the setup on the pycontrol I get the following error.

 

 

 

Searching for suds>=0.3.9

 

Reading http://pypi.python.org/simple/suds/

 

Download error: (101, 'Network is unreachable') -- Some packages may not be found!

 

Couldn't retrieve index page for 'suds'

 

Scanning index of all packages (this may take a while)

 

Reading http://pypi.python.org/simple/

 

Download error: (101, 'Network is unreachable') -- Some packages may not be found!

 

No local packages or download links found for suds>=0.3.9

 

Best match: None

 

 

 

 

 

 

4 Replies

  • That error indicates that the python interpreter used to install pycontrol either couldn't find suds or is looking for a version higher than what is there (>=0.3.9). As a result it's trying to go out to pypi and it's unable to (Network is unreachable). If you're certain that this isn't an issue, you could install pycontrol via "setup.py install"

     

     

    -Matt
  • I was able to add Internet network connectivity to the box and got pycontrol installed but still having a slight problem. I have installed suds.

     

     

    [n7netutil01 python-suds-0.4]$ python2.7

     

     

    Python 2.7.1 (r271:86832, Apr 5 2011, 13:47:31)

     

    [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2

     

    Type "help", "copyright", "credits" or "license" for more information.

     

    >>> import suds

     

    >>> print suds.__version__

     

    0.4

     

    >>> print suds.__build__

     

    GA R699-20100913

     

     

     

    Then I go to install pycontrol.

     

     

     

    [n7netutil01 trunk]$ sudo python2.7 setup.py install

     

    running install

     

    running bdist_egg

     

    running egg_info

     

    writing requirements to pycontrol.egg-info/requires.txt

     

    writing pycontrol.egg-info/PKG-INFO

     

    writing top-level names to pycontrol.egg-info/top_level.txt

     

    writing dependency_links to pycontrol.egg-info/dependency_links.txt

     

    writing manifest file 'pycontrol.egg-info/SOURCES.txt'

     

    installing library code to build/bdist.linux-x86_64/egg

     

    running install_lib

     

    running build_py

     

    creating build/bdist.linux-x86_64/egg

     

    creating build/bdist.linux-x86_64/egg/pycontrol

     

    copying build/lib/pycontrol/setup.py -> build/bdist.linux-x86_64/egg/pycontrol

     

    copying build/lib/pycontrol/__init__.py -> build/bdist.linux-x86_64/egg/pycontrol

     

    copying build/lib/pycontrol/pycontrol.py -> build/bdist.linux-x86_64/egg/pycontrol

     

    copying build/lib/pycontrol/utils.py -> build/bdist.linux-x86_64/egg/pycontrol

     

    byte-compiling build/bdist.linux-x86_64/egg/pycontrol/setup.py to setup.pyc

     

    byte-compiling build/bdist.linux-x86_64/egg/pycontrol/__init__.py to __init__.pyc

     

    byte-compiling build/bdist.linux-x86_64/egg/pycontrol/pycontrol.py to pycontrol.pyc

     

    byte-compiling build/bdist.linux-x86_64/egg/pycontrol/utils.py to utils.pyc

     

    creating build/bdist.linux-x86_64/egg/EGG-INFO

     

    copying pycontrol.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO

     

    copying pycontrol.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO

     

    copying pycontrol.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO

     

    copying pycontrol.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO

     

    copying pycontrol.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO

     

    zip_safe flag not set; analyzing archive contents...

     

    creating 'dist/pycontrol-2.0.1a-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it

     

    removing 'build/bdist.linux-x86_64/egg' (and everything under it)

     

    Processing pycontrol-2.0.1a-py2.7.egg

     

    Removing /opt/python2.7.1/lib/python2.7/site-packages/pycontrol-2.0.1a-py2.7.egg

     

    Copying pycontrol-2.0.1a-py2.7.egg to /opt/python2.7.1/lib/python2.7/site-packages

     

    pycontrol 2.0.1a is already the active version in easy-install.pth

     

     

     

    Installed /opt/python2.7.1/lib/python2.7/site-packages/pycontrol-2.0.1a-py2.7.egg

     

    Processing dependencies for pycontrol==2.0.1a

     

    Searching for suds==0.4

     

    Best match: suds 0.4

     

    Processing suds-0.4-py2.7.egg

     

    suds 0.4 is already the active version in easy-install.pth

     

     

     

    Using /opt/python2.7.1/lib/python2.7/site-packages/suds-0.4-py2.7.egg

     

    Finished processing dependencies for pycontrol==2.0.1a

     

    [n7netutil01 trunk]$

     

     

     

     

    That looks like it installed fine. But then once I enter python it 's acts like suds is not installed.

     

     

     

    [n7netutil01 trunk]$ python2.7

     

    Python 2.7.1 (r271:86832, Apr 5 2011, 13:47:31)

     

    [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2

     

    Type "help", "copyright", "credits" or "license" for more information.

     

    >>> import suds

     

    Traceback (most recent call last):

     

    File "", line 1, in

     

    ImportError: No module named suds

     

    >>> import pycontrol.pycontrol as pc

     

    Traceback (most recent call last):

     

    File "", line 1, in

     

    File "pycontrol/__init__.py", line 32, in

     

    import suds

     

    ImportError: No module named suds

     

    >>>

     

     

     

     

     

     

    Thanks for the other response.

     

     

     

     

     

     

     

     

     

  • Weird. Obviously it looks like something is still going on with your path, but I see what you mean - it looks like it went on fine. It may be worth confirming all this by poking around at sys.path, where you should see suds for sure. Post back your results, and good luck.

     

     

    -Matt

     

  • It was a permissions issue. I was doing the install using sudo but once I sudo to root and then did the install it fix the issue. Thanks for the input.