Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyUki-008mN6-56 for pgsql-novice@arkaria.postgresql.org; Thu, 02 Nov 2023 10:16:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qyUkg-00CjMx-Na for pgsql-novice@arkaria.postgresql.org; Thu, 02 Nov 2023 10:16:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyUkg-00CjMp-AO for pgsql-novice@lists.postgresql.org; Thu, 02 Nov 2023 10:16:38 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qyUkd-004JEp-S6 for pgsql-novice@lists.postgresql.org; Thu, 02 Nov 2023 10:16:37 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-9d0b4dfd60dso111465766b.1 for ; Thu, 02 Nov 2023 03:16:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1698920195; x=1699524995; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=eE+cqTKopFg/yjFRDpEjgEOgb3jkSWwGvmm6ovEpCHw=; b=MpBV3MTsSyvtmVpqx1iICqWE+k8yhUOzi6Z64wTE7YhYe6rl8TpfP2o9mCpt8ObQnU FsNnuIa7VlxVbPQ/+OAalA4Pq6wGxk5bWDwLwA1y1e9+lqsKg+X8AIqFgHX+igagoOe/ /zVBSheIqx57psUkDYYEyJny/DD1UxamLg9HElxiMZ33UW/9BFoW3dysXRWowY6lxBCv F5kWgmdajMtbmD1XlUfPPg/xBJM8VX0d7IlyZ1n1ui7awPQdKUj2o0jpqteR1nBxZBuB /c92Qg1mcs8e3bckrb0Z+qvWxeIh1/D6iAI7zhUCPYd5oFYaOdkNJl3zJcrXuwcxn+s8 T7mQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698920195; x=1699524995; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=eE+cqTKopFg/yjFRDpEjgEOgb3jkSWwGvmm6ovEpCHw=; b=cAQxVnKGTLJ2oDdwhmzT9KOLKXMdOCi5M4t3zNG6pNj+Wt+CykKivoR8qQ+TzdqM3N hSUcxEwveW5Rqhu3L/olhGSqKPEHWmFTKniwlXfVmD3MnOpYkB1GZcnh8BP80h+NpRRI ZKiLo9YAw0PCGHQtwuBLr2ZUPbkvwbnWJDNdFXmTomqyXtTERrzaZHhtthAZBIXe1GTX V70zMEtpsxzT9ohVBrsjyQImbPTbIB1LLQCIL1CNUxei7Msm8c3OgMAVaKXofxLlQDYR BFsKGzg2hKn6HRtimJ5MzIg5RQAGgZvSsIcWUHlBGhqmQniJWdLiP9nqgHygRxB9s4Qj NRrg== X-Gm-Message-State: AOJu0Yw3QFfUyXq+wB0SdnDv1mkzRSbli693KcWFoomj7ZVibocDg7oV CB0oUPGO8vetiAOrcrS/eEDIB0xON7qRCTCmsjM= X-Google-Smtp-Source: AGHT+IE75qck0PtHqjn4q/RJDNEYqNUSqEUv5XB9E+gd6LPLhgOzrJqAix6uyYTwdUCoZCsVwiMu3w== X-Received: by 2002:a17:907:e8b:b0:9ba:65e:7529 with SMTP id ho11-20020a1709070e8b00b009ba065e7529mr4335525ejc.68.1698920194839; Thu, 02 Nov 2023 03:16:34 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:671d:efcb:786d:3c60:89d1]) by smtp.gmail.com with ESMTPSA id f25-20020a1709062c5900b009ad7fc17b2asm936714ejh.224.2023.11.02.03.16.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Nov 2023 03:16:34 -0700 (PDT) Message-ID: Subject: Re: fail to run postgresql16 after update from postgresql13 From: Laurenz Albe To: Ianseeks , pgsql-novice@lists.postgresql.org Date: Thu, 02 Nov 2023 11:16:33 +0100 In-Reply-To: <4842483.GXAFRqVoOG@lian-li> References: <4842483.GXAFRqVoOG@lian-li> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2023-11-02 at 08:14 +0000, Ianseeks wrote: > i hope i've got the correct mailing list for this question/problem. I'm = a=20 > novice. If you upgraded all the way from 9.6 to v16, you are not a novice. But that's fine. I find that - for whatever reason - people who write to the pgsql-novice rarely are. Perhaps modesty. Anyway. > A little history.=20 > I use opensuse tumbleweed and the Kmail/Kontact PIM software which is=20 > contrlled by software called Akondai and this requires a DB. The default= was=20 > Mysql but it caused a lot of reliability issues for me so i migrated to= =20 > Postgresql 9.6 (yes, it was a few years ago) >=20 > I've since then update the DB to 10, 11, 12 until ver 13 which i=20 > have been using until now. I did try updating to ver 14 but it failed w= ith=20 > locale issues during the update and i couldn't get a resolution. >=20 > I just recently managed to get the database converted from postgresql13 t= o=20 > postgresql16 and the data was transferred to the new DB with no issues.= =20 >=20 > I can't get Akonadi to load as it fails to start postgresql16, its failin= g=20 > with a message saying it needs postgesql9.6 as the DB was originally crea= ted=20 > using 9.6. I can't see why it insists on ver 9.6 being there as i've upda= ted=20 > to ver 16 and that process means i create an empty DB. I can't even inst= all=20 > Ver 9.6 to see if that cures the problem as its no longer in the opensuse= =20 > repos. >=20 > Here are the error messages from akonadi and the journal. >=20 > -------------- >=20 > This is from "systemctl status postgresql.service" >=20 > Oct 31 16:24:13 Lian-Li systemd[1]: Starting PostgreSQL database server..= . > Oct 31 16:24:13 Lian-Li postgresql-script[5916]: Your database files wer= e created by PostgreSQL version 9.6. > Oct 31 16:24:13 Lian-Li postgresql-script[5916]: Could not find executab= les for this version. > Oct 31 16:24:13 Lian-Li postgresql-script[5916]: Please install the Post= greSQL server package for version 9.6. > Oct 31 16:24:13 Lian-Li systemd[1]: postgresql.service: Control process e= xited, code=3Dexited, status=3D1/FAILURE > Oct 31 16:24:13 Lian-Li systemd[1]: postgresql.service: Failed with resul= t 'exit-code'. > Oct 31 16:24:13 Lian-Li systemd[1]: Failed to start PostgreSQL database s= erver. These error messages are not from PostgreSQL, but they seem to be from the script "postgresql-script". That script is not part of PostgreSQL. Look into that script and try to figure out how it arrives at that conclusi= on. If you cannot figure it out yourself, please share the relevant parts. Yours, Laurenz Albe