Oops ... I was wrong and answered as if I had written Remo. :-D
I didn't add any dspam backup. If is not a default behaviour in qmailtoaster install scripts, then isn't there.
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.comBasically, Diego, I was asking if you backup your dspam database.
If you do back it up and you don't have --single-transaction specified it could be the culprit when your seeing locks.
If you're not backing up your dspam database then disregard.
On 8/14/2020 8:30 AM, Diego Piñon Conde wrote:
Sorry Remo, I don't know where to look to find that line of code
El 14/08/2020 a las 01:52 a. m., Eric Broch escribió:
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.comDoes you mysqldump look like this:
/usr/bin/mysqldump -udspam -pdspampasswd -hlocalhost dspam --single-transaction > dspam.sql
Have a look here at option --single-transaction (https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html#option_mysqldump_single-transaction):
--single-transactionThis option sets the transaction isolation mode to
REPEATABLE READand sends aSTART TRANSACTIONSQL statement to the server before dumping data. It is useful only with transactional tables such asInnoDB, because then it dumps the consistent state of the database at the time whenSTART TRANSACTIONwas issued without blocking any applications.When using this option, you should keep in mind that only
InnoDBtables are dumped in a consistent state. For example, anyMyISAMorMEMORYtables dumped while using this option may still change state.While a
--single-transactiondump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection should use the following statements:ALTER TABLE,CREATE TABLE,DROP TABLE,RENAME TABLE,TRUNCATE TABLE. A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause theSELECTthat is performed by mysqldump to retrieve the table contents to obtain incorrect contents or fail.The
--single-transactionoption and the--lock-tablesoption are mutually exclusive becauseLOCK TABLEScauses any pending transactions to be committed implicitly.To dump large tables, combine the
--single-transactionoption with the--quickoption.
Maybe the statement should be change to this:
/usr/bin/mysqldump -udspam -pdspampasswd -hlocalhost dspam --single-transaction --quick > dspam.sql
On 8/13/2020 10:44 PM, Remo Mattei wrote:
👍
On Aug 13, 2020, at 9:31 PM, Eric Broch <ebr...@whitehorsetc.com> wrote:
Diego,
Are you backing up your dspam database (mysqldump)?
Eric
On 8/13/2020 10:22 PM, Diego Piñon Conde wrote:
Perfect!
I killed that proccess and two more child and then dspam service run nicely!
One more time, thank you very much Eric!
El 13/08/2020 a las 10:57 p. m., Eric Broch escribió:
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com6856 is the process id
If spamd is not running then those ports are being bound.
Can you kill that process and try to start spamd
On 8/13/2020 7:28 PM, Diego Piñon Conde wrote:
netstat -lptn | grep 'spamd'
tcp 10 0 127.0.0.1:783 0.0.0.0:* LISTEN 6856/spamd child
tcp6 129 0 ::1:783 :::* LISTEN 6856/spamd child
