Atmosphere/Meteorite Down?

[aldeed]

Maybe it's something temporary or unique to me, but mrt update command (latest release) is hanging indefinitely and the atmosphere site is not showing any packages at the moment.

[aldeed]

mrt update works fine for "path" or "git" packages. It hangs on the first atmosphere package it comes to, which points to an atmosphere issue, I guess.

[aldeed]

Looks to be fixed now.

[paralin]

There are some issues with *.meteor.com I believe right now. As another person said, the DDP socket is not responding.

Even though this is not Metoer's or Oortcloud's fault I still believe we should keep this open as a lot of people depend on mrt for packages.

[Tarang]

K cool. Atmosphere is back up. The issue is with mongohqs servers which power .meteor.com servers (I think). Looking at the errors the primary in the replica set is down.

It looks to be back up but its acting up alot this week.

[aldeed]

As an update, currently mrt release and mrt publish aren't working for me. First time I got an "internal server error" message. Subsequent tries with publish yield a "Error: That's not a new version of the package!" message. But the new version isn't displayed on atmosphere. I'm guessing this is related to the general issues @kidovate mentioned.

[Tarang]

It appears you're right. Its down.

I thought we fixed this all right now but its something else. There was an update pushed out yesterday to update it to 0.7.0.1 to fix the bad mongo driver which was thought to be the issue.

I know the error has something to do with not being able to connect to the primary mongodb replica.

Update: back up!

[Tarang]

@aldeed Could you come on IRC? I'd like to catch the error on the logs at the same time you try and publish it

[Tarang]

@aldeed ok its fixed looks like the irc package didn't make its way to the packages file. We publish the number of packages and updates onto IRC and this is where it went wrong.

There was a lot of updates put up yesterday to bring it up to date so this one got missed.

But it should all be fixed now for good hopefully! I think i'll close this one now and if it pops back we'll open it.

In Summary the problem with the downtime was probably due to an older bad mongodb driver. Before yesterday atmosphere was running on Meteor 0.6.6.3

[aldeed]

@Tarangp, sorry, was in a meeting. I was able to release a different package fine, but the package I originally had troubles with (autoform) is still saying "Error: That's not a new version of the package!". Tried a new tag with no luck. Maybe it's caught in limbo due to encountering the original server error? Can I reset it or fool it somehow?

[Tarang]

Whats the version you're trying to push? I can see 0.4.8 as the latest one in the repo.

Try deleting the tags, I can see them in your repo (on github) you can set your version back to Then set your version back to 0.4.9 in smart.json

git tag -d v0.4.9
git tag -d v0.4.10
git tag -d v0.4.11
git push --tags production
mrt release .

[aldeed]

That worked, thanks!

For future reference, git push --tags didn't delete the remote tags, but I was able to delete each remote tag individually with git push origin :refs/tags/v0.4.9.

[aldeed]

@Tarangp, I'm trying to push 0.4.10 now. mrt release successfully created the tag and pushed it, but then threw the "Error: That's not a new version of the package!" message again, and atmosphere still shows 0.4.9. I tried deleting the tags from local and remote and releasing again, but same issue. publish shows the same error, too.

Thinking something must still be amiss with the atmosphere record for this package. (I'm not having troubles with other packages.)

[tmeasday]

Heh, I think you found a problem with the code. Turns out "0.4.10" < "0.4.9" :)

Try again now.

[aldeed]

Stupid string sorting. :) It worked now. Thanks!