-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
Ejabberd Cluster file / images send not working for one node to second node #3359
Comments
Yes indeed there is no sharing token assignments between nodes in this module, so you could be only be able to perform upload on node where slot allocation was performed. To make this work we would need to move slot keeping logic to outside each module state, possibly in memory mnesia db? |
My plan is to get rid of the module state altogether by replacing it with the |
@kamalakkannan1984 right now my suggestion would be to have an external web server handle the actual file uploads by using one of the implementations mentioned here. If you specify the same external_secret for |
The same thing happens to me on ejabberd 19.09.1. |
Sure. The suggested solution would work with 19.09.1 as well. |
Here two catches as I see:
Am I wrong? |
Environment
erl +V
Configuration (only if needed): grep -Ev '^$|^\s*#' ejabberd.yml
Errors from error.log/crash.log
2020-08-19 10:57:54.010 [warning] <0.1997.0>@mod_http_upload:process:563 Rejecting file ca427369-3812-4459-8162-ba4694f831fd.jpg from ::ffff:127.0.0.1 for 7049.xxxx.yyyyy.com: Invalid slot
Ejabberd Clustor file sharing not working for one node to second node
Bug description
The Ejabberd cluster setup via HAProxy load balancer. In the cluster setup I have Node1(Ejabberd server 1) and Node2(Ejabberd server 2). When I upload file some time get rejected regarding invalid slot.
Our setup is HAProxy connect with two nodes(Node1 and Node2)
Note: Single Node(Ejabberd server) working fine.
Please any one share your ideas and feedback.
The text was updated successfully, but these errors were encountered: