You are here

Meshchat No One Receives Messages

6 posts / 0 new
Last post
W4SJN
Meshchat No One Receives Messages
I have meshchat 2.8 running on three Mikrotik hAP ac lite’s firmware 3.23.40.   The meshchat advertised service names are all the same.  When a user logs onto one of the chat instances I see them in Mesh Chat Users so I think the sync is working.  When any user sends a message using the Everyone Channel, no one receives it even though meshchat says the message is sent.  Ideas?
 
WT0F
Well this one is a bit unique
Well this one is a bit unique and interesting.

My first thought is that your message databases have bad permissions, but I would not bet that is the problem. The message DB and remote users are separate files, so it is conceivable. The message send message just means that the message was received by the local MeshChat instance. At some future time the message would be synced with the other instances through meshchatsync process. Can you verify that meshchatsync is running on all MeshChat instances?

I would also ask that you open up a bug report over at https://github.com/hickey/meshchat/issues so that the issue can be properly tracked. In the bug report can you include the 3 node names running MeshChat (if you are connected through a supernode I will be able to probe them a bit) and it might be helpful to have a copy of one of the config files.

73
--
Gerard, WTØF

 
W4SJN
MeshChatSync

I stopped and restarted the meshchatsync on each.  They were all started.  Still no messages sent but the Mesh Chat User area still changes just fine.  My network is still private at this point. 

When I log two users into the same Chat node, messages are still not received.  I'm assuming it does not use sync on the same node.

Just upgraded meshchat to 2.9.  Still no change. Can not receive messages.

W4SJN
Send Message No One Receives
No one can receive messages.  Meshchat 2.9 reports that messages were sent.  I can see all of the Meshchat users so I know sync is working.  see attachment.
File Attachment: 
WT0F
Please see my previous
Please see my previous comment to assist in troubleshooting this issue.
73
--
Gerard, WTØF
 
K7EOK
From your screen shot I see
From your screen shot I see the instance is named MeshChat-1941 ... this looks like the default way MeshChat calls itself when you install it.  Unless you went into port forwarding after installation and renamed them and rebooted etc, my bet is that each one has a different -XXXX ending.  These three meshchats in that case would NOT have the same name and would not link.  I have no idea why two operators on the same node would not link however.

If you did intentionally name each one MeshChat-1941 and it isn't working, and it's just testing so far ... I'd uninstall all three and try again from scratch.  If a database is corrupted that could be a way to clear it all.

BTW it would be nice to be able to remove un neccessary channels, and a way to reset the message database completely for remote nodes.  We have a large MeshChat going here that has about 20 local nodes, ten unneeded channels that folks created because they decided they needed to "test the meshchat" that it's getting to be quite a mess.  I wish there was a super-user command that could reach out and reset the MeshChat without all the node operators having to uninstall as the only way to clean things up.  I also am concerned that we pick up other linked nodes when folks tunnel into our mesh or perhaps it's from Supernodes ... but our MeshChat is full of stations outside our area in Status list.  Also someone decided to create a "new channel" called Everything ... so now our drop down options list has Everything and it also has Everything.

Great service ... and we seem to find new ways to break it!

Ed

Ed
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer