Finally! I tracked down the issue that prevented the Picasa grabber from running on a schedule. It was something silly and basic that took my far too long to figure out.<\/p>\n
The non-propeller heads in the audience can tune-out now, what follows is a load of geek-speak. \ud83d\ude09<\/p>\n
The problem was this; when I ran the Picasa grabber from the command line it worked just fine. However, when it ran via CRON it appeared to not run at all. It didn’t fail with an error message, no messages in the logs, nor did it generate any console message of any kind, it just didn’t do anything<\/em>. It was very frustrating.<\/p>\n The basic problem was that the PATH statement in CRONTAB did not match the PATH statement of my interactive shell. However, the way in which it failed was not detected by any of my monitors. Since the durn thing didn’t even start none of the error checking\/reporting code I have in the app. had any opportunity to catch\/report the failure. Nor did my log scrapers find anything anomalous as there were nothing reported.<\/p>\n I tend to work under the basic Unix tenant of less is more, and specifically that if a process does not detect an error it need not report a ‘normal termination’; simply the absence of an error message is in itself an indication of successful completion. In this scenario this ideal failed completely.<\/p>\n There are two morals to this story, both very basic; “Always check your PATHs” and “Don’t assume (that no response is the same as a positive response).”<\/p>\n","protected":false},"excerpt":{"rendered":" Finally! I tracked down the issue that prevented the Picasa grabber from running on a schedule. It was something silly and basic that took my far too long to figure out. The non-propeller heads in the audience can tune-out now, what follows is a load of geek-speak. \ud83d\ude09 The problem was this; when I ran … Continue reading Picasa updates fixed (or, Pay Attention To The Basic Stuff)<\/span>