Modify

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#14898 closed defect (othersoftware)

Upload failure

Reported by: szhvilmos@… Owned by: team
Priority: major Milestone:
Component: Core Version: latest
Keywords: template_report upload regression api Cc: michael2402, bastiK

Description

What steps will reproduce the problem?

  1. when I try to upload my edition to osm cant do that
  2. every second time its happen (OSM version 12275)
  3. I close the OSM, and run again, and after this I can upload the file to OSM server

What is the expected result?

What happens instead?

Please provide any additional information below. Attach a screenshot if possible.

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-05-29 16:19:58 +0200 (Mon, 29 May 2017)
Build-Date:2017-05-29 14:25:03
Revision:12275
Relative:URL: ^/trunk

Identification: JOSM/1.5 (12275 hu) Linux Linux Mint 18 Sarah
Memory Usage: 874 MB / 3536 MB (639 MB allocated, but free)
Java version: 1.8.0_131-8u131-b11-0ubuntu1.16.04.2-b11, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1280x1024
Maximum Screen Size: 1280x1024
Java package: openjdk-8-jre:amd64-8u131-b11-0ubuntu1.16.04.2
Dataset consistency test: No problems found

Tagging presets:
+ https://josm.openstreetmap.de/josmfile?page=Presets/Turistautkapcsolat&zip=1
+ https://raw.githubusercontent.com/yopaseopor/traffic_signs_preset_JOSM/master/HU.zip
+ https://josm.openstreetmap.de/josmfile?page=Presets/Mountains&zip=1

Map paint styles:
+ https://josm.openstreetmap.de/josmfile?page=Styles/Mountains&zip=1

Last errors/warnings:
- W: java.net.SocketTimeoutException: connect timed out
- W: java.net.SocketTimeoutException: connect timed out
- E: Error body: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=500, Error Body=<<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
- E: Belső kiszolgálóhiba - <html>Az OSM szerver<br>'https://api.openstreetmap.org/api/0.6/'<br>belső szerverhibát jelentett.<br>Ez valószínűleg átmeneti probléma. Kérlek, próbáld újra később.</html>
- E: org.openstreetmap.josm.io.OsmTransferCanceledException: Operation canceled in retry #3
- E: org.openstreetmap.josm.io.OsmTransferCanceledException: Operation canceled
- E: org.openstreetmap.josm.io.OsmTransferCanceledException: Operation canceled
- E: Handled by bug report queue: org.openstreetmap.josm.io.OsmTransferCanceledException: Operation canceled
- W: 1 problems occured during upload/save


=== REPORTED CRASH DATA ===
BugReportExceptionHandler#handleException:
No data collected.

Warning issued by: BugReportExceptionHandler#handleException

=== STACK TRACE ===
Thread: AWT-EventQueue-0 (17) of main
org.openstreetmap.josm.io.OsmTransferCanceledException: Operation canceled
	at org.openstreetmap.josm.io.OsmApi.sleepAndListen(OsmApi.java:560)
	at org.openstreetmap.josm.io.OsmApi.sendRequest(OsmApi.java:658)
	at org.openstreetmap.josm.io.OsmApi.sendRequest(OsmApi.java:600)
	at org.openstreetmap.josm.io.OsmApi.updateChangeset(OsmApi.java:456)
	at org.openstreetmap.josm.io.OsmServerWriter.uploadOsm(OsmServerWriter.java:207)
	at org.openstreetmap.josm.gui.io.UploadLayerTask.run(UploadLayerTask.java:124)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

Attachments (0)

Change History (14)

comment:1 by Don-vip, 7 years ago

Cc: michael2402 bastiK added
Keywords: upload regression added
Priority: normalmajor

It seems we have a regression on upload, as we have many reports of people unable to upload their data: #14900 #14910 #14920

comment:2 by Don-vip, 7 years ago

Milestone: 17.06

comment:3 by Don-vip, 7 years ago

Ticket #14900 has been marked as a duplicate of this ticket.

comment:4 by Don-vip, 7 years ago

Ticket #14910 has been marked as a duplicate of this ticket.

comment:5 by Don-vip, 7 years ago

Ticket #14920 has been marked as a duplicate of this ticket.

comment:6 by wambacher, 7 years ago

This happens only when i want to add changes to the still open changeset. Closing the current changeset without leaving JOOM helps, but the next upload will fail again.

comment:7 by anonymous, 7 years ago

Here is also the problem (JOSM 12275)

comment:8 by anonymous, 7 years ago

As a workaround sending to server without keep changeset open seems works

comment:9 by Don-vip, 7 years ago

Ticket #14932 has been marked as a duplicate of this ticket.

comment:10 by Don-vip, 7 years ago

Summary: upload faliureUpload failure

comment:11 by anonymous, 7 years ago

Seems to be a server side issue?
Just tested with some old versions from March 2016 and March 2017 (which worked before), they also fail to upload the second time to the same changeset.

comment:12 by anonymous, 7 years ago

Server error message on second upload to the same changeset:

Application error

The OpenStreetMap server encountered an unexpected condition that prevented it from fulfilling the request (HTTP 500)
Feel free to contact the OpenStreetMap community if your problem persists. Make a note of the exact URL / post data of your request.
This may be a problem in our Ruby On Rails code. 500 occurs with exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code)

comment:13 by bastiK, 7 years ago

Resolution: othersoftware
Status: newclosed

I've reported the problem on IRC and it got fixed right away. (https://git.openstreetmap.org/rails.git/commitdiff/ea9a4c2)

comment:14 by Don-vip, 7 years ago

Keywords: api added
Milestone: 17.06

great!

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.