New answers tagged server
Here is how I solved the same problem #!/bin/bash NOTIFYEMAIL=<your email> SMSEMAIL=<cell phone number @ sms-gateway> SENDEREMAIL=alert@localhost SERVER=http://127.0.0.1/ PAUSE=60 FAILED=0 DEBUG=0 while true do /usr/bin/curl -sSf $SERVER > /dev/null 2>&1 CS=$? # For debugging purposes if [ $DEBUG -eq 1 ] then echo "STATUS = $CS" ...
Look into using a VM Hypervisor like KVM or Xen. KVM is built into the Linux kernel (and Xen is scheduled to be at sometime in the future). You can manage KVM using a tool like virt-manager.
You have to use an outside IP address to be able to check the forwarding. Forwarding on most routers is only for incoming traffic, not for stuff that originates on the inside. You can use tor to make sure your requests come in from outside.
It seems that flask (lightweight python server framework) is the culprit. I have seen many questions about why it becomes hanging. The behaviour I was describing fits the case, as if flask entered an infinite loop or is waiting for threads to finish or for more memory or ... : the server was running but curl http://localhost... would not return but not fail ...
I had the same problem. I had previously setup ssh keys via the ssh-keygen and then ssh-copy-id -i ~/.ssh/id_rsa.pub firstname.lastname@example.org ssh worked fine without asking me for a password so I was confused as to why sshfs still wanted the password... That is to say, ssh email@example.com worked fine, however sshfs still asked for a password when I ...
What this means, ultimately, is that the SSH server on the other end has crashed or is in some way not working. It's still listening on the socket but it's not capable of performing a cryptographic handshake. The only solution is to restart the process on the remote side.
Try: ssh -2 name@ip or ssh -2 -l name ip
Another alternative would be a terminal server http://www.ltsp.org/ , which is quite common in computer labs as well.
Devote a machine or VM to an LDAP server. This will provide authentication to all of the machines. Devote a machine with lots of storage to provide a centralized file store via NFS. You can hold home directories here and globally installed software exported to /home and /usr/global. Devote a VM to CUPS to provide centralized printing.
When it comes to TCP ports (which port 80 is), you can only bind one process to a given port. The process in this case is Apache, so no other process can use it while Apache is bound to the port. You can use the command netstat with the -t switch to see TCP ports in use. $ netstat -tapn | grep :80 tcp 0 0 :::80 :::* LISTEN ...
You got the Address In Use because Apache already uses port 80. If you want to access your Express app throught port 80, then you have to shutdown Apache and run your app on port 80.
No DHCPOFFER received. You are probably not using a router with DHCP? In case you're using a modem, you have to manually setup your network connection. How? Same way you would do so when using Debian. How? That's off topic here and that's why that article says advanced Linux users only. You had a working /etc/network/interfaces earlier anyway when you ...
GUI for managing NIS No, not one I've ever seen. You typically manage it via text files, these files are often under RCS, CVS, or SVN control. I usually keep the source files in this directory: /etc/yp This is where I check them out to work on them, etc. When I want to propagate changes I cd to this directory: /var/yp Here's where I maintain a ...
The config files look OK except that in the file /var/named/mydomain.com.zone you need to put an A record for mydomain.com, something like this: mydomain.com. IN A x.y.z.t Add this line in /var/named/mydomain.com.zone, don't forget to update the serial at the beginning of the file and then restart or reload the named service.
Idea #1 - UDP port forwarding? Confirm that when you opened this port on your router that you specified either both TCP/UDP or UDP. The types of these ports matters, and can often be overlooked when opening ports on ones firewall/router. Idea #2 - Port forward on pocketmine realms issue? I came across this forum post which sounds like exactly the issue ...
The reason why you don't see LISTEN on the minecraft server port is due to the way the UDP protocol works. A server that uses the TCP protocol "listens" for a connection so that when a client tries to connect, it will commence a session and transfer data using the TCP/IP protocol. If there is nothing "listening" on a certain port for TCP connections, the ...
Top 50 recent answers are included