[Bug]: Messages not received. #29
Assignees
Labels
bug
Something isn't working
Comments
|
I think I was asking for one of the config files so I have some idea how you have the MeshChat instances configured. |
|
Where do I get the config files? I only see the AREDN support file download. |
|
On a standard node install you would be looking for the |
|
meshchat_path = "/tmp/meshchat"
max_messages_db_size = 500
max_file_storage = 512 * 1024
lock_file = meshchat_path .. "/lock"
messages_db_file = meshchat_path .. "/messages"
messages_db_file_orig = meshchat_path .. "/messages"
sync_status_file = meshchat_path .. "/sync_status"
local_users_status_file = meshchat_path .. "/users_local"
remote_users_status_file = meshchat_path .. "/users_remote"
remote_files_file = meshchat_path .. "/files_remote"
messages_version_file = meshchat_path .. "/messages_version"
local_files_dir = meshchat_path .. "/files"
tmp_upload_dir = "/tmp/web/upload"
poll_interval = 10
non_meshchat_poll_interval = 600
valid_future_message_time = 30 * 24 * 60 * 60
connect_timeout = 5
speed_time = 10
speed_limit = 1000
platform = "node"
debug = 0
extra_nodes = {}
protocol_version = "1.02"
app_version = "2.9"
***@***.***:/www/cgi-bin#
…On Wed, Jan 3, 2024 at 10:04 AM Gerard Hickey ***@***.***> wrote:
On a standard node install you would be looking for the
/www/cgi-bin/meshchatconfig.lua file.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZIS54YPYG4K676YWZ7VWEDYMVXOVAVCNFSM6AAAAABBKZTTDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZVGUYTKMJUGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
OK. Good. The poll intervals look adequate. Next thing to look at is what is in Troubleshooting the v2.9 front end will be interesting. I don't think that there were any debug statements to send to the Javascript console. That brings up another though. You do have Javascript turned on in your browser right? You generally would have had to specifically turn off Javascript. |
|
All files are 0 bytes and Java is not disabled.
BC13E6
-rw-rw-rw- 1 root root 0 Sep 23 21:02
messages.MeshChat-1941
QANYCY
-rw-rw-rw- 1 root root 0 Sep 21 20:26
messages.MeshChat-1941
DEC6EC
-rw-rw-rw- 1 root root 0 Sep 21 20:30
messages.MeshChat-1941
Default behavior
Sites automatically follow this setting when you visit them
Sites can use JavaScript
…On Wed, Jan 3, 2024 at 9:06 PM Gerard Hickey ***@***.***> wrote:
OK. Good. The poll intervals look adequate.
Next thing to look at is what is in /tmp/meshchat. At the moment I am
interested in the file sizes, so post the output of ls -l /tmp/meshchat.
I the messages.<ZONENAME> is more than 0 bytes, then the issue is on the
front end code. If you check all three nodes running MeshChat, they all
should have a messages.<ZONENAME> of about the same size (or identical
size).
Troubleshooting the v2.9 front end will be interesting. I don't think that
there were any debug statements to send to the Javascript console. That
brings up another though. You do have Javascript turned on in your browser
right? You generally would have had to specifically turn off Javascript.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZIS54364PB2AQJSBSRV4LDYMYFDRAVCNFSM6AAAAABBKZTTDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGIYTCMJWGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
OK. So with all the message databases being 0 bytes, they have no messages at all. It is starting to sound like to me that the root@WT0F-1:~/meshchat# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 196.0K 28.9M 1% /tmp |
|
DEC6EC:~/meshchat# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 148.0K 28.9M 0% /tmp
QANYCY:/# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 148.0K 28.9M 0% /tmp
BC13E6:~# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 136.0K 28.9M 0% /tmp
…On Wed, Jan 3, 2024 at 11:56 PM Gerard Hickey ***@***.***> wrote:
OK. So with all the message databases being 0 bytes, they have no messages
at all. It is starting to sound like to me that the meshchat cgi-bin
script is trying to write to the DB files but the writes are failing
because of a full filesystem. The easiest way to check this is to execute df
-h /tmp. Here is what you would expect to see:
***@***.***:~/meshchat# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 196.0K 28.9M 1% /tmp
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZIS543T4HDPTM7GAX2A3KLYMYY7RAVCNFSM6AAAAABBKZTTDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGMYTCNJRG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
My latest data is below. Is there anything else I can try?
Steve Nosko
W4SJN
From: Steve Nosko ***@***.***>
Sent: Thursday, January 4, 2024 5:11 PM
To: hickey/meshchat ***@***.***>
Cc: hickey/meshchat ***@***.***>; Author ***@***.***>
Subject: Re: [hickey/meshchat] [Bug]: Messages not received. (Issue #29)
DEC6EC:~/meshchat# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 148.0K 28.9M 0% /tmp
QANYCY:/# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 148.0K 28.9M 0% /tmp
BC13E6:~# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 136.0K 28.9M 0% /tmp
On Wed, Jan 3, 2024 at 11:56 PM Gerard Hickey ***@***.*** ***@***.***> > wrote:
OK. So with all the message databases being 0 bytes, they have no messages at all. It is starting to sound like to me that the meshchat cgi-bin script is trying to write to the DB files but the writes are failing because of a full filesystem. The easiest way to check this is to execute df -h /tmp. Here is what you would expect to see:
***@***.***:~/meshchat# df -h /tmp
Filesystem Size Used Available Use% Mounted on
tmpfs 29.0M 196.0K 28.9M 1% /tmp
—
Reply to this email directly, view it on GitHub <#29 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZIS543T4HDPTM7GAX2A3KLYMYY7RAVCNFSM6AAAAABBKZTTDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGMYTCNJRG4> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AZIS546J6KUPU4CSYPSB34DYMYY7RA5CNFSM6AAAAABBKZTTDCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTP2Y652.gif> Message ID: ***@***.*** ***@***.***> >
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Contact Details
steven.nosko@gmail.com
Version
v2.9
System Type
AREDN node
What happened?
A bug happened! I have three Mikrotik hAP AC Lite routers (firmware 3.23.4.0) running Meshchat 2.8. I can see each user in the Mesh Chat Users box update correctly so I'm assuming sync is working properly. Messages are reported being sent but no messages are ever received. I also tried logging all users onto the same instance of Meshchat on the same router but no message is ever received. I uninstalled all instances of Meshchat 2.8 and installed Meshchat 2.9. Same results.
What browsers are you seeing the problem on?
Firefox, Chrome
The text was updated successfully, but these errors were encountered: