[SOLVED] Huge panic: Subscriptions (DDP) is not working!

help
1

Since I Meteor 1.6.2 to 2.1 I have strange things happening, the worst was just discovered today, after launch: The client does not react to db changes. First I thought it was something with the subscriptions, but then I noticed that changes in the user db is not reflected either, Meteor.user() will ignore any changes made to the profile until next login.

Same with all other data that I subscribe to - I get the data, but updates in the db will not be seem until reload.

Anyone has an idea of where I should start to look?

No errors are generated.

2

Hi @ralof,
We had some breaking changes from 1.6.2 to 2.1. You can look at them here: Changelog | Meteor API Docs

My guess is something has changed, and it’s not updated on your code.

3

Yes, I just went through them (again), but nothing see, to match my problem

4

Could you provide more info? a code snippet would be great too

Do you use Meteor APM or any similar one? You could try to find errors or something suspicious there

1 Like
5

I will do some more research, but the system is huge, so the code snippet would not help I’m afraid, not without being accompanied by thousands of lines of code from 2017

6

Worth checking if the pub/sub messages are coming through the websocket connection at all.
Does this happen on dev as well as production?

2 Likes
7

Open developer tools, go to network tab and see what the socket is doing. Or just add a console.log so you debug the return.

1 Like
8

Install Meteor Dev Tools Evolved in chrome

3 Likes
9

Maybe you were using the package autopublish and you remove it, now you need to make sure your publications are correct.
Also, check your Tracker if they have the correct reactive variables.

Meteor DevTools is great to watch your data, maybe you can find the reason there

10

no, never used that. And the pub’s works, but only once (db changes are not picked up).
The system has been running for years, but it has too much old stuff in it.

I am currently simply doing what I should have done - throw out all atmosphere packages.
To start with. But it is painful :slight_smile:

1 Like
11

Is it using a react frontend and uses withTracker?

12

No, Blaze…
I do wonder though if there might be any React packages on there…

That’s the curse and blessing with node/ meteor – “oh, I just add this package”.
Then that package adds this package and this package adds that…

13

Sounds like the server issue with mongodb oplog setup.

14

Just moments ago I got it working again, tomorrow I will find out exactly why.
What I did was to remove:
matb33:collection-hooks
easy:search
npm-mongo@3.8.1
minimongo@1.6.1
msavin:mongol

One of them must be the culprit.
I have not added npm-mongo or minimongo myself and I was very surprised to see that the system does not seem to need them. Maybe their importance (if any) will show later.

Thanks everyone for suggestions!

1 Like
15

Good to know that you were able to solve this and thanks for sharing the solutions. Keep us updated if it’s going to be any problem

16

Hello.

I am having a similar issue. In my case, pub/sub breaks on production only, on Galaxy. Restarting the container seems to fix things. I need to investigate further with Meteor Dev Tools, but I wanted to ask if you managed to figure out exactly what the source of your issue was.

Thank you!

17

I’m glad you’re able to fix it but I’m curious did you use APM tools like Monti and it failed to capture the errors?

18

No, I never tried to find out the exact reason. What I did was to remove some old packages that maybe once upon a time had a reason to exist but was no longer needed. Removing them allowed other packages to update etcetera. Oh, I got rid of everything that needed coffee script, that abomination…

1 Like