[Plugin: DBC Backup] MySQL client ran out of memory
-
Dear sirs,
Just installed the plugin on a production site. We have lots of users and page views per day so I think database shall be a little big.
After installation/configuration I run a immediate backup.
The log shows success and the SQL file is created. The file is though, very small. And looking inside it shows that MySQL crashed.
Any suggestions? I copied the begining of the file below.Thanks in advance,
— Database Cron Backup
— Version 1.0 for WordPress 2.5+
— Copyright Chris T aka Tefra https://www.t3-design.com
— Generated: Wednesday 22nd of December 2010 04:10 PM
— MySQL Server: Localhost via UNIX socket
— MySQL Server version: 5.1.47
— Database:xxx
— ——————————————————–—
— Table structure of tablewp_StatSurfer
—DROP TABLE IF EXISTS
wp_StatSurfer
;
CREATE TABLE IF NOT EXISTSwp_StatSurfer
(
id
mediumint(9) NOT NULL AUTO_INCREMENT,
date
tinytext COLLATE utf8_unicode_ci,
time
tinytext COLLATE utf8_unicode_ci,
ip
tinytext COLLATE utf8_unicode_ci,
urlrequested
text COLLATE utf8_unicode_ci,
agent
text COLLATE utf8_unicode_ci,
referrer
text COLLATE utf8_unicode_ci,
search
text COLLATE utf8_unicode_ci,
nation
tinytext COLLATE utf8_unicode_ci,
os
tinytext COLLATE utf8_unicode_ci,
browser
tinytext COLLATE utf8_unicode_ci,
searchengine
tinytext COLLATE utf8_unicode_ci,
spider
tinytext COLLATE utf8_unicode_ci,
feed
tinytext COLLATE utf8_unicode_ci,
user
tinytext COLLATE utf8_unicode_ci,
timestamp
tinytext COLLATE utf8_unicode_ci,
threat_score
smallint(6) DEFAULT NULL,
threat_type
smallint(6) DEFAULT NULL,
UNIQUE KEYid
(id
)
) TYPE=MyISAM AUTO_INCREMENT=821370 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;—
— Dumping data for tablewp_StatSurfer
——
— Dumping data for tablewp_StatSurfer
—–MySQL client ran out of memory
—
— Table structure of tablewp_StatSurfer_countries
—–Lost connection to MySQL server during query
—
— Dumping data for tablewp_StatSurfer_countries
- The topic ‘[Plugin: DBC Backup] MySQL client ran out of memory’ is closed to new replies.