Incomplete timeout information

[Javier Collado]

When looking at rsyslog related timeout problems, it turns out that there is
some information that is missing and that should be useful to troubleshoot
problem. For example, in this log:

-----------------------
Apr 1 09:48:29 finish-install: info: Running /usr/lib/finish-install.d/94save-logs
...
Traceback (most recent call last):
...
raise UTAHException('Timeout occurred for {}'.format(message))
UTAHException: Timeout occurred for system booted
-----------------------

The pattern that was matched probably was "94save-logs" and the exception was
raised after 180 seconds (as in the default configuration file). However, it
would be a good idea to have these two pieces of information to be sure that
the timeout wasn't because of a configuration problem (being that another
pattern matched or that the timeout value is different than the default value).