[web2py] Error starting up scheduler with postgresql - "type oid 114 not mapped to py"

Hello, I am having some trouble starting up web2py's scheduler. I am working on a Ubuntu server, using web2py 2.9.9 deployed with nginx, and PostgreSQL. Everything works just right, but whenever I try to run the scheduler (python web2py.py -K myapp), I get continous "*Error retrieving status*"

[web2py] Re: Error starting up scheduler with postgresql - "type oid 114 not mapped to py"

, Sebastian On Tuesday, October 14, 2014 9:26:07 AM UTC-3, Niphlod wrote: > > the problem comes from pg8000 not supporting the json type. Use psycopg2 > instead. > > On Monday, October 13, 2014 9:56:38 PM UTC+2, Sebastian Echeverria wrote: >> >> Hello, >> >> I am h

[web2py] Re: Error starting up scheduler with postgresql - "type oid 114 not mapped to py"

',' > if ou're using a DAL uri as "postgresql://blablabla" the only thing to do > is to install psycopg2 on the system: if available, it takes precedence. > > On Thursday, October 16, 2014 11:13:41 PM UTC+2, Sebastian Echeverria > wrote: >> >> Hello,

[web2py] Re: Error starting up scheduler with postgresql - "type oid 114 not mapped to py"

> > On Thursday, October 16, 2014 11:13:41 PM UTC+2, Sebastian Echeverria > wrote: >> >> Hello, >> >> Thanks for the reply! So in fact, the issue is the same one the other >> poster was facing. Do you have any hints on how to use psycopg2 instead? >>

[web2py] Re: Error starting up scheduler with postgresql - "type oid 114 not mapped to py"

That solved my second problem. Thank you very much! Sebastian On Saturday, October 18, 2014 3:10:31 PM UTC-3, Niphlod wrote: > > update web2py to 2.9.11 please. > > On Saturday, October 18, 2014 5:13:46 AM UTC+2, Sebastian Echeverria wrote: >> >> Ok, so installing psycopg