I installed anaconda on remote server and typed spyder which gave this message:
QXcbConnection: Could not connect to display
Aborted (core dumped)
I have a script I've worked on locally. I could just scp it but would prefer to continue working on the script within spyder. Is this possible?
(Spyder maintainer here) Spyder can't work in a server that doesn't have an X server installed (clearly your case) because it's a graphical application.
Related
when i run the command on administrator settings on my windows 11
wsl --install
it shows me the following error
a connection with the server could not be established
I searched youtube too for the fixes but none worked
Hi I was having same error. I am Indian using Jio Fiber. I connected to VPN to solve the error. It seems that Jio prevents connection to certain url such as https://raw.githubusercontent.com/microsoft/WSL/master/distributions/DistributionInfo.json which are needed for wsl linux installation. You can check by trying to open above link in chrome and running network diagnostics. Basically the above url gets called at the end when you do wsl --install.
I tried to install it with VPN and it works. Using VPN may work for you.
I'm working on a project where the servers and Mysql data bases are inaccessible from my local machine unless I ssh to a remote using terminal. However, I find programming with Jupyter Notebooks the best environment for me. I really miss it as I find programming with just vim remotely via terminal a bit cumbersome. I was wondering if there was a way to launch Jupyter notebook from the server and have my local browser open it up- so I can code from my browser but it would be running from the terminal/remote-server via ssh- so that ways my code can actually connect to my database from my browser via the remote and I can use the interactiveness of a Jupyter notebook to speed up my development. Any ideas? remote is ubuntu and mine is a mac. Thanks
This is pretty simple. You just need to install the jupyter notebook server on your remote machine and make it open to the web, protected by a password to avoid unintended use.
On the remote server, first install Jupyter:
pip3 install jupyter
Then follow this guide to secure it with a password.
At last you can launch it with:
jupyter notebook --ip='*'
This tells Jupyter to make it available from any ip and not only from localhost.
Please do protect it with a password, otherwise very nasty things could happen to your server.
When trying to configure a Remote Python Interpreter in Pycharm using Docker I get the following error:
com.github.dockerjava.api.excepion.DockerClientException: Enabled TLS
verification (DOCKER_TLS_VERIFY=1) but certificate path
(DOCKER_CERT_PATH) '/Users/me/.docker/machine/machines/default'
doesn't exist.
I've $export DOCKER_TLS_VERIFY=0 but with no difference.
I've manually created '/Users/me/.docker/machine/machines/default' but with no joy.
I've deinstalled and reinstalled both Docker and Pycharm but still get the same error.
I'm on a Mac OSX 10.12.1
Pycharm 2016.3
Full disclosure: I use vagrant and virtual box on my mac too.
Any pointers would be appreciated.
Kevin
I fixed it as follows:
Obtain socat (if not already installed)
e.g. brew install socat
Then: socat TCP-LISTEN:2375,reuseaddr,fork UNIX-CONNECT:/var/run/docker.sock
Then in pycharm/docker config:
Api URL: tcp://localhost:2375
Many thanks to the following found on:
https://youtrack.jetbrains.com/issue/IDEA-153973
If you have been using docker-machine for Mac to support PyCharm or the "socat" hack to access Docker API - It is no longer necessary with PyCharm EAP (https://www.jetbrains.com/pycharm/nextversion/) — You can set your remote debugger API_URL directly to: unix:/var/run/docker.sock (supporting debug mode, and the environment runs a lot faster, when not using VirtualBox).
There is a no-questions-asked 30 day trial of EAP before that update goes live (some time this month)
I have this error while trying to launch the command ./runInstaller
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
From Oracle help docs:
sudo yum install xorg-x11-utils -y
worked for me.
If you are executing this via Putty, then I suggest you have a look at Xming, this allows you to have a Putty remote ssh session, and forward your display to you Windows machine...
If you're executing this from a Linux server without a gui, you will either need to connect remotely with a pc with a GUI installed (Gnome, KDE, etc) or you'll need to install the Gui directly on the server.
Check if it's not already installed by using the command on the terminal
$ startx
Error is reproducible thus:
$ export DISPLAY=:0.0
$ ./runInstaller
ERROR: Unable to verify the graphical display setup. This application requires X display. Make sure that xdpyinfo exist under PATH variable.
Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
OP's X server was Hummingbird Exceed. Xming will work as well.
The actual solution depends on:
whether you are su'd to oracle from a different login account.
whether you are using X11 forwarding.
the actual port used by X11 forwarding, which could be 6010 or a different port.
If you logged in and then su'd to oracle, then copy ~/.Xauthority to the oracle account.
If you are using X11 forwarding and the forwarding port is 6010, then DISPLAY=localhost:10.0 is correct.
If you are not using X11 forwarding, and if port 6000 on your PC is reachable from the oracle server, then export DISPLAY=your.pc.ip.address:0.0 is correct.
Install xterm and use xterm to test X windows.
Be sure to install xdpyinfo.
For more details, please refer to my article X windows for Oracle DBAs
I have a fresh install of cygwin and xemacs on my home laptop. I'm trying to get to the packages list in xemacs, but not having much luck.
First of all I was getting an error message telling me "ftp.XXX.com seems not a pty". Following the instructions here I was able to tell efs to use lftp, and got past that error.
Now I get told:
Process not open for writing: #<process "*ftp yyy#ftp.xxx.org*" pid 9999 state:exit>
Any idea what's going on there?
The problem has to do with which ftp you are using. From the message, I believe you are trying to use the ftp that comes with Windows. It won't work as the native Windows ftp does not act like a pty.
The best solution I can suggest is to install the Cygwin port of ftp.