Date / Time: 06-04-2014 10:30 AM - 2:30 PM [UTC]
Services affected: TeamForge services.
Description: We are performing a maintenance on our TeamForge servers, hence the TeamForge services will be affected for some customers.
[NOTE] Some TeamForge customers may experience inaccessibility of TeamForge during this period of time while the maintenance is going on.
Update: Maintenance is completed. Please feel free to file a support ticket if you still have any further issues in accessing services.
Hi Guys,
This seems to be affecting subversion also: svn: E175002: Server sent unexpected return value (500 Internal Server Error) etc...
Same here - SVN error.
For the second week running our essential services are down during the work-day ... 'for maintenance'.
You could do maintenance at a weekend or, preferably, maintenance with no downtime. Hot-hot HA. You should be able to change the engine while the plane is in the air.
Hi All,
We apologize for the inconvenience caused due to this maintenance. SVN service will be partially effected (only commits) if you have a check mark enabled under project-->edit-->enable ticket integration. Please go ahead and disable this temporarily to be able to continue with your commits until the maintenance is completed. Going forward, we will include the partial effect of TeamForge maintenance on SVN service in our status posts. Thank you for your patience.
Ashok.
James, you are so true... it is a bit of a pain to have these updates during our working hours.
@Cloudforge - Is the SVN issue reported above related to the TeamForge Maintenance or is it really unrelated, unplanned downtime? If the former, why wasn't this communicated as part of the TeamForge maintenance posting? If the later, are you aware of the SVN problem or should I "Submit a Request"?
I can read from SVN (i.e. svn update) but I cannot write to SVN (i.e. svn commit):
svn: Commit failed (details follow):
svn: Commit blocked by pre-commit hook (exit code 255) with output:
503 Service Temporarily Unavailable (ref svn10a:uI89DnttkjTalVAT)
I understand the need for occasional downtime, but I agree with the comments above that 6:30AM to 10:30AM EDT is not an ideal time. Further, this is not the first time downtime for one service has caused unintended/unexpressed side effects on other services. That is far more worrying than the downtime because it demonstrates a lack of understanding of your own services and their dependencies.
Version control is a mission-critical service, and to be honest so is the corresponding 'ticket integration'. I would expect planned maintenance like this to be performed after business hours. And the fact that it was planned but not advertised is pretty unbelievable.
7 Comments