Update to working-1.6 fails with mysql: unrecognized service
-
Update to working-1.6 fails with mysql: unrecognized service
System: Debian 12, upgrading from 1.5.10.1629.
See: fog_error_1.6.0-beta.2141.log
* Setting up and starting MySQL..........................System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down mysql.service points to "mariadb" which is not a valid unit name: Invalid cross-device link mysqld.service points to "mariadb" which is not a valid unit name: Invalid cross-device link Failed! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! The installer was not able to run all the way to the end as something has caused it to fail. The following few lines are from the error log file which might help us figure out what’s wrong. Please add this information when reporting an error. !! !! As well you might want to take a look at the full error log in /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2141.log !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ii vsftpd 3.0.3-13+tb2 amd64 lightweight, efficient FTP server written for security ii wget 1.21.3-1tb2 amd64 retrieves files from the web ii zlib1g:amd64 1:1.2.13.dfsg-1 amd64 compression library - runtime New password: Retype new password: passwd: password updated successfully mysql: unrecognized serviceI suspect a mariadb / mysql naming issue. I really do not know where to start so going back to 1.5.10.1629 backup.
Any ideas ?
-
@lperoma This sounds odd, but somehow you have sysvinit on debian 12, when most modern systems are now using systemd.
That said you should be able to fix this by:
apt install systemd-sysv
Though I don’t know if that’s all that will be necessary?Now I would, of course, get a backup of your server before blindly running these things
-
I have created links in /etc/init.d for mysql and mysqld -> mariadb.
Installation seems to progress now a little better, I’ve updated the schema, but still get these errors:
* Setting up and starting MySQL..........................System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down mysql.service points to "mariadb" which is not a valid unit name: Invalid cross-device link mysqld.service points to "mariadb" which is not a valid unit name: Invalid cross-device link OK * Testing connection to database..........................OK * Setting up MySQL user and database......................Skipped * Backing up user reports................................Done * Stopping web service...................................OK * Setting up Apache and PHP files.........................OK * Testing and removing symbolic links if found............OK * Backing up old data.....................................OK * Copying new files to web folder.........................OK * Creating config file....................................OK * Creating redirection index file........................Skipped * Downloading kernel, init and fog-client binaries.......Done * Copying binaries to destination paths....................OK * Enabling apache2 and php services on boot...............OK * Creating SSL Certificate................................OK * Creating auth pub key and cert..........................OK * Resetting SSL Permissions...............................OK * Setting up Apache virtual host (normal).................OK * Configuring PHP FPM.....................................Done * Starting and checking status of web services............OK * Changing permissions on apache log files................OK * Backing up database.....................................Done * You still need to install/update your database schema. This can be done by opening a web browser and going to: http://192.168.0.21/fog/management * Press [Enter] key when database is updated/installed. * Update fogstorage database password.....................OK * Granting access to fogstorage database user.............Skipped * Setting up storage......................................OK * Setting up and starting DHCP Server.....................Skipped * Configuring default PXE file............................OK * Setting up and starting TFTP Server.....................OK * Setting up and starting VSFTP Server....................OK * Setting up FOG Snapins..................................OK * Setting up FOG Snapins..................................OK * Setting up FOG Services.................................OK * Setting up and starting NFS Server......................OK * Configuring UDPCast.....................................OK * Building UDPCast binaries...............................OK * Installing UDPCast......................................OK * Installing FOG System Scripts...........................Failed! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! The installer was not able to run all the way to the end as something has caused it to fail. The following few lines are from the error log file which might help us figure out what’s wrong. Please add this information when reporting an error. !! !! As well you might want to take a look at the full error log in /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2141.log !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! install -m 644 udp-receiver.1 udp-receiver.1 /usr/local/share/man/man1 install -m 644 rateGovernor.h /usr/local/include/udpcast System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down root@fogserver:/root/fogproject#FOG seems to run ok for the moment, despite install errors. Is it OK to use ?
-
@lperoma What do you get running
mariadb -V -
mariadb -V
mariadb Ver 15.1 Distrib 10.11.6-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper -
@lperoma This sounds odd, but somehow you have sysvinit on debian 12, when most modern systems are now using systemd.
That said you should be able to fix this by:
apt install systemd-sysv
Though I don’t know if that’s all that will be necessary?Now I would, of course, get a backup of your server before blindly running these things
-
@Tom-Elliott Success. I switched to single-user with init 1, and installing systemd-sysv worked fine.
As this is a machine upgraded from debian 11, maybe it wasn’t using systemd. Installation of 1.6 worked no problem Thanks,
-
[[undefined-ago, L lperoma, ]]
