Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCOvB-0008T3-Nv for pgsql-bugs@arkaria.postgresql.org; Mon, 02 Jan 2023 17:48:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pCOv9-0004LD-Fo for pgsql-bugs@arkaria.postgresql.org; Mon, 02 Jan 2023 17:48:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCOv8-0004L3-Ic for pgsql-bugs@lists.postgresql.org; Mon, 02 Jan 2023 17:48:23 +0000 Received: from resqmta-h1p-028595.sys.comcast.net ([2001:558:fd02:2446::3]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCOv0-0001wI-PB for pgsql-bugs@lists.postgresql.org; Mon, 02 Jan 2023 17:48:20 +0000 Received: from resomta-h1p-027914.sys.comcast.net ([96.102.179.199]) by resqmta-h1p-028595.sys.comcast.net with ESMTP id CM38pTlNHwIZgCOuvp5jky; Mon, 02 Jan 2023 17:48:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1672681689; bh=M55OoEzavNNKqsFWllQ4NYdMCALQzhX/fgNx7jI9vUc=; h=Received:Received:Content-Type:Message-ID:Date:MIME-Version: Reply-To:Subject:To:From:Xfinity-Spam-Result; b=1732Xa6Pl7rIaFatbxgrSxThCqKHC0RZVzM0fayGp/P4epaw6eOIkO+Y3Cc8cTlhr vBBD7wmGw1zrhbKcl08rdWC4x8vev+ByCxE+5egC7sMc8Eb2Uyj3u1bOHIf+jk8Rxd hL+0pgjrHsvKFCZ6SV5MVPWh3yE1lCDuuYPaPX4brT9ew7AJPcjYid08sbKLAWOAvS rTORoDo7YdsHARJFcPOOxh4fuPpD+4t5vI+AREH3R5EBWG7FvvYHKAdJyg6WGKyMIh iRa8W3hrRegILuWw/1EXtqu4OhdT6/siD6Jhmd1snFpTsX3GjjqFRsACP0Lc1iue41 0Vgm0kZC2DtBw== Received: from [192.168.1.227] ([68.43.246.244]) by resomta-h1p-027914.sys.comcast.net with ESMTPSA id COuWp4I7YeLhSCOuXpFr2n; Mon, 02 Jan 2023 17:47:47 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvhedrjedvgddutdeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucenucfjughrpegtkfffgggfrhfuvfevfhfhjgesrgdtreertdefjeenucfhrhhomhepvfhomhcuffhrhiguvghnuceothgurhihuggvnhestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepleehudeukeegteegtddtvddttdehleettdekueejvdduteevteegtedtteefjeeinecukfhppeeikedrgeefrddvgeeirddvgeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddvvdejngdpihhnvghtpeeikedrgeefrddvgeeirddvgeegpdhmrghilhhfrhhomhepthgurhihuggvnhestghomhgtrghsthdrnhgvthdpnhgspghrtghpthhtohepvddprhgtphhtthhopehtghhlsehsshhsrdhpghhhrdhprgdruhhspdhrtghpthhtohepphhgshhqlhdqsghughhssehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-Xfinity-VMeta: sc=0.00;st=legit Content-Type: multipart/alternative; boundary="------------bERfK5zn4rM1QlAF5Li8454W" Message-ID: <91a563d0-5704-1f86-009d-3e70979c7090@comcast.net> Date: Mon, 2 Jan 2023 12:47:44 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Reply-To: tdryden@comcast.net Subject: Re: PostgreSQL 15 on Fedora 37 Does not start after reboot Content-Language: en-US To: Tom Lane Cc: pgsql-bugs@lists.postgresql.org References: <1309910.1672614883@sss.pgh.pa.us> From: Tom Dryden In-Reply-To: <1309910.1672614883@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------bERfK5zn4rM1QlAF5Li8454W Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Fedora Bugzila report ID 2157651 has been submitted. Thanks Tom On 1/1/23 18:14, Tom Lane wrote: > Tom Dryden writes: >> PostgreSQL 15 on Fedora 37 Does not start after reboot >> The service is enabled and reports a network error after reboot. >> Starting the postgresql service manually after the reboot is successful. >> From the log file: >> 2023-01-01 09:22:26.406 EST [812] LOG: starting PostgreSQL 15.1 on >> x86_64-pc-linux-gnu, compiled by gcc (GCC) 12.2.1 20220819 (Red Hat >> 12.2.1-2), 64-bit >> 2023-01-01 09:22:26.406 EST [812] LOG: could not bind IPv4 address >> "192.168.122.124": Cannot assign requested address > This indicates that Postgres is starting before the network > interface is up, something that systemd is prone to try to do. > >> Suggested fix: >> Edit /usr/lib/systemd/system/postgresql-15.service and change the >> After=network.target line to >> After=network-online.target > Right, although some authorities suggest also adding > Wants=network-online.target > > In any case, that service file is not created or distributed by us. > I suggest filing this as a bug against the Fedora postgresql package. > > regards, tom lane --------------bERfK5zn4rM1QlAF5Li8454W Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Fedora Bugzila report ID 2157651 has been submitted.

Thanks

Tom

On 1/1/23 18:14, Tom Lane wrote:
Tom Dryden <tdryden@comcast.net> writes:
PostgreSQL 15 on Fedora 37 Does not start after reboot
The service is enabled and reports a network error after reboot. 
Starting the postgresql service manually after the reboot is successful.

      
 From the log file:

      
2023-01-01 09:22:26.406 EST [812] LOG: starting PostgreSQL 15.1 on 
x86_64-pc-linux-gnu, compiled by gcc (GCC) 12.2.1 20220819 (Red Hat 
12.2.1-2), 64-bit
2023-01-01 09:22:26.406 EST [812] LOG: could not bind IPv4 address 
"192.168.122.124": Cannot assign requested address
This indicates that Postgres is starting before the network
interface is up, something that systemd is prone to try to do.

Suggested fix:
Edit /usr/lib/systemd/system/postgresql-15.service and change the
After=network.target line to
After=network-online.target
Right, although some authorities suggest also adding
Wants=network-online.target

In any case, that service file is not created or distributed by us.
I suggest filing this as a bug against the Fedora postgresql package.

			regards, tom lane
--------------bERfK5zn4rM1QlAF5Li8454W--