Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Michael Kussmaul]

Hi Brett

I tried with --sort-change, but had the same result.

It looks like I need to re-import the full planet again and then go on with 
daily updates - I just hope the error does not get propagated further along in 
the daily-diffs.

many thanks for your investigation!
Michael

> On 12.05.2016, at 12:33, Brett Henderson  wrote:
> 
> 
> Actually, on closer inspection of the error it looks like the same node 
> (257882) is appearing twice with the same version.  I doubt if sorting will 
> help.  I don't think Osmosis has a way to fix this issue.  The simplify 
> change task could probably cope with it, but the input validation may be too 
> strict.  It may be necessary to fix the file manually ...
> 
> On Thu, 12 May 2016 at 20:30 Brett Henderson  > wrote:
> Okay, so the --simplify-change task is failing because it requires sorted 
> input.
> 
> Can you try this?  It will sort the changes before attempting to simplify 
> them.
> osmosis —read-replication-interval workingDirectory=/import/data/diffs/ 
> --sort-change --simplify-change --write-xml-change 
> /import/data/diffs/data/changes.osc.gz
> 
> 
> On Thu, 12 May 2016 at 19:43 Michael Kussmaul  > wrote:
> Hi Brett
> 
> Sure, here is my stack trace:
> 
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Osmosis Version 0.44.1
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Preparing pipeline.
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Launching pipeline execution.
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Pipeline executing, waiting for completion.
> May 11, 2016 1:48:18 PM 
> org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager 
> waitForCompletion
> SEVERE: Thread for task 1-read-replication-interval failed
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities are 
> not sorted, previous entity type=Node, id=257882, version=5 current entity 
> type=Node, id=257882, version=5.
>   at 
> org.openstreetmap.osmosis.core.sort.v0_6.SortedHistoryChangePipeValidator.process(SortedHistoryChangePipeValidator.java:59)
>   at 
> org.openstreetmap.osmosis.set.v0_6.ChangeSimplifier.process(ChangeSimplifier.java:50)
>   at 
> org.openstreetmap.osmosis.core.sort.v0_6.ChangeSorter.complete(ChangeSorter.java:73)
>   at 
> org.openstreetmap.osmosis.replication.v0_6.ReplicationDownloader.processComplete(ReplicationDownloader.java:116)
>   at 
> org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.runImpl(BaseReplicationDownloader.java:313)
>   at 
> org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.run(BaseReplicationDownloader.java:383)
>   at java.lang.Thread.run(Thread.java:744)
> 
> May 11, 2016 1:48:18 PM org.openstreetmap.osmosis.core.Osmosis main
> SEVERE: Execution aborted.
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks 
> failed.
>   at 
> org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146)
>   at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:92)
>   at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> 
> 
> 
>> On 12.05.2016, at 05:15, Brett Henderson > > wrote:
>> 
>> Can you provide more of the stack trace?  It would be helpful to see exactly 
>> which task in the pipeline is failing.  It *may* be possible to workaround 
>> it it with an intermediate sort task.
>> 
>> On Wed, 11 May 2016 at 21:43 Michael Kussmaul > > wrote:
>> Yes, I see the same problem, I’m using osmosis to keep my local planet file 
>> up-to-date and now see the same error as Jan Michel:
>> 
>> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities 
>> are not sorted, previous entity type=Node, id=257882, version=5 current 
>> entity type=Node, id=257882, version=5.
>> 
>> Again node 257882.
>> 
>> My osmosis command:
>> osmosis —read-replication-interval workingDirectory=/import/data/diffs/ 
>> --simplify-change --write-xml-change /import/data/diffs/data/changes.osc.gz
>> 
>> kind regards
>>

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Brett Henderson]

Actually, on closer inspection of the error it looks like the same node
(257882) is appearing twice with the same version.  I doubt if sorting will
help.  I don't think Osmosis has a way to fix this issue.  The simplify
change task could probably cope with it, but the input validation may be
too strict.  It may be necessary to fix the file manually ...

On Thu, 12 May 2016 at 20:30 Brett Henderson  wrote:

