Re: [OSM-talk] Replication errors

2020-04-16 Thread Andrzej Kępys
Thanks for all answers - latest version of osmosis fixed problem. I've 
also following operations tweeter from now on :)



Pozdrawiam
Andrzej Kępys
gg: 7918247
skype: jedrus305
tel: 605 997 440

W dniu 16.04.2020 o 10:35, Simon Poole pisze:

Sarah has already given the answer, but a small remark anyway: I would
suggest following the operations twitter account
https://twitter.com/OSM_Tech as that is the place you are most likely to
see short term notices about these kind of things.

Simon

Am 16.04.2020 um 08:10 schrieb Andrzej Kępys:

Hi All!

Since few days I have a replication errors using osmosis... Any ideas
how to fix it? Is there anythink I can do or it's sth about a data?

---START
Thu Apr 16 08:05:01 CEST 2020
No current.osc file found, downloading new one...
Apr 16, 2020 8:05:02 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Osmosis Version 0.46
Apr 16, 2020 8:05:02 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Preparing pipeline.
Apr 16, 2020 8:05:02 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Launching pipeline execution.
Apr 16, 2020 8:05:02 AM org.openstreetmap.osmosis.core.Osmosis run
INFO: Pipeline executing, waiting for completion.
Apr 16, 2020 8:05:03 AM
org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager
waitForCompletion
SEVERE: Thread for task 1-read-replication-interval failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Unable to
parse xml file /tmp/change8964114732320454958.tmp.  publicId=(null),
systemId=(null), lineNumber=1775, columnNumber=22.
 at
org.openstreetmap.osmosis.xml.v0_6.XmlChangeReader.run(XmlChangeReader.java:100)
 at
org.openstreetmap.osmosis.replication.v0_6.ReplicationDownloader.processChangeset(ReplicationDownloader.java:107)
 at
org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.processReplicationFile(BaseReplicationDownloader.java:133)
 at
org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.download(BaseReplicationDownloader.java:235)
 at
org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.runImpl(BaseReplicationDownloader.java:271)
 at
org.openstreetmap.osmosis.replication.v0_6.BaseReplicationDownloader.run(BaseReplicationDownloader.java:350)
 at java.lang.Thread.run(Thread.java:748)
Caused by: org.xml.sax.SAXParseException; lineNumber: 1775;
columnNumber: 22; Invalid byte 2 of 4-byte UTF-8 sequence.
 at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
 at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
Source)
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
 at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
 at
org.openstreetmap.osmosis.xml.v0_6.XmlChangeReader.run(XmlChangeReader.java:90)
 ... 6 more
Caused by: org.apache.xerces.impl.io.MalformedByteSequenceException:
Invalid byte 2 of 4-byte UTF-8 sequence.
 at org.apache.xerces.impl.io.UTF8Reader.invalidByte(Unknown Source)
 at org.apache.xerces.impl.io.UTF8Reader.read(Unknown Source)
 at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
 at org.apache.xerces.impl.XMLEntityScanner.scanLiteral(Unknown
Source)
 at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown
Source)
 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown
Source)
 at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown
Source)
 ... 16 more

Apr 16, 2020 8:05:03 AM 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:62)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498

[OSM-talk] Replication errors

2020-04-16 Thread Andrzej Kępys
)


--
Pozdrawiam
Andrzej Kępys
gg: 7918247
skype: jedrus305
tel: 605 997 440


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


Re: [OSM-talk] Issues with diffs

2018-05-09 Thread Andrzej Kępys

Hi

Thank you all for answers. Firstly I was sure that something broke my 
state.txt file, but I checked it and it was OK. Than I've tried some 
different one so I've copied from diffs folder - still no luck. I was 
sure something broke there - things like this happens sometimes, but as 
far as I remember they last no longer than 1 hour...


You were right - it was https... one small letter for the config but 
such big difference for all server ;)


Thanks again

Andy


Pozdrawiam
Andrzej Kępys
gg: 7918247
skype: jedrus305
tel: 605 997 440

W dniu 2018-05-09 o 20:50, Andy Townsend pisze:

On 09/05/2018 19:21, Andrzej Kępys wrote:


OsmosisRuntimeException: The replication state doesn't contain a 
timestamp property.


Any idea where can I post/report this?


Here (or the dev list) is as good a place as any :)

What this normally means is that osmosis has somehow "become confused" 
- somehow some invalid replication data appeared, or you tried to 
reset the replication data and something failed, or you tried to reset 
the replication date for the first time since the http -> https move 
happened.


Here's what's in /var/lib/mod_tile/.osmosis/state.txt on a server of 
mine right now:


#Wed May 09 20:40:05 CEST 2018
sequenceNumber=2963281
timestamp=2018-05-09T18\:39\:01Z

You should have something similar.  If you have something other than a 
valid sequenceNumber / timestamp combination, try resetting the 
replication date to a known-good value.  Typically I'd do that with 
"openstreetmap-tiles-update-expire".  Note that when the OSM servers 
moved from http to https a change to that was needed to ensure that 
the files are obtained from https URLs (since osmosis didn't follow 
redirects).  In the version that I use (and the version referred to by 
the switch2osm guide) that is:


https://github.com/SomeoneElseOSM/mod_tile/blob/switch2osm/openstreetmap-tiles-update-expire#L114 



Best Regards,

Andy





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



---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie 
antywirusowe Avast.
https://www.avast.com/antivirus


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


[OSM-talk] Issues with diffs

2018-05-09 Thread Andrzej Kępys

Hi.

Since about 12 hours I'm having issues with replication.

Osmosis is reporting:

OsmosisRuntimeException: The replication state doesn't contain a timestamp 
property.

Any idea where can I post/report this?

--
Pozdrawiam
Andrzej Kępys
gg: 7918247
skype: jedrus305
tel: 605 997 440


---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie 
antywirusowe Avast.
https://www.avast.com/antivirus


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