Re: Mysql connections after started django app
FYI: I found the conn leak is due to the mysql-connector-python. I started a post here if anyone is interested: http://forums.mysql.com/read.php?50,616862,616862#msg-616862 On Friday, July 4, 2014 4:08:40 PM UTC-4, François Schiettecatte wrote: > > Hi > > Again I think there is a bug somewhere in how django handles CONN_MAX_AGE > when it is not set or set to 0, you should not be seeing those sleeping > connections. > > It is perfectly fine to set CONN_MAX_AGE to some number, though keep it to > less than the wait_timeout in my.cnf. You will still see sleeping > connections but that is normal with a connection pool. Django will create a > number of connections to the database as needed, reusing then when > appropriate and closing them after the timeout you set. This will save you > from having to ping your site to maintain the connections. Setting up a > connection to MySQL is very fast so there should be performance issues if > you set CONN_MAX_AGE to something like 60 (again check my.cnf). > > Cheers > > François > > > On Jul 4, 2014, at 12:39 PM, Zemian Deng <saltn...@gmail.com > > wrote: > > > Thanks for the tips @Francois! Yeah, I already have this CONN_MAX_AGE > set to 0. I even try some positive number, but there is still Sleep > connections remain after the app is started and running without any > traffic. Which is not what I expect when set to 0 value. > > > > I don't even have fancy background tasks that need long running > connection time. But my site is only been use every few days per week, so > it has timeout issue when first use. As I mentioned, my current workaround > is have a crontab task to "curl" my site hourly to keep it alive. Even at > this is not completely reliable since there are 5 established connections, > and not always refresh all of them per ping. > > > > > > > > On Fri, Jul 4, 2014 at 11:24 AM, François Schiettecatte < > fschiet...@gmail.com > wrote: > > Hi > > > > I have a little experience with this, and I have posted about this here > before. > > > > The "MySQL Connection not available" message will occur when MySQL is > dropping the connection before Django is done with it, ie Django is trying > to send something down a dead connection. > > > > I would look at CONN_MAX_AGE in DATABASES (in settings.py) and > wait_timeout in my.cnf, the first should be lower than the second. > > > > For example I have these settings for a number of projects: > > > >'CONN_MAX_AGE': 3500, # 3500 seconds because > wait_timeout = 3600 in my.cnf > > > > And this for another: > > > > 'CONN_MAX_AGE': 50, # 50 seconds because > wait_timeout = 60 in my.cnf > > > > Not setting CONN_MAX_AGE (or setting it to 0) in 1.6 caused the "MySQL > Connection not available" issue, I suspect there is a bug in how Django > handles its pooling but I have not checked. Seeing Sleeping connections on > MySQL is suggestive of that. A Sleeping connection just means it is idle > and waiting for stuff. > > > > I have a number of long running scripts, where more than an hour (3600 > seconds) can elapse between database accesses, and I find I have to ping > the connections to see if they are still alive before I do any database > accesses, so I call the following method to ping the connections, and close > off dead connections: > > > > > > from django.db import connection > > > > def checkConnection(): > > > > # Check the connection, close if needed > > try: > > connection.connection.ping() > > # print 'INFO: connection.connection.ping()' > > except: > > connection.close() > > # print 'INFO: connection.close()' > > > > > > Hope this helps. > > > > https://docs.djangoproject.com/en/1.6/ref/databases/ > > > https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting-CONN_MAX_AGE > > > > Cheers > > > > François > > > > > > On Jul 4, 2014, at 10:46 AM, cercatrova2 <cerca...@gmail.com > > wrote: > > > > > On 04/07/14 16:11, Zemian Deng wrote: > > >> @cercatrova2, > > >> > > >> Yes, my original problem also was (and still is) with "MySQL > Connection not available" after the 8 hours timeout inactivity on > webfaction hosting. I have to restart it whenever this happens and then > problem will go away. My current workaround is to schedule a dummy crontab
Re: Mysql connections after started django app
Thanks for the tips @Francois! Yeah, I already have this CONN_MAX_AGE set to 0. I even try some positive number, but there is still Sleep connections remain after the app is started and running without any traffic. Which is not what I expect when set to 0 value. I don't even have fancy background tasks that need long running connection time. But my site is only been use every few days per week, so it has timeout issue when first use. As I mentioned, my current workaround is have a crontab task to "curl" my site hourly to keep it alive. Even at this is not completely reliable since there are 5 established connections, and not always refresh all of them per ping. On Fri, Jul 4, 2014 at 11:24 AM, François Schiettecatte < fschietteca...@gmail.com> wrote: > Hi > > I have a little experience with this, and I have posted about this here > before. > > The "MySQL Connection not available" message will occur when MySQL is > dropping the connection before Django is done with it, ie Django is trying > to send something down a dead connection. > > I would look at CONN_MAX_AGE in DATABASES (in settings.py) and > wait_timeout in my.cnf, the first should be lower than the second. > > For example I have these settings for a number of projects: > >'CONN_MAX_AGE': 3500, # 3500 seconds because > wait_timeout = 3600 in my.cnf > > And this for another: > > 'CONN_MAX_AGE': 50, # 50 seconds because > wait_timeout = 60 in my.cnf > > Not setting CONN_MAX_AGE (or setting it to 0) in 1.6 caused the "MySQL > Connection not available" issue, I suspect there is a bug in how Django > handles its pooling but I have not checked. Seeing Sleeping connections on > MySQL is suggestive of that. A Sleeping connection just means it is idle > and waiting for stuff. > > I have a number of long running scripts, where more than an hour (3600 > seconds) can elapse between database accesses, and I find I have to ping > the connections to see if they are still alive before I do any database > accesses, so I call the following method to ping the connections, and close > off dead connections: > > > from django.db import connection > > def checkConnection(): > > # Check the connection, close if needed > try: > connection.connection.ping() > # print 'INFO: connection.connection.ping()' > except: > connection.close() > # print 'INFO: connection.close()' > > > Hope this helps. > > https://docs.djangoproject.com/en/1.6/ref/databases/ > > https://docs.djangoproject.com/en/1.6/ref/settings/#std:setting-CONN_MAX_AGE > > Cheers > > François > > > On Jul 4, 2014, at 10:46 AM, cercatrova2 <cercatro...@gmail.com> wrote: > > > On 04/07/14 16:11, Zemian Deng wrote: > >> @cercatrova2, > >> > >> Yes, my original problem also was (and still is) with "MySQL Connection > not available" after the 8 hours timeout inactivity on webfaction hosting. > I have to restart it whenever this happens and then problem will go away. > My current workaround is to schedule a dummy crontab to hit my site every > hour to keep connection timeout refresh. Not ideal, but better than nothing > so far. Thus I am looking for some help here. > >> > >> I really like MySQL, and I have tested my app with it already. It would > be a bummer to switch because of this just now. I have tried direct usage > of mysql.connection with just open and close a connection, and I do see the > process go away properly. This plus the number of process list is > increasing when I try simple "mysite" app lead me to think it might be > django related. I am not sure. Further testing would be need to verify > which end is causing the problem. > >> > >> But good to hear PostgreSQL doesn't have the same issue though. > >> > >> > >> > >> On Fri, Jul 4, 2014 at 1:06 AM, cercatrova2 <cercatro...@gmail.com> > wrote: > >> On 04/07/14 05:04, Zemian Deng wrote: > >>> Hi, > >>> > >>> In my django settings.py I have set CONN_MAX_AGE=0 to use with MySQL > DB, which I understood as closing conn after each request. However when I > start a simple "mysite" tutorial with "python manage.py runserver", I see > immediately 3 connections in mysql that will not close but in Sleep mode. > Did I miss something here? How do we ensure these connections will get > closed while the app is running? > >>> > >>> mysql> show full processlist; > >>> > >>> > +-+--+-+--+-+--+
Re: Mysql connections after started django app
@cercatrova2, yes, these problems are coming using python3 and the mysql-connector-python and I am using their "mysql.connector.django". Currenly I have briefly experimented the default django.db.backends.mysql with Python3 driver https://github.com/clelland/MySQL-for-Python-3, but I still see the Sleep connections in the "mysite" project. So I am not too sure what's going on yet. Would have to dig little deeper in code to find out. I have already committed some effort into my app including testing with python3, so I am not ready to switch back into python 2.7 yet. On Fri, Jul 4, 2014 at 10:46 AM, cercatrova2 <cercatro...@gmail.com> wrote: > On 04/07/14 16:11, Zemian Deng wrote: > > @cercatrova2, > > Yes, my original problem also was (and still is) with "MySQL Connection > not available" after the 8 hours timeout inactivity on webfaction hosting. > I have to restart it whenever this happens and then problem will go away. > My current workaround is to schedule a dummy crontab to hit my site every > hour to keep connection timeout refresh. Not ideal, but better than nothing > so far. Thus I am looking for some help here. > > I really like MySQL, and I have tested my app with it already. It would > be a bummer to switch because of this just now. I have tried direct usage > of mysql.connection with just open and close a connection, and I do see the > process go away properly. This plus the number of process list is > increasing when I try simple "mysite" app lead me to think it might be > django related. I am not sure. Further testing would be need to verify > which end is causing the problem. > > But good to hear PostgreSQL doesn't have the same issue though. > > > > On Fri, Jul 4, 2014 at 1:06 AM, cercatrova2 <cercatro...@gmail.com> wrote: > >> On 04/07/14 05:04, Zemian Deng wrote: >> >> Hi, >> >> In my django settings.py I have set CONN_MAX_AGE=0 to use with MySQL >> DB, which I understood as closing conn after each request. However when I >> start a simple "mysite" tutorial with "python manage.py runserver", I see >> immediately 3 connections in mysql that will not close but in Sleep mode. >> Did I miss something here? How do we ensure these connections will get >> closed while the app is running? >> >> mysql> show full processlist; >> >> >> +-+--+-+--+-+--+---+---+ >> >> | Id | User | Host| db | Command | Time | State | Info >> | >> >> >> +-+--+-+--+-+--+---+---+ >> >> | 316 | root | localhost | NULL | Query |0 | init | show >> full processlist | >> >> | 317 | root | localhost:61695 | test | Sleep |3 | | NULL >> | >> >> | 318 | root | localhost:61696 | test | Sleep |3 | | NULL >> | >> >> | 319 | root | localhost:61697 | test | Sleep |3 | | NULL >> | >> >> >> +-+--+-+--+-+--+---+---+ >> >> 4 rows in set (0.00 sec) >> >> >> Thanks >> >> Zemian >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users+unsubscr...@googlegroups.com. >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/33fcf156-42bd-4c07-819f-952a6b214b76%40googlegroups.com >> <https://groups.google.com/d/msgid/django-users/33fcf156-42bd-4c07-819f-952a6b214b76%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> Zemian - I've run into this also (I think), but the problem showed up >> in a different way. First, after the mysql connection timeout expired, >> django would throw a "MySQL Connection not available" exception when trying >> to access the server. Second, it would throw the same exception when trying >> to access the server after the server had been restarted. This was all with >> CONN_MAX_AGE=0 which as you say should make django open and close a >> connection on each request. >> >> I didn't have time to research things further, but it seems to me t
Re: Mysql connections after started django app
@cercatrova2, Yes, my original problem also was (and still is) with "MySQL Connection not available" after the 8 hours timeout inactivity on webfaction hosting. I have to restart it whenever this happens and then problem will go away. My current workaround is to schedule a dummy crontab to hit my site every hour to keep connection timeout refresh. Not ideal, but better than nothing so far. Thus I am looking for some help here. I really like MySQL, and I have tested my app with it already. It would be a bummer to switch because of this just now. I have tried direct usage of mysql.connection with just open and close a connection, and I do see the process go away properly. This plus the number of process list is increasing when I try simple "mysite" app lead me to think it might be django related. I am not sure. Further testing would be need to verify which end is causing the problem. But good to hear PostgreSQL doesn't have the same issue though. On Fri, Jul 4, 2014 at 1:06 AM, cercatrova2 <cercatro...@gmail.com> wrote: > On 04/07/14 05:04, Zemian Deng wrote: > > Hi, > > In my django settings.py I have set CONN_MAX_AGE=0 to use with MySQL DB, > which I understood as closing conn after each request. However when I start > a simple "mysite" tutorial with "python manage.py runserver", I see > immediately 3 connections in mysql that will not close but in Sleep mode. > Did I miss something here? How do we ensure these connections will get > closed while the app is running? > > mysql> show full processlist; > > > +-+--+-+--+-+--+---+---+ > > | Id | User | Host| db | Command | Time | State | Info > | > > > +-+--+-+--+-+--+---+---+ > > | 316 | root | localhost | NULL | Query |0 | init | show full > processlist | > > | 317 | root | localhost:61695 | test | Sleep |3 | | NULL > | > > | 318 | root | localhost:61696 | test | Sleep |3 | | NULL > | > > | 319 | root | localhost:61697 | test | Sleep |3 | | NULL > | > > > +-+--+-+--+-+--+---+---+ > > 4 rows in set (0.00 sec) > > > Thanks > > Zemian > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/33fcf156-42bd-4c07-819f-952a6b214b76%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/33fcf156-42bd-4c07-819f-952a6b214b76%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > Zemian - I've run into this also (I think), but the problem showed up in a > different way. First, after the mysql connection timeout expired, django > would throw a "MySQL Connection not available" exception when trying to > access the server. Second, it would throw the same exception when trying to > access the server after the server had been restarted. This was all with > CONN_MAX_AGE=0 which as you say should make django open and close a > connection on each request. > > I didn't have time to research things further, but it seems to me that the > issue is with mysql.connector.django i.e. mysql connector/python - it is > somehow keeping its connection open client-side and when that connection > goes away server-side then it gives up. I tried to bring the problem to the > attention of the developer on his blog but he didn't respond. I guess a bug > report should be posted instead. > > Anyway, these problems, coupled with some unsolvable timezone issues when > trying to use mezzanine django cms with mysql connector/python, forced me > to switch to postgresql, which is working very well so far. > > Good luck. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-us
Re: "ResourceWarning: unclosed" error using mysql-connector-python
No problem. Thanks for the reply.
On Fri, Jul 4, 2014 at 12:51 AM, cercatrova2 <cercatro...@gmail.com> wrote:
> On 04/07/14 05:09, Zemian Deng wrote:
>
> Hum... I am surprised that no one has experienced this warning msg yet, or
> maybe I can't catch anyone to reply.
>
> For those are curious, I do now see mysql-connector-python 1.2.2 is
> available, and upgrading to this version got rid off these warnings.
>
> On Thursday, June 12, 2014 11:24:40 PM UTC-4, Zemian Deng wrote:
>>
>> Anyone?
>>
>> On Tuesday, June 10, 2014 11:26:18 PM UTC-4, Zemian Deng wrote:
>>>
>>> Hi there,
>>>
>>> I am using mysql-connector-python (1.1.6) with Django (1.6.5) and
>>> myapp is working fine. But each SQL call to DB will result the following
>>> warning messages:
>>>
>>> Exception ignored in: >> family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=6,
>>> laddr=('127.0.0.1', 62622), raddr=('127.0.0.1', 3306)>
>>>
>>> ResourceWarning: unclosed >> family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=6,
>>> laddr=('127.0.0.1', 62622), raddr=('127.0.0.1', 3306)>
>>>
>>>
>>> Has anyone seen this and know a way to resolve it?
>>> Also, FYI, I am using the following in my settings file.
>>> DATABASES = {
>>> 'default': {
>>>'ENGINE': 'mysql.connector.django',
>>>'NAME': 'mydb',
>>>'USER': 'test',
>>>'PASSWORD': 'test',
>>> },
>>> }
>>>
>>> Thanks,
>>> Zemian
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/a443d950-fe72-4380-bf61-1fc9c71c9af9%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/a443d950-fe72-4380-bf61-1fc9c71c9af9%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> Zemian - I saw these warning messages too with 1.1.6 but indeed they went
> away with 1.2.2 about a month ago so I didn't post anything. Sorry but I
> didn't know of your message at the time.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/53B632EE.2080203%40gmail.com
> <https://groups.google.com/d/msgid/django-users/53B632EE.2080203%40gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAK3t1y38NhS1GH3XVR9aB2TcuzO5JLFXRad1Hct5sP_En822_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: "ResourceWarning: unclosed" error using mysql-connector-python
Hum... I am surprised that no one has experienced this warning msg yet, or
maybe I can't catch anyone to reply.
For those are curious, I do now see mysql-connector-python 1.2.2 is
available, and upgrading to this version got rid off these warnings.
On Thursday, June 12, 2014 11:24:40 PM UTC-4, Zemian Deng wrote:
>
> Anyone?
>
> On Tuesday, June 10, 2014 11:26:18 PM UTC-4, Zemian Deng wrote:
>>
>> Hi there,
>>
>> I am using mysql-connector-python (1.1.6) with Django (1.6.5) and myapp
>> is working fine. But each SQL call to DB will result the following warning
>> messages:
>>
>> Exception ignored in: > type=SocketType.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 62622),
>> raddr=('127.0.0.1', 3306)>
>>
>> ResourceWarning: unclosed > family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=6,
>> laddr=('127.0.0.1', 62622), raddr=('127.0.0.1', 3306)>
>>
>>
>> Has anyone seen this and know a way to resolve it?
>> Also, FYI, I am using the following in my settings file.
>> DATABASES = {
>> 'default': {
>>'ENGINE': 'mysql.connector.django',
>>'NAME': 'mydb',
>>'USER': 'test',
>>'PASSWORD': 'test',
>> },
>> }
>>
>> Thanks,
>> Zemian
>>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/a443d950-fe72-4380-bf61-1fc9c71c9af9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mysql connections after started django app
Hi, In my django settings.py I have set CONN_MAX_AGE=0 to use with MySQL DB, which I understood as closing conn after each request. However when I start a simple "mysite" tutorial with "python manage.py runserver", I see immediately 3 connections in mysql that will not close but in Sleep mode. Did I miss something here? How do we ensure these connections will get closed while the app is running? mysql> show full processlist; +-+--+-+--+-+--+---+---+ | Id | User | Host| db | Command | Time | State | Info | +-+--+-+--+-+--+---+---+ | 316 | root | localhost | NULL | Query |0 | init | show full processlist | | 317 | root | localhost:61695 | test | Sleep |3 | | NULL | | 318 | root | localhost:61696 | test | Sleep |3 | | NULL | | 319 | root | localhost:61697 | test | Sleep |3 | | NULL | +-+--+-+--+-+--+---+---+ 4 rows in set (0.00 sec) Thanks Zemian -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/33fcf156-42bd-4c07-819f-952a6b214b76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
"ResourceWarning: unclosed" error using mysql-connector-python
Hi there,
I am using mysql-connector-python (1.1.6) with Django (1.6.5) and myapp is
working fine. But each SQL call to DB will result the following warning
messages:
Exception ignored in:
ResourceWarning: unclosed
Has anyone seen this and know a way to resolve it?
Also, FYI, I am using the following in my settings file.
DATABASES = {
'default': {
'ENGINE': 'mysql.connector.django',
'NAME': 'mydb',
'USER': 'test',
'PASSWORD': 'test',
},
}
Thanks,
Zemian
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/8488150d-e986-4743-9170-73e75a119dd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: "ResourceWarning: unclosed" error using mysql-connector-python
Anyone?
On Tuesday, June 10, 2014 11:26:18 PM UTC-4, Zemian Deng wrote:
>
> Hi there,
>
> I am using mysql-connector-python (1.1.6) with Django (1.6.5) and myapp
> is working fine. But each SQL call to DB will result the following warning
> messages:
>
> Exception ignored in: type=SocketType.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 62622),
> raddr=('127.0.0.1', 3306)>
>
> ResourceWarning: unclosed family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=6,
> laddr=('127.0.0.1', 62622), raddr=('127.0.0.1', 3306)>
>
>
> Has anyone seen this and know a way to resolve it?
> Also, FYI, I am using the following in my settings file.
> DATABASES = {
> 'default': {
>'ENGINE': 'mysql.connector.django',
>'NAME': 'mydb',
>'USER': 'test',
>'PASSWORD': 'test',
> },
> }
>
> Thanks,
> Zemian
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/9b088458-e57c-4527-94bd-92d2123994a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
"ResourceWarning: unclosed" error using mysql-connector-python
Hi there,
I am using mysql-connector-python (1.1.6) with Django (1.6.5) and myapp is
working fine. But each SQL call to DB will result the following warning
messages:
Exception ignored in:
ResourceWarning: unclosed
Has anyone seen this and know a way to resolve it?
Also, FYI, I am using the following in my settings file.
DATABASES = {
'default': {
'ENGINE': 'mysql.connector.django',
'NAME': 'mydb',
'USER': 'test',
'PASSWORD': 'test',
},
}
Thanks,
Zemian
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/9f03292b-16a4-4224-b89e-a4f57b2dfcc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
