taskMapOSMatic - Tasks: task #10067, Improve maposmaticd logging

 
 

task #10067: Improve maposmaticd logging

Submitted by:  David Decotigny <daviddecotigny>
Submitted on:  Fri 08 Jan 2010 09:39:33 AM UTC  
 
Should Start On:  Fri 08 Jan 2010 12:00:00 AM UTC Should be Finished on:  Fri 06 Aug 2010 10:00:00 PM UTC
Category:  daemon Priority:  6
Status:  Done Privacy:  Public
Percent Complete:  100% Assigned to:  Maxime Petazzoni <mpetazzoni>
Open/Closed:  Closed Release:  None
Effort:  0.00

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue 13 Jul 2010 12:47:51 PM UTC, comment #4: 

Some work was done here during the daemon rewrite and afterwards, but we still need better error reporting from OCitySMap to MapOSMatic so we can display more details on why a rendering failed to the user. We should be able to indicate, at least, the following level of detail:

  * the rendering failed because a PostgreSQL query timed out (although this shouldn't happen in the future)
  * the rendering failed because a PostgreSQL query failed (intersect error, polygon error, invalid db schema, etc)
  * the rendering timed out (during the rendering phase)

Reassigning to myself as David Mentre can't dedicate time to the project these days.

Maxime Petazzoni <mpetazzoni>
Project AdministratorIn charge of this item.
Tue 09 Feb 2010 09:40:03 AM UTC, comment #3: 
Maxime Petazzoni <mpetazzoni>
Project AdministratorIn charge of this item.
Tue 09 Feb 2010 09:38:48 AM UTC, comment #2: 

IIRC, dmentre stepped up to work on this as soon as the daemon-rewrite code has been merged in. We need better logging throughout the rendering process at DEBUG and INFO levels, and better error reporting from OCitySMap to MapOSMatic when the rendering fails with a query or rendering error.

Maxime Petazzoni <mpetazzoni>
Project AdministratorIn charge of this item.
Mon 11 Jan 2010 05:41:54 PM UTC, comment #1: 

I'm taking this. Time for me to dive into the maposmaticd code, and maybe make some improvements there.

Maxime Petazzoni <mpetazzoni>
Project AdministratorIn charge of this item.
Fri 08 Jan 2010 09:39:33 AM UTC, original submission:  

We get far too little info when a rendering fails. And we get far too little info about a rendering in progress, period (we the ocitysmap log go, i just don't remember).

Furthermore, when there is a timeout, we would like to know where the rendering got struck. Not sure it's possible, though, but could be nice.

BTW, why not use processing to spawn the worker children, instead of manually forking ?

David Decotigny <daviddecotigny>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mpetazzoni (Posted a comment)
  • -email is unavailable- added by daviddecotigny (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 12 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2012-04-24 mpetazzoni StatusNone => Done
        Percent Complete50% => 100%
        Open/ClosedOpen => Closed
    2010-07-13 mpetazzoni Should be Finished on2010-01-08 => 2010-08-06
        Priority7 - High => 6
        Percent Complete0% => 50%
        Assigned todmentre => mpetazzoni
    2010-02-09 mpetazzoni Priority6 => 7 - High
        Assigned tompetazzoni => dmentre
        Summaryimprove maposmaticd logging => Improve maposmaticd logging
    2010-01-11 mpetazzoni Priority5 - Normal => 6
        Assigned toNone => mpetazzoni

    Back to the top


    Powered by Savane 3.7