> Okay, so the --simplify-change task is failing because it requires sorted
> input.
>
> Can you try this?  It will sort the changes before attempting to simplify
> them.
> osmosis —read-replication-interval workingDirectory=/import/data/diffs/
> *--sort-change* --simplify-change --write-xml-change
> /import/data/diffs/data/changes.osc.gz
>
>
> On Thu, 12 May 2016 at 19:43 Michael Kussmaul 
> wrote:
>
>> Hi Brett
>>
>> Sure, here is my stack trace:
>>
>> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
>> INFO: Osmosis Version 0.44.1
>> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
>> INFO: Preparing pipeline.
>> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
>> INFO: Launching pipeline execution.
>> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
>> INFO: Pipeline executing, waiting for completion.
>> May 11, 2016 1:48:18 PM
>> org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager
>> waitForCompletion
>> SEVERE: Thread for task 1-read-replication-interval failed
>> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities
>> are not sorted, previous entity type=Node, id=257882, version=5 current
>> entity type=Node, id=257882, version=5.
>> at
>> org.openstreetmap.osmosis.core.sort.v0_6.SortedHistoryChangePipeValidator.process(SortedHistoryChangeP
>> ipeValidator.java:59)
>> at
>> org.openstreetmap.osmosis.set.v0_6.ChangeSimplifier.process(ChangeSimplifier.java:50)
>> at
>> org.openstreetmap.osmosis.core.sort.v0_6.ChangeSorter.complete(ChangeSorter.java:73)
>> at
>> org.openstreetmap.osmosis.replication.v0_6.ReplicationDownloader.processComplete(ReplicationDownloader
>> .java:116)
>> at
>> org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.runImpl(BaseReplicationDownloader
>> .java:313)
>> at
>> org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.run(BaseReplicationDownloader.jav
>> a:383)
>> at java.lang.Thread.run(Thread.java:744)
>>
>> May 11, 2016 1:48:18 PM org.openstreetmap.osmosis.core.Osmosis main
>> SEVERE: Execution aborted.
>> org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks
>> failed.
>> at
>> org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146)
>> at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:92)
>> at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
>>
>>
>>
>> On 12.05.2016, at 05:15, Brett Henderson  wrote:
>>
>> Can you provide more of the stack trace?  It would be helpful to see
>> exactly which task in the pipeline is failing.  It *may* be possible to
>> workaround it it with an intermediate sort task.
>>
>> On Wed, 11 May 2016 at 21:43 Michael Kussmaul 
>> wrote:
>>
>>> Yes, I see the same problem, I’m using osmosis to keep my local planet
>>> file up-to-date and now see the same error as Jan Michel:
>>>
>>> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline
>>> entities are not sorted, previous entity type=Node, id=257882, version=5
>>> current entity type=Node, id=257882, version=5.
>>>
>>> Again node 257882.
>>>
>>> My osmosis command:
>>> osmosis —read-replication-interval workingDirectory=/import/data/diffs/
>>> --simplify-change --write-xml-change /import/data/diffs/data/changes.osc.gz
>>>
>>> kind regards
>>> Michael
>>> ___
>>> dev mailing list
>>> dev@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/dev
>>>
>>
>>
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Brett Henderson]

Okay, so the --simplify-change task is failing because it requires sorted
input.

Can you try this?  It will sort the changes before attempting to simplify
them.
osmosis —read-replication-interval workingDirectory=/import/data/diffs/
*--sort-change* --simplify-change --write-xml-change
/import/data/diffs/data/changes.osc.gz


On Thu, 12 May 2016 at 19:43 Michael Kussmaul  wrote:

