I have found this
https://www.digitalocean.com/community/tutorials/how-to-configure-a-linux-service-to-start-automatically-after-a-crash-or-reboot-part-1-practical-examples

Service section should contain following:
[Service]
Restart=always

It looks like it works,
so I hope it will be well.




Dne pondělí 30. května 2016 12:15:18 UTC+2 Mirek Zvolský napsal(a):
>
> Please help....
>
> Debian Jessie, postgres, web2py-scheduler
>
> How can I prevent following crash - inactive scheduler?
> Or how can I be sure that the scheduler is running and restart it if 
> needed?
>
>
>
> /etc/systemd/system/web2py-scheduler.service
> -------------------------------------------------
> [Unit]
> Description=Web2py Scheduler service
>
> [Service]
> ExecStart=/usr/bin/python /home/www-data/web2py/web2py.py -K 
> codex2020,codex2020,codex2020
> Type=simple
>
> [Install]
> WantedBy=multi-user.target
> -------------------------------------------------
>
>
> systemctl status web2py-scheduler
> -------------------------------------------------
> web2py-scheduler.service - Web2py Scheduler service 
>                                                                               
>          
>   Loaded: loaded (/etc/systemd/system/web2py-scheduler.service; enabled) 
>                                                                    
>   Active: inactive (dead) since Mon 2016-05-30 02:16:39 CEST; 9h ago       
>  <---- INACTIVE !!!!!!                                                     
>                   
>  Process: 5552 ExecStart=/usr/bin/python /home/www-data/web2py/web2py.py 
> -K codex2020,codex2020,codex2020 (code=exited, status=0/SUCCESS)   
> Main PID: 5552 (code=exited, status=0/SUCCESS) 
>                                                                               
>                
>
>                                                                               
>                                                               
> May 30 02:16:39 mzDebian python[5552]: File 
> "/home/www-data/web2py/gluon/contrib/pg8000/core.py", line 1697, in execute 
>                      
> May 30 02:16:39 mzDebian python[5552]: self.handle_messages(cursor) 
>                                                                          
> May 30 02:16:39 mzDebian python[5552]: File 
> "/home/www-data/web2py/gluon/contrib/pg8000/core.py", line 1770, in 
> handle_messages              
> May 30 02:16:39 mzDebian python[5552]: self._close() 
>                                                                               
>           
> May 30 02:16:39 mzDebian python[5552]: File 
> "/home/www-data/web2py/gluon/contrib/pg8000/core.py", line 1438, in _close 
>                       
> May 30 02:16:39 mzDebian python[5552]: self._flush() 
>                                                                               
>           
> May 30 02:16:39 mzDebian python[5552]: File 
> "/usr/lib/python2.7/socket.py", line 303, in flush 
>                                               
> May 30 02:16:39 mzDebian python[5552]: 
> self._sock.sendall(view[write_offset:write_offset+buffer_size]) 
>                                       
> May 30 02:16:39 mzDebian python[5552]: error: [Errno 32] Broken pipe 
>                                                                         
> May 30 02:16:39 mzDebian python[5552]: Processes started                   
>                                         
>
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to