[opensuse] Processes quitting
I have a perplexing problem with my lampserver. My location has a dynamic IP, so I use a DDNS service which, in this case, requires multiple instances (-M option) of the DDNS client. I give the command, the processes start and all is right with the world until some unknown time later when the dirty $#@! quits. Uptime shows this: lampserver:/home/fred # uptime 09:25am up 53 days 7:45, lampserver:/home/fred # ps -ef |grep noip nobody 14358 1 0 Jan03 ? 00:00:00 /usr/local/bin/noip2 -M -c /usr/local/etc/<first>.conf nobody 14360 1 0 Jan03 ? 00:00:00 /usr/local/bin/noip2 -M -c /usr/local/etc/<second>.conf nobody 14362 1 0 Jan03 ? 00:00:00 /usr/local/bin/noip2 -M -c /usr/local/etc/<third>.conf So, the system has been up for almost 2 months and I have had to restart the client three times. OK, I know several ways to work around the problem, to bandaid it, but I would really like to discover what is causing it in the first place. Any pointers would be welcome. Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 04.01.2015 um 16:44 schrieb Fred n Sandy:
I have a perplexing problem with my lampserver. My location has a dynamic IP, so I use a DDNS service which, in this case, requires multiple instances (-M option) of the DDNS client. I give the command, the processes start and all is right with the world until some unknown time later when the dirty $#@! quits.
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, -- 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
On 01/04/2015 10:44 AM, Fred n Sandy wrote:
I have a perplexing problem with my lampserver. My location has a dynamic IP, so I use a DDNS service which, in this case, requires multiple instances (-M option) of the DDNS client. I give the command, the processes start and all is right with the world until some unknown time later when the dirty $#@! quits.
Depending on your ISP, you might have a consistent host name, even
though your IP address changes. If so, just use that host name, instead
of bothering with DDNS. For example, my ISP provides a DHCP address,
which changes so seldom it's virtually static. However, the host name
is based on the cable modem and firewall MAC addresses and so never
changes, unless I change hardware. Failing that, there should be a hook
in the DHCP client, which you can use to trigger a DDNS update.
participants (3)
-
Aaron Digulla -
Fred n Sandy -
James Knott