8000 [Bug]: Not working, syslog errors · Issue #57 · hickey/meshchat · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Bug]: Not working, syslog errors #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
la9ky opened this issue Dec 13, 2024 · 5 comments
Open

[Bug]: Not working, syslog errors #57

la9ky opened this issue Dec 13, 2024 · 5 comments
Assignees
@hickey
Labels
bug Something isn't working

Comments

@la9ky
Copy link
la9ky commented Dec 13, 2024

Contact Details

la9ky.frank@gmail.com

Version

v2.12.0

System Type

AREDN node

What happened?

After reinstalling my nodes with Night Build latest, installing v2.12.1 Meshchat I only get the windows for messages but does not accept new messages.

I am on Night build version on hAP ac lite and also Nanobeam,
I have tried to get Meshchat to work since I had to leave latest release for the Aredn bug in vlan tagging / DtD.

I have installed Meschat 2.12.1 and I get the login and the message window.
The syslog gets flooded with
Wed Dec 11 20:53:47 2024 daemon.err uhttpd[1491]: /usr/bin/lua: /www/cgi-bin/meshchat:52: attempt to call field 'Request' (a nil value)
Wed Dec 11 20:53:48 2024 daemon.err uhttpd[1491]: /usr/bin/lua: /www/cgi-bin/meshchat:52: attempt to call field 'Request' (a nil value)
Wed Dec 11 20:53:58 2024 daemon.err uhttpd[1491]: /usr/bin/lua: /www/cgi-

and I see a file /meshchat/messages.MeshChat-6349 that probably should have been written over when I set up the service with Meshchat-LA9KY (ex)

The installation is the meschat_2.12.1_all.ipk on the hAP ac2 lite. for now the service is deleted, to avoid the messages in syslog, but can be started on short notice.

MeshChat configuration

<Insert config file here>

Connection type

Mesh network connected through IP tunnel

Node name

LA9KY-home

What browsers are you seeing the problem on?

Chrome, Safari, Microsoft Edge
@la9ky la9ky added bug Something isn't working needs triage labels Dec 13, 2024
@la9ky
Copy link
Author
la9ky commented Dec 13, 2024

the config file for meshchat, where is that located ?

@K5RA
Copy link
K5RA commented Dec 17, 2024 •
edited
Loading

My system is a Raspberry Pi running Meshchat_all_1.02 and a hAP ac lite running Meshchat_api_2.12.1.
The configuration file, meshchatconfig.pm, in my system is in the R-Pi root directory, in folder
/usr/lib/cgi-bin

@la9ky
Copy link
Author
la9ky commented Dec 17, 2024

My system is a Raspberry Pi running Meshchat_all_1.02 and a hAP ac lite running Meshchat_api_2.12.1. The configuration file, meshchatconfig.pm, in my system is in the R-Pi root directory, in folder /usr/lib/cgi-bin

hi, have I misunderstood that Rpi should have the api version but hAP ac lite should have the meshchat_2.12.1_all.ipk ?
Because I dont have /usr/lib/cgi-bin directory on my hAP.

@K5RA
Copy link
K5RA commented Dec 17, 2024

We run the meshchat_api (v2.12.1) in our hAP aredn nodes, and run the meshchat_all (v1.02) program in our raspberry pi service computers. Meschat_all 12.2.1 is a .ipk file and will not load on an R-Pi machine with R-Pi OS (Debian - bookworm).

@hickey
Copy link
Owner
hickey commented Dec 18, 2024

LA9KY,

I will be traveling for a little more than a week, so it will be a bit before I can fully dig into this issue. In the mean time, here are some notes that may help you.

The configuration should be located in /www/cgi-bin/meshchatconfig.lua. This is where older versions of MeshChat kept their configuration. Starting with v2.12 the meshchatconfig.lua file should not be modified and instead any configuration changes should be put in /www/cgi-bin/meshchat_local.lua as explained in the comments a the top of meshchatconfig.lua. So you should look for both files in /www/cgi-bin.

If you change the name of the service, it is best to reboot the node to insure that the new filename get created correctly. This is mostly for insuring that meshchatsync is looking at the correct files. After the reboot, the old message database may still be present, but it should not receive any further updates and can be removed. The new message database should be receiving any updates (either from meshchatsync or from the local UI).

I hope that this helps you some.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hickey hickey

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hickey @K5RA @la9ky
0