Securityhome.eu

After a lot of searching a found the problem.

the command less is used in my script.
Under normal use, under my login in bash it is
/usr/bin/less but is the same in /bin/less, /sbin/less and /usr/sbin/less -> vesion: less 692 (PCRE2 regular expressions)
Works perfect without problem.

But not when ...

I found a work around,
put all the output of the script to /dev/null in cron,
so it doesn't send mails. But this is not exactly what I want.
I want to know the rootcause.

I get the following errors when cron executes scripts

'unknown': I need something more specific.

It is new, since the last update of cronie.
It happens on several script. (But not all)
The version is : cronie (OpenRC) 0.63

You can turn it off in
opera://password-manager/settings

Sure it is crashing because of disk ?

You can disable mounting the disk in /etc/fstab
Just comment it out with #
or you can add noauto , so it doesn't mount at boot.
like for a cd-rom
# Device Mountpoint FStype Options Dump Pass#
/dev/cd0 /cdrom cd9660 ro,noauto 0 0

Or you can add nofail, so ...

You can use:
sudo hdparm -Tt /dev/sda

You should see something like this:
/dev/sda:
Timing cached reads: 15132 MB in 1.99 seconds = 7586.99 MB/sec
Timing buffered disk reads: 330 MB in 3.00 seconds = 109.86 MB/sec

or for M2 SSD:
/dev/nvme0n1p2:
Timing cached reads: 17356 MB in 2.00 seconds ...

You can choose to add a swap-file.
Similar to what windows does.

you create a swap-file, usually in root. But do it on the partition with the most space.
sudo fallocate -l 2G /swapfile

Usually you take 2 times the available ram, 1G ram x 2 = 2G swapfile.

Assign it read/write permissions for ...

This usually means you have the wrong ta.key installed on Server or client.

Check or Make sure the are the same.

Excellent tools are nmap and fping
nmap -sP 192.168.1.1/24

fping -a -r 0 -g 192.168.1.1/24

But if you don't want to install a new tools,
you can try with the default ping.

for i in {1..254}; do (ping -vc 1 -t 4 192.168.1.$i); done

Or, if you want a clearer output, add grep:
for i in {1 ...

It looks like there is problem with the key.

If you can post part of your server/client config
we can verify a little more.