On Thu, Nov 12, 2009 at 11:06 AM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm sorry Dave.
>
> I'm unable to... :(
>
> Whenever I try to get a backtrace it's already frozen solid and
> there's nothing to do other than kill it...
If you start it under gdb, d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm sorry Dave.
I'm unable to... :(
Whenever I try to get a backtrace it's already frozen solid and
there's nothing to do other than kill it...
BR,
Pedro
On 11/12/2009 10:43 AM, Dave Page wrote:
> On Thu, Nov 12, 2009 at 10:41 AM, Pedro Doria Meuni
On Thu, Nov 12, 2009 at 10:41 AM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dave,
>
> With SSL disable it's the same thing...
Can you get the trace please?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgadmin-support mailing lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
With SSL disable it's the same thing...
BR,
Pedro.
On 11/12/2009 09:22 AM, Dave Page wrote:
> On Wed, Nov 11, 2009 at 8:00 PM, Pedro Doria Meunier
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Ok. please disregard that l
On Wed, Nov 11, 2009 at 8:00 PM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ok. please disregard that last one... :)
>
> This is the last output of valgrind before I had to kill pgadmin:
>
> ==671== Thread 2:
> ==671== Syscall param write(buf) points to uninit
On Wed, Nov 11, 2009 at 6:57 PM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Dave
>
> Did as you asked...
>
> problem:
> ./pgadmin3: error while loading shared libraries:
> libwx_gtk2ud_stc-2.8.so.0: cannot open shared object file: No such
> file or director
I did a bit more checking and there appears to be some server configurations
that may affect keeping the connection alive:
tcp_keepalives_idle (integer)
On systems that support the TCP_KEEPIDLE socket option, specifies the number
of seconds between sending keepalives on an otherwise idle connecti
I checked the server logs and found messages like this:
2009-11-11 15:08:36 PSTLOG: could not receive data from client: Connection
reset by peer
2009-11-11 16:18:11 PSTLOG: could not receive data from client: Connection
timed out
I do not know if this means that the server did the disconnect or
I was able to reproduce the problem within PgAdmin as well as with another
(java-based) tool connecting to the same database from the same (Windows XP)
machine.
I opened an query window and ran a query (that did not take long to
complete) in both tools. I then waited 1/2 hour and ran the query aga
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok...
I've tried with valgrind and gdb attached ... no luck
with gdb alone and trying to get a stack trace ... no luck
whatever is happening with pgadmin3 under the beforementioned
conditions *freezes* everything ...
BR,
Pedro
On 11/11/2009 08:00
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok. please disregard that last one... :)
This is the last output of valgrind before I had to kill pgadmin:
==671== Thread 2:
==671== Syscall param write(buf) points to uninitialised byte(s)
==671==at 0xBC4F4B: (within /lib/libpthread-2.10.1.so)
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dave
Did as you asked...
problem:
./pgadmin3: error while loading shared libraries:
libwx_gtk2ud_stc-2.8.so.0: cannot open shared object file: No such
file or directory
(on execution, after compilation)
This library is nowhere to be found...
Do
On Wed, Nov 11, 2009 at 3:36 PM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm "glad" :] I'm not alone in this...
>
> It's definitely not the router. It's something else...
>
> For instance:
>
> - - One opens a table. leave it be for some time and the next op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm "glad" :] I'm not alone in this...
It's definitely not the router. It's something else...
For instance:
- - One opens a table. leave it be for some time and the next operation
freezes pgAdmin, especially if one tries to open another database
obj
It just happened again. I ran a query in a window and after it completed I
waited 10-15 minutes and ran it again.
I got a connection error. I ran the query again (by hitting the green >
icon) and it caused pgAdmin to crash.
Moreover, I was simultaneously running another tool that was connected to
It happens to me quite a lot, as well. I will lose the contents of the SQL
window as well when it happens.
It would be good if PgAdmin would automatically try to reconnect (at least
once) before giving up.
On Wed, Nov 11, 2009 at 8:08 AM, Eugene Lisitsky wrote:
>
> I see such problem when remot
I see such problem when remote servers replies slowly.
2009/11/1 Pedro Doria Meunier
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Replying to self:
> Altering the tcp_keepalive_time, tcp_keepalive_intvl values *didn't*
> solve the problem.
>
>
> On 11/01/2009 03:04 PM, Pedro Doria Meun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Replying to self:
Altering the tcp_keepalive_time, tcp_keepalive_intvl values *didn't*
solve the problem.
On 11/01/2009 03:04 PM, Pedro Doria Meunier wrote:
>
> Sorry forgot to tell it happens on a remote connection... :)
>
> This is AFAICS is most p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry forgot to tell it happens on a remote connection... :)
This is AFAICS is most probably a timeout problem.
It makes me wonder if my router isn't dropping idle connections...
Anyway I'm playing with tcp_keepalive_time, tcp_keepalive_intvl values
- Original Message -
From: "Dave Page"
To: "Pedro Doria Meunier"
Cc: "pgAdmin Support"
Sent: Sunday, November 1, 2009 6:07:39 PM GMT +05:30 Chennai, Kolkata, Mumbai,
New Delhi
Subject: Re: [pgadmin-support] pgAdmin ver 1.10 freezing all too frequently
O
On Sun, Nov 1, 2009 at 11:04 AM, Pedro Doria Meunier
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> pgAdmin ver 1.10.0 rev. 7945:7946 freezes after a short time of
> inactivity...
> Fedora 11 - kernel 2.6.30.9-90.fc11.i686.PAE
>
> Reproducible by:
> - - connect to a db
> - -
21 matches
Mail list logo
