Staring noip2 with boot

fabula · 02-25-2016, 04:14 AM

I have Slackware 14.1 64bit with multilib. I installed noip2 from SlackBuilds Repository. During a boot OS rc.local does not start noip2. /etc/rc.d/rc.local is set correctly with:

Code:

if [ -x /etc/rc.d/rc.noip2 ]; then
 . /etc/rc.d/rc.noip2 start
fi

Scripts in rc.local before this work properly, but after this script not work at all.

When I run /etc/rc.d/rc.local, after entering in KDE, noip2 working properly like all scripts in rc.local.

ponce · 02-25-2016, 04:43 AM

Quote:

Originally Posted by fabula

Code:

if [ -x /etc/rc.d/rc.noip2 ]; then
 . /etc/rc.d/rc.noip2 start
fi

if you add a "." before the script it means you source it and this way the start argument is never passed to the script.

you should be ok just removing that, like

Code:

if [ -x /etc/rc.d/rc.noip2 ]; then
  /etc/rc.d/rc.noip2 start
fi

fabula · 02-25-2016, 06:01 AM

Quote:

Originally Posted by ponce

if you add a "." before the script it means you source it and this way the start argument is never passed to the script.

you should be ok just removing that, like

Code:

if [ -x /etc/rc.d/rc.noip2 ]; then
  /etc/rc.d/rc.noip2 start
fi

Thanks for the quick answer. First, I must say that I appreciate very much your work.
Now, rc.local start scripts before and after this code:

Code:

/etc/rc.d/rc.noip2 start

But in KDE:

user:

Code:

bash-4.2$ /etc/rc.d/rc.noip2 status
no-ip client daemon is not runnig

root:

Code:

bash-4.2$ /etc/rc.d/rc.noip2 status
no-ip client daemon is not runnig

ponce · 02-25-2016, 06:06 AM

"status" doesn't seem to work (report the thing to the maintainer): to check if it's running do it with

Code:

ps aux | grep noip

fabula · 02-25-2016, 06:11 AM

Quote:

Originally Posted by ponce

"status" doesn't seem to work (report the thing to the maintainer): to check if it's running do it with

Code:

ps aux | grep noip

Code:

bash-4.2$ ps aux | grep noip
1000      1449  0.0  0.0   7116   976 pts/1    S+   12:08   0:00 grep noip

slacker1337 · 02-25-2016, 06:19 AM

Just to cover all the bases, are both /etc/rc.d/rc.local and /etc/rc.d/rc.noip2 set as executable?

ponce · 02-25-2016, 06:20 AM

it can be it errors something when launched: as the start script just execute it with its config file as an argument, I suppose you can also launch it manually from a root terminal

Code:

/usr/bin/noip2 -c /etc/no-ip2.conf

and see which error it spits.
check also the other command line options

Code:

$ noip2 --help
noip2: invalid option -- '-'

USAGE: noip2 [ -C [ -F][ -Y][ -U #min]
        [ -u username][ -p password][ -x progname]]
        [ -c file][ -d][ -D pid][ -i addr][ -S][ -M][ -h]

Version Linux-2.1.9
Options: -C               create configuration data
         -F               force NAT off
         -Y               select all hosts/groups
         -U minutes       set update interval
         -u username      use supplied username
         -p password      use supplied password
         -x executable    use supplied executable
         -c config_file   use alternate data path
         -d               increase debug verbosity
         -D processID     toggle debug flag for PID
         -i IPaddress     use supplied address
         -I interface     use supplied interface
         -S               show configuration data
         -M               permit multiple instances
         -K processID     terminate instance PID
         -z               activate shm dump code
         -h               help (this text)

you can also open two other terminals executing the following commands when you execute it like above and see eventual output in /var/log/messages and /var/log/syslog flowing

Code:

tail -f /var/log/messages
tail -f /var/log/syslog

fabula · 02-25-2016, 06:23 AM

Quote:

Originally Posted by slacker1337

Just to cover all the bases, are both /etc/rc.d/rc.local and /etc/rc.d/rc.noip2 set as executable?

yes

slacker1337 · 02-25-2016, 06:27 AM

I also recall (it's been a while), that I had to run the noip2 setup before I could get the service to start correctly. Essentially, your service could be attempting to start but, because it hasn't been configured with your noip username/password, it's failing.

fabula · 02-25-2016, 06:54 AM

Quote:

Originally Posted by slacker1337

I also recall (it's been a while), that I had to run the noip2 setup before I could get the service to start correctly. Essentially, your service could be attempting to start but, because it hasn't been configured with your noip username/password, it's failing.

no-ip.conf is created. This is ok. When I execute /etc/rc.d/rc.noip2 start from KDE IP adress is renewed...

fabula · 02-25-2016, 07:08 AM

Quote:

Originally Posted by ponce

it can be it errors something when launched: as the start script just execute it with its config file as an argument, I suppose you can also launch it manually from a root terminal

Code:

/usr/bin/noip2 -c /etc/no-ip2.conf

and see which error it spits.
check also the other command line options
[code]$ noip2 --help
noip2: invalid option -- '-'

.......

you can also open two other terminals executing the following commands when you execute it like above and see eventual output in /var/log/messages and /var/log/syslog flowing

Code:

tail -f /var/log/messages
tail -f /var/log/syslog

Code:

/usr/bin/noip2 -c /etc/no-ip2.conf

Code:

tail -f /var/log/messages

noip2[1362]: v2.1.9 daemon started with NAT enabled

an my ip is renewed....

But on boot nothing happened...

bassmadrigal · 02-25-2016, 07:15 AM

How do you connect to your internet? If it is wireless with wicd/NetworkManager, it could be that you're not connected to the internet when the script originally runs, since (I believe) you usually don't connect until the GUIs come up. From other posts on the forum, it sounds like Network Manager will allow you to run scripts after it connects to the network, so you could have it run noip2 that way.

fabula · 02-25-2016, 07:29 AM

Quote:

Originally Posted by bassmadrigal

How do you connect to your internet? If it is wireless with wicd/NetworkManager, it could be that you're not connected to the internet when the script originally runs, since (I believe) you usually don't connect until the GUIs come up. From other posts on the forum, it sounds like Network Manager will allow you to run scripts after it connects to the network, so you could have it run noip2 that way.

My connection is cable/NetworkManager. How can I run script after it connects to the network.

bassmadrigal · 02-25-2016, 07:55 AM

That I don't know. I've never used Network Manager. I'd imagine it'd be in Network Manager's settings, but you might need to enable a passwordless sudo for it to work properly (since I imagine noip2 requires root to start).

fabula · 02-25-2016, 08:45 AM

Quote:

Originally Posted by bassmadrigal

That I don't know. I've never used Network Manager. I'd imagine it'd be in Network Manager's settings, but you might need to enable a passwordless sudo for it to work properly (since I imagine noip2 requires root to start).

I think that Network Manager is not problem. When I restarted my system to Default runlevel (id:3:initdefault

, DHCP gave me IP address, but noip2 did not update the DNS.