I have a Server running CentOS 6.0 and I'm trying to use it as a remote host for cuda debugging. In order to do this, I installed cuda-toolkit 5.5 both on the server and my notebook, which is running ubuntu 12.10 OS. I configured the two machines as the NVIDIA-cuda-instruction told me, yet when I started the Nsight eclipse edition and tried to remote debug my cuda applications, I ran into error, whcih says:
Failed to execute MI command:
-target-select remote 192.168.2.105:2345
Error message from debugger back end:
192.168.2.105:2345: Connection timed out
I googled this error, someones says it is a firewall issue and I need to open the port manually, so I modified the /etc/sysconfig/iptables file and add this:
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2345 -j ACCEPT
to open the 2345 port. But it turn out to be of no use. Can anyone give me some suggestion and help me solve this problem?
By the way, I have tested local debugging using nsight eclipse edition on my server, and it works well.
I have the same problem in an OpenSuse server. I have managed to make it work by disabling the firewall in the server.
#/sbin/rcSuSEfirewall2 stop
You can start later by
#/sbin/rcSuSEfirewall2 start
Related
Let me say first and foremost, I am not trying to INSTALL Xdebug locally on my Mac and can not run the application on my Mac. I also can not downgrade my OS below Catalina so let's just not discuss those options please...
I got a new Macbook Pro running MacOS Catalina (10.15.7) and can not get Xdebug working to save my life. The PHP application runs on a SHARED development server hosted on Amazon. Seeing as how the environment is shared among several developers, we use Xdebug via remote_connect_back setting.
With my old Macbook Pro running High Sierra (10.13.3), it connects just fine and step debugging has been working for years. The result is the same with all of my co-workers: those on Mojave and below have no issue and Xdebug works wonderfully. All of us with Catalina and higher can not get Xdebug to connect to our machines from the shared dev server. We are all running PhpStorm 2020.3, and use the Chrome Xdebug helper plugin (with "phpstorm" set as the IDE key).
I have set up this configuration at least 2 dozen times (and wrote the company guide for setting up the dev environments including Xdebug), so it's a bit embarrassing that it won't work on newer Macbooks.
The computer I am currently testing has the firewall disabled, no internet security, clean install as of yesterday. Also tried with gatekeeper disabled, rootless protection disabled and Allow Remote connections from ANYONE. All to no avail. On my previous laptop, I can ssh into the dev server, and open a telnet session on port 9000 to my local laptop and it works fine. On the NEW computer, if I attempt a telnet session on port 9000 it just times out.
What is interesting is if I turn OFF listening for Xdebug connections in PhpStorm and run the telnet command again, I IMMEDIATELY get a connection refused message. So I KNOW I am getting the right machine, it's almost as if Apple implemented some security through obscurity logic between Mojave and Catalina.
It's also worth noting that one co-worker is running Catalina, but version 10.15.2 and his connects just fine and he is refusing to update (reasonably so). Any help would be greatly appreciated.
Edit/Update: I have tried both xdebug 2.7.2 via remote connect back on port 9000 and 3.02 via discover remote host on port 9003.
Second Edit/Update: If I open a reverse ssh tunnel on my laptop (ssh -N -R 9003:127.0.0.1:9003 dev_server_host) I can get Xdebug to work. However this solution isn't practical on a SHARED dev server as if more than one person does this we get cross talk. Just noting it to help with troubleshooting.
Third Edit/Update: This issue is still unresolved so I would love to find a solution at some point, but I have moved on by working with coworkers to get it running locally on docker. On docker we have no issue getting xdebug to connect. Our unit tests run a bit slower in docker, whether the code is mounted via a volume or not, but that is another topic for another day.
I have installed visual studio code and dependencies to my ubuntu trusty OS in Oracle VM Ware. And I run code with these commands.
ssh -X myserver
code
But when i use mysql extension in code it gives me an error like
Unknown or unsupported transport “disabled” for address “disabled:”
Here is a picture of the error.
I've googled it, Gave remote permissions to to all privileges and no luck. My MySQL server is on another VM and ubuntu server and vs-code is on another VM and I am working on the mother os.
This means dbus isn't running.
See https://github.com/microsoft/vscode/issues/120392
I have a project that uses Entity Framework 6.1.3 and uses the 6.9.9 MySQL connector with a MySQL 5.6.x DB. I have MySQL on Ubuntu 16.04 on a remote image and I have a matching Docker image running on my local workstation.
The Docker image works. I can use EF's Update-Database command on my Docker image. I can run my application and all the SQL things happen as they should. But nothing works on the remote. From the start, I get a timeout error when I run Update-Database from the Package Manager console in Visual Studio 2015.
I can, however, connect to the remote image with DataGrip on my workstation and perform all of the same SQL commands that are performed by Update-Database. In my mind this precludes network / firewall / configuration / permission issues. This points an accusatory finger at Visual Studio, Powershell, and Entity Framework.
How do I diagnose what is happening with the Update-Database command?
Assuming your MySQL port is 3306, when you launch docker, try publishing the port:
docker run -d -p 3306:3306 my-mysql-image
Fire up VS after and see if that resolves your issue.
I'm using xampp v1.8.1
While not installing Mysql and Apache as services, everything is ok and I can run both of them on default ports.
but when I install them as services only Apache runs normally. but Mysql is frozen at "Attempting to start MySQL service..." and there is no error in its log file and nothing in xampp control panel log.
there is no problem with port numbers because it can run on default port without the service checkbox checked
FYI my OS is: Windows Server 2008 SP2.
thanks
The problem solved by using the xampp installer instead of extracted zip archive. It seems that there is some problems with the config in the portable edition.
Disclaimer: I know that this question has been asked numerous times, but before Nsight 5.5 the answer simply was "You can't."
I'm trying to debug a CUDA program with Nsight 5.5 on Ubuntu. The remote machine is also an Ubuntu with CUDA Toolkit 5.5.
I setup debugging in NSight using the "Debug an application on a remote system".
Whenever I try to run the application I get a "Could not start gdbserver on the remote host" error.
This is what I get on the console:
Last login: Thu Aug 1 16:09:26 2013 from host.whatever.edu
echo $PWD'>'
:2345 /tmp/nsight-debug/flow;exit
someuser#remotehost:~$ echo $PWD'>'
/home/someuser>
someuser#remotehost:~$ :2345 /tmp/nsight-debug/flow;exit
:2345: command not found
logout
Both gdbserver and cuda-gdbserver are installed on both machines.
If I ssh to the remote host, I can run /tmp/nsight-debug/flow manually.
What might be the problem here? Is there anything missing from the setup?
This looks like a bug in Nsight, we will take a look into this matter.
Please make sure that you have remote toolkit configured for your connection.
From the main menu, select Run -> Debug Configurations...
In the left-hand tree, select you debug configuration under C/C++ Remote Application
Make sure that Remote toolkit combo has proper toolkit selected. If you don't have any toolkit configured, click Manage... and setup the toolkit.
Usually you will only have to setup the toolkit once per your connection - e.g. you will not have to setup it if you want to debug another application on the same remote system.