System Temporarily Unavailable after 3 days of new beta

[devriendtm 0]

Hello,

I'm using with great satisfaction for 3 days the new beta

This afternoon, all of a sudden my system did not respond anymore when pussing on a device.

Refreshing the page gave me a: "system temporarily unavailabe" warning.

waiting did not help.

I did a recovery,

everyting till 1.44 works, but therafter going back to the beta version results back again in the same "system temorarily unavailable".

i tried to recover 3 times.

please help fibaro peops,

greetings,

Miguel

[Guest deraaij]

Hi I had it once but a hard reboot (without restoring) helped.

I would also e-mail to: [email protected] if I were you.

Regards,

Mark

[devriendtm 0]

Hi I had it once but a hard reboot (without restoring) helped.

I would also e-mail to: [email protected] if I were you.

Regards,

Mark

I mailed fibaro,

how do you do a hard reboot?

[Guest deraaij]

Well I just unplugged the power....

[devriendtm 0]

Well I just unplugged the power....

mjah, did that 3 times

Please login or register to see this image.

/emoticons/default_wink.png" alt=";)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[Guest deraaij]

You don't use backups from before the new architecture (beta)?

[devriendtm 0]

nope

if i upgrade, i immediately now get the warning now

[byackee 0]

I have same message: "System temporarily unavailable" fore mor than 3 days after update 3.341. What is the solution?

Thank you

[Guest deraaij]

I have same message: "System temporarily unavailable" fore mor than 3 days after update 3.341. What is the solution?

Thank you

You already cut the power? (hard reboot) For me that worked...

[robmac 173]

Thought I would test the beta. All appeared to be working but yesterday started to notice a few odd behaviours:

I now have same issue as others as of today.

Actions before:

1) was creating new scenes

2) checked i-Pad interface first time since beta upgrade

then things started to fail

3) did a backup but while it showed progress it did not appear on the list of backups

4) scenes that I thought were working did not appear to be working (not for sure)

so

5) restarted from config screen

now get redirect to

Please login or register to see this link.

even after hard reset.

BUT can ping unit and it responds. +

I have homeseer as a secondary controller. When I rescan the Home Center Z-Wave device it responds. I think the z-wave is therefore loaded.

Anyone had any response from support? I am guessing a full log file of some sort.

[byackee 0]

I have same message: "System temporarily unavailable" fore mor than 3 days after update 3.341. What is the solution?

Thank you

You already cut the power? (hard reboot) For me that worked...

Thank you, it's work for me.

[Guest deraaij]

Thank you, it's work for me.

I am glad it worrekd!

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

[byackee 0]

Thank you, it's work for me.

I am glad it worrekd!

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

Arfff, another message " System Temporaly Unavailable" after hard reboot. Work few hours and after i get this message.

I need update ...

Bye

[robmac 173]

Arfff, another message " System Temporaly Unavailable" after hard reboot. Work few hours and after i get this message.

Might have the same here. Can navigate to login by entering url but password does not work.

Even if I recover and reinstall it is no good as the unit does not appear to load fully at boot after re-install of Beta. No lights on front of unit.

Is this the same on your unit?

I am running on 1.044 again which is sad as the Beta was working very well with my system.

Warning to others: It is possible to make the beta non functioning with no way to tidy up.

The last changes I made before the issue:

1) adding some custom icons

2) backing up.

Not sure if this was what failed but the backups never showed in the list and the system became unresponsive. I restarted and have not managed to get the beta running since.

Still a very happy customer but keen to get back testing some scripts etc.

I am also waiting from some help from support or a new version to try that cleans up what has gone wrong.

[nmnetmedia 0]

I had exact the same problem, could not login in new beta.

Use recovery mode to restore 1.044 and wait....

I tried like 7 times and at a certain point even recovery mode wasn't working anymore. (z-wave network was down on my 1.044, restore backup didn't helped) Fibaro Engineer needed to fix my box remotely

Had also custom icons, so possible that may have caused the problem.

[A.Socha 133]

byackee, after restart HC2 was still problem with "System Temporally Unavailable"? what you got on? any scenes that could crash web services?

[devriendtm 0]

byackee, after restart HC2 was still problem with "System Temporally Unavailable"? what you got on? any scenes that could crash web services?

A.Socha,

as told to kristian, you may take over my system , upgrade back to beta 3 and you will see that i immediately get the messege now.

I ran the first beta without problems, upgraded to the current version without any problem.

After 3 days the system crashed, and after the cold reboot, the message appeared

after 4 recovery's i gave up ...

and the "stable" 1.44 is giving me probs to, (devices that are not responding , dead nodes , ...)

[robmac 173]

and the "stable" 1.44 is giving me probs to, (devices that are not responding , dead nodes , ...)

Possibly the same here with dead nodes post recovery and upgrade back to 1.044. Very odd situation...

All nodes worked well in Beta but now in a 1.044 recovery post Beta something is not working.

If I look at them via my secondary controller, z-wav is talking so I am not sure where the issue is? Is it possible that z-wave on HC2 is not restored back?

Robert

Please login or register to see this attachment.

Please login or register to see this attachment.

[robmac 173]

Routing???

Now I look at this again there is definitely an issue here with HC2. It is reporting direct links to nodes that it can not possibly communicate directly with. The nodes are just too far away.

From the test times it is clearly not. You can see this from the time to send and receive 10 packets some of my nodes are definitely routed via others as they should be.

Is HC2 trying to use these spurious direct connections it reports and therefore failing?

Why is it not automatic to mend these bad routes?

Is there a way to force HC2 to rebuild all routing and remove these spurious direct links? I think that the HC2 is not updating its routing table properly post the recovery.

[robmac 173]

Update: Back on Beta and working. The fix was posted by jin against the Beta and involved moving the old backup files.