Thread: BUG #1678: pw_shadow BUS ERROR
The following bug has been logged online: Bug reference: 1678 Logged by: Haluk GUNCER Email address: halukguncer@hotmail.com PostgreSQL version: 7.4 to 8.0.3 Operating system: HP-UX B.11.11 Description: pw_shadow BUS ERROR Details: the system is a high end system used in a major project in TURKEY. HP guys could not figure it out. Version 7.3.10 works fine. version 7.4.8 ,8.0.0 and 8.0.3 never starts. $ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale C. fixing permissions on existing directory /usr/local/pgsql/data ... ok creating directory /usr/local/pgsql/data/global ... ok creating directory /usr/local/pgsql/data/pg_xlog ... ok creating directory /usr/local/pgsql/data/pg_xlog/archive_status ... ok creating directory /usr/local/pgsql/data/pg_clog ... ok creating directory /usr/local/pgsql/data/pg_subtrans ... ok creating directory /usr/local/pgsql/data/base ... ok creating directory /usr/local/pgsql/data/base/1 ... ok creating directory /usr/local/pgsql/data/pg_tblspc ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 1000 creating configuration files ... ok creating template1 database in /usr/local/pgsql/data/base/1 ... ok initializing pg_shadow ... sh: 2419 Bus error(coredump) child process exited with exit code 138 initdb: removing contents of data directory "/usr/local/pgsql/data" ************************************* After BUS ERROR semafore remains. have to be removed with "ipcrm". /home/postgres$ipcs -a | grep post m 61447 0x00000001 --rw------- postgres dba postgres dba 0 10403840 2419 2419 18:14:36 no-entry 18:14:36 s 331802 0x00000002 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36 s 442395 0x00000003 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36 s 401436 0x00000004 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36 s 372765 0x00000005 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36 s 352286 0x00000006 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36 s 352287 0x00000007 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36 s 352288 0x00000008 --ra------- postgres dba postgres dba 1 7 18:14:36 18:14:36
Haluk GUNCER wrote: > fixing permissions on existing directory /usr/local/pgsql/data ... ok > creating directory /usr/local/pgsql/data/global ... ok > creating directory /usr/local/pgsql/data/pg_xlog ... ok > creating directory /usr/local/pgsql/data/pg_xlog/archive_status ... ok > creating directory /usr/local/pgsql/data/pg_clog ... ok > creating directory /usr/local/pgsql/data/pg_subtrans ... ok > creating directory /usr/local/pgsql/data/base ... ok > creating directory /usr/local/pgsql/data/base/1 ... ok > creating directory /usr/local/pgsql/data/pg_tblspc ... ok > selecting default max_connections ... 100 > selecting default shared_buffers ... 1000 > creating configuration files ... ok > creating template1 database in /usr/local/pgsql/data/base/1 ... ok > initializing pg_shadow ... sh: 2419 Bus error(coredump) > child process exited with exit code 138 Can you get a stack trace from the core file? (Depending on where the core file gets created, you may need to use the '-n' option to initdb to stop the partially-created data directory from being removed.) -Neil
I've seen this before, and that was due to unaligned memory access, which is not supported on some platforms. I thought we didn't do unaligned memory access?? ... John=20 > -----Original Message----- > From: pgsql-bugs-owner@postgresql.org=20 > [mailto:pgsql-bugs-owner@postgresql.org] On Behalf Of Haluk GUNCER > Sent: Wednesday, May 25, 2005 1:23 AM > To: pgsql-bugs@postgresql.org > Subject: [BUGS] BUG #1678: pw_shadow BUS ERROR >=20 >=20 > The following bug has been logged online: >=20 > Bug reference: 1678 > Logged by: Haluk GUNCER > Email address: halukguncer@hotmail.com > PostgreSQL version: 7.4 to 8.0.3 > Operating system: HP-UX B.11.11 > Description: pw_shadow BUS ERROR > Details:=20 >=20 > the system is a high end system used in a major project in=20 > TURKEY. HP guys could not figure it out. >=20 >=20=20 > Version 7.3.10 works fine. > version 7.4.8 ,8.0.0 and 8.0.3 never starts. >=20 > $ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data >=20 > The files belonging to this database system will be owned by=20 > user "postgres". > This user must also own the server process. >=20 > The database cluster will be initialized with locale C. >=20 > fixing permissions on existing directory=20 > /usr/local/pgsql/data ... ok creating directory=20 > /usr/local/pgsql/data/global ... ok creating directory=20 > /usr/local/pgsql/data/pg_xlog ... ok creating directory=20 > /usr/local/pgsql/data/pg_xlog/archive_status ... ok creating=20 > directory /usr/local/pgsql/data/pg_clog ... ok creating=20 > directory /usr/local/pgsql/data/pg_subtrans ... ok creating=20 > directory /usr/local/pgsql/data/base ... ok creating=20 > directory /usr/local/pgsql/data/base/1 ... ok creating=20 > directory /usr/local/pgsql/data/pg_tblspc ... ok selecting=20 > default max_connections ... 100 selecting default=20 > shared_buffers ... 1000 creating configuration files ... ok=20 > creating template1 database in /usr/local/pgsql/data/base/1=20 > ... ok initializing pg_shadow ... sh: 2419 Bus=20 > error(coredump) child process exited with exit code 138 > initdb: removing contents of data directory "/usr/local/pgsql/data" >=20 > ************************************* >=20 > After BUS ERROR semafore remains. > have to be removed with "ipcrm". >=20 > /home/postgres$ipcs -a | grep post > m 61447 0x00000001 --rw------- postgres dba=20=20 > postgres dba > 0 10403840 2419 2419 18:14:36 no-entry 18:14:36 > s 331802 0x00000002 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 > s 442395 0x00000003 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 > s 401436 0x00000004 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 > s 372765 0x00000005 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 > s 352286 0x00000006 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 > s 352287 0x00000007 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 > s 352288 0x00000008 --ra------- postgres dba=20=20 > postgres dba=20 > 1 > 7 18:14:36 18:14:36 >=20 > ---------------------------(end of=20 > broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index=20 > scan if your > joining column's datatypes do not match >=20 >=20
Haluk GÜNÇER wrote: > I did it with -n option. The generated core file is attached. I hope it > will help. The core file itself is not much use -- you need to get a stack trace from the core file (which I can't do, since I don't have the binaries you built -- or an HPUX system for that matter). You can get a stack trace via gdb using "gdb /path/to/binary /path/to/core" followed by "bt"; there may be a different / better way to do things on HPUX (HP support should be able to tell you, at any rate). -Neil
On Mon, 2005-05-30 at 19:36 +0300, Haluk GÜNÇER wrote: > #0 0x23cf64 in CreatePortal+0x1f4 () > (gdb) bt > #0 0x23cf64 in CreatePortal+0x1f4 () > #1 0x23ce28 in CreatePortal+0xb8 () > #2 0x19c094 in exec_simple_query+0x194 () > #3 0x19daa8 in PostgresMain+0x1520 () > #4 0x12f918 in main+0x1e0 () Weird -- it's difficult to see how there could be a problem in CreatePortal(), as that is both simple and widely used code. (The recursive call to CreatePortal() also makes no sense, but perhaps that is just weirdness in the backtrace.) Would it be possible to get a stacktrace with a copy of Postgres that has been compiled with --enable-debug? -Neil
Neil Conway <neilc@samurai.com> writes:
> Weird -- it's difficult to see how there could be a problem in
> CreatePortal(), as that is both simple and widely used code.
The other interesting point is that we've certainly tested on HPUX
recently --- I know I've checked both 11.11 and 11.23 using HP's
testdrive machines. So the question here is not so much "why doesn't
PG work on HPUX" as "what weird configuration are you using?"
regards, tom lane
Hello Neil, Does this output mean anything to you? $ gdb /usr/local/pgsql/bin/postgres /usr/local/pgsql/data/base/1/core bt . Core was generated by `postgres'. Program terminated with signal 10, Bus error. warning: The shared libraries were not privately mapped; setting a breakpoint in a shared library will not work until you rerun the program. #0 0x23cf64 in CreatePortal+0x1f4 () (gdb) bt #0 0x23cf64 in CreatePortal+0x1f4 () #1 0x23ce28 in CreatePortal+0xb8 () #2 0x19c094 in exec_simple_query+0x194 () #3 0x19daa8 in PostgresMain+0x1520 () #4 0x12f918 in main+0x1e0 () thanks. Haluk ----- Original Message ----- From: "Neil Conway" <neilc@samurai.com> To: "Haluk GÜNÇER" <halukguncer@hotmail.com> Cc: <pgsql-bugs@postgresql.org> Sent: Thursday, May 26, 2005 4:02 AM Subject: Re: [BUGS] BUG #1678: pw_shadow BUS ERROR > Haluk GÜNÇER wrote: >> I did it with -n option. The generated core file is attached. I hope it >> will help. > > The core file itself is not much use -- you need to get a stack trace from > the core file (which I can't do, since I don't have the binaries you > built -- or an HPUX system for that matter). You can get a stack trace via > gdb using "gdb /path/to/binary /path/to/core" followed by "bt"; there may > be a different / better way to do things on HPUX (HP support should be > able to tell you, at any rate). > > -Neil >
I have already rebuilt it with -g option. Is it possible to get the binaries for HPUX from you? I wonder if the problem persists with yours. I would also like to get for solaris8 afterwards as well. thanks a lot. Haluk. ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: "Neil Conway" <neilc@samurai.com> Cc: "Haluk GÜNÇER" <halukguncer@hotmail.com>; <pgsql-bugs@postgresql.org> Sent: Tuesday, May 31, 2005 9:13 AM Subject: Re: [BUGS] BUG #1678: pw_shadow BUS ERROR > Neil Conway <neilc@samurai.com> writes: >> Weird -- it's difficult to see how there could be a problem in >> CreatePortal(), as that is both simple and widely used code. > > The other interesting point is that we've certainly tested on HPUX > recently --- I know I've checked both 11.11 and 11.23 using HP's > testdrive machines. So the question here is not so much "why doesn't > PG work on HPUX" as "what weird configuration are you using?" > > regards, tom lane >
Haluk GÜNÇER <halukguncer@hotmail.com> writes: > I would like to get the patch list installed on the machine you compiled > postgresQL FROM YOU , so that I can compare with ours. It takes about 12kB. I used one of the PA-RISC servers provided by HP's testdrive program http://www.testdrive.hp.com ... I don't remember exactly which one, but hopefully they are all configured alike. (Of course, they may have updated them since I last tried it, which was early January or so.) You can sign up for an account and check all the details you like... regards, tom lane
Hello Tom, You wrote that you ran postgresql on HPUX11.11. Our Server type: V2500 12CPU 16GB RAM. I would like to get the patch list installed on the machine you compiled postgresQL FROM YOU , so that I can compare with ours. It takes about 12kB. Command for patch list # swlist .. PHSS_30478 1.0 X11 Font Library Patch PHSS_30791 1.0 XClientsPeriodic Patch PHSS_30970 1.0 ld(1) and linker tools cumulative patch .. # # swlist > patchlist.txt # Regards. Haluk. ----- Original Message ----- From: "Haluk GÜNÇER" <halukguncer@hotmail.com> To: "Neil Conway" <neilc@samurai.com>; "Tom Lane" <tgl@sss.pgh.pa.us> Cc: <pgsql-bugs@postgresql.org> Sent: Thursday, June 02, 2005 6:17 PM Subject: Re: [BUGS] BUG #1678: pw_shadow BUS ERROR > Hello Neil & Tom, > > I re-installed everthing many many times. I've also installed every > missing > libraries readline, zlib etc. > > Here, I have attached the debug output of the following command. I > recently > compiled everything in debug mode. > As you requested I could not get detailed info via gdb. > > /usr/local/pgsql/bin/initdb -d -n > out.log 2>debug.log > > > by the way, I succesfully installed 8.0.3 on fujitsu-siemens solaris 8. > > thanks, > regards. > > Haluk > > > > > > ----- Original Message ----- > From: "Tom Lane" <tgl@sss.pgh.pa.us> > To: "Neil Conway" <neilc@samurai.com> > Cc: "Haluk GÜNÇER" <halukguncer@hotmail.com>; <pgsql-bugs@postgresql.org> > Sent: Tuesday, May 31, 2005 9:13 AM > Subject: Re: [BUGS] BUG #1678: pw_shadow BUS ERROR > > >> Neil Conway <neilc@samurai.com> writes: >>> Weird -- it's difficult to see how there could be a problem in >>> CreatePortal(), as that is both simple and widely used code. >> >> The other interesting point is that we've certainly tested on HPUX >> recently --- I know I've checked both 11.11 and 11.23 using HP's >> testdrive machines. So the question here is not so much "why doesn't >> PG work on HPUX" as "what weird configuration are you using?" >> >> regards, tom lane >> >
Tom, My problem is solved! I compiled postgresql 8.0.3 on HP test drive machine. Then it worked succesfully. I tar'ed and copied the generated code to our server , and it worked. I suggest to put binaries for each vendor to this website for downloading so that we wont waste out time for compiling. Thanks a lot to you all. Haluk ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: "Haluk GÜNÇER" <halukguncer@hotmail.com> Cc: <pgsql-bugs@postgresql.org> Sent: Friday, June 03, 2005 5:29 PM Subject: Re: [BUGS] BUG #1678: pw_shadow BUS ERROR > Haluk GÜNÇER <halukguncer@hotmail.com> writes: >> I would like to get the patch list installed on the machine you compiled >> postgresQL FROM YOU , so that I can compare with ours. It takes about >> 12kB. > > I used one of the PA-RISC servers provided by HP's testdrive program > http://www.testdrive.hp.com ... I don't remember exactly which one, > but hopefully they are all configured alike. (Of course, they may have > updated them since I last tried it, which was early January or so.) > You can sign up for an account and check all the details you like... > > regards, tom lane >