RN102 problems after upgrade to 6.10

[937carrera]

John, PM sent

[kronos85]

I have the exact same problem. After numerous tests I am sure that the firmware 6.10 has a problem with the second https port configuration

[StephenB]

---

@kronos85 wrote:

I have the exact same problem. After numerous tests I am sure that the firmware 6.10 has a problem with the second https port configuration

---

I got a PM from Netgear confirming that it is a bug.

[Icewaterhot]

We will fix it on 6.10.1.    Thanks!

[937carrera]

Many thanks for the update.

What will be addressed ?

- the second https port,

- the new error referring to GetUnitFileState

- or both

Can you please advise when is 6.10.1 is scheduled to be released

[StephenB]

---

@937carrera wrote:

- the new error referring to GetUnitFileState

---

FWIW, I was told that this error is benign (can be ignored).   Though of course it should be cleaned up.

[JohnCM_S]

Hi @937carrera, @StephenB, @kronos85,

The recently released OS 6.10.1-T32 (Beta 1) has a fix for this issue. You may download it here.

Regards,

[937carrera]

Thanks John,

I have downloaded and upgraded the firmware and the NAS has successfully rebooted.

Until I am at the remote location I cannot confirm that the issue is solved, but I expect to be able to do that over the next couple of days.

I have copied below the log from the reboot, it would appear that the GetUnitFileState error arising from 6.10.0 remains as an issue and continues to fill the logs

-- Reboot --
May 10 17:51:11 Nas-102 readynasd[2478]: readynasd log started
May 10 17:51:15 Nas-102 readynasd[2478]: readynasd started. (restarted=0)
May 10 17:51:45 Nas-102 readynasd[2478]: Failed to call method GetUnitFileState: No such file or directory
May 10 17:51:47 Nas-102 readynasd[2478]: Using fan mode: quiet
May 10 17:51:51 Nas-102 readynasd[2478]: Firmware was upgraded to 6.10.1-T32.
May 10 17:51:51 Nas-102 readynasd[2478]: ReadyNASOS background service started.
May 10 17:53:57 Nas-102 readynasd[2478]: Failed to call method GetUnitFileState: No such file or directory

I will post again when I have changed my router settings to test the forward

[937carrera]

I am happy to report that the Port 2 setting is now working again.