It did not solve the issue.

On Tuesday, February 17, 2015 at 8:50:15 AM UTC-5, Jason Lee wrote:
>
> I will attempt to try now.
>
> On Monday, February 16, 2015 at 12:37:22 AM UTC-5, Massimo Di Pierro wrote:
>>
>> can you check if the latest nightly build fixes the problem. Actually you 
>> do not have to replace all the code but only web2py/gluon/storage.py from 
>> the git repo.
>>
>> Does it solve the problem?
>>
>> On Sunday, 15 February 2015 17:55:27 UTC-6, Jason Lee wrote:
>>>
>>> I am storing the sessions in a mysql database called users.
>>>
>>> I dropped and created the users database again.  I still get the error.
>>>
>>>
>>>
>>> On Wednesday, February 11, 2015 at 11:12:18 AM UTC-5, Jason Lee wrote:
>>>>
>>>> I am storing the session data in a database.
>>>>
>>>> I am using the latest web2py.
>>>>
>>>> I have deleted everything, reinstalled fresh, deleted the database and 
>>>> rebuilt it and I still get this error.
>>>>
>>>> The error occurs when I reboot the system.  I can fix it by restarting 
>>>> apache2 service once the server has rebooted.
>>>>
>>>>
>>>> I have a number of serverrs doing this.  It only started when I 
>>>> upgraded.
>>>>
>>>> Error details;
>>>>
>>>> Traceback (most recent call last):
>>>>   File "/usr/share/www-data/web2py/gluon/main.py", line 435, in wsgibase
>>>>     session.connect(request, response)
>>>>   File "/usr/share/www-data/web2py/gluon/globals.py", line 934, in connect
>>>>     session_pickled = pickle.dumps(self, pickle.HIGHEST_PROTOCOL)
>>>> TypeError: 'NoneType' object is not callable
>>>>
>>>>
>>>>

-- 
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