Re: pgadmin3 crash report - Mailing list pgadmin-support

Le 30/06/2010 10:16, r d a écrit :
> [...]
> pgadmin3 crashes when I try to see the server statistics (menu Tools -->
> Server Status).
> I think that I configured my installation correctly, details follow below.
> 
> My configuration:
> ---------------------------------------------------------------------------------
> - Linux FC12 installed clean, plus YUM upgrades from network
> uname -a == Linux L3 2.6.32.14-127.fc12.x86_64 #1 SMP Fri May 28
> 04:30:39 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
> 
> - PostgreSQL 8.4.4 installed via YUM from net
> postgresql-server-8.4.4-1.fc12.x86_64
> (and all postgresql-* packages plus dependencies)
> 
> - pgadmin3 1.10.3 - installed via YUM from net
> pgadmin3-1.10.3-2.fc12.x86_64
> 
> - wx 2.8.11 installed from net via YUM
> wxBase-2.8.11-1.fc12.x86_64
> wxPython-2.8.11.0-1.fc12.x86_64
> wxGTK-media-2.8.11-1.fc12.x86_64
> wxGTK-devel-2.8.11-1.fc12.x86_64
> wxGTK-gl-2.8.11-1.fc12.x86_64
> wxPython-devel-2.8.11.0-1.fc12.x86_64
> wxGTK-2.8.11-1.fc12.x86_64
> ---------------------------------------------------------------------------------
> 
> I set up the instrumentation, logging, ...  as per instructions, i.e.
> 1) psql --username=username dbname -f adminpack.sql   (actually, I have
> all contribs installed into all databases)
> 2) logging output filename is (postgresql.conf) log_filename =
> 'postgresql-%Y-%m-%d_%H%M%S.log'
> 3) logs are written into data/pg_log (default)
> 4) log files look like this (ls -l)
> 
> -rw-------. 1 postgres postgres       171 2010-06-30 01:41
> postgresql-2010-06-30_000000.log
> -rw-------. 1 postgres postgres    322532 2010-06-30 09:43
> postgresql-2010-06-30_084323.log
> 
> 5) Sample contents of a log content looks like this:
> STATEMENT:  SELECT
> pg_file_read('pg_log/postgresql-2010-06-30_084323.log', 0, 50000)
> LOG:  EXECUTOR STATISTICS
> DETAIL:  ! system usage stats:
>         !       0.000242 elapsed 0.000000 user 0.000000 system sec
>         !       [0.016997 user 0.005999 sys total]
>         !       0/0 [64/0] filesystem blocks in/out
>         !       0/4 [0/1563] page faults/reclaims, 0 [0] swaps
>         !       0 [0] signals rcvd, 0/0 [0/0] messages rcvd/sent
>         !       0/0 [21/28] voluntary/involuntary context switches
>         ! buffer usage stats:
>         !       Shared blocks:          0 read,          0 written,
> buffer hit rate = 0.00%
>         !       Local  blocks:          0 read,          0 written,
> buffer hit rate = 0.00%
>         !       Direct blocks:          0 read,          0 written
> STATEMENT:  SELECT
> pg_file_read('pg_log/postgresql-2010-06-30_084323.log', 0, 50000)
> LOG:  unexpected EOF on client connection
> LOG:  unexpected EOF on client connection
> LOG:  unexpected EOF on client connection
> 
> 
> 6) /var/log/messages contains this:
> Jun 30 09:43:23 localhost kernel: pgadmin3[5984]: segfault at 700000005f
> ip 000000382b815d2c sp 00007fff574b47f0 error 4 in
> libwx_gtk2u_core-2.8.so.0.7.0[382b600000+3a3000]
> Jun 30 09:43:24 localhost abrt[28553]: saved core dump of pid 5984
> (/usr/bin/pgadmin3) to /var/cache/abrt/ccpp-1277883803-5984.new/coredump
> (20774912 bytes)
> Jun 30 09:43:24 localhost abrtd: Directory 'ccpp-1277883803-5984'
> creation detected
> Jun 30 09:43:24 localhost abrtd: Crash is in database already (dup of
> /var/cache/abrt/ccpp-1277659638-8405)
> Jun 30 09:43:24 localhost abrtd: Deleting crash ccpp-1277883803-5984
> (dup of ccpp-1277659638-8405), sending dbus signal
> (coredumps available on request)
> 
> The DB runs as user postgres, which was created at DBMS install, and all
> files belong to this user. selinux is enforcing/strict.
> pgadmin3 runs as root and connects to the DBs using various roles, it is
> very stable.
> Changing the user or the permissions seems to make no difference.
> When I try to shoow the "Server Status", it pops up the window for a
> short moment and then the whole application crashes.
> 
> If I can supply any other info, please ask / send instructions.

I installed a VM with FC12, and cannot reproduce your issue. I don't
launch pgadmin3 as root, but I don't think it can have that effect.
Perhaps there is something in your log files it doesn't like. Care to
share them with me?


-- 
Guillaumehttp://www.postgresql.frhttp://dalibo.com