Am Dienstag, 31. Januar 2012, 12:14:55 schrieb Karsten Keil:
On Tue, Jan 31, 2012 at 09:34:29AM +0100, Adrian Schröter wrote:
Am Dienstag, 31. Januar 2012, 01:59:52 schrieb Karsten Keil: ...
After reboot MySQL was not running, because it did start before the /obs directory was mounted - fixed with Required-Start: $network $remote_fs obsstoragesetup in the mysql startscript and insserv. obsstoragesetup did not mount /dev/OBS/cache, moved the mount in the startscript before the worker setups.
We found out yesterday that the "boot.lvm" script is not enabled by default anymore. Changed now in the appliance.
Hmm, but I saw some extra mdadm and lvm calls in the obsstorage script, so it still works somehow, but maybe not early enough for mysql.
What I still cannot explain is, that on the first boot /obs/MYSQL was here and mysql was started - because if not mysql-update would not start at all but it did - and destroyed the database.
yes, me neither.
It also seems that the database migration does run on every reboot.
yes, there is no way to detect for the appliance if the database is new enough. Should not harm usually. ..
chown -R mysql:mysql /obs/MySQL
Yep, noticed also.
Does this maybe explain the database update crash - wrong rights ?
IMHO not. If mysqld has not enough permissions, it should also not be able to trash the file content. However, we need to fix it anyway.
Any idea to the scheduler issue - why did a manual run be required and what does the difference be to a run from the obsscheduler script ?
no. I need first to find out how to configure with kiwi to boot via sysvinit, (everything got rewritten so far). systemd boot is just hopelesse atm.
And KVM is missing on the appliance - intended or bug ?
kvm package is in the file list. Or what do you mean ?
Karsten
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org