The problem was fixed and we are back up. We are running the server in
debug mode for now, to catch assertions and have faster turn-a-rounds
on bugs like this. That means queries will be somewhat slower. The
load on the server is pretty low however, so I don't expect any
serious performance
On 02/11/15 19:34, Patrick Niklaus wrote:
> We are not sure yet what is causing the problems with the current
> dataset. I'm currently digging through the changesets.
http://osrm.rdm2.co.uk/ is up and running again. Looks like the problem
on mine was an SUSE update that messed something up, but
On 02/11/15 15:14, Patrick Niklaus wrote:
> What version are you running? Our production servers are definitely
> working with the current OSM extracts.
My update process had stopped which is why I was asking if your problem
was related to something similar or a local hardware problem? I do need
What version are you running? Our production servers are definitely
working with the current OSM extracts.
On Sun, Nov 1, 2015 at 9:53 PM, Lester Caine wrote:
> On 01/11/15 20:42, Patrick Niklaus wrote:
>> The data on the demo server seems to have gotten corrupted. We are
>>
We are not sure yet what is causing the problems with the current
dataset. I'm currently digging through the changesets.
In the meantime the data on the demo server is frozen to the 30th October.
On Mon, Nov 2, 2015 at 4:34 PM, Lester Caine wrote:
> On 02/11/15 15:14,
Hey,
The data on the demo server seems to have gotten corrupted. We are
currently reverting back to an older dataset, while we investigate
what went wrong. Should be all up and running in a few hours.
Best,
Patrick
___
OSRM-talk mailing list