IPython console doesn't start in some cases

[Christian Münker]

Using WinPython 2.7.3.3 and Spyder 2.2.0rc under Windows7 32bit, Spyder runs incredibly stable on my system and I'm really happy with the software.

One little hiccup I get from time to time is that I can't start a new IPython console from the menu ('Interpreters -> Open an IPython console'). A new IPython Tab appears in the Tab <Console> but it is greyed out (see screenshot), hasn't got a Kernel ID and the window only contains the message

Assertion failed: Permission denied (..\..\..\src\err.cpp:247)

I haven't been able yet to track down the conditions under which this error occurs, it might be related to switching the IPython graphic mode using

Tools -> Preferences -> IPython -> Graphics -> Backend -> e.g. from Inline to Automatic

Switching to e.g. Qt usually allows to start a new IPython console again, so, not really annoying.

Cheers,

Christian
 

[Dave Hirschfeld]

I've seen this with 64bit WinPython as well. I'm not sure it's always the same file err.cpp but it's always a permission denied error. It is however sporadic and the way I found to work around it is to simply try opening multiple IPython consoles until one succeeds. 

-Dave

 

[Carlos Córdoba]

Hi Christian,

I'm glad you are enjoying our latest release. About your problem: a
quick google search seems to point to a problem with zmq (the library
for interprocess communication used by IPython). See this link:

https://zeromq.jira.com/browse/LIBZMQ-279

The proposed solution in that bug report is:

"The problem could be solved by fixing the port used for sockepair
emulation and configuring the firewall so that local connections on
given port are allowed."

Cheers,
Carlos

El 18/04/13 14:53, Christian Münker escribió:

> --
> You received this message because you are subscribed to the Google
> Groups "spyder" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to spyderlib+...@googlegroups.com.
> To post to this group, send email to spyd...@googlegroups.com.
> Visit this group at http://groups.google.com/group/spyderlib?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Christian Münker]

Hi Carlos,

thanx for the idea! I'll take a look at it, although this is slightly above my head - for a start, I wouldn't know how to fix the port for socketpair emulation. At least, now I know what's pyzmq for ... Configuring the firewall should be easy in comparison.

I'll try disabling the firewall (currently, I'm just using the Windows firewall with default settings) and will post about the results.

Cheers,

Christian

[Christian Münker]

Carlos was right: adding a new rule for the Windows firewall did the job:

Windows Firewall -> Extended Settings -> Incoming Rules -> New Rule
   Allow connection
   Program: <path to spyder executable>
   Protocol and Ports: TCP
   IP-Adress incoming and outgoing port: 127.0.0.1

Maybe the rule could be constrained further, but I'm not a network expert.

You do need Admin rights under Windows 7 to change firewall setting, so this might be a problem for some users at their workplace.

Cheers,

Christian

[Carlos Córdoba]

Great! I'm really glad you figured it out by yourself what to do in this case.

Cheers,
Carlos

El 14/05/13 12:59, Christian Münker escribió:

[Dave Hirschfeld]

Unfortunately at our work some firewall settings can't be changed by the user (even with admin rights). My previous solution of simply directing people to try several times until it works seems to no longer work as after a single failure the "Open an IPython console" option is now greyed out & inactive. Was this an intended change? Can it be changed back so you can happily try to open an IPython console as often as you like?

Thanks,

Dave

[Jed Ludlow]

On Monday, June 10, 2013 9:07:11 AM UTC-6, Dave Hirschfeld wrote:

Unfortunately at our work some firewall settings can't be changed by the user (even with admin rights). My previous solution of simply directing people to try several times until it works seems to no longer work as after a single failure the "Open an IPython console" option is now greyed out & inactive. Was this an intended change? Can it be changed back so you can happily try to open an IPython console as often as you like? 

 

 

Hi, Dave.

The only way I know of to make the IPython console stuff grey out is if the IPython console plugin itself is not visible. Check to see that View >  Windows and toolbars > IPython console is checked active.

Jed

[B Ware]

I'm having this error as well. I first encountered it in ipython notebook, but it seems to show in spyder as well. I'm running the current (32 bit) anaconda installation of python, ipython, and spyder. The error message is "Assertion failed: Permission denied (..\..\..\src\err.cpp:247)" and it causes (in ipython notebook) the kernel to restart and shutdown continuously a number of times before sometimes eventually working if I wait long enough.

For me, the error still occurs even with Windows Firewall turned off. 

Anyone learn anything else about this error? I can't even seem to find the source file, or any more details about how it is triggered, except for this discussion. 

Thanks for your help

[Carlos Córdoba]

What is your Windows version? I recall reading somewhere that this error appears only on WinXP.

Cheers,
Carlos

El 06/10/13 00:15, B Ware escribió:

--

You received this message because you are subscribed to the Google Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spyderlib+...@googlegroups.com.
To post to this group, send email to spyd...@googlegroups.com.

Visit this group at http://groups.google.com/group/spyderlib.

[Christian Münker]

I had this problem running Windows 7, but as I posted earlier, it disappeared I when added an exception to the Windows firewall. After a recent hard disk crash I installed the latest Anaconda version (1.7.0) as well, but for some reason I didn't need to tweak the firewall this time. One issue that might be related (or not) is that I cannot open IPython notebooks via the launcher: The IPython dashboard uses the program directory as its working directory and fails because it has no write access for the autosave files (new in IPython 1.0). The workaround in this case is to put a link in your working directory and start the IPython notebook from there.

Cheers,

Christian