My boinc directory has an older one that is not linked to the other ones. At some point, I had downloaded one in my download directory, but wasn't sure what to do with it? Not sure if copying that one into the boinc directory or linking the one in the directory to the other links? Seems the final file is a PEM file??
The contents of the ca-bundle.crt in my boinc directory had some info that the others didn't seem to include, but did the following.
mv ca-bundle.crt ca-bundle.crt.org
ln -s /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ca-bundle.crt That seems to have resolved the issue, since it can no connect, and has downloaded things?
Not sure if I should link to the pem file that seems to be the final file, or the other ca-bundle.crt?
... In the project directory I find ca-bundle.crt from February 15, 2018.
It shouldn't be in the project directory. Perhaps that's just a typo and you really meant BOINC directory??
The latest version I know about is mid-April and virtually all my hosts are using that but I know of around 3 hosts using older versions that are not having problems communicating. I don't think there should be a problem with your Feb version that could be fixed by an April version. I suspect there must be something else. When you say "kicked out", what messages do you see? If for some reason, your file is in the project dir, stick it in the BOINC dir and try again :-).
Indeed, I chose the wrong word, I meant BOINC directory. Anyway, the only message I get is:
' Notice from BOINC
BOINC can't access Internet - check network connection or proxy configuration '
However, I obviously have access to the web account. There, the hardware reported for that machine is wrong, obviously because Boinc can't connect to my Boinc manager. I tried project reset, uninstall/install Boinc.
May well be a problem unrelated to the certificate problem, but I'm currently out of ideas for a solution.
/ EDIT / Quick follow up: Got the system up and running now. Followed the usual path: reinstall, reset, reboot, plus new display driver. Something or a combination of that must have worked. :-)
Not sure if I should link to the pem file that seems to be the final file, or the other ca-bundle.crt
If things are working correctly now, just leave it alone :-).
From the data in your previous message, the problem was fairly certainly caused by the very old copy of the file in the BOINC directory (Mar 5 2010). The one in your Downloads directory is the current one (I believe) since it has exactly the same size as my current one. Your simplest solution would have been to delete the old Mar 5 copy and move the one in your Downloads directory into the BOINC directory and leave all the system files alone. My understanding is that BOINC would only rely on a system file if it can't use its own file.
If you were sufficiently curious, you could prove that quite easily :-).
The contents of the ca-bundle.crt in my boinc directory had some info that the others didn't seem to include, but did the following.
mv ca-bundle.crt ca-bundle.crt.org
ln -s /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ca-bundle.crt
That seems to have resolved the issue, since it can no connect, and has downloaded things?
Not sure if I should link to the pem file that seems to be the final file, or the other ca-bundle.crt?
I'll second Gary and say if things work, you shouldn't try to 'fix' them.
That being said, you did exactly what I would have suggested: link the 'system' bundle of certificates (tls-ca-bundle.pem) to your BOINC directory, naming it 'ca-bundle.crt'. The extensions 'crt' 'pem', etc don't have any real meaning in Linux. All these files contain the same thing, a series of root certificates that client software (in this case BOINC) uses to validate the Web certificate we (E@H) present to you. It's better to use the system bundle of certificates as it gets updated periodically. The BOINC bundle does not get updated as often. I'm glad we were able to diagnose and fix your problem too. Thanks for all the number-crunching!
Indeed, I chose the wrong word, I meant BOINC directory. Anyway, the only message I get is:
' Notice from BOINC
BOINC can't access Internet - check network connection or proxy configuration '
However, I obviously have access to the web account. There, the hardware reported for that machine is wrong, obviously because Boinc can't connect to my Boinc manager. I tried project reset, uninstall/install Boinc.
May well be a problem unrelated to the certificate problem, but I'm currently out of ideas for a solution.
/ EDIT / Quick follow up: Got the system up and running now. Followed the usual path: reinstall, reset, reboot, plus new display driver. Something or a combination of that must have worked. :-)
I'm glad you got things working again. For future reference, if you see an error that says BOINC can't access the internet, do try to add 'http_debug' to the client config. See my comment below:
It will help diagnose what problem BOINC is having connecting to the project: e.g., a web certificate problem, proxy error, etc.
Did a search thru whole
)
Did a search thru whole system for ca-bundle.crt
My boinc directory has an older one that is not linked to the other ones. At some point, I had downloaded one in my download directory, but wasn't sure what to do with it? Not sure if copying that one into the boinc directory or linking the one in the directory to the other links? Seems the final file is a PEM file??
find . | grep ca-bundle.crt
./usr/share/apps/kssl/ca-bundle.crt
lrwxrwxrwx. 1 root root 32 Dec 29 12:22 /usr/share/apps/kssl/ca-bundle.crt -> /etc/pki/tls/certs/ca-bundle.crt
./usr/share/kf5/kssl/ca-bundle.crt
lrwxrwxrwx. 1 root root 32 May 7 15:46 ./usr/share/kf5/kssl/ca-bundle.crt -> /etc/pki/tls/certs/ca-bundle.crt
./usr/share/kde4/apps/kssl/ca-bundle.crt
lrwxrwxrwx. 1 root root 32 Oct 1 2017 ./usr/share/kde4/apps/kssl/ca-bundle.crt -> /etc/pki/tls/certs/ca-bundle.crt
./usr/share/gwenhywfar/ca-bundle.crt
lrwxrwxrwx. 1 root root 32 Mar 31 06:44 ./usr/share/gwenhywfar/ca-bundle.crt -> /etc/pki/tls/certs/ca-bundle.crt
./home/msetzerii/BOINC/ca-bundle.crt
-rw-r--r--. 1 msetzerii msetzerii 238100 Mar 5 2010 ./home/msetzerii/BOINC/ca-bundle.crt
./home/msetzerii/Downloads/ca-bundle.crt
-rw-rw-r--. 1 msetzerii msetzerii 224409 May 9 22:14 ./home/msetzerii/Downloads/ca-bundle.crt
./etc/pki/tls/certs/ca-bundle.crt.rpmsave
-rw-r--r--. 1 root root 757128 Dec 18 2013 ./etc/pki/tls/certs/ca-bundle.crt.rpmsave
./etc/pki/tls/certs/ca-bundle.crt
lrwxrwxrwx. 1 root root 49 Feb 6 23:48 ./etc/pki/tls/certs/ca-bundle.crt -> /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
ls -l /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
-r--r--r--. 1 root root 211658 May 9 22:33 /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
The contents of the
)
The contents of the ca-bundle.crt in my boinc directory had some info that the others didn't seem to include, but did the following.
mv ca-bundle.crt ca-bundle.crt.org
ln -s /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ca-bundle.crt
That seems to have resolved the issue, since it can no connect, and has downloaded things?
Not sure if I should link to the pem file that seems to be the final file, or the other ca-bundle.crt?
Gary Roberts schrieb:solling2
)
Indeed, I chose the wrong word, I meant BOINC directory. Anyway, the only message I get is:
' Notice from BOINC BOINC can't access Internet - check network connection or proxy configuration '
However, I obviously have access to the web account. There, the hardware reported for that machine is wrong, obviously because Boinc can't connect to my Boinc manager. I tried project reset, uninstall/install Boinc.
May well be a problem unrelated to the certificate problem, but I'm currently out of ideas for a solution.
/ EDIT / Quick follow up: Got the system up and running now. Followed the usual path: reinstall, reset, reboot, plus new display driver. Something or a combination of that must have worked. :-)
msetzerii wrote:Not sure if I
)
If things are working correctly now, just leave it alone :-).
From the data in your previous message, the problem was fairly certainly caused by the very old copy of the file in the BOINC directory (Mar 5 2010). The one in your Downloads directory is the current one (I believe) since it has exactly the same size as my current one. Your simplest solution would have been to delete the old Mar 5 copy and move the one in your Downloads directory into the BOINC directory and leave all the system files alone. My understanding is that BOINC would only rely on a system file if it can't use its own file.
If you were sufficiently curious, you could prove that quite easily :-).
Cheers,
Gary.
msetzerii wrote:The contents
)
I'll second Gary and say if things work, you shouldn't try to 'fix' them.
That being said, you did exactly what I would have suggested: link the 'system' bundle of certificates (tls-ca-bundle.pem) to your BOINC directory, naming it 'ca-bundle.crt'. The extensions 'crt' 'pem', etc don't have any real meaning in Linux. All these files contain the same thing, a series of root certificates that client software (in this case BOINC) uses to validate the Web certificate we (E@H) present to you. It's better to use the system bundle of certificates as it gets updated periodically. The BOINC bundle does not get updated as often. I'm glad we were able to diagnose and fix your problem too. Thanks for all the number-crunching!
Einstein@Home Project
solling2 wrote:Indeed, I
)
I'm glad you got things working again. For future reference, if you see an error that says BOINC can't access the internet, do try to add 'http_debug' to the client config. See my comment below:
It will help diagnose what problem BOINC is having connecting to the project: e.g., a web certificate problem, proxy error, etc.
Einstein@Home Project
Sorry, I know I'm in the
)
Sorry, I know I'm in the wrong place but:
Not sure where else to go.
I'm trying to make Einstein@home my fourth project. As I go thru the normal steps everything seems to work fine.
However, at the last step after he indicates "finished" I get msg "Page not Found."
Any ideas?
Thx,
Bluelazer1