for at least one of my bots the log file doesn't appear to be being written to. If I force it not to detach from the terminal log messages are reported.
The problem was that if you initialize logging and then close file handles 0,1,2 (AKA stdin/stdout/stderr) the logging module stops working. The solution is to initialize logging after you detach from the console.
The problem was that if you initialize logging and then close file handles 0,1,2 (AKA stdin/stdout/ stderr) the logging module stops working. The solution is to initialize logging after you detach from the console.