SETUP
I have a windows 10 PC connecting to my linux server (ubuntu 18.04.2). I run/edit code on my powerful server by remotely accessing the server through VS code's ssh ability. It is super convenient to edit my code on the server with VS code...
THE ISSUE
Visual Studio code won't connect to my Linux server. What is weird is that I am able to ssh into the server from the terminal within VScode by just literally typing ssh <username>#<server-hostname>
However, when I do the Remote-SSH option within VScode then it does not want to connect to the server...strange...
Here is how I remotely SSH into server with VScode built in functionality (marked with red rectangle). Also part of this screenshot is my config file, which I have triple checked as correct (IP address and .ssh/id_rsa_gpu_1_solarpv_ssh location)
HERE IS THE ERROR OUTPUT
MY ATTEMPTS
I have made sure that the config file is setup correctly and that the IP address is correct.
I have ensured that the server's IP address is also in the 'known_hosts' file located at /Users/.ssh/
I even generated my own private key for SSH connection as advised by the great documentation here: https://code.visualstudio.com/docs/remote/troubleshooting#_quick-start-using-ssh-keys
Still getting the error of failed to create hard link...
With all of my back-end stuff done right, I am absolutely clueless regarding why this is an issue.
After spending literally 9 hours on this issue...here is the answer:
When you launch VScode and remotely access the linux server, the linux server is instructed to download and install a vscode server so that you (on the other side) can remotely connect to the server.
If the server does not have internet just make sure the following setting is ticked
This allows the remote server (without or with internet connection) to get the vscode server running.
To eliminate the "failed to create hard link error" go to the directory mentioned by the error, which in this case on linux server is
navigate to /home/<username>/.vscode-server/bin/0ba0ca.../
then remove/delete the hardlink file and target file which also has
the same name as the directory.
Then just attempt to remotely access your server again through
vscode and all should be fine
Here is also a discussion regarding the issue...if you still have problems https://github.com/microsoft/vscode-remote-release/issues/2507
I solved this by enabling the option Lockfiles in Tmp:
i just deleted the whole library and it works, i don't see anything wrong with doing that.
rm -r /path_to_project/.vscode-server/
if i'm wrong feel free to correct me :)
Try this
Just in case others need to try the same here is the detail
ctrl-shift-p and choose:
Remote-SSH: kill VS Code Server on Host...
Chose the host name
Selected the platform type (linux)
https://github.com/microsoft/vscode-remote-release/issues/4307#issuecomment-762882247
worked for me.
Related
I have installed CouchDB on my Windows machine but while starting the CouchDB service, I am getting a message like:
Windows could not start the Apache CouchDB service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, please contact your system administrator.
As the service is not running, I am unable to access Fauxton too.
I am using Windows 7. CouchDB is 2.0.0. Port 5984 is not in use.
I don't think your question is a duplicate of https://stackoverflow.com/a/44107335/219187 because you are on Windows 7, and the problem described there is for Windows 10 with the creators update.
But maybe the solution fixes your problem as well? Here is the procedure:
Download the prelease build 2.2.4-101 from https://nssm.cc/download
Stop the CouchDB service through the Windows Services dialog (paused is not enough)
Overwrite nssm.exe in <CouchDbInstallDir>\bin with the one from the downloaded ZIP file (make sure you pick the right version 32 bit / 64 bit)
Start the CouchDB service
Issue it's happening since the last updates released by Microsoft. I'm not completely aware of what's causing it, but I think it's something related to CouchDB service not been able to start using Local Administrator rights.
However I've managed to start the service manually, by doing so:
Open Command Prompt - in the Search from the Start Menu or Task Bar type "cmd"
Run it as an Administrator - right click on the Command Prompt application and choose "Run as administrator" option /this is really IMPORTANT as it will allow the service to have administrator access/
Navigate to the folder where CouchDB is install - default path is "D:/CouchDB", but could be anywhere else; you have to find it
Go to the "bin" folder in there
Type "couchdb" as a command to start the service
You will see a message showing after this - "kernel-poll not supported; "K" parameter ignored"
If it adds some error messages after it or closes the whole terminal, you're making some things bad from this guide, so follow it strictly.
You can now open up the Fauxton application in the browser like normal from here - http://localhost:5984/_utils/
Keep in mind that you have to leave the cmd opened in order the service to be working as expected. As far as I saw no information was lost, so it's all good.
This is a temporary solution though, as we are waiting a relase from either Microsoft or Apache to solve the issue, or at least give us more explanation about it.
i just met the same problem.
the cause is space, you have to install CouchDB in a path without any space, even Program Files folder, because there is a space between Program and Files...
I currently am using Cmder (which is effectively conemu) to SSH into a university cluster from my Windows machine. I want to enable x-forwarding, and I have Xming installed. I followed the instructions here, which I swear I've used before but doesn't seem to work right now. Specifically, I type
DISPLAY=localhost:0.0;export DISPLAY;
once I open up a Cmder terminal (with Xming already loaded), but the error I get back is
Error: cannot open display: localhost:0.0
despite Xming saying it is Xming server:0.0. Any suggestions? I should add that the x-forwarding works perfectly fine with MobaXterm, but I'd prefer to stick with Cmder.
The issue was that I was setting the display variable on the client server, not the host computer. On my Windows machine, I opened Xming and then did
set DISPLAY=127.0.0.1:0.
Afterwards, I SSH'd into the client server via
ssh -X myname#address.
Now everything works as intended.
I have exactly the same problem. However, I have observed that if I open up a Putty session with x11 forwarding set, then add the display number to my ConEmu session that is ssh'd into the Linux box, then x11 works from ConEmu. Weird.
It is an inconvenient workaround at best.
I made it work for me.
Even so Xming was telling me "localhost:0.0", after connecting to the my server (using the "-x" ssh's option) I rather did :
DISPLAY=:10.0;export DISPLAY;
The following worked for me:
export DISPLAY=127.0.0.1:0
ssh -XC <hostname>
When I try to start Worklight server in Worklight 6.2 on mac OS. I keep getting:
Several ports (10080, 10443) required by Worklight Development Server are already in use
When I change the port to a different number in the server config, I just get the same error (with the new port).
How I can resolve this?
Run Activity Monitor and search for "java" process. Kill it.
Try TCPView software and delete the port number as you mentioned in the above.Then clean project and Run the server.
Hope this helps.
Try this out:
Finder -> Go -> Go to folder. Type in the following location /etc
Search for a file named hosts. Copy it to your desktop.
Check for a line containing localhost and remove that line, and add a new line as follows: (If no such line is present, no problem add a new line)
127.0.0.1 localhost
Save the file and replace the file in /etc.
Close eclipse and now start the server.
Note: Try this only if using lsof command or killing the java process didn't solve your problem.
I'm trying to connect to an admin server in WLST using config and key files. There are no error messages but I am prompted for a username and password. These files were created (by another developer who is long gone[1]) with the storeUserConfig() command. My call to connect looks something like this: connect(userConfigFile=configFile, userKeyFile=keyFile, url='t3://somehost:7031')).
Is there some restriction in using these files, such as it can only be used on the host where created, or it needs access to the domain's boot.properties file?
Note: I'm trying to connect to an admin server on a different host and non-standard port (e.g. not 7001). The server I am running WLST on and the remote host are the same version of Weblogic.
Some of the things I have tried:
verified that these files appear correct, the key file being binary data and the config file having a line for "weblogic.management.username={AES}..." and "weblogic.management.password={AES}...".
verified that there is a server on the specified port by entering a known login and password that is successful
specified the admin server in the connect parameter
turn on debug(true); the only output is <wlst-debug> connect : Will check if userConfig and userKeyFile should be used to connect to the server and another line giving the path to the userConfig file
turn on Python logging in jython with -Dpython.verbose=debug; nothing relevant to decryption operation
Munging the key or the config files generates no error messages and behaviour as above
[1]: These files are still used today by other existing WLST scripts. However, these scripts are so convoluted and deliberately obfuscated that they are very difficult to reverse-engineer how connect() is being called.
You do not need to access to the domain's boot.properties file. You just need to make sure the configFile and keyFile pointing to the right files. FYI, here is one of the commands we are using:connect(userConfigFile='./user.secure',userKeyFile='./key.secure',url='t3://somehost:7001')
Have you check the network connectity that might be having a firewall in between that troubling you, check the traceroute from the script machine to the Remote machine. Recently I have faced simalar issue. once the routing table updated with allow the WL admin server port everything got set.
Hope this could helps you!
I had this problem too. In a script, I exported the Linux variables userConfigFile and userKeyFile. Then I connected by running:
url='t3://localhost:7002'
userConfigFile='$userConfigFile'
userKeyFile='$userKeyFile'
connect(userConfigFile=$userConfigFile, userKeyFile=#userKeyFile, url=url)
That all worked in a script, but would not work interactively. I changed to doing the following:
url='t3://localhost:7002'
userConfigFile='/users/me/weblogic-2014/weblogic-admin-WebLogicConfig.properties'
userKeyFile='/users/me/weblogic-2014/weblogic-admin-WebLogicKey.properties'
connect(userConfigFile=userConfigFile, userKeyFile=userKeyFile, url=url)
And that worked interactively.
I installed Oracle 10g express. Installation went well, But the home page is not coming up.
I can connect using sqlplus but not with Sql Developer.
I checked tnsnames.ora and listener.ora everything looks fine.
Listener is also started. I can always reinstall and see. But I thought better inquire the cause.
Regarding the home page. This is the address that comes up in browser. Localhost:8080
http://127.0.0.1:8080/apex
I did a netstat to see whether there is any port conflict for 8080, but that port is not in use.
Have anybody faced this issue?
Yes. It is practically a FAQ on the XE Oracle forum.
Firstly, can you connect to Oracle using
sqlplus user/pass
If so, Oracle is up an running (which appears to be your situation, but may not be for a future reader with a similar problem). If not, you can try
sqlplus / as sysdba
startup
Once Oracle is up, check that the listener can see the Oracle instance by
sqlplus user/pass#xe
If not, then either the listener is not up, or the 'listener does not know of the service'. Make sure the listener is started (lsnrctl, then start). Make sure the database is registered with the listener
sqlplus / as sysdba
alter system register;
Now you should be able to connect using the '#xe' syntax. Worthwhile verifying the embedded PL/SQL gateway is set up to use the 8080 port
select dbms_xdb.GETHTTPPORT from dual;
On Windows you can use netstat -ab to see if tnslsnr.exe is listening on the port.
Then I'd suggest looking at browser settings (specifically any proxy settings that might be forwarding your request to a machine that has no idea what to do with it) and firewalls (which could well be set to ignore or hide any access to the port).
I had the same problem. I tried this and it sorted out my problem...
1. goto start->run
2.type services.msc and hit enter
3.In the applet that opened, scroll down(in right pane) to figure out the option of "OracleServiceXE" and right click on it. 4. In general tab do->>> startup type "Automatic" and click the "start button".
5. Repeat step 4. for the option "OracleXETNSListener".
close the window.
now, i hope, the problem should be solved....
Check your windows firewall,If it is on it blocks the opening of the homepage.Either you shut down the windows firewall or allow these following ports :
1521: Oracle database listener
2030: Oracle Services for Microsoft Transaction Server
8080: HTTP port for Oracle XML DB and the Oracle Database XE graphical user interface
See software requirements in the below URL:
http://download.oracle.com/docs/cd/B25329_01/doc/install.102/b25143/toc.htm#BABEBCDB
It worked for me!
Try this ( I'm assuming Windows system )
using
netstat
without anyother parameter would tell you if port 8080 is already open.
Also you can try this:
telnet localhost 8080
If the server answers ( the screen goes blank [or black] ) then the server is up and running.
Try using your hostname instead of localhost.
See if you're using a proxy and not skipping the local addresses.
Also you can see what's the executable that starts the home page and see if it could start successfully.
Thanks for the response guys.
I finally figured out how to solve the issue, but not really the root cause.
Problem 1 - Can not login to oracle admin console.
It was the problem with not adding 127.0.0.1 in the IE intranet sites.
Go to tools>internet options>security>local intranet sites>advanced>
add http://127.0.0.1:8080/apex in the list.
It works fine after this.
But if I go back to the same place again and see the sites, I cant find the url I added sometimes back... Dont know why that is happening. May be some company security is messing up.
Anyways the admin console is now coming up.
Problem 2 - Cannot connect using SQL Developer.
After I did the fix for problem 1, this is also magically working.
I still don't know how security settings in IE affects SQL Developer?
Any comments on this?
hey guys one important fact if u r using IE7 (explorer7) then u wd face certain problem in using 10g, such as not displaying home page.
For Windows 8 simply click on Get Started With OracleXE.... When internet explorer opens up, select the View on the desktop option in the Page View icon (icon with a wrench).
You should now be able to view your page.
I had a similar problem, I was able to connect to SQLPLUS using terminal but on access in browser as it was showing error as you have described. So, I went back to terminal and mounted my database using
startup
and it resolved my problem. This might be the case.