> Hi Brett
>
> Sure, here is my stack trace:
>
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Osmosis Version 0.44.1
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Preparing pipeline.
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Launching pipeline execution.
> May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
> INFO: Pipeline executing, waiting for completion.
> May 11, 2016 1:48:18 PM
> org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager
> waitForCompletion
> SEVERE: Thread for task 1-read-replication-interval failed
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities
> are not sorted, previous entity type=Node, id=257882, version=5 current
> entity type=Node, id=257882, version=5.
> at
> org.openstreetmap.osmosis.core.sort.v0_6.SortedHistoryChangePipeValidator.process(SortedHistoryChangeP
> ipeValidator.java:59)
> at
> org.openstreetmap.osmosis.set.v0_6.ChangeSimplifier.process(ChangeSimplifier.java:50)
> at
> org.openstreetmap.osmosis.core.sort.v0_6.ChangeSorter.complete(ChangeSorter.java:73)
> at
> org.openstreetmap.osmosis.replication.v0_6.ReplicationDownloader.processComplete(ReplicationDownloader
> .java:116)
> at
> org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.runImpl(BaseReplicationDownloader
> .java:313)
> at
> org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.run(BaseReplicationDownloader.jav
> a:383)
> at java.lang.Thread.run(Thread.java:744)
>
> May 11, 2016 1:48:18 PM org.openstreetmap.osmosis.core.Osmosis main
> SEVERE: Execution aborted.
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks
> failed.
> at
> org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146)
> at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:92)
> at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
>
>
>
> On 12.05.2016, at 05:15, Brett Henderson  wrote:
>
> Can you provide more of the stack trace?  It would be helpful to see
> exactly which task in the pipeline is failing.  It *may* be possible to
> workaround it it with an intermediate sort task.
>
> On Wed, 11 May 2016 at 21:43 Michael Kussmaul 
> wrote:
>
>> Yes, I see the same problem, I’m using osmosis to keep my local planet
>> file up-to-date and now see the same error as Jan Michel:
>>
>> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities
>> are not sorted, previous entity type=Node, id=257882, version=5 current
>> entity type=Node, id=257882, version=5.
>>
>> Again node 257882.
>>
>> My osmosis command:
>> osmosis —read-replication-interval workingDirectory=/import/data/diffs/
>> --simplify-change --write-xml-change /import/data/diffs/data/changes.osc.gz
>>
>> kind regards
>> Michael
>> ___
>> dev mailing list
>> dev@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/dev
>>
>
>
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Michael Kussmaul]

Hi Brett

Sure, here is my stack trace:

May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.44.1
May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Launching pipeline execution.
May 11, 2016 1:34:36 PM org.openstreetmap.osmosis.core.Osmosis run
INFO: Pipeline executing, waiting for completion.
May 11, 2016 1:48:18 PM 
org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager 
waitForCompletion
SEVERE: Thread for task 1-read-replication-interval failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities are 
not sorted, previous entity type=Node, id=257882, version=5 current entity 
type=Node, id=257882, version=5.
at 
org.openstreetmap.osmosis.core.sort.v0_6.SortedHistoryChangePipeValidator.process(SortedHistoryChangePipeValidator.java:59)
at 
org.openstreetmap.osmosis.set.v0_6.ChangeSimplifier.process(ChangeSimplifier.java:50)
at 
org.openstreetmap.osmosis.core.sort.v0_6.ChangeSorter.complete(ChangeSorter.java:73)
at 
org.openstreetmap.osmosis.replication.v0_6.ReplicationDownloader.processComplete(ReplicationDownloader.java:116)
at 
org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.runImpl(BaseReplicationDownloader.java:313)
at 
org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.run(BaseReplicationDownloader.java:383)
at java.lang.Thread.run(Thread.java:744)

May 11, 2016 1:48:18 PM org.openstreetmap.osmosis.core.Osmosis main
SEVERE: Execution aborted.
org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks 
failed.
at 
org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146)
at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:92)
at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)



> On 12.05.2016, at 05:15, Brett Henderson  wrote:
> 
> Can you provide more of the stack trace?  It would be helpful to see exactly 
> which task in the pipeline is failing.  It *may* be possible to workaround it 
> it with an intermediate sort task.
> 
> On Wed, 11 May 2016 at 21:43 Michael Kussmaul  > wrote:
> Yes, I see the same problem, I’m using osmosis to keep my local planet file 
> up-to-date and now see the same error as Jan Michel:
> 
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities are 
> not sorted, previous entity type=Node, id=257882, version=5 current entity 
> type=Node, id=257882, version=5.
> 
> Again node 257882.
> 
> My osmosis command:
> osmosis —read-replication-interval workingDirectory=/import/data/diffs/ 
> --simplify-change --write-xml-change /import/data/diffs/data/changes.osc.gz
> 
> kind regards
> Michael
> ___
> dev mailing list
> dev@openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/dev 
> 

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Brett Henderson]

Can you provide more of the stack trace?  It would be helpful to see
exactly which task in the pipeline is failing.  It *may* be possible to
workaround it it with an intermediate sort task.

On Wed, 11 May 2016 at 21:43 Michael Kussmaul  wrote:

> Yes, I see the same problem, I’m using osmosis to keep my local planet
> file up-to-date and now see the same error as Jan Michel:
>
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities
> are not sorted, previous entity type=Node, id=257882, version=5 current
> entity type=Node, id=257882, version=5.
>
> Again node 257882.
>
> My osmosis command:
> osmosis —read-replication-interval workingDirectory=/import/data/diffs/
> --simplify-change --write-xml-change /import/data/diffs/data/changes.osc.gz
>
> kind regards
> Michael
> ___
> dev mailing list
> dev@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/dev
>
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Michael Kussmaul]

