ReadyNAS Update Process Logs

[steveoelliott]

Hi all,

I saw the following in my logs upon reloading my device today... I upgraded to 6.8.1 successfully but curious as to what the below means.

Oct 12 19:11:45 DESPAIR systemd[1]: Starting ReadyNAS Update...
Oct 12 19:11:48 DESPAIR rn-update.sh[7333]: E: Unable to correct problems, you have held broken packages.
Oct 12 19:11:48 DESPAIR systemd[1]: rn-update.service: Main process exited, code=exited, status=100/n/a
Oct 12 19:11:48 DESPAIR systemd[1]: Failed to start ReadyNAS Update.
Oct 12 19:11:48 DESPAIR systemd[1]: rn-update.service: Unit entered failed state.
Oct 12 19:11:48 DESPAIR systemd[1]: rn-update.service: Failed with result 'exit-code'.

Thanks...

[mdgm-ntgr · Accepted solution]

There is a check done after every reboot (could take about 15 minutes after the reboot before hot-fix installation is complete) and weekly after that for available hot-fixes.

For some reason your system is having trouble with this check. If it still doesn't work for you on 6.9.0 it would be worth investigating this further.

[Retired_Member]

Hello steveoelliott

can you check if your network setting in NAS is correct?please make sure DNS and gateway is configured correctly then check the log again to confirm if it can fix update issue. 

[steveoelliott]

Hi,

Thanks for your response....

Just to clarify, there are no issues per se with the device other than I noticed those messages within the logs. Also I can confirm that DNS resolution works and the GW / DNS settings are correct.

Thanks...

[mdgm-ntgr]

Does your packages.log show that some packages are not installed properly? It sounds like the update service is not working because of that.

[steveoelliott]

Not that I can see... I can provide the packages.log to you if you would like to take a look?

[mdgm-ntgr]

Packages that are installed properly would show ii next to them.

[steveoelliott]

All packages within packages.log have "ii" next to them.

[steveoelliott]

Still seeing the following in my logs... No idea as to what is happening here.

Oct 26 19:13:11 DESPAIR systemd[1]: Starting ReadyNAS Update...
Oct 26 19:13:11 DESPAIR systemd[1]: Starting Debian Package List Updater...
Oct 26 19:13:14 DESPAIR rn-update.sh[14776]: E: Unable to correct problems, you have held broken packages.
Oct 26 19:13:14 DESPAIR systemd[1]: rn-update.service: Main process exited, code=exited, status=100/n/a
Oct 26 19:13:14 DESPAIR systemd[1]: Failed to start ReadyNAS Update.
Oct 26 19:13:14 DESPAIR systemd[1]: rn-update.service: Unit entered failed state.
Oct 26 19:13:14 DESPAIR systemd[1]: rn-update.service: Failed with result 'exit-code'.
Oct 26 19:13:16 DESPAIR apt-update.sh[15013]: Get:1 http://egnyte-cdn.egnyte.com/storagesync/netgear6/en-us 6.8 InRelease [3,170 B]
Oct 26 19:13:16 DESPAIR apt-update.sh[15013]: Hit:2 http://security.debian.org jessie/updates InRelease
Oct 26 19:13:17 DESPAIR apt-update.sh[15013]: Ign:3 http://mirrors.kernel.org/debian jessie InRelease
Oct 26 19:13:17 DESPAIR apt-update.sh[15013]: Hit:4 http://apt.readynas.com/packages/readynasos 6.8.1 InRelease
Oct 26 19:13:17 DESPAIR apt-update.sh[15013]: Hit:5 http://mirrors.kernel.org/debian jessie Release
Oct 26 19:13:17 DESPAIR apt-update.sh[15013]: Fetched 3,170 B in 1s (1,778 B/s)
Oct 26 19:13:18 DESPAIR apt-update.sh[15013]: Reading package lists...
Oct 26 19:13:18 DESPAIR apt-update.sh[15013]: Reading package lists...
Oct 26 19:13:18 DESPAIR apt-update.sh[15013]: Building dependency tree...
Oct 26 19:13:18 DESPAIR apt-update.sh[15013]: Reading state information...
Oct 26 19:13:18 DESPAIR apt-update.sh[15013]: 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Oct 26 19:13:18 DESPAIR systemd[1]: Started Debian Package List Updater.

All packages in packages.log have "ii" next to them.

[steveoelliott]

To further add... The next day 27th, logs seemed clean but you'll notice it isn't the same as 26th where we see "Starting ReadyNAS Update". This seems to happen once a week.

Oct 27 19:13:21 DESPAIR systemd[1]: Starting Debian Package List Updater...
Oct 27 19:13:22 DESPAIR apt-update.sh[2889]: Get:1 http://egnyte-cdn.egnyte.com/storagesync/netgear6/en-us 6.8 InRelease [3,170 B]
Oct 27 19:13:22 DESPAIR apt-update.sh[2889]: Get:2 http://security.debian.org jessie/updates InRelease [63.1 kB]
Oct 27 19:13:23 DESPAIR apt-update.sh[2889]: Hit:3 http://apt.readynas.com/packages/readynasos 6.8.1 InRelease
Oct 27 19:13:23 DESPAIR apt-update.sh[2889]: Ign:4 http://mirrors.kernel.org/debian jessie InRelease
Oct 27 19:13:23 DESPAIR apt-update.sh[2889]: Hit:5 http://mirrors.kernel.org/debian jessie Release
Oct 27 19:13:23 DESPAIR apt-update.sh[2889]: Fetched 66.2 kB in 2s (32.8 kB/s)
Oct 27 19:13:24 DESPAIR apt-update.sh[2889]: Reading package lists...
Oct 27 19:13:24 DESPAIR apt-update.sh[2889]: Reading package lists...
Oct 27 19:13:24 DESPAIR apt-update.sh[2889]: Building dependency tree...
Oct 27 19:13:24 DESPAIR apt-update.sh[2889]: Reading state information...
Oct 27 19:13:24 DESPAIR apt-update.sh[2889]: 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Oct 27 19:13:24 DESPAIR systemd[1]: Started Debian Package List Updater.

[mdgm-ntgr]

Do you still have issues with this if you update to 6.9.0?

[Kimera]

Steveoelliott wrote: ...This seems to happen once a week.

Nothing that can be related to ReadyNAS OS autonomous weekly check for possible Hot-Fix(es)? hope not to be wrong with this suggestion.

[mdgm-ntgr · Accepted solution]

There is a check done after every reboot (could take about 15 minutes after the reboot before hot-fix installation is complete) and weekly after that for available hot-fixes.

For some reason your system is having trouble with this check. If it still doesn't work for you on 6.9.0 it would be worth investigating this further.

[steveoelliott]

Hi MDGM / all,

I saw this error right after upgrading to 6.8.1 and it has continued every week thereafter. I can try the upgrade to 6.9.0 in the next week or so but I was a little concerned that it may create further problems if there was already an issue with the device running an update etc.

Should the software update to 6.9.0 work irrespective of the ReadyNAS update status? 

How would this potentially resolve the issue? Presumably many folks are still running with 6.8.1 without issues with the weekly ReadyNAS update. I will provide you with the logs I downloaded yesterday in case they give you any clue.

Really appreciate your help.

Thanks... 

[steveoelliott]

MDGM / all - I just wanted to follow up with on this...

[steveoelliott]

Following upgrade to 6.9.0. The update has ran without error.

No idea what the issue was but it is resolved now. Something must have got screwed up with the previous upgrade.

[mdgm-ntgr]

Glad updating to 6.9.0 resolved it.