On Tuesday, 11 July 2017 12:06:21 UTC+10, Alex Miler wrote: > > I found what the issue was; I did not have a root privilege when running > the import script. There was no any indication that data was not written > into database. Script completed and final message was that everything was > successful. >
If I could just add a little on the use of wee_import. Whilst wee_import has a deal of smarts within it to handle various sources, it relies on the weeWX 'API' for storing records in the weeWX database. Consequently, wee_import can only provide as much feedback to the user as wee_import receives back from the API when, for example, wee_import asks the API to store some records in the database. At the end of the day, unless there is a fatal error, wee_import cannot be certain exactly what records were saved and what were not (for example, records with a timestamp already in the database are ignored). The real proof/record as to what was stored in the database (and what was not) is in the weeWX log. Consequently, when wee_import is run and non-dry-run import undertaken, the user should be presented with a message similar to the following on completion: Records processed: 70685; Unique records: 70685; Last timestamp: 2010-09-04 04:20:00 AEST (1283538000) Finished import. 70685 raw records resulted in 70685 unique records being processed in 276.63 seconds. Those records with a timestamp already in the archive will not have been imported. Confirm successful import in the weeWX log file. I appreciate that the last two lines of this message could be missed, so I will take it on board to have a look at what how situations like this could be better handled/reported. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
