Unknown or unsupported transport “disabled” for address “disabled:” - mysql

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

Related

Ejabberd STUN issue: unknown module mod_stun_disco failed to start

I'm trying to get video calls working with my ejabberd server, following this guide.
My server runs the latest Debian.
Ejabberd fails to start after these changes and logs the following error:
#gen_mod:start_module:228 Failed to start unknown module mod_stun_disco: make sure there is no typo and mod_stun_disco.beam exists inside either /usr/lib/x86_64-linux-gnu/ejabberd-18.12.1-2/ebin or /opt/ejabberd/.ejabberd-modules directory
#gen_mod:maybe_halt_ejabberd:311 ejabberd initialization was aborted because a module start failed.
How can I install mod_stun_disco?
My server runs the latest Debian.
And what version exactly is "the latest Debian" that you are running?
Also, what is the ejabberd version you have installed?
mod_stun_disco.erl was first included in ejabberd 20.04
https://github.com/processone/ejabberd/commit/69d1d62add92511acf58f5f71383ad64e4757464#diff-44e2dc2000d1cc7230e63af3a7f9618a7bb9afb64df1aec0cc91bf31c21c91bc
If you are running an older ejabberd release, obviously that module is not included.

The specified password for user account 'root' is not valid, or failed to connect to database server when installing wordpress

I installed windows server 2016 on virtual machine on virtualbox and then I want to install wordpress in iis by using the web platform installer. but the installuation failed and shows this error "The specified password for user account 'root' is not valid, or failed to connect to database server"
Firstly, please use the command line tool to check whether the root password is correct.
Secondly, please check whether MySQL Connector/Net is installed. If it is not installed, please install it. If it is installed, please check its version.

How can I diagnose Entity Framework migration errors?

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.

nsight eclipse remote debugging timed out error

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

How to do remote debugging with Nsight 5.5 on Linux?

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.