https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-11-19T07:56:59ZopenSUSE Project Management ToolopenQA Infrastructure - action #78064: failing logrotate on monitor.qa.suse.de due to mariadb/mysql?https://progress.opensuse.org/issues/78064?journal_id=3519922020-11-19T07:56:59Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2020-11-24</i></li><li><strong>Status</strong> changed from <i>Workable</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>asked nsinger in chat</p>
openQA Infrastructure - action #78064: failing logrotate on monitor.qa.suse.de due to mariadb/mysql?https://progress.opensuse.org/issues/78064?journal_id=3531222020-11-21T22:40:10Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>he said that likely not needed, I could check existing database content. With <code>sudo -u mysql mysql</code> and the SQL command <code>show databases;</code> I found only a "test" database so likely we can easily remove everything here :) I did that now and so I would not expect logrotate to fail on mariadb/mysql anymore.</p>
openQA Infrastructure - action #78064: failing logrotate on monitor.qa.suse.de due to mariadb/mysql?https://progress.opensuse.org/issues/78064?journal_id=4114412021-05-28T17:13:06Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/93195">action #93195</a>: [Alerting] Failed systemd services alert (except openqa.suse.de) on 2021-05-28, logrotate.service on openqaworker-arm-1</i> added</li></ul>