From nobody Tue Feb 25 10:35:10 2025 X-Original-To: erlang@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z2DWf3Bz0z5pc82 for ; Tue, 25 Feb 2025 10:35:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z2DWf2dyQz46Hl for ; Tue, 25 Feb 2025 10:35:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740479710; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WH0DReAoaI/NTb2LGQx+QxY6YiNaoKWUoIi7P0/HtFs=; b=hIm0IlfdK+kOFU4+y/RinmA5fJ9BYDrywjBZlDRAORUAURjqe1yOzrHjOCrOqEvGy1qLxk HN1/We6nCRQNTjv1VddQwyYO/+T/ZlxlGc58VKTKAUNdc/l5yXpjY638X1iRSJlebBZCk3 mTAaBPHT/zaJgJkI+opZvmDaa9EgOdRsva5MqeMaIKCz0I28dwQHZpDBFjmEjgGW8WGSHw uYRnlQGxRJcPM7z7tM8XtfjCVP1GQoOgyBsebTJ7tcuPrz78v2g6Weq1vzpmK/2UR1AlUP 7RTEjE6tJZXqImThgls0PyOuHIBSDRlh0/FqVEAWlzYARafF+IAHq1zdb72wzQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740479710; a=rsa-sha256; cv=none; b=SyhSsTvEAoCaKNPVeZAXKfimgYrfAY2p+fJcr3HwYnUSUPSOZ/2U5FGBsLbKcnib83Vpy0 T5FqKwWSAfS1RengKgP/uQMSE/ar3ZjiRxFqNil1Yv/Uq2Ze55lFhZv9n+q6gtwQCanFHR m9whsL8pTE8TrFsGECBR149dt49UQGbxeYeh8t0bjqB/vD4yPJ1YpdcPIZbGLP5yE66NzD zp+GF52UbFrq9h5thqsof7CcHjRwwVQ8i+mT6INHfVtBzrHLbgpM2NysyN8GZ55pN7iOuL RAwjaD2DhDwrWcJIsy2oneH4BNqtCtZqnI5LT6GL6+SEYFk/cPEaSFW2duydHg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740479710; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WH0DReAoaI/NTb2LGQx+QxY6YiNaoKWUoIi7P0/HtFs=; b=io4EVDIBFhJ+9B+swgUFrUlxJOnr4qHYUyASbgc8KD2Rl/cSkfLRvTYZz8hBj5Iqd5MWtH Z7+N5nyAQ0iXAYA8Xqoo6uvZO5VEY3AJMRS/bVGXUIXs8bCUwqydDobsKWOpi6w43WMS7Z ssokiFuvCeJZlNKh3nPOJYWTgTnQvqDe2Nq72lbrDqQ9IOCJhj8+vkwVJXqqvL/HZfZySi /4vRmGjIzo6AUhvE3qA7oduytaaPgbaJB3sjooVLA9cm//5th7/pELR0pLCr6KLX0HsL+c POoEUGWe/nYUA5IC1UegQhl0EGhISQbg4t0JzdOiEEseow9BXdJAIHw5SqO8oA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z2DWf2DqKz7fP for ; Tue, 25 Feb 2025 10:35:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51PAZArn014469 for ; Tue, 25 Feb 2025 10:35:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51PAZA4O014468 for erlang@FreeBSD.org; Tue, 25 Feb 2025 10:35:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: erlang@FreeBSD.org Subject: [Bug 285020] net/rabbitmq: fix crash on start Date: Tue, 25 Feb 2025 10:35:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dch@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: dch@freebsd.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: assigned_to cc bug_status attachments.created Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Support of Erlang-related ports List-Archive: https://lists.freebsd.org/archives/freebsd-erlang List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-erlang@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285020 Dave Cottlehuber changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|erlang@FreeBSD.org |dch@freebsd.org CC| |dch@freebsd.org Status|New |Open --- Comment #2 from Dave Cottlehuber --- Created attachment 257914 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D257914&action= =3Dedit alternative approach thanks Marek! I can't replicate it here in a fresh 14.2-RELEASE jail, I think we should probably use rabbitmq_chdir here, and make sure that all of the *HOME flavoured variables line up. Can you try this and see if it helps? ## reproduce steps root@bunny:/ # pkg install -r FreeBSD rabbitmq Updating FreeBSD repository catalogue... [bunny.skunkwerks.at] Fetching meta.conf: 100% 178 B 0.2kB/s 00:01 [bunny.skunkwerks.at] Fetching data.pkg: 100% 7 MiB 1.5MB/s 00:05 Processing entries: 100% FreeBSD repository update completed. 35857 packages processed. All repositories are up to date. The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: erlang-runtime27: 27.1.2_1 [FreeBSD] rabbitmq: 4.0.4 [FreeBSD] Number of packages to be installed: 2 The process will require 139 MiB more space. 55 MiB to be downloaded. Proceed with this action? [y/N]: y [bunny.skunkwerks.at] [1/2] Fetching rabbitmq-4.0.4.pkg: 100% 16 MiB=20=20 2.8MB/s 00:06 [bunny.skunkwerks.at] [2/2] Fetching erlang-runtime27-27.1.2_1.pkg: 100% = 39 MiB 3.7MB/s 00:11 Checking integrity... done (0 conflicting) [bunny.skunkwerks.at] [1/2] Installing erlang-runtime27-27.1.2_1... [bunny.skunkwerks.at] [1/2] Extracting erlang-runtime27-27.1.2_1: 100% [bunny.skunkwerks.at] [2/2] Installing rabbitmq-4.0.4... =3D=3D=3D> Creating groups Creating group 'rabbitmq' with gid '135' =3D=3D=3D> Creating users Creating user 'rabbitmq' with uid '135' =3D=3D=3D> Creating homedir(s) [bunny.skunkwerks.at] [2/2] Extracting rabbitmq-4.0.4: 100% =3D=3D=3D=3D=3D Message from erlang-runtime27-27.1.2_1: -- To use this runtime port for development or testing, just prepend its binary path ("/usr/local/lib/erlang27/bin") to your PATH variable. =3D=3D=3D=3D=3D Message from rabbitmq-4.0.4: -- First-time users will want to run: sudo -u rabbitmq rabbitmq-plugins enable rabbitmq_management sudo -u rabbitmq rabbitmqctl enable_feature_flag --experimental khepri_db and restart, to enable the web admin console at http://localhost:15672/ with a default username and password of guest:guest. You should change it.. See https://www.rabbitmq.com/docs for install help, and https://www.rabbitmq.com/docs/configure for further options. root@bunny:/ # sudo -u rabbitmq rabbitmq-plugins enable rabbitmq_management Enabling plugins on node rabbit@bunny: rabbitmq_management The following plugins have been configured: rabbitmq_management rabbitmq_management_agent rabbitmq_web_dispatch Applying plugin configuration to rabbit@bunny... The following plugins have been enabled: rabbitmq_management rabbitmq_management_agent rabbitmq_web_dispatch set 3 plugins. Offline change; changes will take effect at broker restart. root@bunny:/ # sudo -u rabbitmq rabbitmqctl enable_feature_flag --experimen= tal khepri_db Error: unable to perform an operation on node 'rabbit@bunny'. Please see diagnostics information and suggestions below. Most common reasons for this are: * Target node is unreachable (e.g. due to hostname resolution, TCP connect= ion or firewall issues) * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server) * Target node is not running In addition to the diagnostics info below: * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more * Consult server logs on node rabbit@bunny * If target node is configured to use long node names, don't forget to use --longnames with CLI tools DIAGNOSTICS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D attempted to contact: [rabbit@bunny] rabbit@bunny: * connected to epmd (port 4369) on bunny * epmd reports: node 'rabbit' not running at all no other nodes on bunny * suggestion: start the node Current node details: * node name: 'rabbitmqcli-625-rabbit@bunny' * effective user's home directory: /var/db/rabbitmq * Erlang cookie hash: 2MNtNN90Ut00NNgJZ3fypg=3D=3D root@bunny:/ # sysrc rabbitmq_enable=3Dyes rabbitmq_enable: -> yes root@bunny:/ # service rabbitmq restart Starting rabbitmq. root@bunny:/ # sockstat -46l|grep 5672 rabbitmq beam.smp 12629 19 tcp4 100.64.112.33:25672 *:* rabbitmq beam.smp 12629 37 tcp4 100.64.112.33:15672 *:* rabbitmq beam.smp 12629 38 tcp6 fca2:927d:4de2:8e50:6c98::7021:5672 *:* rabbitmq beam.smp 12629 39 tcp4 100.64.112.33:5672 *:* ``` --=20 You are receiving this mail because: You are the assignee for the bug.=