Return-Path: postman Delivery-Date: Wed, 25 Aug 93 02:07:49 PDT Return-Path: postman Received: by postgres.Berkeley.EDU (5.61/1.29) id AA14657; Wed, 25 Aug 93 01:52:28 -0700 Resent-From: postman (POSTGRES mailing list) Resent-Message-Id: <9308250852.AA14657@postgres.Berkeley.EDU> Sender: owner-postman@postgres.Berkeley.EDU X-Return-Path: aoki@postgres.Berkeley.EDU Received: from faerie.CS.Berkeley.EDU by postgres.Berkeley.EDU (5.61/1.29) id AA14649; Wed, 25 Aug 93 01:52:23 -0700 Received: from localhost (localhost [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.1C/8.1B) with SMTP id CAA24296; Wed, 25 Aug 1993 02:01:57 -0700 Message-Id: <199308250901.CAA24296@faerie.CS.Berkeley.EDU> From: aoki@postgres.Berkeley.EDU (Paul M. Aoki) To: Gunter Strube Cc: postgres@postgres.Berkeley.EDU Subject: Re: Another FATAL error In-Reply-To: Your message of Wed, 25 Aug 1993 09:35:43 +0200 <93Aug25.083558met_dst.6185@redamoi.regent.e-technik.tu-muenchen.de> Date: Wed, 25 Aug 93 02:01:56 -0700 X-Sender: aoki@postgres.Berkeley.EDU X-Mts: smtp Resent-To: postgres-dist Resent-Date: Wed, 25 Aug 93 01:52:27 PDT Gunter Strube writes: > Ok, I got my postgres running again and it worked fine for the rest > of yesterday. > Today however, I get the FATAL error: > FATAL 1:Aug 25 08:25:55:initialization failed on sony jukebox > on anything I do. This seems strange to me and I have no Idea how to > deal with this - especially since nothing has changed in our > configuration. two items. by mistake, the precompiled 4.1 systems had support for the sony MO disk jukebox built in. this should not have been turned on but this is harmless. the reason this appears is that the first set of files the system tries to open are the _sj_* files in .../data. if it can't open those files read/write, it quits. sounds to me like someone either changed the ownership to a user besides "postgres" (since the files in .../data are installed mode 600 this would prevent read/write) or the file permissions have changed so that they are not readable and/or writable. or those files have been deleted, which is also bad. :-) in any case it sounds like someone is screwing around too much with your .../data directory. if you think files are gone or damaged, cleardbdir followed by initdb always works :-) -- Paul M. Aoki | CS Div., Dept. of EECS, UCB | aoki@postgres.Berkeley.EDU | Berkeley, CA 94720 | ...!uunet!ucbvax!aoki