IPython Permission Denied - permission-denied

I'm encountering a problem starting an ipython notebook or an ipython console in spyder that results in the error message "Assertion failed: Permission denied (......\src\err.cpp:247) and (in ipython notebook) the kernel endlessly restarts.
I'm using Anaconda installation of python on Windows 7, and have the same problems with both ipython 1.1 and ipython 1.0. I did not have this problem when I ran ipython versions before 1.0, before I switched to Anaconda.
A google search finds another instance of this problem, which suggests that its due to interactions with PyZMQ and a firewall. I've tried adding specific exceptions for python and ipython to my firewall, and turning the firewall off completely, with no change. I can run ipython in command line, but neither the notebook or the console in spyder work (giving the error above.)
Any information about this would be helpful. I couldn't find any file err.cpp in any folder \src\ in my python installation, so I can't confirm what triggers the error has any relation to PyZMQ or firewalls. No change is made when turning off the firewall or elevating the command prompt. What else can I try?

I realise this is two years old, but I've just been able to sort out a similar problem, so it would have been good to see more answers to this.
In my case it wasn't the Windows Firewall or virus scanner, but that my employer's IT services group runs VNC over the same port that is hardcoded into 0MQ, as used by iPython in Anaconda.
Enough people complained that IT provided a script to move the VNC port for affected people, while also logging the change in their own records, so everybody is happy.
Try doing a "netstat -ab" from the command line, and check if anything is listening on port 5905, which iPython needs (at least as it is in early 2016, with Anaconda). You'll need to use "Run As Administrator" with cmd. If you can't do that just use "netstat -a". The difference is the b option will also list the process that has taken the port, and in our case we see vncserve.exe there. But -a is enough to see listening ports.

Related

Yarn Project Not Working After Mac OS Ventura Installation

I have updated my mac's OS and when I try to run the same commands that I did prior to the update (see file, it was simply just yarn), I get a vomit of errors on my terminal and I get a system prompt that states: The "make" command requires the command line developer tools. Would you like to install the tools now? After I click Install it takes about 20 minutes and it says installation finished, only to have the same behavior when I run the same command in my terminal.
Any one else a developer using Ventura running into weird problems running their code base?
Will be happy to share my output logs if somebody cares to help.
Did exactly what system prompts said, only to give me the same behavior when trying to run my code locally. It is in a feedback loop and am un sure how to approach it at this point.

omnetpp does not start on Ubuntu

I use Ubuntu-20.04 via wsl. There, I have installed ometpp-5.6. Also, on Windows, I have installed VcXserver to run onmetpp IDE.
But when I run in the command prompt on Ubuntu omnetpp I get Starting the OMNeT++ IDE..., but no IDE window is being open, even though I have configured my environment as described here.
How could I solve my problem?
Adding separate inbound rule for TCP port 6000 as described here solved the issue.

Ubuntu - I can't lauch apps and run command with sudo

I am writing this post because after several hours of research I did not manage to find an answer.
I have been using Ubuntu 20.04 for a few months in dualboot on my original Windows. But since a few days I have not been able to launch applications (example: Chromium, Firefox, Visual Studio Code, Settings), I tried to launch them via the terminal, but I have no response, not even an error. I also cannot execute a command with sudo
After several searches I understood that it could come from gnome, I then try several subject recommend it to execute
$ killall gnome-control-center
$ gnome-control-center
When I try to kill I get no response, and when I run gnome-control-center I get the following error :Failed to register: Timeout was reached
I cannot move forward in my plans because of this problem, would you have a solution please?
This might just be that something on your system is corrupted, you might just have to copy the files you use all the time (Code, pdfs) wipe the drive and reinstall your ubuntu. Also, check if the Windows is working if that's not working it might be a problem with your computers internals.

Using manual STAF commands on Linux

I've recently started working with STAF and couldn't get 2 machines to communicate with each other. One of those machines is a Linux ec2-instance on AWS and can't be pinged.
I was planning on pinging STAF from one virtual machine to another to see if the company firewall could be the cause of this but I can't seem to use commands on linux (like "staf local ping ping" on windows for example). When I try to run STAFProc with gdb (in /usr/local/staf/bin) I get the following error.
(gdb) run
Starting program: /usr/local/staf/bin/STAFProc
/bin/bash: /usr/local/staf/bin/STAFProc: No such file or directory
(The STAFProc file is there though. Does gdb work from another directory?)
I'm not exactly experienced with STAF, AWS or even Linux so any help to get me started with debugging would be greatly appreciated.
Though it is a bit long since the question is asked and the op seem to figure it out already, I might still post my solution as well.
There is a possibility that it is caused by trying to open a 32bit binary on a 64bit device.
If you are working on Debian based os, try
sudo apt-get install lib32stdc++6

IPython notebook connection failed issue

This is probably very simple; and I am embarrassed to ask; but I spent a long time trying to solve it already. I am trying to use an IPython notebook and on the click to get a Python 3 notebook, I often (but not always) get:
Connection failed
A connection to the notebook server could not be established. The notebook will continue trying to connect, but until it does, you will NOT be able to run code. Check your network connection or notebook server connection."
The obvious answer might appear that I have no internet connection; but I can access the internet and interact with external websites. It seems to be a problem of connecting with something local to my computer.
The really frustrating part is that sometimes in the past this has worked with no problem. That suggests to me that it is a simple setting issue. Does anyone have suggestions about how I can debug this?
My operating system is Windows (both 7, and 8.1). I am also using Anaconda 2.3 and Python 3.4
Downgrade Tornado to 5.1.1 from 6.0, that will solve it.
Apparently, Tornado 6.0 breaks notebook.
I anwser a similar question. And I agree with tchakravarty.
Maybe resulting from your proxy?I have been troubled for one afternoon for that,because I use nginx proxy_pass fo my jupyter to proxy to that port. But it always didn't connect, i look through the docs of jupyter notebook and found that Jupter Proxy Issue
And i change to use nginx rewrite rather than proxy, it works. So in my case, it can be caused by proxy.
I was also facing the same problem and as the few people suggested to update the tornado version , I did but it din't help.
What helped me was ---
I ran this two following commands -
python2 -m pip install --upgrade ipykernel
python2 -m ipykernel install
In Jupyter Notebooks, the kernel is responsible for executing Python code. When you install the Anaconda System for Python3, this version also becomes the default for the notebooks. In order to enable Python 2.7 in your notebooks, you need to install a new kernel.

Resources