eventlogging and database have been moved to deployment-eventlogging03 instance. Needed to upgrade from Precise to Trusty. Please use that instance now, deployment-eventlogging02 will be removed.

I apologize for the lack of an announcement on this. What is the proper channel?

Many thanks @Ottomata!! K I see it now in /var/log/eventlogging/all-events.log. It's not getting through to MySQL though, but I think that's an issue with nested schemas (as per this log that @Milimetric found, not sure exactly where, though).

In T112926#1650405, @Ottomata wrote:

What is the proper channel?

• Absolute minimum: use !log in #wikimedia-releng so it shows up here: https://tools.wmflabs.org/sal/releng (or if you're old school: https://wikitech.wikimedia.org/wiki/Release_Engineering/SAL). Think just like you would with production.
• Emailing appropriate lists if it can have a big impact (eg qa@lists and any other relevant one).

Ok, thanks. I think I migrated this service very hastily, since we were changing puppetization for production, which broke in labs because the changes didn't work on Precise.

Next time will do that. Can I email qa@lists or do I need to join?

I think it let's anyone email it. I clean the backlog daily, fwiw (thanks to listadmin).

In T112926#1650405, @Ottomata wrote:

Please use that instance now, deployment-eventlogging02 will be removed.

@Ottomata: https://tools.wmflabs.org/sal/log/AU_igRQw1oXzWjit5mYu
"deployment-eventlogging02:/var full due to massive eventlogging_processor-server-side-0.log.1 ("(MainThread) Unable to process" errors)"

Just deleted deployment-eventlogging02

Thanks so much! Closing... For MySQL querying of the banner history events, only T112947 is still out there... :)