[SiRoB1]

Hi everyone,

just seen this message to movescount facebook page:

Apologies for the short notice, but due to issues in our backend systems, a necessary Movescount maintenance update will be done Tue 3rd June morning (CET time).

Not sure what it means, but this doesn't sounds good.
I may be wrong...

 

[j_winston]

Re: Beware Movescount Maintenance

Most likely related to the slowness / sync issues during last couple of weekends. A couple of new, more efficient servers perhaps to be installed?

 

[SiRoB1]

Re: Beware Movescount Maintenance

Most likely related to the slowness / sync issues during last couple of weekends. A couple of new, more efficient servers perhaps to be installed?

Probably.
It should prevent bad gateway reply due to too much synch request during weekend.
Maybe it's time to put strava service on its own server. :think:

 

[SiRoB1]

Re: Beware Movescount Maintenance

Movescount back to "normal".

 

[morey000]

Re: Beware Movescount Maintenance

This is the first time in 6 months that I was unable to sync with movescount.
Back when i was relying on Garmin Connect... it seemed to be a couple times a week it wouldn't sync.

so- all things considered, Movescount, like their watches, has been exceptionally stable.

 

[SiRoB1]

Re: Beware Movescount Maintenance

This is the first time in 6 months that I was unable to sync with movescount.
Back when i was relying on Garmin Connect... it seemed to be a couple times a week it wouldn't sync.

so- all things considered, Movescount, like their watches, has been exceptionally stable.

Of course, but with a little more explication about issue would be much more acceptable.
Anyway we have a better anticipated warning this time:

19 hours ago
Next scheduled Movescount maintenance updates:
Tue 10th June approx 8am CET
Mon 16th June approx 8am CET.
Expected downtime for the maintenance update is 3-5 hours (could be more, or less)
In addition, during peak hours in weekends, the site may be slower than usual. We appreciate your patience while we build an improved Movescount.

 

[SiRoB1]

Re: Beware Movescount Maintenance

I think we can expect an unexpected maintenance very soon.
While i was able to synchronize my watch this morning, I'm unable to do it right now.

EDIT: after multiple try and an app crash (that i've never seen before), it is ok. Ready to go.
But there is still a major issue around Synchronization process.

 

[kurtie]

Re: Beware Movescount Maintenance

I cannot synchronize settings right now... :-(

Edit: After some errors and tries, I finally was able to upload the move. Its just that is a lot slower than usual.

Regards,
Kurt.-

 

[Sir McKey]

Re: Beware Movescount Maintenance

I have the same problems since the last update :-(

 

[morey000]

Re: Beware Movescount Maintenance

I cannot synchronize settings right now... :-(

Edit: After some errors and tries, I finally was able to upload the move. Its just that is a lot slower than usual.

Regards,
Kurt.-

I had that issue this morning. Read some forum tips. Restarted my mac and it worked. It wasn't slower than usual tho', it just got stuck at synchronizing settings.

 

[kurtie]

Re: Beware Movescount Maintenance

I had that issue this morning. Read some forum tips. Restarted my mac and it worked. It wasn't slower than usual tho', it just got stuck at synchronizing settings.

In my case it also got stuck at synchronizing settings. In the output.log file I can see some:

[18:11:09] [INFO] Arrest: got return code 504 (Gateway time-out)

This is the Moveslink app trying to communicate with the Movescount REST API (https://uiservices.movescount.com/), and the last one failing to answer in a timely manner. Maybe there were too much people uploading moves at that time. But definitely was being much slower than usual in my case. The time it has worked it took like 10 minutes to synchronize settings (it usually was some seconds).

At that time the web was working nicely... so it seems that some parts of the infrastrucutre got upgraded lately, but there are still some parts that cannot keep with the pace of moves uploaded in the rush hours. Hopefully this will be improved shortly.

Regards,
Kurt.-

 

[SiRoB1]

Re: Beware Movescount Maintenance

Interesting, i didn't get any 504 return this time.

So the issue of Synchronization setting is still around.

But movescount is not impacted this time.
So maybe less visible maintenance next time.

 

[kurtie]

Re: Beware Movescount Maintenance

And once again, more 504:

[13:06:49] [INFO] SyncService: Setting device time to 2014-06-22T13:06:49[13:06:50] [INFO] Device firmware version: 2.0.9
[13:06:50] [INFO] SyncService: checking for firmware update
[13:07:49] [ERROR] Arrest: server complained:
[13:07:49] [INFO] Arrest: got return code 504 (Gateway time-out)
[13:07:49] [ERROR] SyncService: failed to contact server
[13:07:50] [INFO] SyncService: syncDevice Suunto Ambit2 R (SerialNo, BluebirdDevice)...
[13:09:03] [INFO] PMemExerciseParser: Number of exercises: 13
[13:16:57] [ERROR] Arrest: server complained:
[13:16:57] [INFO] Arrest: got return code 504 (Gateway time-out)
[13:16:57] [ERROR] MovescountService: Failed to get waypoints from Movescount.
[13:16:57] [ERROR] SyncService: syncWaypoints failed: error code 3

Ok... not a big problem as I can do it during the night when there is less traffic and then it will work... but I hope this issues will be addressed during the next weeks so that I can upload the moves when I want and not when the server allows me to...

Regards,
Kurt.-

 

[SiRoB1]

Yep i'm experiencing the same right now.

Wanted to add some POIs.

If Suunto can't find a solution, we have good hope to see an offline watch manager.

 

[WEM]

Hi all,

my name is Werner an I own a black Ambit 2. In general I'm very happy with my watch.

Since a few days I'm not able to sync the watch with Movescount. Same as reported before in this thread.

As a frequently user of the nav feature this is a serious problem fpr me.

Does it work for you now?

Regards
Werner

 

[kurtie]

Hi all,

my name is Werner an I own a black Ambit 2. In general I'm very happy with my watch.

Since a few days I'm not able to sync the watch with Movescount. Same as reported before in this thread.

As a frequently user of the nav feature this is a serious problem fpr me.

Does it work for you now?

Regards
Werner

Hi Werner,

Right now is not working for me either. Yesterday I was able to upload the move after like a dozen tries and it took 816 seconds to synchronize (thats only the try that worked... with all the other tries I was trying for more than an hour, so the performance of the synchronization process could not be called good... the same saturday), when before it took around 16 seconds.

And yes, I agree that not being able to synchronize is a very serious problem for this watch. I am begin to be concerned about this issues because I am a new user and if this is going to be this way in the future, I am not happy :-(. Let's hope Suunto cares for its users...

Regards,
Kurt.-

 

[WEM]

Also today no sync :-(

It's extremely annoying......

 

[iapyx]

Ah, well, good. I thought it only happened to me. No sync.

 

[morey000]

Also today no sync :-(

It's extremely annoying......

I haven't had an issue the past two days. ???

 

[pjc3]

I haven't had an issue the past two days. ???

Likewise, I have only had one or two problems in the whole period people have been having issues. We have 4 devices and minimum two moves each day getting uploaded. It certainly is hit and miss. I feel for those with the continuing issues .... tracking my exercise is one of my significant motivators (sad I know).