Fedora Linux Support Community & Resources Center
Old 29th June 2011, 02:10 AM
m1boli Offline
Registered User
Join Date: Sep 2010
Posts: 23
systemd exec 203 failed service startup (a non-starter, so to speak)

I am having trouble starting a flash policy daemon under systemd in Fedora 15. It uses my own .service file. It dies during bootup with status=203/EXEC.

Flashpolicyd.py is a little Python program that opens up a socket on TCP port 843 and listens. It is not a forking server.

After putting the flashpolicyd.service file in /etc/systemd/system/multi-user.target.wants/, all seems good. The new service shows up on the systemctl list of all services, I can enable it and start it manually with systemctl start flashpolicyd.service

However flashpolicyd fails during bootup with exit status 203.

I set up the systemd debugging parameters on the kernel, where I see the following:
systemd[1]: Installed new job flashpolicyd.service/start as 91
systemd[1]: About to execute: /usr/local/sbin/flashpolicyd.py --file=/var/www/crossdomain.xml
systemd[1]: Forked /usr/local/sbin/flashpolicyd.py as 746
systemd[1]: flashpolicyd.service changed dead -> running
systemd[1]: Job flashpolicyd.service/start finished, result=done
systemd[1]: Got SIGCHLD for process 746 (sd.exec)
systemd[1]: Child 746 died (code=exited, status=203/EXEC)
systemd[1]: Child 746 belongs to flashpolicyd.service
systemd[1]: flashpolicyd.service: main process exited, code=exited, status=203
systemd[1]: flashpolicyd.service changed running -> auto-restart
...and it retries several times before giving up

-- There is a Python try/except block around the main code in an effort to print errors in a better form, but it does not seem to be catching anything.
-- I have played with the After= in the .service file to make sure everything imaginable is loaded.
-- I cannot find any documentation on Python error code 203
-- And, as mentioned, it works just fine if I start it manually with systemctl.

Any ideas?

Here is my flashpolicyd.service file:

After=basic.target syslog.target network.target

ExecStart=/usr/local/sbin/flashpolicyd.py --file=/var/www/crossdomain.xml


Reply With Quote
Old 18th March 2016, 08:05 PM
rablanken Offline
Registered User
Join Date: Mar 2016
Location: SF, California
Posts: 1
Re: systemd exec 203 failed service startup (a non-starter, so to speak)

Check the permissions of /usr/local/sbin/flashpolicyd.py and make sure that it is executable.
Reply With Quote

error 203, service startup error, systemd

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
change startup runlevel & exec boot loader CopyrightPhilly Using Fedora 0 12th May 2009 07:15 PM
Running mldonkey as a service, service does not startup Dhana Servers & Networking 2 14th August 2006 04:43 AM
new FC5 2.6.16 install - exec of init () failed!!! sbbaxter EOL (End Of Life) Versions 8 24th April 2006 06:01 PM
on first install exec of anaconda failed error billco Installation, Upgrades and Live Media 0 24th April 2006 11:30 AM

Current GMT-time: 17:16 (Sunday, 20-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

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