Change Details

I'm getting this after provisioning the ores and elk roles. ``` ==> default: Notice: /Stage[main]/Role::Ores/Mediawiki::Maintenance[check ORES model versions]/Exec[check ORES model versions]/returns: PHP Fatal error: Uncaught exception 'LogicException' with message 'The UdpSocket to 127.0.0.1:10514 has been closed and can not be written to anymore' in /vagrant/mediawiki/vendor/monolog/monolog/src/Monolog/Handler/SyslogUdp/UdpSocket.php:45 ``` Maybe there are problems with logging to ELK from a maintenance script?

This error shows up when provisioning the `elk` role: ``` ==> default: Notice: /Stage[main]/Role::Ores/Mediawiki::Maintenance[check ORES model versions]/Exec[check ORES model versions]/returns: PHP Fatal error: Uncaught exception 'LogicException' with message 'The UdpSocket to 127.0.0.1:10514 has been closed and can not be written to anymore' in /vagrant/mediawiki/vendor/monolog/monolog/src/Monolog/Handler/SyslogUdp/UdpSocket.php:45 ``` A similar exception is shown on every page view too. This is caused by `LBFactory::__destruct` (indirectly) logging messages after `UdpSocket::__destruct` was called and thus the socket does not exist anymore. We should either make sure that all long handlers swallow errors when called after they have been destroyed, or that no classes try to log from their destructor.

I'm getting this afterThis error shows up when provisioning the ores and elke `elk` roles.: ``` ==> default: Notice: /Stage[main]/Role::Ores/Mediawiki::Maintenance[check ORES model versions]/Exec[check ORES model versions]/returns: PHP Fatal error: Uncaught exception 'LogicException' with message 'The UdpSocket to 127.0.0.1:10514 has been closed and can not be written to anymore' in /vagrant/mediawiki/vendor/monolog/monolog/src/Monolog/Handler/SyslogUdp/UdpSocket.php:45 ``` Maybe there are problems with logging to ELK from a maintenance script?A similar exception is shown on every page view too. This is caused by `LBFactory::__destruct` (indirectly) logging messages after `UdpSocket::__destruct` was called and thus the socket does not exist anymore. We should either make sure that all long handlers swallow errors when called after they have been destroyed, or that no classes try to log from their destructor.