Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#19798 closed Uncategorized (invalid)

Django Randomly crashes postgres

Reported by: paologallo@… Owned by: nobody
Component: Database layer (models, ORM) Version: 1.4
Severity: Normal Keywords: postgres crash
Cc: Florian Apolloner Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Hallo guys,

I installed django 1.4 on a Ubuntu 12.04 LTS 64 Bit, working with postgresql 9.1 via psycopg2 Python 2.7 . All is perfectly working, but randomly after a day or a couple of days postgres is going down, this is what survived of postgres after these crashes :

paolo@webgis:~$ ps auwwx|grep postg
paolo 17422 0.0 0.0 8108 880 pts/0 S+ 11:18 0:00 grep --color=auto postg
postgres 31552 0.0 0.1 128736 6240 ? Ss Feb08 0:00 postgres: geonode geonode localhost(33523) idle

Obviously django is showing that he cannot connect to db ... after that i restart postgres and everything is working for a while. I've tried many fixes, none af them is working.
Any Help would be appreciated ...

Change History (3)

comment:1 Changed 5 years ago by Florian Apolloner

Cc: Florian Apolloner added
Resolution: needsinfo
Status: newclosed

It's hard to believe that django would crash postgres. If you think this is actually the case you'll have to provide more information than that and some proof…

comment:2 Changed 5 years ago by anonymous

Postgres log is not helping:

2013-02-06 14:21:42 CET LOG: 00000: disconnection: session time: 0:00:00.184 user=geonode database=geonode host= port=48737
2013-02-06 14:21:42 CET LOCATION: log_disconnections, postgres.c:4375
2013-02-06 21:58:07 CET LOG: 00000: database system was interrupted; last
known up at 2013-02-06 14:24:02 CET

Here is the system kernel:

kernel: [376938.427460] postgres[17901]: segfault at 38 ip 0000000000000038 sp 00007fffe15785d0 error 14 in postgres[400000+4dc000]

comment:3 Changed 5 years ago by Jacob

Resolution: needsinfoinvalid

This really isn't going to be a Django bug; it's something wrong with your system.

Note: See TracTickets for help on using tickets.
Back to Top