#1886 Enable muc_mam causing Failed to connect database (mySQL)
Reporter
Dave
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Priority-Medium
Status-Invalid
Type-Defect
Dave
on
Hi I am new in here so apologize if I not 100% follow the rules in advance.
OS: Centos Stream 9
mySQL: Community via dnf
Prosody: the latest via yum
Enabled mySQL module has no problem. Can see my account is created in database. However when I enable muc_man in configuration file it gives me "sql error Error in SQL transaction: Failed to connect to database: Can't connect to local server through socket '/var/lib/mysql/mysql.sock' (13)"
It seems somehow (selinux/firewall) not allow this module to access the socket?
Zash
on
Thanks for the report. Note that this is an issue tracker, not a support or discussion forum. The chatroom is probably better suited at diagnosing your problem. <https://prosody.im/discuss>
The error code (13) most likely means this is a permission problem, that seems unlikely to be a problem with Prosody itself, but rather configuration.
https://manpages.debian.org/bookworm/freebsd-manpages/errno.2freebsd.en.html#Permission
If it works in one section but not another (ie VirtualHosts, Components) then make sure e.g. sql connection settings are correct for each section or placed in the global section to be identical for all hosts.
Hi I am new in here so apologize if I not 100% follow the rules in advance. OS: Centos Stream 9 mySQL: Community via dnf Prosody: the latest via yum Enabled mySQL module has no problem. Can see my account is created in database. However when I enable muc_man in configuration file it gives me "sql error Error in SQL transaction: Failed to connect to database: Can't connect to local server through socket '/var/lib/mysql/mysql.sock' (13)" It seems somehow (selinux/firewall) not allow this module to access the socket?
Thanks for the report. Note that this is an issue tracker, not a support or discussion forum. The chatroom is probably better suited at diagnosing your problem. <https://prosody.im/discuss> The error code (13) most likely means this is a permission problem, that seems unlikely to be a problem with Prosody itself, but rather configuration. https://manpages.debian.org/bookworm/freebsd-manpages/errno.2freebsd.en.html#Permission If it works in one section but not another (ie VirtualHosts, Components) then make sure e.g. sql connection settings are correct for each section or placed in the global section to be identical for all hosts.
Changes