Using Parabuild v.4.1.9, all of my builds are failing and reporting the following error. Help please!
Result: SYSTEM ERROR
Description: could not insert: [viewtier.autobuild.object.BuildRunAttribute]
Nothing has changed on our end as far as I know.
Here is some data surrounding the error in parabuild_debug.log:
[main] 13:19:59,826 ERROR: error.a.c ( 9) - Parabuild was requested to start
[BuildRunner:25447] 13:20:30,180 ERROR: DBCExceptionReporter( 58) - Integrity constraint violation - no parent BUILD_RUN_PARTICIPANT_FC2 table: CHANGELIST in statement [insert into BUILD_RUN_PARTICIPANT (BUILD_RUN_ID, CHANGELIST_ID, FIRST_BUILD_RUN_ID, FIRST_BUILD_RUN_NUMBER, ID) values (?, ?, ?, ?, null)]
[BuildRunner:25447] 13:20:30,180 ERROR: error.a.c ( 50) - Error while running build: could not insert: [viewtier.autobuild.object.BuildRunParticipant]: viewtier.autobuild.configuration.UnexpectedErrorException: could not insert: [viewtier.autobuild.object.BuildRunParticipant]
at viewtier.autobuild.configuration.ConfigurationManager.a(ConfigurationManager.java:442)
at viewtier.autobuild.configuration.ConfigurationManager.a(ConfigurationManager.java:412)
at viewtier.autobuild.configuration.ConfigurationManager$4.a(ConfigurationManager$4.java:21)
at viewtier.autobuild.configuration.ConfigurationManager.a(ConfigurationManager.java:132)
at viewtier.autobuild.configuration.ConfigurationManager.a(ConfigurationManager.java:478)
at viewtier.autobuild.build.dc.a(dc.java:289)
at viewtier.autobuild.build.dc.a(dc.java:154)
at viewtier.autobuild.build.dc.a(dc.java:381)
at viewtier.autobuild.build.gb$0.run(gb$0.java:3)
at viewtier.autobuild.build.gb$c_.run(gb$c_.java:5)
at viewtier.autobuild.build.gb.c(gb.java)
at viewtier.autobuild.build.dc.run(dc.java:195)
Caused by: net.sf.hibernate.exception.ConstraintViolationException: could not insert: [viewtier.autobuild.object.BuildRunParticipant]
at net.sf.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:73)
at net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
at net.sf.hibernate.persister.AbstractEntityPersister.convert(AbstractEntityPersister.java:1331)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:540)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:426)
at net.sf.hibernate.impl.ScheduledIdentityInsertion.execute(ScheduledIdentityInsertion.java:28)
at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2449)
at net.sf.hibernate.impl.SessionImpl.doSave(SessionImpl.java:943)
at net.sf.hibernate.impl.SessionImpl.doSave(SessionImpl.java:868)
at net.sf.hibernate.impl.SessionImpl.saveWithGeneratedIdentifier(SessionImpl.java:786)
at net.sf.hibernate.impl.SessionImpl.save(SessionImpl.java:749)
at net.sf.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:1398)
at viewtier.autobuild.configuration.x.saveOrUpdate(x.java:43)
at viewtier.autobuild.configuration.ConfigurationManager$133.a(ConfigurationManager$133.java)
at viewtier.autobuild.configuration.ConfigurationManager.a(ConfigurationManager.java:132)
... 11 more
Caused by: java.sql.SQLException: Integrity constraint violation - no parent BUILD_RUN_PARTICIPANT_FC2 table: CHANGELIST in statement [insert into BUILD_RUN_PARTICIPANT (BUILD_RUN_ID, CHANGELIST_ID, FIRST_BUILD_RUN_ID, FIRST_BUILD_RUN_NUMBER, ID) values (?, ?, ?, ?, null)]
at org.hsqldb.jdbc.Util.throwError(Unknown Source)
at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:233)
at net.sf.hibernate.persister.EntityPersister.insert(EntityPersister.java:518)
... 22 more
could not insert viewtier.autobuild.object.BuildRunAttribute
-
- Posts: 45
- Joined: Tue Dec 07, 2010 3:45 pm
- Location: Huntsville Alabama USA
- Contact:
-
- Posts: 45
- Joined: Tue Dec 07, 2010 3:45 pm
- Location: Huntsville Alabama USA
- Contact:
I ended up restoring from a backup to recover from this error. It appears to have occurred when the machine ran out of disk space.
To clean up the machine, I removed most of the folders in C:\parabuild\etc\logs. This cleared just over 80GB of data.
I also noticed that there are over 10GB of data in the C:\parabuild\etc\index folder and is responsible for most of my disk fragmentation. Is it possible to tell Parabuild to recreate the contents of this folder?
To clean up the machine, I removed most of the folders in C:\parabuild\etc\logs. This cleared just over 80GB of data.
I also noticed that there are over 10GB of data in the C:\parabuild\etc\index folder and is responsible for most of my disk fragmentation. Is it possible to tell Parabuild to recreate the contents of this folder?
Return to “parabuild.ci.support”
Who is online
Users browsing this forum: No registered users and 5 guests