Stream: committers
Topic: gForge down
Lloyd McKenzie (Feb 16 2017 at 14:33):
Apparently our gForge hosting provider's hosting provider needed to do an unplanned host migration. Which has taken 9 hours and counting. HQ is aware and gForge is aware and the hosting provider is being leaned on. I'll let you know as soon as I know anything further. In the meantime, if you're wanting to have a clue what trackers are related to "your stuff", you can query the tracker XML (hosted on Google) here: https://docs.google.com/a/lmckenzie.com/uc?id=0B285oCHDUr09Q2VENW9Ta005QkE
Lloyd McKenzie (Feb 16 2017 at 14:35):
Obviously that won't let you update tracker items, nor does it let you coordinate with anyone else, but at least you can still see what needs to be done with a bit of XML and xPath. If anyone's not sure how to find what they need out of the list, let me know and I'll run a query for you. Host is in Dallas, so they've been awake for a bit, hopefully this won't take too much longer and hopefully we haven't lost any data in the process.
Lloyd McKenzie (Feb 16 2017 at 14:36):
One more reason to migrate off gForge :(
Lloyd McKenzie (Feb 16 2017 at 15:08):
Also, if you need help, I'll respond faster on Skype (lmckenzi)
Lloyd McKenzie (Feb 16 2017 at 15:43):
Current ETA is 1-2 hrs.
Rob Hausam (Feb 16 2017 at 17:37):
it's back up again
Grahame Grieve (Feb 16 2017 at 18:02):
that was a particularly badly timed downtime
Rob Hausam (Feb 16 2017 at 18:04):
yes, it certainly was
Last updated: Apr 12 2022 at 19:14 UTC
