From: "Massimo S." Received: from mail2.quasarbbs.net ([80.86.52.115] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 3290043 for ecs-isp@2rosenthals.com; Wed, 05 Aug 2026 03:37:32 -0400 DKIM-Signature: v=1; q=dns/txt; a=rsa-sha256; c=relaxed/relaxed; s=default; d=ecomstation.it; bh=n5pm8eJBrqe+IMGQPTyHHMDluhwthz2ptv66kMwdVs4=; h=Return-Path:From:To:Subject:Date:Message-ID; b=CCCO37ddvbVJJahP7d8orCn5lBTajb3R3Ni8cSNW7q47Y4PhGSAV98EpTLFj5JRAVtyXY JooOifoaL3mRs5aLqYf9Q6sBSyBunpev0Ak+a//M+Om8PgKvnMl/4yzLgF2frnKKmKi+N+7 4gnxXyo1u9Rl1NX4kDidu/b+slGhMwGk3+SdUaRMXPiEjvNhQHnLJFe9xBQdJGVIyi1A+FS CB0BlrZzXsQZ2tmrfXKIHDcWeYTVBXAyx7MgebRGwfyn3i7xHhm7RYs0XHEM0uxgmSDQA8y A7TEEUSPDU2EaBmJ7S2uOeA7oX4iefKJbmKQJCoMJxjCO3tz2TwmmKybegAw== Authentication-Results: srv2; spf=none smtp.helo=[192.168.10.199]; spf=pass smtp.mailfrom=ecomstation.it Received: from [192.168.10.199] (dtp [192.168.10.199]) by srv2 (Weasel v3.143) for ; Wed, 05 Aug 2026 09:37:28 -0000 Reply-To: ml@ecomstation.it Subject: Re: [eCS-ISP] uacme 1.2.4 issue To: eCS ISP Mailing List References: Organization: Massimo S. Message-ID: <08fff6ca-120c-58cf-015b-6ae2810057b8@ecomstation.it> Date: Wed, 5 Aug 2026 09:37:25 +0200 User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; it-IT; rv:1.7.13) Gecko/20060424 Thunderbird/1.0.8 Mnenhy/0.7.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it Content-Transfer-Encoding: 8bit Il 05/08/2026 01:13, Peter Moylan ha scritto: > On 05/08/26 07:47, Paul Smedley wrote: >> On 4/8/26 22:31, Massimo S. wrote: >>> Il 09/06/2026 10:50, Paul Smedley ha scritto: > >>>> My guess would be the ca-certs rpm package is either missing or out >>>> of date. > >>> this is what i believed too.. >>> i've downloaded the new cacert.pem but this doesnt' help. >>> >>> Maybe uacme starting from version 1.2.4 (like 1.8.1 by Andrey too) has >>> some issue with /2 paths. >>> >>> cp: impossibile eseguire stat di >>> 'c:etcssluacme/www.myfakedomain.com/cert.pem': No such file or directory >>> >>> What's that "C:etcssluacm..."? >>> >> My 'guess' would be a shell issue.  Is this only when your scheduler >> starts uacme? Perhaps the schedule is overriding the statemetnts in >> config.sys that set *SHELL* to sh.exe > > That sounds like a Unixism. My config.sys has >       SET OS2_SHELL=C:\OS2\CMD.EXE > > I don't use cron, so I don't know whether cron overrides that. > > I've just realised that my updating script explicitly specifies the shell: >      Path and file name: cmd.exe >      Parameters:    /C issue_pmoylan.org.cmd > >> Sorry, I can't be bothered fixing my typos, I'm coming off some meds, so >> I'm not feeling great. > > Hope you're feeling better soon, Paul. Hi Peter, i'm trying to write, with the help of Copilot, an ACME rexx client that use open ssl 1.1.1s (or better), but it' really hard even if it's the chatbot that do code, it do a number of syntax errors :) Anyway please, could you send me your "cron" script/program? Even yesterday evening the renewal of some certificates started with UACME 1.8.1, all went KO. I had to connect to the VM and start manually the same script on the command prompt and of course all went well. This behaviour, that only fails if scheduled, is making me crazy :D Of course i've tried another cron (the rexx one), with no success. I've also tried to start from the cron a script that only do a start /C of the renewal script, but it still fail, what the f$ck! :D Thanks. massimo