nil pointer panics handling bgapi requests

[andmar]

We started getting nil pointer panics related with fsock and syslog calls and got it down to this piece of code that seems to log something when handling bgapi requests. We're initializing with the NewFsock function with nil value for the sysloger argument.

func (self *FSock) doBackgroudJob(event string) { // add mutex protection
   evMap := EventToMap(event)
   jobUuid, has := evMap["Job-UUID"]
   if !has {
        self.logger.Err("<FSock> BACKGROUND_JOB with no Job-UUID")
        return
   }
...

We noticed that elsewhere, whenever self.logger.Err is called it's guarded by something like "if self.logger != nil".