Port Bug Report: initdb: stuck spinlock

From: Unprivileged user <nobody>
To: pgsql-ports(at)postgresql(dot)org
Subject: Port Bug Report: initdb: stuck spinlock
Date: 1999-05-08 10:46:43
Message-ID: 199905081046.GAA21033@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-ports


============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : James Klicman
Your email address : james(at)klicman(dot)com

Category : install: other
Severity : critical

Summary: initdb: stuck spinlock

System Configuration
--------------------
Operating System : Linux 2.2.5

PostgreSQL version : 6.0

Compiler used : egcs-1.1.2

Hardware:
---------
Alpha 500Mhz, 256M RAM, RedHat-6.0
Linux alpha.klicman.com 2.2.5-16 #1 Tue Apr 27 04:55:03 EDT 1999 alpha unknown

Versions of other tools:
------------------------
make 3.77
flex 2.5.4

--------------------------------------------------------------------------

Problem Description:
--------------------
[postgres(at)alpha pgsql]$ initdb

We are initializing the database system with username postgres (uid=65).
This user will own all the files and must also own the server process.

Creating template database in /usr/local/pgsql/data/base/template1

FATAL: s_lock(202e8560) at spin.c:114, stuck spinlock. Aborting.

FATAL: s_lock(202e8560) at spin.c:114, stuck spinlock. Aborting.
initdb: could not create template database
initdb: cleaning up by wiping out /usr/local/pgsql/data/base/template1

--------------------------------------------------------------------------

Test Case:
----------
run initdb.
happens everytime I run it.

--------------------------------------------------------------------------

Solution:
---------

--------------------------------------------------------------------------

Browse pgsql-ports by date

  From Date Subject
Next Message David Wetzel 1999-05-08 19:11:24 pqReadData() -- backend closed the channel unexpectedly.
Previous Message Unprivileged user 1999-05-07 22:48:34 Port Bug Report: Parse error for insert statement when using jdbc.