Scheduler as a service RHEL 7

[Michael M]

Currently I have "/etc/systemd/system/web2py-scheduler.service":
---------------------------------
[Unit]
Description=Web2py Scheduler service

chedulerService]
ExecStart=  /usr/bin/python /opt/www-data/web2py/web2py.py -K networktools -Q &
Restart=always
KillSignal=SIGQUIT
Type=notify
NotifyAccess=all

[Install]
WantedBy=multi-user.target
-----------------------


RHEL 7 and Im when i enable and start then get status i get "starting"  but never fully starts.  Am i calling it wrong or any thoughts?

Thanks!

[Michael M]

[root@server~]# systemctl status web2py-scheduler.service -l
● web2py-scheduler.service - Web2py Scheduler service
   Loaded: loaded (/etc/systemd/system/web2py-scheduler.service; enabled; vendor preset: disabled)
   Active: activating (start) since Sun 2016-03-13 19:09:14 PDT; 38s ago
 Main PID: 13549 (python)
   CGroup: /system.slice/web2py-scheduler.service
           └─13549 /usr/bin/python /opt/www-data/web2py/web2py.py -K networktools &

Mar 13 19:09:14 server systemd[1]: Starting Web2py Scheduler service.

[Michael M]

When I take off the '&' at the end of the command I get the following message:

# systemctl restart web2py-scheduler.service
Job for web2py-scheduler.service failed because a fatal signal was delivered to the control process. See "systemctl status web2py-scheduler.service" and "journalctl -xe" for details.

[Michael M]

I'm not stuck on getting it running as a Service. 

Just getting it so it runs when the server is power cycled or otherwise.  Insuring that the scheduler is running so it can do DB updates of flat-files that get dumped on the box daily.

[Dave S]

On Tuesday, March 15, 2016 at 2:35:40 PM UTC-7, Michael M wrote:

I'm not stuck on getting it running as a Service. 

Just getting it so it runs when the server is power cycled or otherwise.  Insuring that the scheduler is running so it can do DB updates of flat-files that get dumped on the box daily.

It's not clear whether that runs at an appropriate privilege level.  The upstart example in the deployment recipes has an explicit sudo in the invocation.  Do you need a sudo in your ExecStart?

<URL:http://web2py.com/books/default/chapter/29/13/deployment-recipes#Start-the-scheduler-as-a-Linux-service--upstart->

/dps

[Michael M]

I read though that a ton of times but I believe RHEL 7 retired that method in /etc/init/ and conf files and moved to systemd and services. 

Ill try the sudo in ExecStart.  And report back.

[Michael M]

So some googling later for "Persistant Python script Rhel7 service"
I changed the service to the following and now the service will run.

Thank-you Dave for getting me back to thinking about writing the service correctly.

Between the dashes below is this file: 

"/etc/systemd/system/web2py-scheduler.service"

And can be activated via:

"systemctl enable web2py-scheduler.service"
"systemctl start web2py-scheduler.service"

-------------
[Unit]
Description=Web2py Scheduler service

[Service]
ExecStart=/usr/bin/python /opt/www-data/web2py/web2py.py -K networktools,networktools,networktools
Type=simple

[Install]
WantedBy=multi-user.target
--------------

[Dave S]

On Tuesday, March 15, 2016 at 6:49:44 PM UTC-7, Michael M wrote:

So some googling later for "Persistant Python script Rhel7 service"
I changed the service to the following and now the service will run.

Thank-you Dave for getting me back to thinking about writing the service correctly.

And you've got me studying 

<URL:https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Managing_Services_with_systemd-Services.html

>

I'm on section 8.2 so far.

 

Between the dashes below is this file: 

"/etc/systemd/system/web2py-scheduler.service"

And can be activated via:

"systemctl enable web2py-scheduler.service"
"systemctl start web2py-scheduler.service"

-------------
[Unit]
Description=Web2py Scheduler service

[Service]
ExecStart=/usr/bin/python /opt/www-data/web2py/web2py.py -K networktools,networktools,networktools
Type=simple

[Install]
WantedBy=multi-user.target
--------------

/dps

[Michael M]

Sorry Dave, I know how that goes :)

If you find a more elegant solution. I'm open.