I am running the mnist_wiht_summaries and running the tensorboard pointing to the same log dir. It seems like the tensorboard is running successfully it shows:
Starting TensorBoard 47 at http://0.0.0.0:6006
(Press CTRL+C to quit)
but when I open http:/0.0.0.0:6006 it indicates
Network Error (tcp_error)
A communication error occurred: "" The Web Server may be down, too
busy, or experiencing other problems preventing it from responding to
requests. You may wish to try again at a later time.
For assistance, contact your network support team.
This is often resolved by using http://localhost:6006
I have had this issue myself several times. What you can do is access your computer at its external IP address.
Simply run ipconfig (windows) or ifconfig (linux) to find the ip adress, and then open your browser at that adress, e.g. 10.153.82.75:6006.
In some cases, it also seems that accessing localhost:6006 works.
Related
I'm trying to follow the instructions on how to create a persisted connection to an Azure Storage File Share. However from my Windows 10 machine I cannot get the cmdkey / net use combination to work:
C:\>cmdkey /add:myaccountname.file.core.windows.net /user:myaccountname /pass:myaccountkey
CMDKEY: Credential added successfully.
C:\>net use \\myaccountname.file.core.windows.net\mysharename
System error 53 has occurred.
The network path was not found.
However if I provide the username and password in a single net use command it works correctly:
C:\>net use z: \\myaccountname.file.core.windows.net\mysharename /u:myaccountname myaccountkey
The command completed successfully.
So it doesn't look like a firewall issue.
Any ideas? Is there another port that needs to be open to allow the cmdkey scenario to work?
Error 53 usually means that port 445 is blocked. Check the firewall on your computer, and if you are in a corporate environment, ask your corporate IT guys if they are blocking it. Many common ISP's block that port as well. For example, I know it doesn't work on Comcast but I've heard Time Warner Cable does not block it.
I've got problem with my Go server.
When I'm connected to my NAS via SSH and do ./gogs web, the server is starting. But when I close the SSH connection, the server is stopped.
How I can start my Go server permanently?
You have scripts in gogs allowing you to launch the server as a daemon:
scripts/init/debian/gogs (recently fixed with issue 519)
scripts/init/centos/gogs
That would allow the process to remain while the session is closed.
You have other options in issues 172.
This is not a Go-specifioc problem, what is happening is that the Go program is still attached to your terminal and when you log out, the kernel will trigger a SIGHUP to every binary still connected to that terminal session.
Your best option is probably to use nohup ./gogs web.
Second-best option would be to rewrite main, so that it intercepts and handles SIGHUP, stopping it from killing your program. However, doing so requires handling quite a few things properly (you really should close stdin, stdout and stderr; make sure all your logging is done through the log library, ...)
I've got a Windows 7 machine setup with vagrant/virtualBox - each morning when I try to access my development site it always a 'Unable to connect' error message in my Firefox browser.
Even though I have booted the machine using the 'vagrant up' command for some reason it only seems to be accessible via the browser once I have done the 'vagrant provision' command. This is obviously annoying as it starts doing stuff from scratch.. eg installing my mysql database again.
Can anyone provide any light into this, and why it seems to fail to connect all the time - as this provision command is only a temporary fix as i'll need to amend the DB everytime which is only feasible in the short term.
Might just be my own setup - but I noticed nginx was restarting so have to restart this each time
Hi I am writing a WPF app that needs to access my files on another PC on my network (domain). My first try to access a remote folder has not been a raging success.
On my Windows 7 laptop I entered in Windows Explorer
\\WIN-DCname\c$
, this is the path to C drive on my test domain controller, and when challenged I logged in with the administrator account for the DC. I can then access the folder tree of C drive as expected.
As a test application I used the following to probe that same drive:
Try
Dim DirInfo As New DirectoryInfo("\\WIN-DCname\c$")
Dim Dirs = DirInfo.GetDirectories.OrderByDescending(Function(x) x.FullName)
Catch ex As Exception
End Try
but the GetDirectories line throws an exception:
The system detected a possible attempt to compromise security. Please
ensure that you can contact the server that authenticated you.
I'm starting to think there is a permissions problem here.... Do I have to programmatically authenticate again prior to doing this? If so how?
Or is it not possible to do a GetDirectories over the network? Is there another way?
Thanks for any advice!
In the end it turns out that I needed to use Impersonation, which lets me programmatically emulate another user while executing a block of code. No opening of ports was required.
Microsoft explains it all as follows:
CAUSE This problem occurs because the network firewall filters Kerberos traffic.
RESOLUTION To resolve this problem, configure the network firewall so that TCP port 88 and UDP port 88 are not blocked for either domain.
Multiple network connections - Wireless, Wired Ethernet
The error “The system detected a possible attempt to compromise security.” started happening for me when I started alternately using a Wireless network connection at night and a wired Ethernet connection during the day.
I am using some EC2 instances to run some large jobs I can not run locally. The issue I am seeing is that after a while (X hours since the process started) my connection on my shell gives me a broken pipe error
ubuntu#ip-10-122-xxx-xxx:~/stratto/ode$ Write failed: Broken pipe
The instance is still there because I can reconnect with no problems, but how can I reconnect and get back at seeing the logs of the process as before the 'Broken Pipe'
Any tip much appreciated,
Thanks!
Redirect your output to a file and then run the program "nohup ..." to ensure the disconnect doesn't kill it. Use "tail -f" to monitor the redirected file.
Note: Originally said to use "tee" but that won't work. I think a straight redirect and then tail on the file works.
You can use screen to run processes in the cloud even when you are not connected to the server.
sudo apt install screen
To specifically address the issue described in the original post (e.g. connecting to AWS EC2 instances) I a basic example and a more advanced example of using screen.
You can use "screen". Detach from it and ping to google.com. So there ssh session will be active through out the installation.