Fedora Linux Support Community & Resources Center
  #1  
Old 15th February 2012, 09:40 PM
sidebrnz Online
Registered User
 
Join Date: Oct 2007
Location: Freedonia
Age: 64
Posts: 2,605
linuxfirefox
Troubleshooting a failing service

For several months, now, I've been using dynamic DNS from https://www.dnsexit.com/ to make my home box visible on the Internet as a subdomain of my own private domain. Everything worked fine until I "upgraded" to F16 and the New! Improved! Shiny! systemd. Now, I get an error message at boot that the service failed and if I run

systemctl status ipUpdate.service

I'm told that it failed with this error: (code=exited, status=203/EXEC). And, if I use nslookup, I get the wrong IP. However, if I run this:

/usr/sbin/ipUpdate.pl

it works Just Fine, and I start getting the right IP. (From what I can tell, running that script is the core of what the service does.) I've emailed their support twice with a request for assistance but received no reply because they only support paying customers and my domain's not hosted there. Does anybody know how to troubleshoot this? If not, I'll probably have to set it up as a cron job, running the script directly but I'd rather not go that route if I don't have to.
__________________
Registered Linux user #470359 and permanently recovered BOFH.

Any advice in this post is worth exactly what you paid for it.
Reply With Quote
  #2  
Old 15th February 2012, 09:51 PM
jpollard Offline
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,830
linuxfedorafirefox
Re: Troubleshooting a failing service

It may be running the "service" before the network is ready. This is a normal problem of systemd as it does not easily permit scheduling of startup processes.

You can try adding an "after=NetworkManager-wait-online.service" and possibly adding "network.target" as another.
Reply With Quote
  #3  
Old 15th February 2012, 10:14 PM
sidebrnz Online
Registered User
 
Join Date: Oct 2007
Location: Freedonia
Age: 64
Posts: 2,605
linuxfirefox
Re: Troubleshooting a failing service

The service runs every few hours so that if my dynamic IP changes, my DNS gets updated. No matter when I check, it tells me the same thing:

[root@khorlia Desktop]# systemctl status ipUpdate.service
ipUpdate.service - LSB: DnsExit.Com dynamic dns client.
Loaded: loaded (/etc/rc.d/init.d/ipUpdate)
Active: failed since Tue, 14 Feb 2012 18:28:00 -0800; 19h ago
CGroup: name=systemd:/system/ipUpdate.service

As I only reboot for a kernel update, and haven't had time to do so since the one this morning, you can see what I mean. And, here's what I get if I stop and restart it:

[root@khorlia Desktop]# systemctl stop ipUpdate.service
[root@khorlia Desktop]# systemctl start ipUpdate.service
Job failed. See system logs and 'systemctl status' for details.
[root@khorlia Desktop]# systemctl status ipUpdate.service
ipUpdate.service - LSB: DnsExit.Com dynamic dns client.
Loaded: loaded (/etc/rc.d/init.d/ipUpdate)
Active: failed since Wed, 15 Feb 2012 14:11:59 -0800; 12s ago
Process: 21010 ExecStart=/etc/rc.d/init.d/ipUpdate start (code=exited, status=203/EXEC)
CGroup: name=systemd:/system/ipUpdate.service
__________________
Registered Linux user #470359 and permanently recovered BOFH.

Any advice in this post is worth exactly what you paid for it.
Reply With Quote
  #4  
Old 16th February 2012, 12:59 AM
jpollard Offline
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,830
linuxfedorafirefox
Re: Troubleshooting a failing service

And what is in the /system/ipUpdate.service file?
Reply With Quote
  #5  
Old 16th February 2012, 01:23 AM
sidebrnz Online
Registered User
 
Join Date: Oct 2007
Location: Freedonia
Age: 64
Posts: 2,605
linuxfirefox
Re: Troubleshooting a failing service

Here's the contents of /etc/rc.d/init.d/ipUpdate, which worked Just Fine under F14:

Code:
# chkconfig: 345 85 60
# description: DnsExit.Com dynamic dns client.
# processname: ipUpdate.pl

### BEGIN INIT INFO
# Provides: ipUpdate
# Required-Start: $local_fs $network 
# Should-Start: 
# Required-Stop:
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
# Short-Description: DnsExit.Com dynamic dns client.
# Description: DnsExit.Com dynamic dns client.
### END INIT INFO

# Source function library.
if [ -f /etc/SuSE-release ]; then
   SUSE=1
   START=startproc
   STATUS="rc_status -v"
   . /etc/rc.status
   rc_reset
else
   SUSE=0
   START=daemon
   STATUS=echo
   . /etc/rc.d/init.d/functions

fi

start() {
	echo -n $"Starting ipUpdate: "
	$START /usr/sbin/ipUpdate.pl
	touch /var/lock/subsys/ipUpdate
	$STATUS
}

stop() {
	echo -n $"Shutting down ipUpdate: "
	killproc ipUpdate.pl
	rm -f  /var/lock/subsys/ipUpdate
        $STATUS
}

