I have tensorboard summaries saved in D:\0. I launch tensorboard from cmd, change the drive from C to D and launch tensorboard --logdir="D:\0". The problem is, tensorboard sometimes works, sometimes I get the error:
ERROR
The requested URL could not be retrieved
The following error was encountered while trying to retrieve the URL: http://nsv:6006/
Unable to determine IP address from host name nsv
The DNS server returned:
Name Error: The domain name does not exist.
This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
Your cache administrator is webmaster.
One time to fix it, I change the computer name restarted the laptop and it worked. But I don't want to do this everytime. Is there a simpler solution?
OK. This is really silly. The reason for this error seems to be because I am connected to VPN to access lab servers. Once I disconnect from the VPN, tensorboard works.
Related
I am new to AWS and learning through hands on labs. As per the instructions in the lab, I launched an EC2 instance, installed apache and displayed a simple index.html file when the instance IP was accessed. This worked great and when I was done for the day I stopped the instance. Now when I select the instance, go to Actions > Instance State > Start it shows me that the instance is running but when I enter the IP address in the browser I get an error message that says:
This page isn’t working
[IP ADDRESS] didn’t send any data.
ERR_EMPTY_RESPONSE
Why is this happening when I have not changed anything else in the instance? How can I get it to work and show the index.html file again? I see no errors in the AWS console. I tried creating a new instance, which worked, stopped it and started again and faced the same problem.
Based on the comments.
The issue was that apache was not starting automatically after instance re-start.
The solution was to enable the automate start of the web server.
Yesterday I had to revert to a recent snapshot of my vm. This vm was working flawlessly at the time I took it.
But now I can no longer resolve any url from this host. All git pull commands, all curl requests, host lookups, etc.. are failing. For instance:
# host www.google.com
; connection timed out; no servers could be reached
Yet this host is reachable from the outside world, as I can ssh to it, and http requests coming in are being serviced.
What am I forgetting?
Turns out that the file /etc/resolv.conf has been automagically populated roughly 18 hours after spinning up the instance.
Not super convenient, but glad it is resolved.
Had I known at the time, I think I would have been able to resolve the issue by adding this to /etc/resolve.conf:
domain c.[Project ID].internal
search c.[Project ID].internal.google.internal.
nameserver 169.254.169.254
This is the expected behavior, the hostname of an instance in the GCP is provided by the metadata server. Every time an instance boots up, it will get the hostname from the metadata server, therefore resetting any changes made on the instance level, please see 1 and 2.
I am running this example http://kaaproject.github.io/kaa/docs/v0.10.0/Programming-guide/Your-first-Kaa-application/ .
But data is not storing on the server side.
What should I do now?
When I running db.logs_my_application_token.
find() from mongo console,
it is showing nothing.
Do I have to provide some IP or host in my code, I am using KAA SANDBOX from AWS.
Console Output of Raspberry Pi attachedenter image description here here...
Finally I am able to do that using ..
Perform these two steps may be this can solve your problem.
Just run this command on host machine
sudo /usr/lib/kaa-sandbox/bin/change_kaa_host.sh $new host name/ip$
Then change the IP address of using Admin UI, for that you need to
sign in using username : kaa and passwword : kaa123
then go to setting > general setting then change the IP address preceded by :8080, enter your machine's public IP address, that can be easily accessible from anywhere.
Tips :: if you are using AWS instance then use public IP address of your instance.
Further error persist then drop your previous instance and launch a new instance.
For more details go the official documentation page
Hope it will be helpful for you.
You do not need to provide IP address.
You should download the generated SDK file and compile it with the source code. and then run it.
I have two instances. They are going to run the same app, but one is set up with a slightly different configuration. Right now I can go to their assigned elasticip and see that my site works on both. Th eonly other difference is that one is a micro instance and one is a small instance. Also, I have a bunch of DNS records pointing my domain name to the ip of the micro instance.
But what I want to do is swap them so that the small instance is now my main instance that has my domain pointing to it. I was hoping I could just disassociate the ip's and then reassociate the ip's only flipped around. But when I do that and then try to go to my domain.com I just get an error page. When I swap them back they both seem to work again. Is there something a more complicated I have to do?
edit:
When I try to SSH I also get all this stuff:
###########################################################
# WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! #
###########################################################
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
d6:ed:23:65:9c:da:0c:1b:2d:94:34:18:4d:68:8f:a5.
Please contact your system administrator.
Add correct host key in /Users/croberts/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/croberts/.ssh/known_hosts:17
RSA host key for 54.183.212.154 has changed and you have requested strict checking.
Host key verification failed.
Something nasty! haha.
The error message is indicating that the remote computer does not match the computer previously recorded in the known_hosts file.
When using ssh, each computer generates a fingerprint and this is recorded against the computer identifier (eg IP Address) that you are using to connect to the remote machine.
If you are switching an Elastic IP address between instances and also using the Elastic IP address to ssh into the instance, then the error quite correctly is warning you that the computer is not the same computer to which you last connected on that address.
You can remove the offending entry from the known_hosts file, or even delete the whole known_hosts file (which admittedly will remove such warnings even if they are legitimate).
You should have no problem swapping the elastic IP from one instance to another. It can take a few minutes to take effect, so make sure that you can reach the correct instance before testing.
You don't describe the error, but if you are using name-based virtual hosts, and are using a different name, that could be one cause. If you restart apache after swapping EIPs, does the problem go away?
Finally, to fix the ssh error, remove the entry from the known_hosts file - if you read the error message, it's on line 17.
I cannot access the ColdFusion 10 CFAdmin area and when I do I get the following in my logs
You tried to access the ColdFusion Administrator from a disallowed IP address (123.456.789.1).
The ColdFusion Administrator can only be concurrently accessed from localhost and 2 more IP addresses.
The specific sequence of files included or processed is: ........
The problem is that I am trying this on my own machine which has (for example here) the IP address of 123.456.789.1
I've tried restarting the services but I get the same error still?
Anyone seen this before?
Some clarification for what I've tried. Let say my remote server has the 123.456.789.1
1st attempt.
Restarted services and ensured I was the first person to try and access the CFAdmin area - No luck
2nd attempt
Used the "123.456.789.1" server as a SSH tunnel so my machines IP address would be the same as the servers when I tried to connect. Again restarted and got same error (in the logs)
3rd attempt (getting desperate)
Installed "elinks" (a text based browser) on the actual server. Again restarted and got same error (in the logs) when trying to log in.
This means that the IP restriction to CF Admin is applied. Go to Security > Allowed IP Addresses in CF Admin and remove the IPs (if any) from Allowed IP Addresses for ColdFusion Administrator access section.
That should fix it.
Edit: Since you are unable to access CF Admin, try this. Take a backup of neo-security.xml at C:\ColdFusion10\cfusion\lib. Open it with text editor and locate
<var name='allowedAdminIPList'><string>IP_Address</string></var>
Delete the IP listed there (IP_Address in example) and now it should look like
<var name='allowedAdminIPList'><string></string></var>
Save the file, restart ColdFusion Application Service and check CF Admin.
Is this a full copy of ColdFusion server or just a developer edition? The '2 more IP addresses' makes me think its a developer copy and you have it open in other places.