X-Loop: [email protected] Subject: bug#829: cryptroot-unlock: remote unlock fails with "Try again later" Reply-To: tux2bsd <[email protected]>, [email protected] Resent-From: tux2bsd <[email protected]> Resent-To: [email protected] Resent-CC: [email protected] X-Loop: [email protected] Resent-Date: Sun, 07 Jan 2024 20:40:11 +0000 Resent-Message-ID: <[email protected]> Resent-Sender: [email protected] X-Devuan-PR-Message: report 829 X-Devuan-PR-Package: cryptsetup-initramfs X-Devuan-PR-Keywords: Received: via spool by [email protected] id=B.1704659945541 (code B); Sun, 07 Jan 2024 20:40:11 +0000 Received: (at submit) by bugs.devuan.org; 7 Jan 2024 20:39:05 +0000 Delivered-To: [email protected] Received: from email.devuan.org [2a01:4f9:fff1:14::58c6:6475] by doc.devuan.org with IMAP (fetchmail-6.4.16) for <debbugs@localhost> (single-drop); Sun, 07 Jan 2024 20:39:05 +0000 (UTC) Received: from email.devuan.org by email.devuan.org with LMTP id jky+A+ILm2WhNgAAmSBk0A (envelope-from <[email protected]>) for <[email protected]>; Sun, 07 Jan 2024 20:38:58 +0000 Received: by email.devuan.org (Postfix, from userid 109) id 03519614; Sun, 7 Jan 2024 20:38:57 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=185.70.43.25; helo=mail-4325.protonmail.ch; [email protected]; receiver=<UNKNOWN> Received: from mail-4325.protonmail.ch (mail-4325.protonmail.ch [185.70.43.25]) by email.devuan.org (Postfix) with ESMTPS id BCF281D for <[email protected]>; Sun, 7 Jan 2024 20:38:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1704659932; x=1704919132; bh=UKYoZ7A34lslz5kR9cFQ/MDbxE6cUqRVQgnTan2P/Ps=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=dM05eZRVMRwLMicbXYnvjUdrRLISNreM61XvJpotJJ5HIRmpa+9FJS8VpRKJlpGH2 2BaXkyMEieTmI3DDEwIxtKmPlOVeIe3L6ayax/5k03JjigtDrxaqvHn5EtTXiBAXwq 1TNbEbIKdPgeTtEhrnMcXqpt/5KLxw4ko5KqmwZLh9/6IfLKx8R5LxfmOB8DIwyvnU xF6tO5TYEVzEAdGixljW0To3lPcW2NrZE6h3fY/xA/Bt03Oxhtr7tQcn8KDT1WFrqR EsU0AW9zYHXk0upoZYq0fLD8GBWTnh1/GiRZhVZTLujzvHw1MWpgOhBzvLt9kW20sm OIKTNxlR/FDeQ== Date: Sun, 07 Jan 2024 20:38:41 +0000 To: "[email protected]" <[email protected]> From: tux2bsd <[email protected]> Message-ID: <e7tTQRDVCrHyf_uketHm0QAPWgN_6PJKneVSwnEgVOnrN5erYypf7dplA9M9eZEl98TRQxqACTjhpGl0tAVjwafd2SWAGAYNlpub9ewv8Eo=@protonmail.com> Feedback-ID: 34758390:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Package: cryptsetup-initramfs Version: 2:2.6.1-4~deb12u1 Devuan Daedalus ssh to unlock via cryptsetup-initramfs remotely met with "Try again later" = from cryptroot-unlock script. As per the discussion and information from https://dev1galaxy.org/viewtopic.php?pid=3D47015 This two line change fixes the problem: diff /usr/share/cryptsetup/initramfs/bin/cryptroot-unlock.bug /usr/share/cr= yptsetup/initramfs/bin/cryptroot-unlock 33c33 < if [ ! -f "$TABFILE" ] || [ "$TABFILE" -ot "/proc/1" ]; then --- > if [ ! -f "$TABFILE" ] ; then 35c35 < echo "Try again later" >&2 --- > echo "Error: $TABFILE missing." >&2
Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 X-Loop: [email protected] From: "Devuan bug Tracking System" <[email protected]> To: tux2bsd <[email protected]> Subject: bug#829: Acknowledgement (cryptroot-unlock: remote unlock fails with "Try again later") Message-ID: <[email protected]> References: <e7tTQRDVCrHyf_uketHm0QAPWgN_6PJKneVSwnEgVOnrN5erYypf7dplA9M9eZEl98TRQxqACTjhpGl0tAVjwafd2SWAGAYNlpub9ewv8Eo=@protonmail.com> X-Devuan-PR-Message: ack 829 X-Devuan-PR-Package: cryptsetup-initramfs Reply-To: [email protected] Date: Sun, 07 Jan 2024 20:40:12 +0000 Thank you for filing a new bug report with Devuan. You can follow progress on this bug here: 829: https://bugs.devuan.org/cgi/= bugreport.cgi?bug=3D829. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): [email protected] If you wish to submit further information on this problem, please send it to [email protected]. Please do not send mail to [email protected] unless you wish to report a problem with the Bug-tracking system. --=20 829: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D829 Devuan Bug Tracking System Contact [email protected] with problems
Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd,
1994-97 Ian Jackson.
Devuan Bugs Owner <[email protected]>.
Last modified:
Wed, 29 Jan 2025 20:39:01 UTC