June 27, 20206 yr Hi there, I have a 16 disk server, after last reboot it now writes Cannot contact key-server. Please check your network settings. and can't start array. I use - static IP address - static DNS server, all pingable in the terminal. - USB stick with license is good, is shown and mounted and shows license green (have the big license) - date is shown correctly on the terminal, so mainboard battery seems to be good Rebooted already for the 5th time, still the same. Any hints as to what ese I might check? Thanks much, highly appreciated. Edited June 27, 20206 yr by starcat
June 27, 20206 yr Author #ping www.google.com #ping www.unraid.com in the terminal work as well, so DNS resolution shouldn't be a problem. But I still can't start the array and get Cannot contact key-server. Please check your network settings. Edited June 27, 20206 yr by starcat
June 27, 20206 yr Is this a trial key that you're using? Paid keys do attempt to contact the key server. I'd post your diagnostics.
June 27, 20206 yr Author No, real key, probably 10 years old. in /var/log/syslog I see Pro key detected, GUID: .... /boot/config/Pro1.key is readable as well. Edited June 27, 20206 yr by starcat
June 27, 20206 yr Author I am using 6.2.0-rc3 DNS works, network also. pinging www.google.com and others return results. Edited June 27, 20206 yr by starcat
June 27, 20206 yr Author I am not allowed to post them. Anything I should look for? I scrolled through all files and don't find anything of interest. Server worked before reboot just fine for long time. This is from /var/log/syslog Jun 27 15:30:45 name emhttp: get_limetech_time: _time: -2 (60) 0 Jun 27 15:30:45 name emhttp: Pro key detected, GUID: 0..8 FILE: /boot/config/Pro1.key Should I worry about the get_limetech_time output? What is the server Ip to try to ping it? Edited June 27, 20206 yr by starcat
June 27, 20206 yr 16 minutes ago, starcat said: I am not allowed to post them. Why 27 minutes ago, starcat said: I am using 6.2.0-rc3 6.2.0-rc series did require internet access in order to validate the key (this was in case LT wanted to pull a release). Beyond that, 6.2 is beyond ancient, and borderline stone-age. I honestly have no idea if the key server still is the same address or not. No idea what to look for, and no suggestions other than take a backup of the flash and update to 6.8.3
June 27, 20206 yr Author 24 minutes ago, Squid said: Why 6.2.0-rc series did require internet access in order to validate the key (this was in case LT wanted to pull a release). Beyond that, 6.2 is beyond ancient, and borderline stone-age. I honestly have no idea if the key server still is the same address or not. No idea what to look for, and no suggestions other than take a backup of the flash and update to 6.8.3 All this is fine but the server worked just fine, and was rebooted couple of time during last months, all without issues. Now, after a reboot because I am adding a new drive and array doesn't start. What went wrong in between with the Key Server?? There is obviously not a network issue on my end. Edited June 27, 20206 yr by starcat
June 27, 20206 yr Author Regarding 6.8.3 upgrade, do I still copy bz* to the flash stick and reboot? Edited June 27, 20206 yr by starcat
June 27, 20206 yr 4 minutes ago, starcat said: Regarding 6.8.3 upgrade, do I still copy bz* to the flash stick and reboot? yes
June 27, 20206 yr Author What is the bzfirmware file doing? I won't bother with the EFI folder as I don't have EFI, right?
June 27, 20206 yr Then from the terminal, diagnostics and post the entire resulting zip file here (will be stored in /logs on the flash drive)
June 27, 20206 yr Author Works now. Interesting why the old 6.2.0-rc3 server could not contact the key server? Is there anything that I should look into after the upgrade to 6.8.3? Thanks again very much!
Archived
This topic is now archived and is closed to further replies.