This time I have a different ReadyNAS, slightly newer than my previous ReadyNAS Ultra 2, now I have a ReadyNAS 212 which has a quad core 1.4GHz ARM Cortex A15 processor inside it, running ReadyNAS OS 6.10.6.
Taking onboard the advice mentioned in previous threads, I am attempting to install Syncthing without root priviliges. So after setting up another user, I SSH’d into the ReadyNAS as that user and attempted the install using the instructions on the Debian/Ubuntu Packages page to see if it worked as the ReadyNAS OS is apparently a modified version of Debian.
There was a slight bump in the road as the user ID I used did not have sufficient priviliges to run the Sudo command, this appeared to be overcome by using instructions I found on linuxhint: How to fix debian sudo command not found.
I appeared to get the Server Certificate Verification Failed error. So I ran
sudo apt-get update
sudo apt-get upgrade ca-certificates
as advised but now get an error referencing the nfs-kernel-server. I will continue to attempt to research a solution but if anyone has any immediate insight they can give, that would be much appreciated.
NewUser@NewNas:~$ sudo apt-get update
Hit:1 http://security.debian.org jessie/updates InRelease
Ign:2 http://mirrors.edge.kernel.org/debian jessie InRelease
Ign:3 https://apt.syncthing.net syncthing InRelease
Hit:4 http://mirrors.edge.kernel.org/debian jessie Release
Hit:5 https://apt.readynas.com/packages/readynasos 6.10.6 InRelease
Ign:7 https://apt.syncthing.net syncthing Release
Ign:8 https://apt.syncthing.net syncthing/stable armel Packages
Ign:9 https://apt.syncthing.net syncthing/stable armhf Packages
Ign:10 https://apt.syncthing.net syncthing/stable all Packages
Ign:8 https://apt.syncthing.net syncthing/stable armel Packages
Ign:9 https://apt.syncthing.net syncthing/stable armhf Packages
Ign:10 https://apt.syncthing.net syncthing/stable all Packages
Ign:8 https://apt.syncthing.net syncthing/stable armel Packages
Ign:9 https://apt.syncthing.net syncthing/stable armhf Packages
Ign:10 https://apt.syncthing.net syncthing/stable all Packages
Ign:8 https://apt.syncthing.net syncthing/stable armel Packages
Ign:9 https://apt.syncthing.net syncthing/stable armhf Packages
Ign:10 https://apt.syncthing.net syncthing/stable all Packages
Ign:8 https://apt.syncthing.net syncthing/stable armel Packages
Ign:9 https://apt.syncthing.net syncthing/stable armhf Packages
Ign:10 https://apt.syncthing.net syncthing/stable all Packages
Err:8 https://apt.syncthing.net syncthing/stable armel Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign:9 https://apt.syncthing.net syncthing/stable armhf Packages
Ign:10 https://apt.syncthing.net syncthing/stable all Packages
Reading package lists... Done
W: The repository 'https://apt.syncthing.net syncthing Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://apt.syncthing.net/dists/syncthing/stable/binary-armel/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
NewUser@NewNas:~$ sudo apt-get install syncthing
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package syncthing
NewUser@NewNas:~$ sudo apt-get upgrade ca-certificates
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version (20141019+deb8u4).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up nfs-kernel-server (1:1.2.8-9+deb8u1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
update-rc.d: error: initscript does not exist: /etc/init.d/nfs-kernel-server
dpkg: error processing package nfs-kernel-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
nfs-kernel-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
NewUser@NewNas:~$ sudo dpkg --configure -a
Setting up nfs-kernel-server (1:1.2.8-9+deb8u1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
update-rc.d: error: initscript does not exist: /etc/init.d/nfs-kernel-server
dpkg: error processing package nfs-kernel-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
nfs-kernel-server
Especially for older distributions, your system TLS certificate store might be outdated. Since October 2021, a newer Let’s Encrypt root certificate must be installed
So, from what I can gather I can’t update the certificate beyond 20141019+deb8u4 because the OpenSSL needs to be upgraded on the NAS? I found the following thread on the Let’s Encrypt website: Debian8 impact question
I’m not sure how to go about that.
I’m also not sure if the error with the nfs-kernel-server is related to the above, although I suspect it isn’t and I need to do something else to resolve that.