[ -f /usr/sbin/ipUpdate.pl ] || exit 0
grep "daemon[:space:]*=[:space:]*no" /etc/dnsexit.conf >/dev/null 2>&1 && exit 0
case "$1" in
    start)
        start
        ;;
    stop)
        stop
        ;;
    status)
        ;;
    restart)
        stop
        start
        ;;
    condrestart)
        ;;
    reload)
        ;;
    *)
        echo $"Usage: $0 {start|stop|status|restart|condrestart|reload}"
        ;;
esac
[ $SUSE -eq "1" ] && rc_exit
exit 0
Please note that there doesn't seem to be anything in the file that generates that kind of error message, and I don't know enough about this kind of thing to work our what's causing it now that wasn't doing it before.
__________________
Registered Linux user #470359 and permanently recovered BOFH.

Any advice in this post is worth exactly what you paid for it.
Reply With Quote
  #6  
Old 16th February 2012, 05:41 AM
cazo Offline
Registered User
 
Join Date: Sep 2005
Location: Redneck Riviera
Posts: 358
linuxchrome
Re: Troubleshooting a failing service

It looks to me like the code is missing something
Code:
else
   SUSE=0
   START=daemon
   STATUS=echo
   . /etc/rc.d/init.d/functions
fi

start() {
	echo -n $"Starting ipUpdate: "
	$START /usr/sbin/ipUpdate.pl
	touch /var/lock/subsys/ipUpdate
	$STATUS
}
I think that just calls echo (after running 'ipUpdate.pl'), instead of returning anything useful. You can try adding something like:
Code:
else
   SUSE=0
   START=daemon
   STATUS=echo
   . /etc/rc.d/init.d/functions
fi

start() {
	echo -n $"Starting ipUpdate: "
	$START /usr/sbin/ipUpdate.pl
        RETVAL=$?
	touch /var/lock/subsys/ipUpdate
	$STATUS
        return $RETVAL
}
and see if that helps.
Reply With Quote
  #7  
Old 16th February 2012, 06:05 AM
sidebrnz Online
Registered User
 
Join Date: Oct 2007
Location: Freedonia
Age: 64
Posts: 2,605
linuxfirefox
Re: Troubleshooting a failing service

Remember, this script worked Just Fine, TYVM, exactly as it is now, right up until I "upgraded" to F16.
__________________
Registered Linux user #470359 and permanently recovered BOFH.

Any advice in this post is worth exactly what you paid for it.
Reply With Quote
  #8  
Old 16th February 2012, 02:01 PM
jpollard Offline
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,830
linuxfedorafirefox
Re: Troubleshooting a failing service

F16 uses systemd which is NOT a SysVinit compatible system, so things don't work the same.

I expect you put a file in /lib/systemd/system (or /etc/systemd/system) named ipUpdate.service.

This file determines how/when it runs. What does this file contain?

Or are you trying to use the SysVinit "compatability" operation?
Reply With Quote
  #9  
Old 16th February 2012, 06:36 PM
sidebrnz Online
Registered User
 
Join Date: Oct 2007
Location: Freedonia
Age: 64
Posts: 2,605
linuxfirefox
Re: Troubleshooting a failing service

I installed the service (from a .rpm) when I was running F14 and it worked. Now that I've "upgraded" to F16, it doesn't. There's no file in either of those two directories that appears to control this, so I have no idea what's calling it or how.
__________________
Registered Linux user #470359 and permanently recovered BOFH.

Any advice in this post is worth exactly what you paid for it.
Reply With Quote
  #10  
Old 16th February 2012, 07:23 PM
jpollard Offline
Registered User
 
Join Date: Aug 2009
Location: Waldorf, Maryland
Posts: 6,830
linuxfedorafirefox
Re: Troubleshooting a failing service

Try moving the startup into rc.local, and change the options on rc.local to delay until after the network is functional.

There are a number of threads on that subject.
Reply With Quote
  #11  
Old 16th February 2012, 07:44 PM
sidebrnz Online
Registered User
 
Join Date: Oct 2007
Location: Freedonia
Age: 64
Posts: 2,605
linuxfirefox
Re: Troubleshooting a failing service

I don't know if I haven't made myself clear, or if you're just not reading what I've written.

If I were to restart that service RIGHT NOW, without rebooting, it would still fail in exactly the same way. I know, because I've tried it, more than once. Changing the start time at boot won't help.
__________________
Registered Linux user #470359 and permanently recovered BOFH.

Any advice in this post is worth exactly what you paid for it.
Reply With Quote
Reply

Tags
failing, service, troubleshooting

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
chkconfig wokrs but service start says unknow service gkk Servers & Networking 4 10th December 2007 02:45 AM
Troubleshooting service hang AlFrugal Using Fedora 0 13th November 2007 06:14 PM
Running mldonkey as a service, service does not startup Dhana Servers & Networking 2 14th August 2006 04:43 AM
how to connect my roadrunner service or aol service to my fedora core 1 on my compter john nelson jr Using Fedora 1 14th March 2005 12:22 AM


Current GMT-time: 06:45 (Tuesday, 02-09-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat