Just trying to access https://eu-west-1.galaxy.meteor.com/ from here gives me an infinite loading error, also, all of my applications are failing to deploy. Perhaps someone from Meteor/Galaxy could take a look quickly?
The control panel now seems to be back up, but all deployments have gone nuts…
I don’t see any issues listed on the Galaxy status page, but there were updates made to the
eu-west-1 region yesterday; might be worth opening a Galaxy support ticket directly.
Yeah I can’t seem to deploy anything. It is having some sort of build issue… can’t find multiple modules. It first couldn’t find object-assign and now it can’t find this:
w99t 2016-10-18 07:46:21-04:00/app/bundle/programs/server/node_modules/fibers/future.js:280 w99t 2016-10-18 07:46:21-04:00 throw(ex); w99t 2016-10-18 07:46:21-04:00 ^ w99t 2016-10-18 07:46:21-04:00 w99t 2016-10-18 07:46:21-04:00Error: Cannot find module 'fbjs/lib/invariant' w99t 2016-10-18 07:46:21-04:00 at Function.Module._resolveFilename (module.js:325:15) w99t 2016-10-18 07:46:21-04:00 at Function.Module._load (module.js:276:25) w99t 2016-10-18 07:46:21-04:00 at Module.require (module.js:353:17) w99t 2016-10-18 07:46:21-04:00 at require (internal/module.js:12:17) w99t 2016-10-18 07:46:21-04:00 at Object.<anonymous> (/app/bundle/programs/server/npm/node_modules/react/lib/PooledClass.js:16:17) w99t 2016-10-18 07:46:21-04:00 at Module._compile (module.js:409:26) w99t 2016-10-18 07:46:21-04:00 at Object.Module._extensions..js (module.js:416:10) w99t 2016-10-18 07:46:21-04:00 at Module.load (module.js:343:32) w99t 2016-10-18 07:46:21-04:00 at Module.Mp.load (/app/bundle/programs/server/npm/node_modules/meteor/babel-compiler/node_modules/reify/node/runtime.js:16:23) w99t 2016-10-18 07:46:21-04:00 at Function.Module._load (module.js:300:12) w99t 2016-10-18 07:46:21-04:00Application exited with code: 1 signal: null w99t 2016-10-18 07:46:21-04:00Application process closed with code: 1 signal: null w99t 2016-10-18 07:46:40-04:00The container has crashed. A new container will be started to replace it. jnk4 2016-10-18 07:47:46-04:00Application process starting, version: 21 on apprunner (embedded)
I’ve opened a ticket, but it’s unusable at present. My advice to those using Galaxy, DON’T DEPLOY.
20 min ago I uploaded the code to galaxy EU without problems
I have one app that deployed fine and another that is acting wacky.
I’m wondering if it is related to this:
“It happened to me when the WIFI went down during an npm install.”
That was not the issue. I still can’t deploy unfortunately. The project runs 100% fine locally though.
Seems okay now, but just be aware I guess.
Well I’m getting extremely weird behaviour in my newly deployed app:
The logs are showing:
mef92016-10-18 14:29:58+01:00Application exited with code: null signal: SIGKILL mef92016-10-18 14:29:58+01:00Application process closed with code: null signal: SIGKILL mef92016-10-18 14:30:04+01:00The container has run out of memory. A new container will be started to replace it.
Yet I’ve never had an issue with this previously.
I’m still having trouble deploying an app as well:
Error: Cannot find module 'fbjs/lib/invariant'
Application exited with code: 1 signal: null Application process closed with code: 1 signal: null The container has crashed. A new container will be started to replace it
But it is running fine locally
Hi, we had resolved an issue that was affecting access to the eu-west Galaxy management interface and was affecting some eu-west app deployments around 3 AM PDT / 10 AM GMT on October 18th (today).
At this point, The eu-west management interface and app deployments should be generally accessible and functional. If there are issues with any specific apps, please file a ticket and we’ll investigate specifically through the ticket.
This looks to be an application issue with specific packages being used in your application, and not related to the eu-west deployment issues.
Please file a support ticket for this application and we can help investigate there.
Rohit is correct that this is a good way to use a support ticket. That said, I took a quick peek at your app. Note that your app is in the US, not the EU, so is unrelated to the issue above.
When you deployed version 19 of your app yesterday, it instantly started crashing on startup. Because Galaxy was never able to successfully launch a v19 container for your app, it kept the v18 container around indefinitely. When we replaced the machines that run containers last night, the v18 container went away too, and since v19 could not start, your app went down.
It’s possible in the future that we may augment the deploy process so that if a newly deployed version fails to start up for a period of time, we automatically roll back the “active” version to the last successful version. In the meantime, it’s important to use the web console to verify that your newly deployed version actually starts properly.
You figure out what was causing the issue? I just upgraded an app to 1.4 and am getting the same error. Works locally but not in production.
Well they were having some deployment issues that now seem to be resolved, other than that, the out-of-memory issue was my own and my fault. Just an unfortunate coincidence that it coincided with a lot of issues their end too,
This topic was about a specific instance of the EU control panel being down. Please ask other questions in a new thread.