Subject: The mailing list for listmasters using Sympa
List archive
- From: jose antonio Fernandez <address@concealed>
- To: "address@concealed" <address@concealed>
- Subject: [sympa-users] Lost connection database
- Date: Tue, 23 Jul 2013 11:52:36 +0200
Hi everyone,
I have some questions about sympa behavior with the database. In our scenery, database server is separated from sympa's servers, and it's possible to happen that the sympa's servers lose the connection with the database server. In that case, sympa still receives mails to the lists, but gives no output. Only when the connection to the database is restored, sympa resolves all the mails in the spool. Is there any way to change that behavior and give output with the database's link broken? Maybe something like pointing the list configuration and subscriber's information to a disk file.
Another question, when this happens and we try to execute "sympa stop", we observe that bulk.pl can't be stoped, it hangs. Is this a normal behavior? Can be stopped somehow?
Thanks in advance.
I have some questions about sympa behavior with the database. In our scenery, database server is separated from sympa's servers, and it's possible to happen that the sympa's servers lose the connection with the database server. In that case, sympa still receives mails to the lists, but gives no output. Only when the connection to the database is restored, sympa resolves all the mails in the spool. Is there any way to change that behavior and give output with the database's link broken? Maybe something like pointing the list configuration and subscriber's information to a disk file.
Another question, when this happens and we try to execute "sympa stop", we observe that bulk.pl can't be stoped, it hangs. Is this a normal behavior? Can be stopped somehow?
Thanks in advance.
- [sympa-users] Lost connection database, jose antonio Fernandez, 07/23/2013
Archive powered by MHonArc 2.6.19+.