[opencms-dev] The table'CMS_BACKUP_CONTENTS'isfull-Errormessagewhen publishing
Jeremy Wilson
jeremy.wilson at laplink.com
Wed Jun 1 18:22:58 CEST 2011
Yes, I went ahead and ran the 'optimize' command in mysql on that particular table and in the end, I cleared out only about 1-2 MB of additional space from the full 4.2+ GB table.
This really only bought me a little bit of time. I'm reasonably certain that the next steps, short of an OpenCMS upgrade, involve either upgrading to MySQL 5+ and or running the ALTER command to increase the max_table_length for CMS_BACKUP_CONTENTS
Thanks again.
Still holding out for some feedback on the usefulness of a MySQL server upgrade, specifically as to whether or not it will address this max_table_length issue.
-----Original Message-----
From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Schliemann, Kai
Sent: Wednesday, June 01, 2011 12:55 AM
To: The OpenCms mailing list
Subject: Re: [opencms-dev] The table'CMS_BACKUP_CONTENTS'isfull-Errormessagewhen publishing
Hi Jeremy,
we set up a cron job for that for one of our customers. So optimize table is fine.
Best regards
Kai
-----Ursprüngliche Nachricht-----
Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Jeremy Wilson
Gesendet: Dienstag, 31. Mai 2011 21:50
An: The OpenCms mailing list
Betreff: Re: [opencms-dev] The table'CMS_BACKUP_CONTENTS'isfull-Errormessage when publishing
Would executing an 'optimize table' command in mysql, on this table, be suggested or highly inadviseable?
-----Original Message-----
From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Schliemann, Kai
Sent: Monday, May 30, 2011 1:15 AM
To: The OpenCms mailing list
Subject: Re: [opencms-dev] The table 'CMS_BACKUP_CONTENTS'isfull-Errormessage when publishing
Hi Jeremy,
if I recall correctly there was a bug since 7.5.3 which doesn't really shrink the size of this table.
I had a look at the 7.5.4 release notes (http://www.opencms.org/en/news/110328-opencms-v754-releasenotes.html):
Fixed issue #1949: Database size does not decrease after (completely) deleting resources
I guess this solves the problem.
HTH
Regards
Kai
-----Ursprüngliche Nachricht-----
Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Jeremy Wilson
Gesendet: Freitag, 27. Mai 2011 19:33
An: The OpenCms mailing list
Betreff: Re: [opencms-dev] The table 'CMS_BACKUP_CONTENTS' isfull-Errormessage when publishing
Two more questions on this issue before I execute the recommended
"ALTER" table command.
1) Can anyone please tell me what specifically is contributing to sheer
size of this 'CMS_BACKUP_CONTENTS' table?
a) Is it something to do with version history? I had this
server set at 100 but have since dialed it down to 20 in the hopes of
mitigating this problem, particularly in my live environment.
b) Is clearing history in the OpenCMS Administration panel going
to serve any useful purpose in reducing the size of the database table?
c) Apart from version history settings, is this related to file
size of certain documents/images/multimedia files published in the
OpenCMS 6 environment?
2) Is there any way to clean this table up and remove old entries? I've
NOT noticed any change to the size of the 'CMS_BACKUP_CONTENTS' table
despite completely deleting a large number of old/abandoned or otherwise
archive directories on this server. Furthermore, I had hoped that by
deleting and publishing those deletions it would completely wipe them
from existence in so far as OpenCMS is concerned. That does not seem to
be the case and confirms to me that I seem to have zero understanding of
what constitutes the contents this table.
Thanks again in advance.
-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Jeremy Wilson
Sent: Monday, May 16, 2011 12:05 PM
To: The OpenCms mailing list
Subject: Re: [opencms-dev] The table 'CMS_BACKUP_CONTENTS' is
full-Errormessage when publishing
Hein,
Thank you very much. Very helpful.
-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Hein van der
Kallen
Sent: Monday, May 16, 2011 11:46 AM
To: The OpenCms mailing list
Subject: Re: [opencms-dev] The table 'CMS_BACKUP_CONTENTS' is full
-Errormessage when publishing
Jeremy
see
http://www.opencms-forum.de/opencms-forum/viewthread?thread=3545#9313
Hein van der Kallen
----- Original Message -----
From: "Jeremy Wilson" <jeremy.wilson at laplink.com>
To: "The OpenCms mailing list" <opencms-dev at opencms.org>
Sent: Monday, May 16, 2011 8:24 PM
Subject: [opencms-dev] The table 'CMS_BACKUP_CONTENTS' is full -
Errormessage when publishing
> Recently a my web staging environment started producing the following
> error, "The table 'CMS_BACKUP_CONTENTS' is full", when trying to
publish
> certain files under /sites/default/ and now it is popping up on some
> files under /system/modules/ as well. It is not consistent except
that
> currently it seems limited to larger *.swf, *.pdf, and *.wmv files.
>
> Can anyone tell me if this is easily rectified and maybe a pointer or
> two in the right direction?
>
>
> Here is the text of the console message/error.
>
> Validating links ...
> ... finished validating links
> Publishing resources ...
> Publishing files ...
> ( 1 / 1 ) Publishing file
> /system/modules/com.abc.www/includes/styles/global.css ... Error
> publishing file
> "/system/modules/com.abc.www/includes/styles/global.css".
> Exception org.opencms.db.CmsDbSqlException: An SQL error occurred when
> executing the following query:
> com.mysql.jdbc.ServerPreparedStatement[39] - INSERT INTO
> CMS_BACKUP_CONTENTS
> (CONTENT_ID,RESOURCE_ID,FILE_CONTENT,PUBLISH_TAG,VERSION_ID,BACKUP_ID)
> VALUES
>
('88f13f72-3620-11e0-a36c-000c295d1071','69e07889-400a-11da-be17-0030482
> b843c',** STREAM DATA
> **,11426,137,'17a03424-7fe8-11e0-8f57-000c295d1071').
> at
>
org.opencms.db.generic.CmsBackupDriver.internalWriteBackupFileContent(Cm
> sBackupDriver.java:1253)
> at
>
org.opencms.db.generic.CmsBackupDriver.writeBackupResource(CmsBackupDriv
> er.java:1087)
> at
>
org.opencms.db.generic.CmsProjectDriver.publishFile(CmsProjectDriver.jav
> a:1073)
> at
>
org.opencms.db.generic.CmsProjectDriver.publishProject(CmsProjectDriver.
> java:1654)
> at
>
org.opencms.db.CmsDriverManager.publishProject(CmsDriverManager.java:449
> 3)
> at
>
org.opencms.db.CmsSecurityManager.publishProject(CmsSecurityManager.java
> :2893)
> at org.opencms.file.CmsObject.publishProject(CmsObject.java:1975)
> at
>
org.opencms.workplace.threads.CmsPublishThread.run(CmsPublishThread.java
> :122)
> Caused by: java.sql.SQLException: The table 'CMS_BACKUP_CONTENTS' is
> full
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2928)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1571)
> at
>
com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedState
> ment.java:1124)
> at
>
com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedSta
> tement.java:676)
> at
>
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:11
> 66)
> at
>
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:10
> 82)
> at
>
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:10
> 67)
> at
>
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delega
> tingPreparedStatement.java:101)
> at
>
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delega
> tingPreparedStatement.java:101)
> at
>
org.opencms.db.generic.CmsBackupDriver.internalWriteBackupFileContent(Cm
> sBackupDriver.java:1250)
> ... 7 more
> Statistics: published files: 1, published folders: 0, deleted folders:
> 0, duration: 00:00:00
> Exception org.opencms.db.CmsDbSqlException: Error publishing file
> "/system/modules/com.abc.www/includes/styles/global.css".
> at
>
org.opencms.db.CmsDbSqlException.createException(CmsDbSqlException.java:
> 103)
> at org.opencms.db.CmsDbContext.throwException(CmsDbContext.java:213)
> at org.opencms.db.CmsDbContext.report(CmsDbContext.java:197)
> at
>
org.opencms.db.generic.CmsProjectDriver.publishProject(CmsProjectDriver.
> java:1675)
> at
>
org.opencms.db.CmsDriverManager.publishProject(CmsDriverManager.java:449
> 3)
> at
>
org.opencms.db.CmsSecurityManager.publishProject(CmsSecurityManager.java
> :2893)
> at org.opencms.file.CmsObject.publishProject(CmsObject.java:1975)
> at
>
org.opencms.workplace.threads.CmsPublishThread.run(CmsPublishThread.java
> :122)
> Caused by: org.opencms.db.CmsDbSqlException: An SQL error occurred
when
> executing the following query:
> com.mysql.jdbc.ServerPreparedStatement[39] - INSERT INTO
> CMS_BACKUP_CONTENTS
> (CONTENT_ID,RESOURCE_ID,FILE_CONTENT,PUBLISH_TAG,VERSION_ID,BACKUP_ID)
> VALUES
>
('88f13f72-3620-11e0-a36c-000c295d1071','69e07889-400a-11da-be17-0030482
> b843c',** STREAM DATA
> **,11426,137,'17a03424-7fe8-11e0-8f57-000c295d1071').
> at
>
org.opencms.db.generic.CmsBackupDriver.internalWriteBackupFileContent(Cm
> sBackupDriver.java:1253)
> at
>
org.opencms.db.generic.CmsBackupDriver.writeBackupResource(CmsBackupDriv
> er.java:1087)
> at
>
org.opencms.db.generic.CmsProjectDriver.publishFile(CmsProjectDriver.jav
> a:1073)
> at
>
org.opencms.db.generic.CmsProjectDriver.publishProject(CmsProjectDriver.
> java:1654)
> ... 4 more
> Caused by: java.sql.SQLException: The table 'CMS_BACKUP_CONTENTS' is
> full
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2928)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1571)
> at
>
com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedState
> ment.java:1124)
> at
>
com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedSta
> tement.java:676)
> at
>
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:11
> 66)
> at
>
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:10
> 82)
> at
>
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:10
> 67)
> at
>
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delega
> tingPreparedStatement.java:101)
> at
>
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Delega
> tingPreparedStatement.java:101)
> at
>
org.opencms.db.generic.CmsBackupDriver.internalWriteBackupFileContent(Cm
> sBackupDriver.java:1250)
> ... 7 more
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please
visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please
visit
http://lists.opencms.org/mailman/listinfo/opencms-dev
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please
visit
http://lists.opencms.org/mailman/listinfo/opencms-dev
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev
More information about the opencms-dev
mailing list