This is a static archive of our old OSM Help Site. Please post any new questions and answers at community.openstreetmap.org.

osmosis permanent breakdown: “pipes have not been terminated with appropriate output sinks”

1

I terminated osmosis several times during the run by Ctrl+c, and now it cannot do enen simplest tasks, giving an error: "The following named pipes () and 1 default pipes have not been terminated with appropriate output sinks."

$ osmosis --rx file="my.xml"
14.05.2016 14:24:29 org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.44.1
14.05.2016 14:24:29 org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
14.05.2016 14:24:29 org.openstreetmap.osmosis.core.Osmosis main
SEVERE: Execution aborted.
org.openstreetmap.osmosis.core.OsmosisRuntimeException: The following named pipes () and 1 default pipes have not been terminated with appropriate output sinks.
at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.connectTasks(Pipeline.java:94)
at org.openstreetmap.osmosis.core.pipeline.common.Pipeline.prepare(Pipeline.java:116)
at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:86)
at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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)

I'm on OSX 10.8, rebooting or even

 brew uninstall osmosis
 brew install osmosis

don't help. How can I fix it?

asked 14 May '16, 12:29

Pantlmn's gravatar image

Pantlmn
91226
accept rate: 0%


One Answer:

2

The command you are using will yield this error message on any system. The --rx opens a pipe and puts data in it. Osmosis expects you to specify where this data should go, but you don't. Add --write-null to your command line (which means "discard the data") and it will stop complaining. Of course, to make Osmosis do something useful, you'll have to specify something else than --write-null...

answered 14 May '16, 13:05

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
82.5k927201273
accept rate: 23%

1

Thanks, that's my fault. --wx file="NNN" fixes that.

(14 May '16, 13:18) Pantlmn
(18 May '16, 10:08) Piskvor