Re: [opensuse] Processes quitting
On Sunday 04 January 2015, Aaron Digulla wrote:
Where did you get "noip2"? Is that from your DDNS provider? If so, which one do you use? Is there a man page? Does it support options for logging? If so, did you set them to "log everything" and looked in the log file?
Note that most DDNS clients simply connect to a server telling them the name of the connection. So basically, if your local name is "a.b.c", then they connect to the DDNS server and send them the string "a.b.c". The TCP/IP protocol will then tell the server what the IP address of the client is and that's it.
A problem here is when the client doesn't get notified properly when the local IP address changes - in that case, your IP address would change but the client wouldn't notify the DDNS server right away.
Hence if you can't get logging to work properly, you just have to restart the client every N days or hours.
Regards,
As I read it, the client phones home every 30 minutes and the server gets the IP info from that, so the client is independent of any address changes. It is really a dumb process... brute force, if you will, but it works. Usually. Until it mysteriously quits. Yes, I could write a script to restart the job and cron it but that is a bandaid. If there is some fundamental f.u. going on I'd like to discover it. Logging has been no help. Oh, and why "noip2"? Because that is the name of the client. Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Fred n Sandy
As I read it, the client phones home every 30 minutes and the server gets the IP info from that, so the client is independent of any address changes. It is really a dumb process... brute force, if you will, but it works. Usually. Until it mysteriously quits. Yes, I could write a script to restart the job and cron it but that is a bandaid. If there is some fundamental f.u. going on I'd like to discover it. Logging has been no help.
No need to "write a script", but you should configure the noip2 app and it is really quite simple. noip2 -h will get you there. You can configure the time-lapse for the "call home" function to what-ever you like. In your case occasionally 30 minutes appears to be too long. I run a server and keep mine at 10 minutes. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 04.01.2015 um 18:43 schrieb Fred n Sandy:
As I read it, the client phones home every 30 minutes and the server gets the IP info from that, so the client is independent of any address changes. It is really a dumb process... brute force, if you will, but it works. Usually. Until it mysteriously quits. Yes, I could write a script to restart the job and cron it but that is a bandaid. If there is some fundamental f.u. going on I'd like to discover it. Logging has been no help.
Ok, some rough outline of the remote help process: You supply us with reliable information about your system, program versions, possibly links to where you got unusual tools (like the noip2 executable) and we rise our voices when we spot something. Remote help isn't telepathy. If you want us to help you, you need to tell us everything you know and everything which might be related. Which isn't easy - usually, when someone reaches out for help, they are frustrated. Not an idea state of mind to think about everything that some unknown person on the other side of the globe might need to know to help you. With that out of the way, to keep a process alive, there are several ways which are better than cron. If you have a Linux system with the old init system (https://en.wikipedia.org/wiki/Init), you should look at daemonize (http://linux.die.net/man/1/daemonize). If you have a more modern startup system like systemd (https://en.wikipedia.org/wiki/Systemd), then they have config files where you can say "start this when this happend and restart it when it exist and make sure it stays alive but only restart it 10 times if it terminates after 10 seconds". If you know old System V init scripts, this explains how to convert the information for systemd: http://0pointer.de/blog/projects/systemd-for-admins-3.html Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Aaron Digulla
-
Fred n Sandy
-
Patrick Shanahan