On Sun, 14 Jul 2019, Larry Fahnoe wrote:
The issue appears to be caused by my upssched.conf file having the original
commented out declaration of CMDSCRIPT which is what is showing up via the
grep in the script.
Oof! Easy to fix. I have just uploaded an updated nut-report script which
shoul
On Jul 12, 2019, at 2:39 PM, David White wrote:
>
> Thanks Roger for all your help here. I hope the 2 attachments come through.
> The .sh is my doctored version of the script and the .report is its output. I
> welcome any suggestions or ideas about what might be causing my problems with
> monit
On Sun, 14 Jul 2019, Larry Fahnoe wrote:
A couple of different issues with the reporting script. First the password
masking is not working as intended: I have three different passwords in my
ups.users file and only the last one is masked.
Hello Larry, Thanks for the report. I've found the pas
A couple of different issues with the reporting script. First the password
masking is not working as intended: I have three different passwords in my
ups.users file and only the last one is masked. Here's the first part of
the resulting report where I've replaced the unmasked passwords with
.
Roger, I get 4.3.8(1)-release
There was good reason, BTW, for the script to NOT fine the journal
script on my machine. I had not downloaded it yet.
On 7/14/2019 9:06 AM, Roger Price wrote:
On Sun, 14 Jul 2019, David White wrote:
... I saw nothing that looked like a problem with the report s
On Sun, 14 Jul 2019, David White wrote:
... I saw nothing that looked like a problem with the report save the
sections "Cannot access . Perhaps this is from the
missing journal?
I'm wondering if the =~ operator in Bash is working as expected. What does
command
echo $BASH_VERSION
report
Roger, I just tried the journal report and it is unable to find
journalctl on my system. I am not very expert but this MAY be because my
Ubuntu install is actually running chroot'ed on an Android TV computer
and the expected systemd may not be there. Could the desired information
be elsewhere?
Hi Roger and thanks! I have attached my nut report from the new script
(sans journal). I saw nothing that looked like a problem with the report
save the sections "Cannot access . Perhaps this
is from the missing journal?
On 7/14/2019 7:52 AM, Roger Price wrote:
On Tue, 9 Jul 2019, Charles Le
On Tue, 9 Jul 2019, Charles Lepple wrote:
Can you please run this script to get more information about your setup? I
think just gzip'ing the report file should be sufficient to make it small
enough to attach to an email reply. (Also, for Ubuntu, you will need to change
D="/etc/ups" to D="/etc/
