You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Lenik <le...@bodz.net> on 2010/07/07 17:30:52 UTC
`mvn deploy' failed
The output:
[INFO]
------------------------------------------------------------------------
[INFO] Building SECCA :: SEMS :: Parent
[INFO] task-segment: [deploy]
[INFO]
------------------------------------------------------------------------
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/appserv/build/parent/pom.xml to
/home/appserv/.m2/repository/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-SNAPSHOT.pom
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from seccasnapshots
[INFO] repository metadata for: 'snapshot
com.seccaproject.sems:parent:1-SNAPSHOT' could not be found on
repository: seccasnapshots, so will be created
Uploading:
http://m2.secca-project.com/snapshots/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-20100707.152611-1.pom
583b uploaded (parent-1-20100707.152611-1.pom)
[INFO] Retrieving previous metadata from seccasnapshots
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
'39b09dae90456d0a47c1cc626d8b582235631de6' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
'39b09dae90456d0a47c1cc626d8b582235631de6' - IGNORING
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error installing artifact's metadata: Error installing metadata:
Error updating group repository metadata
in epilog non whitespace content is not allowed but got t (position:
END_TAG seen ...</metadata>\nt... @9:2)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Wed Jul 07 23:26:11 CST 2010
[INFO] Final Memory: 9M/17M
[INFO]
------------------------------------------------------------------------
I have no idea what to do next.
Thanks,
Lenik
Re: `mvn deploy' failed
Posted by Olivier Dehon <od...@gmail.com>.
On Thu, 2010-07-08 at 14:58 +1000, Brett Porter wrote:
> On 08/07/2010, at 1:46 PM, Olivier Dehon wrote:
>
> > I am getting these kinds of metadata corruption all the time.
> >
> > It seems to be linked to concurrent writes by mvn deploy (from
> > Continuum) and the Archiva "consumers" to fix the metadata. Notably,
> > after a release, the first snapshot build seems to get this "corrupted
> > metadata" error a lot, which I would link to the Archiva consumer that
> > deletes snapshots of released versions.
>
> This is a possibility we should investigate.
>
> Have you tried adjusting the scanning & build schedules to ensure they don't conflict?
>
As a matter of fact, after a bit more analysis on this issue (getting
forced builds only), it seems that Archiva is the sole culprit for the
corruption, and it doesn't seem linked to concurrency between continuum
deploys and Archiva metadata "fixing", but more like Archiva is
corrupting the metadata all by itself.
And in all cases that I have seen so far, this happens after the first
snapshot build that follows a release... The metadata file that gets
corrupted is the one that sits next to the "version" folders, not the
one next to the .pom and .jar files.
It is hard to give more info as the issue happens randomly, but
definitely too often for it to be a mere concurrency issue. Or maybe
concurrency between 2 different consumers within Archiva.
Thanks for your insights.
-Olivier
Re: `mvn deploy' failed
Posted by Brett Porter <br...@apache.org>.
On 08/07/2010, at 1:46 PM, Olivier Dehon wrote:
> I am getting these kinds of metadata corruption all the time.
>
> It seems to be linked to concurrent writes by mvn deploy (from
> Continuum) and the Archiva "consumers" to fix the metadata. Notably,
> after a release, the first snapshot build seems to get this "corrupted
> metadata" error a lot, which I would link to the Archiva consumer that
> deletes snapshots of released versions.
This is a possibility we should investigate.
Have you tried adjusting the scanning & build schedules to ensure they don't conflict?
>
> Another investigative track I am trying to follow is the potential
> discrepancy between the metadata model used by maven 2.2.1 (and its
> associated deploy plugin) and the one used by Archiva 1.2.x.
This was a problem in Maven 2.1.0 and Archiva 1.1.3 (Maven started writing namespace & xml headers Archiva wasn't prepared for), but shouldn't be an issue with newer versions of either in use.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: `mvn deploy' failed
Posted by Olivier Dehon <od...@gmail.com>.
I am getting these kinds of metadata corruption all the time.
It seems to be linked to concurrent writes by mvn deploy (from
Continuum) and the Archiva "consumers" to fix the metadata. Notably,
after a release, the first snapshot build seems to get this "corrupted
metadata" error a lot, which I would link to the Archiva consumer that
deletes snapshots of released versions.
Another investigative track I am trying to follow is the potential
discrepancy between the metadata model used by maven 2.2.1 (and its
associated deploy plugin) and the one used by Archiva 1.2.x.
If anyone has any hints/pointers/advice, I'd be glad to read them.
Thanks in advance, -Olivier
On Thu, 2010-07-08 at 09:48 +0800, Deng Ching wrote:
> Can you check if the metadata file is correct? It looks like there are some
> escape characters that got in the metadata file..
>
> On Wed, Jul 7, 2010 at 11:30 PM, Lenik <le...@bodz.net> wrote:
>
> > The output:
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Building SECCA :: SEMS :: Parent
> > [INFO] task-segment: [deploy]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> > [INFO] [install:install {execution: default-install}]
> > [INFO] Installing /home/appserv/build/parent/pom.xml to
> > /home/appserv/.m2/repository/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-SNAPSHOT.pom
> > [INFO] [deploy:deploy {execution: default-deploy}]
> > [INFO] Retrieving previous build number from seccasnapshots
> > [INFO] repository metadata for: 'snapshot
> > com.seccaproject.sems:parent:1-SNAPSHOT' could not be found on repository:
> > seccasnapshots, so will be created
> > Uploading:
> > http://m2.secca-project.com/snapshots/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-20100707.152611-1.pom
> > 583b uploaded (parent-1-20100707.152611-1.pom)
> > [INFO] Retrieving previous metadata from seccasnapshots
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
> > '39b09dae90456d0a47c1cc626d8b582235631de6' - RETRYING
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
> > '39b09dae90456d0a47c1cc626d8b582235631de6' - IGNORING
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Error installing artifact's metadata: Error installing metadata:
> > Error updating group repository metadata
> >
> > in epilog non whitespace content is not allowed but got t (position:
> > END_TAG seen ...</metadata>\nt... @9:2)
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 9 seconds
> > [INFO] Finished at: Wed Jul 07 23:26:11 CST 2010
> > [INFO] Final Memory: 9M/17M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> >
> >
> >
> > I have no idea what to do next.
> >
> > Thanks,
> > Lenik
> >
Re: `mvn deploy' failed
Posted by Lenik <le...@bodz.net>.
Yes, I've fixed this problem by deleteing the folder containing the
broken metadata files.
But this broken artifact is one in a million files in the m2 repository,
how do I scan/check all the rest? I can 'scan now' a repository in the
Archiva admin page, but it only discovers if there are new ones, and
never check the file checksum again the metadata. Is it possible to do
this integrity-check-and-fix within archiva?
Thanks,
Lenik
On 2010-7-8 09:48, Deng Ching wrote:
> Can you check if the metadata file is correct? It looks like there are some
> escape characters that got in the metadata file..
>
> On Wed, Jul 7, 2010 at 11:30 PM, Lenik<le...@bodz.net> wrote:
>
>
>> The output:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building SECCA :: SEMS :: Parent
>> [INFO] task-segment: [deploy]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
>> [INFO] [install:install {execution: default-install}]
>> [INFO] Installing /home/appserv/build/parent/pom.xml to
>> /home/appserv/.m2/repository/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-SNAPSHOT.pom
>> [INFO] [deploy:deploy {execution: default-deploy}]
>> [INFO] Retrieving previous build number from seccasnapshots
>> [INFO] repository metadata for: 'snapshot
>> com.seccaproject.sems:parent:1-SNAPSHOT' could not be found on repository:
>> seccasnapshots, so will be created
>> Uploading:
>> http://m2.secca-project.com/snapshots/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-20100707.152611-1.pom
>> 583b uploaded (parent-1-20100707.152611-1.pom)
>> [INFO] Retrieving previous metadata from seccasnapshots
>> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>> 'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
>> '39b09dae90456d0a47c1cc626d8b582235631de6' - RETRYING
>> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
>> 'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
>> '39b09dae90456d0a47c1cc626d8b582235631de6' - IGNORING
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error installing artifact's metadata: Error installing metadata:
>> Error updating group repository metadata
>>
>> in epilog non whitespace content is not allowed but got t (position:
>> END_TAG seen ...</metadata>\nt... @9:2)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 9 seconds
>> [INFO] Finished at: Wed Jul 07 23:26:11 CST 2010
>> [INFO] Final Memory: 9M/17M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>>
>>
>> I have no idea what to do next.
>>
>> Thanks,
>> Lenik
>>
>>
>
>
Re: `mvn deploy' failed
Posted by Deng Ching <oc...@apache.org>.
Can you check if the metadata file is correct? It looks like there are some
escape characters that got in the metadata file..
On Wed, Jul 7, 2010 at 11:30 PM, Lenik <le...@bodz.net> wrote:
> The output:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building SECCA :: SEMS :: Parent
> [INFO] task-segment: [deploy]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
> [INFO] [install:install {execution: default-install}]
> [INFO] Installing /home/appserv/build/parent/pom.xml to
> /home/appserv/.m2/repository/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-SNAPSHOT.pom
> [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Retrieving previous build number from seccasnapshots
> [INFO] repository metadata for: 'snapshot
> com.seccaproject.sems:parent:1-SNAPSHOT' could not be found on repository:
> seccasnapshots, so will be created
> Uploading:
> http://m2.secca-project.com/snapshots/com/seccaproject/sems/parent/1-SNAPSHOT/parent-1-20100707.152611-1.pom
> 583b uploaded (parent-1-20100707.152611-1.pom)
> [INFO] Retrieving previous metadata from seccasnapshots
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
> '39b09dae90456d0a47c1cc626d8b582235631de6' - RETRYING
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'ca2ed90f79e38f171313fe040d7275d48c206350'; remote =
> '39b09dae90456d0a47c1cc626d8b582235631de6' - IGNORING
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error installing artifact's metadata: Error installing metadata:
> Error updating group repository metadata
>
> in epilog non whitespace content is not allowed but got t (position:
> END_TAG seen ...</metadata>\nt... @9:2)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 9 seconds
> [INFO] Finished at: Wed Jul 07 23:26:11 CST 2010
> [INFO] Final Memory: 9M/17M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
>
> I have no idea what to do next.
>
> Thanks,
> Lenik
>