I'm (very occasionally) seeing log lines in /var/log/messages from ctld that ignore the timezone (appear to be logged in UTC):

# -6 / CST at this point
Jan 30 16:42:07 mr-kronecker ctld[98590]: 10.0.1.2 (iqn.1994-09.org.freebsd:<...>): requested target "iqn.1988-03.<...>" not found
Jan 30 10:43:10 mr-kronecker ctld[3359]: child process 98590 terminated with exit status 1
Jan 30 10:43:10 mr-kronecker ctld[98741]: 10.0.1.2 (iqn.1994-09.org.freebsd:<...>): requested target "iqn.1988-03.<...>" not found
Jan 30 10:43:10 mr-kronecker ctld[3359]: child process 98741 terminated with exit status 1
Jan 30 10:44:12 mr-kronecker ctld[98896]: 10.0.1.2 (iqn.1994-09.org.freebsd:<...>): requested target "iqn.1988-03.<...>" not found

# -5 / CDT at this point
May  7 14:02:07 mr-kronecker ctld[38307]: 10.0.1.2 (iqn.1994-09.org.freebsd:<...>): requested target "iqn.1988-03.<...>" not found
May  7 09:02:07 mr-kronecker ctld[2517]: child process 38307 terminated with exit status 1
May  7 09:03:10 mr-kronecker ctld[38445]: 10.0.1.2 (iqn.1994-09.org.freebsd:<...>): requested target "iqn.1988-03.<...>" not found
May  7 09:03:10 mr-kronecker ctld[2517]: child process 38445 terminated with exit status 1
May  7 09:04:13 mr-kronecker ctld[38610]: 10.0.1.2 (iqn.1994-09.org.freebsd:<...>): requested target "iqn.1988-03.<...>" not found

In both instances I was modifying /etc/ctl.conf and reloading ctld with attempts to attach from the client. Subsequent reloads (visible above) didn't have the aberrant behavior.

Certainly an odd one; not critical, but it stands out since the logs ought to be chronological. (And are, but the timestamps are incorrect on the first of each batch there; in UTC rather than local time.)

Checking for (yay awk) similar lines in my /var/log/messages and rotated logs only turned up the above lines from ctld. (But may be artifactual.)