Meteor Site Offline

deployment
1

Hi all,

I have two meteor sites hosted and I can’t access them - getting the “This site is loading” page, and I’ve been getting it for the past hour. I just tried redeploying my application to a new URL, only o get the following error, printed in my console:

Deploying to myCustomUrl.meteor.com.

Error deploying application: <!DOCTYPE html>
<html>
<head>
<title>Error</title>
<style type="text/css">
body {
font-family: 'Helvetica Neue', Helvetica, Arial, san-serif;
padding: 0;
margin: 0;
text-align: center;
}
.meteor {
padding-top: 200px;
padding-bottom: 20px;
height: 142px;
}
.message {
padding-top: 50px;
font-size: 3em;
color: #777;
letter-spacing: -1px;
font-weight: bold;
}

.submessage {
padding-top: 20px;
font-size: 1.5em;
color: #777;
letter-spacing: -1px;
font-weight: bold;
}

.counter {
padding-top: 30px;
font-size: 1em;
color: #aaa;
letter-spacing: -1px;
}

</style>
</head>
<body>
<div class="meteor"><img
src="//warehouse.meteor.com/mother-assets/meteor-logo-final.png"/></div>
<div class="message">
This site is down.
</div>
<div class="submessage">
Try again later.
</div>
<div id="counter" class="counter">
</div>


<script type="text/javascript">
var refreshTime = 0 ;
if (refreshTime) {
var counterDiv = document.getElementById("counter");
var countdown = function () {
if (refreshTime < 1) {
counterDiv.innerHTML =
"Retrying...";
location.reload(true);
} else {
counterDiv.innerHTML =
"Retrying in " + refreshTime + " seconds...";
refreshTime = refreshTime - 1;
setTimeout(countdown, 1000);
}
}
countdown();
}
</script>

</body>
</html>

Has anyone else been experiencing downtime today? I live in the eastern United States, if that would help when resolving where downage may exist.

Thanks!

1 Like
2

Yes. It was down for me yesterday, then up, now down today for at least 8 hours.

3

I’m having similar downtime issues, and checked the logs (using meteor logs <appname>.meteor.com)
Apparently the account-base packages is causing issues on server boot.
Looks like a MongoDB error (Error: No primary found in set)

I hoped to resolve the issue by deleting and redeploying my app,but i got similar output.
I also tried deploying my app to a new subdomain, which is indeed still not working.

It reminds me of issues I had last week.
Looks like deployment to Meteor servers is pretty unstable in the last couple of weeks.

I know it’s free to use, but it’s costing me a lot of valuable time to finally figure out that there’s an outage on the Meteor infrastructure. A kind of status page or @meteorstatus twitter account would help a lot

2 Likes
4

You could use a free-tier monitoring service. https://www.pingdom.com/ has always been valuable to me.

5

Experiencing the same issue as @robvangroenewoud’s describing.

6

Yep, down for me aswell. Maybe it’s time to try out Heroku.

7

Same here… Hope it is fixed soon!

8

@mjkaufer I live in the eastern US and have been experiencing the same issue for just under 24 hours: The “Meteor This site is loading.” splash is the only thing rendering.

Check your logs:
meteor logs site.meteor.com

Mine suggest a Mongo issue on Meteor’s end.

The app runs fine on my local machine.

9

I seem to be having the same issue with http://latest.is - and I can’t get any logs. If I get any response I just get an html file back, no real logs.

10

@gori do you get a response from meteor mongo site.meteor.com ?

11

No, no response. Just like with meteor logs.

12

I’m having these same problems here in Portugal with ceres.meteor.com. Is there any word on when this will be fixed?

Thanks!

13

When I do meteor mongo I get a html response, just as when I do a meteor logs. However, the site is back up but it seems to be having issues writing to the database.

This is what meteor mongo returns:
Couldn’t open a mongo connection:
… and then an error html page in the terminal …

This is what meteor logs returns:
Couldn’t view logs:
… and then an error html page in the terminal …

14

Yay. My database just woke up after 23h.

I can’t write a new reply because I’m a new user, so I’ll edit my reply in here @ekate

The instability wasn’t just last night, it was for 23h for me, and it seems I got an old database in the end.

I understand that issues like this happen - and for me this isn’t a big deal - but please just acknowledge them, post a (short!) tweet saying that there are some issues or at least answer our tweets about them? Please?

15

Hi everyone!

Thank you for your patience!

We’re sorry for the instability last night. We’ve been dealing with some intermittent mongo issues affecting some of the apps.

We believe we resolved this specific instance earlier this morning, but are still working to stabilize our clusters in the long run. Hopefully the impact will be more limited.

Thanks!

3 Likes
16

Nice that it’s back up again, although looks like database has been rolled back to a few days ago. Lost all users and info that was added over the last 2 days. :frowning:

17

My Mongo database is down again. I know you guys are providing a free service but it would still be nice to have some visibility on downtime, any thoughts on that?

I worry that when these hosted apps go down, it creates a perception that Meteor is unreliable / flaky when that’s not the case.

18

My application, which until today usually comes back from sleeping in about 5s, is taking about 30s to wake up. And then when it is up, it runs really, really slowly. It looks like it’s due to very slow mongodb response. ‘meteor log appname.meteor.com’ gives me no error messages. So it doesn’t seem like problems have been resolved yet.

1 Like
19

We’re back in August 2013! This is the output for meteor logs q42.nl:

[Mon May 11 2015 22:32:29 GMT+0000 (UTC)] WARNING Error: No replica set primary available for query with
ReadPreference PRIMARY
at Object.Future.wait (/meteor/dev_bundles/0.4.18/lib/node_modules/fibers/future.js:395:16)
at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:733:1)
at [object Object].Mongo.Collection._ensureIndex (packages/mongo/collection.js:620:1)
at Accounts.urls (packages/accounts-base/accounts_server.js:1309:1)
at /meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/packages/accounts-base.js:1616:4
at /meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/packages/accounts-base.js:1659:3
at /meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/boot.js:222:10
at Array.forEach (native)
at Function._.each._.forEach (/meteor/dev_bundles/0.4.18/lib/node_modules/underscore/underscore.js:79:11)
at /meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/boot.js:117:5
- - - - -
at [object Object].ReplSet.checkoutReader
(/meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/repl_set.js:613:14)
at Cursor.nextObject
(/meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:748:48)
at Cursor.toArray
(/meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:169:10)
at Db.indexInformation
(/meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1629:39)
at Db.ensureIndex
(/meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1496:8)
at Collection.ensureIndex
(/meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/collection/index.js:68:11)
at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:732:1)
at [object Object].Mongo.Collection._ensureIndex (packages/mongo/collection.js:620:1)
at Accounts.urls (packages/accounts-base/accounts_server.js:1309:1)
at /meteor/containers/a1a06f69-4906-ecf7-daab-d00b99daa57a/bundle/programs/server/packages/accounts-base.js:1616:4
[Mon May 11 2015 22:32:29 GMT+0000 (UTC)] ERROR Application crashed with code: 8
20

I am facing the same issue since yesterday. When is it expected to be to be solved?