Is it possible to include any details about an update failure in an email notification?
I guess the best you could do is include the contents of update.log, which would include a relevant exception.
Presumably if this was a custom exception (eg like 10389), the message from that exception would be visible.
I’ve just found that sometimes an error email does include log messages, but sometimes not. Gioan suggests it depends on what phase it was up to.
Once we’ve had a go at 10389, hopefully I can report back with more detail.
I’ve trawled through some old funnelback error emails, and found that one collection on one server did produce details from logs in the email, while all others don’t. Looks like it was during the index phase. I wonder if it’s something specific to that setup? Here’s what it looked like:
HOST: xxx-funnelback01.squiz.net
COLLECTION: xxxx
MESSAGE: Error: Error running “/opt/funnelback/linbin/ActivePerl/bin/perl-static /opt/funnelback/bin/index.pl /opt/funnelback/conf/xxxx/collection.cfg”.
UPDATE LOG
…CRAWL LOG
…MESSAGE end
I’ve tried using a bash script to return an error code on the following workflow commands, but none of them cause logs to appear in the failure email:
Would it make any difference if I were running a groovy script? I can’t see how it would. I suppose this just doesn’t work for workflow commands.
Anybody able to shed some light?