It just happened again. I deleted the cache file and restarted my service. It does not appear to be a unique event.
Thanks,
Alec
Search found 5 matches
- Wed Apr 01, 2015 10:54 am
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: python API DeadlockWrap error
- Replies: 7
- Views: 14587
- Tue Mar 17, 2015 1:19 pm
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: python API DeadlockWrap error
- Replies: 7
- Views: 14587
Re: python API DeadlockWrap error
Yes, I used a new database file on 3/14 and haven't had the error since then. But before I deleted the file I had previously fixed the problem by restarting the service, and to my best recollection this has happened 3 or 4 times over a couple months. I suppose I thought the file wasn't corrupt becau...
- Fri Mar 13, 2015 2:00 pm
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: python API DeadlockWrap error
- Replies: 7
- Views: 14587
Re: python API DeadlockWrap error
{ "api": { "version": "v1", "key": "xxxx:xxxx", "server": "api.wurflcloud.com" }, "http": { "timeout": 1000, "compression": true }, "cache": { "type": "file", "file": "/tmp/cloud_cache.db", "expiration": 86400 }, "misc": { "report_interval": 60 } }
- Fri Mar 13, 2015 12:50 pm
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: python cloud library bug using NullCache
- Replies: 1
- Views: 6274
python cloud library bug using NullCache
I am using the python cloud client and want to switch to NullCache because I'm having problems with your FileCache. I have just redownloaded version 1.0.1 of your python library (file was WurflCloudClient-Python-1.0.1-Simple.zip). When I initialize Wurfl with the NullCache this error occurs: File "/...
- Fri Mar 13, 2015 11:37 am
- Forum: ScientiaMobile WURFL Cloud Service
- Topic: python API DeadlockWrap error
- Replies: 7
- Views: 14587
python API DeadlockWrap error
I am running a flask python app via a uwsgi server and occasionally getting the error below. Restarting the uwsgi server solves the issue. At first I thought it was because I was running 4 uwsgi processes, so I changed it to a single process. But the error occurred again. Before I start digging into...