Thanks for that Niphlod. On Friday, 19 October 2012 11:10:17 UTC-4, Niphlod wrote: > > -K starts the scheduler. Scheduler and webserver are meant to be executed > on different processes. > So, web2py.py -i .... -p 8000 -a apassword in one shell and web2py.py -K > applicationName in another one. > > From 2.0.0 onwards, there is the possibility to start two separate > processes from one command line, but you have to use -X too. > So, ./web2py.py -i xxx.xxx.xx.xx -p 8000 -c /etc/ssl/certs/cert-file.crt > -k /etc/ssl/certs/key-file.key -a apassword -K applicationName -X > does what > ./web2py.py -i xxx.xxx.xx.xx -p 8000 -c /etc/ssl/certs/cert-file.crt -k > /etc/ssl/certs/key-file.key -a apassword > and > ./web2py.py -K applicationName > previously did in older versions. > > > On Friday, October 19, 2012 4:55:26 PM UTC+2, Mike Anson wrote: >> >> I upgraded to the newest web2py (2.1.1) >> >> Launch it with: >> ./web2py.py -i xxx.xxx.xx.xx -p 8000 -c /etc/ssl/certs/cert-file.crt -k >> /etc/ssl/certs/key-file.key -a apassword -K applicationName >> >> When I run the -K application (ie scheduler) I am then unable to access >> the admin or front end of the site. I simply see the dreaded Safari "Cannot >> connect to server" message. >> >> The scheduler does nothing crazy. It updates a file in /tmp/ with the >> current date/time 3 times over a 60 second period. >> >> Had anyone else experienced this? >> >
--
