Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
Hi Andrew, please take a look at [1]. The man page description of "sel time set" is invalid. You must use the locale's date / time format. CU Jörg https://codeberg.org/IPMITool/ipmitool/issues/18 -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
On Sat, 2023-12-16 at 08:32 +0100, Jörg Frings-Fürst wrote: > Hi Andrew, > > Am Samstag, dem 16.12.2023 um 08:12 +0100 schrieb Jörg Frings-Fürst: > > Hello Andrew, > > > > > > the ipmitool code in this area has not changed for years. If I > > remember > > correctly, there was a change in the shell where a parameter was > > activated by > > default. > > > > > > Can you escape the outer "? Like this > > > > ipmitool sel time set \"$(date "+%m/%d/%Y %T")\" > > the % must be escaped to > > ipmitool sel time set \"$(date "+\%m/\%d/\%Y \%T")\" hello - this still fails: # ipmitool sel time set \"$(date "+\%m/\%d/\%Y \%T")\" Specified time could not be parsed i don't think that shell escapes are the issue. the same command on the same system will succeed or fail depending on the installed version of the ipmitool package. here is a transcript of a test without the added complexity of the `date` call. it still shows the version- specific behavior: # ipmitool -V ipmitool version 1.8.18 # ipmitool sel time set "12/14/2023 11:40:47" 12/14/2023 11:40:47 # apt -y install ipmitool=1.8.19-4 [...] # ipmitool -V ipmitool version 1.8.19 # ipmitool sel time set "12/14/2023 11:40:47" IANA PEN registry open failed: No such file or directory Specified time could not be parsed # dpkg -i /tmp/ipmitool_1.8.18-10.1_amd64.deb [...] # ipmitool -V ipmitool version 1.8.18 # ipmitool sel time set "12/14/2023 11:40:47" 12/14/2023 11:40:47 as far as i can tell 1.8.18 works as expected and 1.8.19 does not. for what it's worth the "IANA PEN registry" message does not appear when testing with 1.8.19-6 but the "Specified time could not be parsed" error remains. i also tried escaping quotes without effect: # ipmitool sel time set \"12/14/2023 11:40:47\" # ipmitool sel time set \""12/14/2023 11:40:47\"" thank you. andy -- andrew bezella internet archive
Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
Hi Andrew, Am Samstag, dem 16.12.2023 um 08:12 +0100 schrieb Jörg Frings-Fürst: > Hello Andrew, > > > the ipmitool code in this area has not changed for years. If I remember > correctly, there was a change in the shell where a parameter was activated by > default. > > > Can you escape the outer "? Like this > > ipmitool sel time set \"$(date "+%m/%d/%Y %T")\" the % must be escaped to ipmitool sel time set \"$(date "+\%m/\%d/\%Y \%T")\" > > > CU > Jörg > > Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
Hello Andrew, the ipmitool code in this area has not changed for years. If I remember correctly, there was a change in the shell where a parameter was activated by default. Can you escape the outer "? Like this ipmitool sel time set \"$(date "+%m/%d/%Y %T")\" CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. Am Freitag, dem 15.12.2023 um 11:31 -0800 schrieb andrew bezella: > On Fri, 2023-12-15 at 16:10 +0100, Jörg Frings-Fürst wrote: > > [...] > > thank you for the quick reply! > > > Please can you test with > > > > ipmitool sel time set now > > this reports success (and i changed our crontab over to it yesterday): > # ipmitool sel time set now > 12/15/2023 04:20:53 PM UTC > > > and with > > > > ipmitool sel clear && ipmitool sel time set "$(date "+%m/%d/%Y %T")" > > this fails (tried repeatedly just in case it actually needed "a few > seconds"): > # ipmitool sel clear && ipmitool sel time set "$(date "+%m/%d/%Y %T")" > > Clearing SEL. Please allow a few seconds to erase. > Specified time could not be parsed > > i also tested on an older system where i upgraded only the ipmitool > package with the same results. > > > one slight correction to my original bug report: i first noticed the > issue w/1.8.19-4 (i had reported "1.8.19-6") > > hope that helps. thanks again. > > andy > signature.asc Description: This is a digitally signed message part
Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
On Fri, 2023-12-15 at 16:10 +0100, Jörg Frings-Fürst wrote: [...] thank you for the quick reply! > Please can you test with > > ipmitool sel time set now this reports success (and i changed our crontab over to it yesterday): # ipmitool sel time set now 12/15/2023 04:20:53 PM UTC > and with > > ipmitool sel clear && ipmitool sel time set "$(date "+%m/%d/%Y %T")" this fails (tried repeatedly just in case it actually needed "a few seconds"): # ipmitool sel clear && ipmitool sel time set "$(date "+%m/%d/%Y %T")" Clearing SEL. Please allow a few seconds to erase. Specified time could not be parsed i also tested on an older system where i upgraded only the ipmitool package with the same results. one slight correction to my original bug report: i first noticed the issue w/1.8.19-4 (i had reported "1.8.19-6") hope that helps. thanks again. andy -- andrew bezella internet archive
Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
Hello Andrew, thank you for your efforts in creating the bug report. You are making Debian better. Please can you test with ipmitool sel time set now and with ipmitool sel clear && ipmitool sel time set "$(date "+%m/%d/%Y %T")" Many thanks. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. Am Donnerstag, dem 14.12.2023 um 16:06 -0800 schrieb andrew bezella: > Package: ipmitool > Version: 1.8.19-6 > Severity: normal > > Dear Maintainer, > > after upgrading a system from bullseye to bookworm i found that the > ipmitool command we had been using to set the bmc time was failing. > > the crontab entry was: > ipmitool sel time set "$(date "+%m/%d/%Y %T")" > > this worked up to ipmitool 1.8.18-10.1 and started failing with > 1.8.19-6. i confirmed the usage and the problem via: > # ipmitool sel time set > usage: sel time set "mm/dd/ hh:mm:ss" > # ipmitool sel time set "12/14/2023 11:40:47" > Specified time could not be parsed > > investigation showed that a cleaner solution in our case is: > # ipmitool sel time set now > > but the inability to set an arbitrary time looks like a bug. > > thanks in advance. > > andy > > > -- System Information: > Debian Release: 12.3 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, > 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-13-amd64 (SMP w/64 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ipmitool depends on: > ii init-system-helpers 1.65.2 > ii libc6 2.36-9+deb12u3 > ii libfreeipmi17 1.6.10-1+b1 > ii libreadline8 8.2-1.3 > ii libssl3 3.0.11-1~deb12u2 > > Versions of packages ipmitool recommends: > pn openipmi > > ipmitool suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#1058711: ipmitool: sel time set fails: "Specified time could not be parsed"
Package: ipmitool Version: 1.8.19-6 Severity: normal Dear Maintainer, after upgrading a system from bullseye to bookworm i found that the ipmitool command we had been using to set the bmc time was failing. the crontab entry was: ipmitool sel time set "$(date "+%m/%d/%Y %T")" this worked up to ipmitool 1.8.18-10.1 and started failing with 1.8.19-6. i confirmed the usage and the problem via: # ipmitool sel time set usage: sel time set "mm/dd/ hh:mm:ss" # ipmitool sel time set "12/14/2023 11:40:47" Specified time could not be parsed investigation showed that a cleaner solution in our case is: # ipmitool sel time set now but the inability to set an arbitrary time looks like a bug. thanks in advance. andy -- System Information: Debian Release: 12.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/64 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ipmitool depends on: ii init-system-helpers 1.65.2 ii libc62.36-9+deb12u3 ii libfreeipmi171.6.10-1+b1 ii libreadline8 8.2-1.3 ii libssl3 3.0.11-1~deb12u2 Versions of packages ipmitool recommends: pn openipmi ipmitool suggests no packages. -- no debconf information
