Re: [web2py] All messed up

Thanks for the pointers. @Massimiliano, the suggestion is a good one but I found my pg_hba.conf file was OK. I finally got this working by rebooting the machine, so I'm closing the issue. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2p

Re: [web2py] All messed up

"actively refused it" means that the socket you're pointing to is not open(able) . Review the listening ports and/or the firewall. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/

Re: [web2py] All messed up

Is your pg_hba.conf allowing your connections? On Tue, Jun 9, 2015 at 9:47 AM, weheh wrote: > Alright, a little further now. I figured I needed to reinstall/upgrade > psycopg2, which I did. Now I'm getting the ticket: > > Traceback (most recent call last): > File "G:\web2py\gluon\restricted.py

Re: [web2py] All messed up

Alright, a little further now. I figured I needed to reinstall/upgrade psycopg2, which I did. Now I'm getting the ticket: Traceback (most recent call last): File "G:\web2py\gluon\restricted.py", line 227, in restricted exec ccode in environment File "G:/web2py/applications/myapp/models/0_

Re: [web2py] All messed up

@Niphlod: OK, I reinstalled Windows from source and this time web2py is back in working order. However, I'm still unable to connect to postgresql. I'm getting this ticket: Traceback (most recent call last): File "G:\web2py\gluon\restricted.py", line 227, in restricted exec ccode in enviro

Re: [web2py] All messed up

did you by any chance update web2py using the "update" button on admin ? if so, and if you were running a rather old web2py instance, the updater probably left some files behind that shouldn't be there (mainly DAL structure with the new subpackage). See what the standard folder structure in gluo

Re: [web2py] All messed up

Alright. I took the error message over to another machine that has an older version of web2py running. Looks pretty fundamental. CountFileError10_0_globals.pyAttributeError: type object 'DAL' has no attribute 'Field' + details

Re: [web2py] All messed up

Hi Kiran, thanks for the response. Unfortunately, I can't see my error files now because I can't get through to web2py admin. Before updating web2py, there were absolutely no error messages about not being able to connect to postgres. And yes, I have run from the console but still no luck in ge

Re: [web2py] All messed up

* Take a look at your web2py error logs - it usually gives you the reason as to what is wrong (even if your admin app does not work, just open the error logs in a text editor and view it) * Did you try running web2py from the console - python web2py -S Then you can try to do the usu

Re: [web2py] All messed up

* Take a look at your web2py error logs - it usually gives you the reason as to what is wrong (even if your admin app does not work, just open the error logs in a text editor and view it) * Did you try running web2py from the console - python web2py -S Then you can try to do the usu

[web2py] All messed up

Grrr. I just upgraded postgresql to the latest version 9.4 on Windows. I was surprised to see that it didn't overwrite the Postgres 9.2 install on my system. So I backed up my 9.2 db, created a new db under 9.4 and restored the 9.2 db into the 9.4 db. Everything seemed OK. But web2py wouldn't