Q)After installing geth getting an error while attaching.How to fix this error?
geth attach
Fatal: Unable to attach to remote geth: no known transport for URL scheme "c"
If you're using 1.8, you need to include the IPC path:
geth attach ipc:\\.\pipe\geth.ipc
See https://github.com/ethereum/go-ethereum/issues/15746
If you using windows then try:
geth attach http://localhost:8545
this will properly work for windows work.
you don't have access to personal and mine objects using localhost ... eth.personal
undefined. Apparently you need to use ipc to get to the lower level objects
Related
I am new to Kuma and am trying to set up Multi-Zone deployment mode after experimenting with standalone mode. Currently, I have managed to setup the Global Control Plane on an Azure VM and it seems to be working well.
My problem lies in setting up the Zone Control Planes. I have tried setting up on both Docker, WSL and a VirtualBox Ubuntu VM but I am receiving the same error again and again. It should be noted that I am attempting to set this up using Universal mode, as described on Kuma docs, and have tried both versions 1.4.1 and 1.2.3. The error in question is as below:
ERROR kds-zone.kds-mux-client component terminated with an error (“generationID”: 6, “error”: “rpc error; code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: tls: first record does not look like a TLS handshake””}
I have tried googling this problem, but can’t seem to find any similar problems relating to Kuma, and have also tried experimenting in the kuma.conf.yml file but to no avail.
Thank you in advance to anyone who may have any advice on how to solve this.
Regards,
Daniel
TortoisePlink Fatal Error Disconnected: No support authentication methods available (server sent: publickey)
I found a similar post here that involved TortoiseGit.
How to solve TortoiseGitPlink Fatal Error?
But the interface given in the top solution didn't match up with Tortoise HG.
The sequence for TortoiseHG was this:
TortoiseHG->Global Settings->Sync->SSH Command
Put ssh.exe in that slot. Assuming you have all of the other ssh configurations set up correctly, that should get TortoiseHG working for you.
I'm struggling to get the connected mode to connect to my local instance of SonarQube.
I'm suspecting it has something to do with the way my system is set up.
I'm using a Mac (OS X 10.11.x) and I have PHP and Apache set up according to this tutorial. I think perhaps there is an issue with a firewall rule or something.
When I connect to http://localhost:9000/api/system/status with a browser, there is no problem. telnet localhost 9000 works fine too.
But when I enter credentials and create a configuration in SonarLint, I always get:
error testing connection: Fail to request http://localhost:9000/api/system/status
Anybody have a clue?
It is also worth to check SonarLint issue tracker. Issue looks related rather to the plugin than PhpStorm itself.
Check your Phpstorm log folder ~/Library/Logs/PhpStormVERSION/FILE.log (FILE - some log file for phpstorm, in Intellij it's idea.log)
I see the tutorial you followed enabled SSL and I guess that should be because of a certificate.
I tried to run example from HornetQ and I got this error:
[java] HornetQServer_0 out: Deployment "JNDIServer" is in error due to: java.rmi.server.ExportException: Port already in use: 1098
Actually this is not the first time I got this kind of error. I can verify that port 1098 is indeed already in use (using Netstat command) but I just don't know which service using it. Is anybody has encountered such problem?
Thanks in advance for any response and help. :)
Could be JBOSS or Remote Admin Tool. Or something else like Outlook or Firefox.
While I was trying to start ApacheDS 1.5.7 on windows platform, An Error 04450 occurs and the apacheds-rolling.log contains:
[21:07:27] ERROR [org.apache.directory.shared.ldap.entry.DefaultServerAttribute] - ERR_04450 The value {0} is incorrect, it hasnt been added
[21:07:27] ERROR [org.apache.directory.server.Service] - Cannot start the server : reuseAddress can't be set while the acceptor is bound.
How can i fix this problem? Anybody could help me? many thanks!
The warning log message is a bit misleading, actually this is not a serious issue, the server should be running despite of this warning, this has been fixed a while back in the latest trunk code (which will be released as 2.0 instead of 1.5.8).
According to this post, the dc=example,dc=org context entry is not created by default anymore but no one has updated the documentation to reflect this. I installed 1.5.7 and it looks to me like the partition was created fine, but I'm getting the same error as described above. I suggest installing an older version.
The 2nd error message suggests that the port is already in use. Is there a chance that you already had another ApacheDS process running, or that another program is using the ports?
This isn't a domain controller perchance, is it? If so, the default LDAP ports 389 & 636 are already in use for Active Directory, so you'll need to choose another. However, I believe the defaults for ApacheDS are 10389 (LDAP) and 10636 (LDAPS), in which case they would typically be open on a Windows box.
You can check for processes on the ports with the netstat -abn command, and look through the list for the process listening on port 10389 or whichever custom port you chose.