Re: [Sqlgrey-users] Couple Problems with 1.6.0

[Ed S. (s. list) <sq...@cr...>]

Lionel Bouton wrote:

>You may want to check the number of connections to the database. Do
>something like "netstat -anp | grep <sqlgrey-pid>" to check open TCP
>connections. You should only have one conection to the PostgreSQL server.
>  
>
darkside:~# ps aux |grep sqlgrey
sqlgrey   9082  0.0  0.9  13872  8792 ?        Ss   11:50   0:01
/usr/bin/perl -w /usr/sbin/sqlgrey -d
postgres  9085  0.0  0.9  18064  8948 ?        S    11:50   0:00
postgres: sqlgrey sqlgrey 127.0.0.1 idle
sqlgrey  31292  0.0  0.0      0     0 ?        Z    18:49   0:00
[sqlgrey] <defunct>
root      6135  0.0  0.0   1620   516 pts/1    S+   21:16   0:00 grep
sqlgrey
darkside:~# netstat -anp |grep 9082
tcp        0      0 127.0.0.1:2501          0.0.0.0:*              
LISTEN     9082/perl
tcp        0      0 127.0.0.1:36435         127.0.0.1:5432         
ESTABLISHED9082/perl
tcp        1      0 127.0.0.1:2501          127.0.0.1:34774        
CLOSE_WAIT 9082/perl
unix  3      [ ]         STREAM     CONNECTED     29082    9199/master
unix  3      [ ]         STREAM     CONNECTED     28680    9082/perl


>Hope it can make a difference. If all fails, I'll make the fork
>configurable and inactive by default.
>  
>
While reverting back to self->cleanup() fixed the lockup problem with
1.6.0 and 1.7.0, I have the same lockup problem with 1.6.2.


Cheers,
-- 

Ed