Thank God for SSH! I gave a quick (not to thorough) look through the cups logs and I didn't find anything related to the disabling of the printer. My guess is that the logs filled up to fast and everything in them was related mostly to the work I was doing when ssh-ed in to fix the problem. I think our best guess is to wait till the problems happen again and then see if we can find something through the log. By a quick interwebs search it looks like other people have experienced this in the past. A quick fix could be to write a cron job that monitors the printers' statuses and enables the printer if it's discovered to be disabled (this could present admin problems in the future if we manually disable the printer, we'll just have to keep this in mind if we go this route).
Thank God for SSH! I gave a quick (not to thorough) look through the cups logs and I didn't find anything related to the disabling of the printer. My guess is that the logs filled up to fast and everything in them was related mostly to the work I was doing when ssh-ed in to fix the problem. I think our best guess is to wait till the problems happen again and then see if we can find something through the log. By a quick interwebs search it looks like other people have experienced this in the past. A quick fix could be to write a cron job that monitors the printers' statuses and enables the printer if it's discovered to be disabled (this could present admin problems in the future if we manually disable the printer, we'll just have to keep this in mind if we go this route).