Just saw this traceback on a dev system:
[2014-08-21 10:34:01,130: ERROR/MainProcess] Task provisioningserver.tasks.periodic_probe_dhcp[07f03687-38ac-411c-973c-f383325dce6a] raised unexpected: NotImplementedError(u"Don't log exceptions to maaslog; use the default Django logger instead",)
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/celery/app/trace.py", line 218, in trace_task
R = retval = fun(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/celery/app/trace.py", line 398, in __protected_call__
return self.run(*args, **kwargs)
File "src/provisioningserver/tasks.py", line 102, in wrapper
func(*args, **kwargs)
File "provisioningserver/tasks.py", line 121, in wrapper
func(*args, **kwargs)
File "provisioningserver/tasks.py", line 457, in periodic_probe_dhcp
detect.periodic_probe_task()
File "src/provisioningserver/dhcp/detect.py", line 363, in periodic_probe_task
"Failed to probe sockets; did you configure authbind as per "
File "src/provisioningserver/logger/log.py", line 29, in exception
"Don't log exceptions to maaslog; use the default "
NotImplementedError: Don't log exceptions to maaslog; use the default Django logger instead
Underlying error aside, it looks like the error-reporting code needs an update.
s/maaslog. exception/ maaslog. error/ to fix.