XF 1.5 Database restore.


Active member
I have been creating automagic database backups for the "just in case" disaster recovery and testing offline for some time.

I have come to restore a recent backup and am having issues with the recovery. It looks like a conversation post is causing the issue as seen by

INSERT INTO `xf_email_bounce_log` VALUES (3,1448363048,1448357995,'unknown','',NULL,NULL,'Return-path: <email address here >\r\nEnvelope-to: another address here \r\nDelivery-date: Tue, 24 Nov 2015 04:39:58 -0500\r\nReceived: from mail-vk0-f48.google.com ([]:33162)\r\n by my host here with esmtps (TLSv1.2:AES128-GCM-SHA256:128)\r\n (Exim 4.85)\r\n
Is there any way of killing this message on the live server , and therefore mitigation the error ?


Active member
Can you please post the full error message?

INSERT INTO `xf_email_bounce_log` VALUES (3,1448363048,1448357995,'unknown','',NULL,NULL,'Return-path: <from address>\r\nEnvelope-to: to address\r\nDelivery-date: Tue, 24 Nov 2015 04:39:58 -0500\r\nReceived: from mail-vk0-f48.google.com ([]:33162)\r\n by hosting company with esmtps (TLSv1.2:AES128-GCM-SHA256:128)\r\n (Exim 4.85)\r\n (envelope-from <from address>)\r\n id 1a1A4r-000nV5-5v\r\n for to address; Tue, 24 Nov 2015 04:39:58 -0500\r\nReceived: by vkfr145 with SMTP id r145so7604050vkf.0\r\n for to address; Tue, 24 Nov 2015 01:39:55 -0800 (PST)\r\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r\n d=gmail.com; s=20120113;\r\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r\n :content-type;\r\n bh=9NvhHidqc/XhvxXDOZCZN5rhocU2qz7rqR1NlGBWcQI=;\r\n b=0gTtbNPInHrKh9+OnCHs2kVn0/OsHuWvIWhd5Fi6JGUYJEbWKdDkhXAGukN6xfKbIC\r\n [...]


Active member
Backing up using an automated cron job that runs at 0300 - paid for app. Previous backups to a point worked.

Approx 155k posts


Well-known member
Appears to be a bounce log issue. Dare not drop that table on a live server
That table holds the emails that were not able to be delievered by the system. You can truncate it, but not drop it. If you are going to truncate it, make a backup of it before hand. In the worst case scanario, you can restore the table back.