1 month late is sometimes better than never. This happens to be an
error that is shown when a user hides the turbogears app behind
another webserver like apache using mod_wsgi. If so, i'd say that your
wsgi file probably isn't injecting the commands to enable identity.
Please let us know if you are using mod_wsgi, and if I'm on the right
track here.

Steven

On Feb 12, 6:56 am, Jim Steil <[email protected]> wrote:
> Hi
>
> I have a web app that has been running for over a year.  One of our
> users got a virus on their machine this week (AntiVirus 360) and I was
> able to clear it up using MalwareBytes.  However, since then, they
> cannot access my TG app over the web.  All other websites I've tried
> from that computer work just fine, but my TG app fails.  I can get to
> the login page, but when I try to logon (doesn't matter what profile I
> use) it eventually times out.  Here is the relevant error information:
>
> A 500 error occurred on serverwww.ic.qlf.comat 2009-02-12 07:38:21.604000.
>
> ---------- Request ----------------------------------
>
> POST /dashboard/ HTTP/1.0
>
> ---------- Exception traceback ------------------
>
> Traceback (most recent call last):
>   File 
> "C:\Python25\lib\site-packages\cherrypy-2.3.0-py2.5.egg\cherrypy\_cphttptools.py",
>  line 114, in _run
>     self.processBody()
>   File 
> "C:\Python25\lib\site-packages\cherrypy-2.3.0-py2.5.egg\cherrypy\_cphttptools.py",
>  line 240, in processBody
>     keep_blank_values=1)
>   File 
> "C:\Python25\lib\site-packages\cherrypy-2.3.0-py2.5.egg\cherrypy\_cpcgifs.py",
>  line 8, in __init__
>     cgi.FieldStorage.__init__(self, *args, **kwds)
>   File "C:\Python25\lib\cgi.py", line 532, in __init__
>     self.read_urlencoded()
>   File "C:\Python25\lib\cgi.py", line 637, in read_urlencoded
>     qs = self.fp.read(self.length)
>   File 
> "C:\Python25\lib\site-packages\cherrypy-2.3.0-py2.5.egg\cherrypy\lib\httptools.py",
>  line 522, in read
>     data = self.rfile.read(size)
>   File "C:\Python25\lib\socket.py", line 309, in read
>     data = self._sock.recv(recv_size)
> timeout: timed out
>
> ---------- Request information ------------------
>
> remote_addr: '24.206.246.223'
> remote_port: 1090
> requestLine: 'POST /dashboard/ HTTP/1.0'
> protocol: 'HTTP/1.0'
> method: 'POST'
> browser_url: 'http://www.ic.qlf.com/dashboard/'
>
> ---------- Request headers ----------------------
>
> REFERER: 'http://www.ic.qlf.com/dashboard/'
> Content-Length: '45'
> USER-AGENT: 'Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 
> 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648)'
> CONNECTION: 'close'
> COOKIE: 'tg-visit=14d19fe7ac54d9812a8b2838c72c107774cedd55'
> CONTENT-LENGTH: '45'
> HOST: 'www.ic.qlf.com'
> UA-CPU: 'x86'
> CACHE-CONTROL: 'no-cache'
> CONTENT-TYPE: 'application/x-www-form-urlencoded'
> ACCEPT: 'image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, 
> application/x-shockwave-flash, application/xaml+xml, 
> application/vnd.ms-xpsdocument, application/x-ms-xbap, 
> application/x-ms-application, application/vnd.ms-excel, 
> application/vnd.ms-powerpoint, application/msword, */*'
> Remote-Addr: '24.206.246.223'
> ACCEPT-LANGUAGE: 'en-us'
> Content-Type: 'application/x-www-form-urlencoded'
>
> ---------- User information ------------------
>
> Error getting user info: An attempt was made to use a facility of the 
> TurboGears Identity Management framework, but identity management hasn't been 
> enabled in the config file [via identity.on].
>
> This works fine for all other users.  No one else is experiencing this.  
> Happens on that (Windows) client with IE or Firefox.  Any clues as to
> where to look for help on this one?
>
> Thanks
>
>     -Jim
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to