Page MenuHomePhabricator

Python can't be started at tools-bastion-02/03
Closed, InvalidPublic

Description

Python can't be started at tools-bastion-02 and tools-bastion-03. See https://cs.wikipedia.org/wiki/Wikipedista:Martin_Urbanec/Tool_Labs_Python for output.

Event Timeline

Urbanecm triaged this task as Unbreak Now! priority.EditedJun 29 2016, 9:27 PM

This is breaking usage of running one-time scripts based on PWB for example.

Urbanecm renamed this task from Python can't be started at tools-bastion-02 to Python can't be started at tools-bastion-02/03.Jun 29 2016, 9:29 PM
Urbanecm updated the task description. (Show Details)

Something you are doing is odd maybe.

rush@tools-bastion-03:~$ python
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

which python
/usr/bin/python

What does type -a python output for you on either of the bastions? It looks like you have aliased python to something non-standard based on the "Python 3.2.3" output you got on tools-exec-1207.

Thanks. My virtualenv caused it. Its in /homr/urbanecm/envbak. But I'm sure that it worked a few days ago...