Problem in MatchMaker.remoteRoomCall

I was investigating a bit using clusters on my Colyseus server.

I found when I was using a cluster, just after requestJoin and before onAuth The client never joined. On the log, I found than the error “remote room timed out” was thrown. After a bit of finding and testing, I found the problem:

When the room is called in MatchMaker.remoteRoomCall the room id is: “147,10,170,66,107,101,79,81,116,121,104,105,102,1” or something like that, but when it publishes the message it is a room id like “HkuXKy2jM” instead, making getRoomChannel to return wildly different values.

I’ll try to isolate my bit of code than is causing troubles and post an update. I tried using both RedisPresence and MemsharedPresence, so it seems it’s not a problem on either of them.

[endel]

Hey @bamsutler, that’s really odd. I’ve just tried the code you pasted and my logs look like this:

BasicRoom created! {}
room created: BkaM1VJ1X
Listening on http://localhost:2727
[ { clients: 0,
    maxClients: 4,
    metadata: undefined,
    roomId: 'BkaM1VJ1X' } ]
BJIXTmy17 joined BkaM1VJ1X

The getInspectData method comes from colyseus-monitor project. My guess is that you had the monitor open viewing a room on a tab, and then rebooted the server - then the monitor would try to retrieve data for an unexisting room, could that be the case?

Cheers!

[endel]

I’m closing this since it seems to be fixed on 0.9.16. Let me know if you still see this error!