Yes, I see the same problem, I’m using osmosis to keep my local planet file 
up-to-date and now see the same error as Jan Michel:

org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities are 
not sorted, previous entity type=Node, id=257882, version=5 current entity 
type=Node, id=257882, version=5.

Again node 257882.

My osmosis command:
osmosis —read-replication-interval workingDirectory=/import/data/diffs/ 
--simplify-change --write-xml-change /import/data/diffs/data/changes.osc.gz

kind regards
Michael
___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Jan Michel]

Hi,
I'm still having trouble updating the planet file from a week ago using 
daily diffs ( http://planet.osm.org/pbf/planet-160425.osm.pbf )
I get the same error on node http://www.osm.org/node/257882 , deleted on 
April 27th. I don't know whether this is related to this issue.


Jan

On 29.04.2016 23:41, Tom Hughes wrote:


There was an issue with the web server yesterday morning that led to one
of the hourly diffs not finishing properly which in turn led to
duplication in the next one. That then got folded into the daily which
is created by merging the hourlies.

I've emptied the failed hourly now, as I believe everything in it is
also in the following one, and rebuilt the daily.

Tom





___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Gerardo Velez]

Hello Tom,

Thanks it is fixed now.

Gerardo Vélez




-Mensaje original-
De: Tom Hughes [mailto:t...@compton.nu] 
Enviado el: viernes, 29 de abril de 2016 04:41 p.m.
Para: egve...@gscssoftware.com; dev@openstreetmap.org
Asunto: Re: Osmosis RuntimeException: Pipeline entities are not sorted

On 29/04/16 20:52, Gerardo Velez wrote:

> I’ve been using osmosis ver 0.44.1 to update my openstreetmap database 
> for at least a month without any problem, but today trying to process 
> http://planet.osm.org/replication/day/000/001/325.osc.gz change file I 
> got the following error:
>
> SEVERE: Thread for task 1-read-xml-change failed
>
> org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline 
> entities are not sorted, pr
>
> evious entity type=Node, id=199245, version=7 current entity 
> type=Node, id=199245, version=7

There was an issue with the web server yesterday morning that led to one of the 
hourly diffs not finishing properly which in turn led to duplication in the 
next one. That then got folded into the daily which is created by merging the 
hourlies.

I've emptied the failed hourly now, as I believe everything in it is also in 
the following one, and rebuilt the daily.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/


___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Re: [OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Tom Hughes]

On 29/04/16 20:52, Gerardo Velez wrote:


I’ve been using osmosis ver 0.44.1 to update my openstreetmap database
for at least a month without any problem, but today trying to process
http://planet.osm.org/replication/day/000/001/325.osc.gz change file I
got the following error:

SEVERE: Thread for task 1-read-xml-change failed

org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline
entities are not sorted, pr

evious entity type=Node, id=199245, version=7 current entity type=Node,
id=199245, version=7


There was an issue with the web server yesterday morning that led to one 
of the hourly diffs not finishing properly which in turn led to 
duplication in the next one. That then got folded into the daily which 
is created by merging the hourlies.


I've emptied the failed hourly now, as I believe everything in it is 
also in the following one, and rebuilt the daily.


Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

[OSM-dev] Osmosis RuntimeException: Pipeline entities are not sorted

[Gerardo Velez]

 

Hello,

 

I’ve been using osmosis ver 0.44.1 to update my openstreetmap database for
at least a month without any problem, but today trying to process
http://planet.osm.org/replication/day/000/001/325.osc.gz change file I got
the following error:

 

SEVERE: Thread for task 1-read-xml-change failed

org.openstreetmap.osmosis.core.OsmosisRuntimeException: Pipeline entities
are not sorted, pr

evious entity type=Node, id=199245, version=7 current entity type=Node,
id=199245, version=7

.

 

Looking at the changes file content I notice there are several lines with
exactly the same data which I suppose is the problem, like the following
lines:

 













 

What I did just to test was deleting the first one and reprocess the file,
the first error went away but I got the same error for other nodes so I
believe the duplicate data is the problem, as it was working perfect for a
time until today I guess the problem is in the changes file but it would
also be good if osmosis could handle this kind of issues, or if it already
handle them I’d appreciate some hints to remove all duplicate nodes and
process this change file. 

 

Thanks in advance for your help.  

 

Gerardo Vélez

 

 

 

 

___
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev