Overpass API developpement

[Igor Brejc <>]

Hi Roland,

Answering you below...

On Wed, Sep 6, 2017 at 6:24 AM, Roland Olbricht <> wrote:

Hi Igor,

I notice that if the main dispatcher stops working for some reason (file locks etc.), the apply_osc_to_db.sh script does not really detect that, instead its log reports new diffs were applied in a rapid fashion without reporting any errors (cca. 1 second for a diff, while it usually takes around 15 seconds).

Thank you for reporting the issue. Can you please give details?

Basic details: I run both the main dispatcher and the diff script (as described on my page) as systemd units. Since I don't keep the server running when I don't need Overpass, I pm-suspend it until the next use. Usually, after I bring the machine back from suspension:

1. the main unit (dispatcher) is down for some reason (I don't really know why, but I do know I have to delete the lock files before I can restart it), 
2. while the diff unit goes on applying next diffs and does not detect the main service being down, as I described in the initial mail.

If the logfile of the dispatcher ($DB_DIR/transactions.log) is of a decent size then please send that file. 

Unfortunately I don't have it any more, I cleaned everything and recloned the database since I needed a working instance. I have restarted the diff service and when it happens again, I'll send the files.

 

Has the script, in particular update_from_dir called from the script, produced any output? If so, could you please send that as well?

I'm running the script as a systemd unit. I can't find any output other than apply_osc_to_db.log and transaction.log files, unless it saves the output somewhere else?

 

Could you please verify which script is actually running? Your documentation
https://wiki.openstreetmap.org/wiki/User:Breki/Overpass_API_Installation#Configuring_Diffs
mentions both apply_osc_to_db.sh and fetch_osc_and_apply.sh

No, only one script (.sh) is mentioned. It runs fetch_osc_and_apply.sh and the script writes into apply_osc_to_db.log file. 

Cheers,

Igor