[osmosis-dev] Specifying ports for replication

[Paul Norman]

So, the problem went away and I didn't bother debugging the cause, but it's
intermittently back now. 

> From: Igor Podolskiy [mailto:igor.podolskiy at vwi-stuttgart.de]
> Subject: Re: [osmosis-dev] Specifying ports for replication
> 
> 
> On 17.06.2012 06:46, Paul Norman wrote:
> > I'm trying to get script to work to update my apidb, but I keep
> > getting errors with trying to specify the location of the minutely
> > replication diffs. I suspect it is related to the port in my change
> > file URL
> >
> > My simplified command line is osmosis --rri --sc --wdc
> >
> > I have tried both
> >
> > baseUrl=http://merry.paulnorman.ca:7201/minute-redaction-replicate/
> >
> > and
> >
> > baseUrl=http://merry.paulnorman.ca\:7201/minute-redaction-replicate/
> >
> > The error I get is:
> >[...]
> 
> Hmm... Sadly I cannot reproduce this. No matter whether I'm using
> 
>    http://my.server.local/planet/replicate
> 
> or
> 
>    http://my.server.local:80/planet/replicate
> 
> it works fine. From the stack trace you posted it looks like your server
> is returning a malformed response. Here are some things to check:
> 
> 1. Is there any information regarding those requests access and error
> logs of the HTTP server listening on port 7201? The relevant entries
> should look like:
> 
> 127.0.0.1 - - [23/Jun/2012:13:37:05 +0200] "GET /minute-redaction-
> replicate/state.txt HTTP/1.1" 200 409 "-" "Java/1.6.0_24"

When it's working it shows them, but I don't believe it's showing attempted
accesses by osmosis when it's not working.

> 2. Could you try to access
> 
>    http://merry.paulnorman.ca:7201/minute-redaction-replicate/state.txt
> 
> with a web browser?

It shows a valid state.txt file. 

> If you don't see any log entries in the access or error logs that you
> can relate to Osmosis, then there is most probably some kind of a
> network problem between your client and your server machine. Or maybe
> the server on port 7201 isn't running? :)

It's running, and the client is running on the server. Also it works for
other applications that consume minutely diffs.

It would be helpful if osmosis gave a less cryptic error message.