systemapic / pile

PostGIS tile server
0 stars 2 forks source link

Server blocks not sending any more logs #13

Closed strk closed 8 years ago

strk commented 8 years ago

The tiler is not giving any sign of life on style update. It did render the initial tiles:

pile_1 | rendered tile in  15 ms
pile_1 | rendered tile in  17 ms
pile_1 | rendered tile in  22 ms
pile_1 | rendered tile in  27 ms
pile_1 | rendered tile in  21 ms

But it didn't give any more signs of life when I hit "Update style" or navigated the map after that.

strk commented 8 years ago

This might actually be a systemapic.js bug as I don't see any attempt to even reload the page (using firebog). No error on the console.

strk commented 8 years ago

The logs from the wu server operation triggering an end of tiles:

wu_1          | [ 'layerUuid',
wu_1          |   'layer-c0838e31-c1bf-4cbe-bce1-85a6cef39160',
wu_1          |   'strk',
wu_1          |   { style: '{"point":{"enabled":false,"color":{"column":false,"range":[-426.6,105.9],"staticVal":"yellow","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]},"opacity":{"column":false,"range":[-426.6,105.9],"value":0.5},"pointsize":{"column":false,"range":[0,10],"value":1}},"polygon":{"enabled":true,"color":{"column":false,"range":[-426.6,105.9],"staticVal":"#111f7b","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]},"opacity":{"column":false,"range":[-426.6,105.9]},"line":{"width":{"column":false,"range":false,"value":1},"opacity":{"column":false,"range":[-426.6,105.9],"value":0.5},"color":{"column":false,"range":[-426.6,105.9],"staticVal":"green","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]}},"targets":[]},"line":{"enabled":false,"width":{"column":false,"range":false,"value":1},"opacity":{"column":false,"value":0.5},"color":{"column":false,"range":[-426.6,105.9],"staticVal":"green","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]}}}',
wu_1          |     layer: 'layer-c0838e31-c1bf-4cbe-bce1-85a6cef39160',
wu_1          |     uuid: 'project-fcd363c3-2913-4258-86c1-e40d043c8957',
wu_1          |     access_token: 'pk.bFeHn59Ze6OoImRbV5XIaLF9zBelmBxopycewkWP' } ]
wu_1          | [ 'up[date layer!',
wu_1          |   { style: '{"point":{"enabled":false,"color":{"column":false,"range":[-426.6,105.9],"staticVal":"yellow","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]},"opacity":{"column":false,"range":[-426.6,105.9],"value":0.5},"pointsize":{"column":false,"range":[0,10],"value":1}},"polygon":{"enabled":true,"color":{"column":false,"range":[-426.6,105.9],"staticVal":"#111f7b","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]},"opacity":{"column":false,"range":[-426.6,105.9]},"line":{"width":{"column":false,"range":false,"value":1},"opacity":{"column":false,"range":[-426.6,105.9],"value":0.5},"color":{"column":false,"range":[-426.6,105.9],"staticVal":"green","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]}},"targets":[]},"line":{"enabled":false,"width":{"column":false,"range":false,"value":1},"opacity":{"column":false,"value":0.5},"color":{"column":false,"range":[-426.6,105.9],"staticVal":"green","value":["#ff0000","#ffff00","#00ff00","#00ffff","#0000ff"]}}}',
wu_1          |     layer: 'layer-c0838e31-c1bf-4cbe-bce1-85a6cef39160',
wu_1          |     uuid: 'project-fcd363c3-2913-4258-86c1-e40d043c8957',
wu_1          |     access_token: 'pk.bFeHn59Ze6OoImRbV5XIaLF9zBelmBxopycewkWP' } ]
wu_1          | [ 'create layer, err, doc', null, [object Object] ]
wu_1          | [ null ]
strk commented 8 years ago

@knutole this issue prevents me from using/testing the services on update. There could be some issue with tokens in mongo or redis (no idea where those keys are stored). Not having any trace of error in the log makes it hard to figure.

knutole commented 8 years ago

Can you check your network log in the browser? You will there see if there are tile requests being sent. If the tile requests are not sent after doing an "Update Style" (or moving around on map with an active layer in layermenu), then something is indeed wrong client-side.

Perhaps try to create new layers, add to layermenu and see if they show up.

If tile requests are being sent, but never returns, something is up server-side. You can try to add console.logs to the routes in /pile/src/server.js.

Unfortuneately, it's a bit tricky for me to debug on your localhost. But this is how I'd start debugging this.

knutole commented 8 years ago

Keys for mongo/redis are set in /docks/config/localhost/. See pile-config.js, redis.conf etc. However, failed AUTH should definitively yield errors in server-logs.

strk commented 8 years ago

I confirm no tiles are being requested from the very moment I click on "Update Style" and any further navigation of the map. Tiles are requested (and successfully served) if I reload the page and re-select a layer from the Style tab (and keep working while navigating the map). The working tiles always have the default RED color (they are polygons).

Should I file this to systemapic.js ?

knutole commented 8 years ago

Sure. Can you please include the layer (file) that causes the issue? (Or is it like this on all layers? Funny thing is, we don't have this problem on other portals.) Also, a screendump of browser logs after clicking Update Style would be good, as well as server-logs. (Even if they contain nothing interesting.)

strk commented 8 years ago

Found out more, reported in https://github.com/systemapic/systemapic.js/issues/59

strk commented 8 years ago

Closing as better handled in https://github.com/systemapic/systemapic.js/issues/59