Update on this topic. We are keeping the command-line utility for converting to InnoDB in beta until we feel it is ready, given the importance of this functionality. I expect that we will release it later, after 10.6, rather than with the 10.6 release, so that we can further validate it.

So, no utility currently?

@mhegge coming very soon in the September 10.7.0. We weren't confident in it and had to hold it until this next release.

@mhegge Given something as fundamentally central as the database, I wouldn't jump on anything that hasn't been released until they are ready to release it.

That being said, you might ask your Jamf buddy if they are accepting applications to test new versions of Jamf Pro in your sandbox environment. Sometimes you get early access to stuff to see how it works before it goes into support and before you put your production environment on the new builds.

So, I'm attempting to run this, I get as far as Pre-Conversion then as far as this and get the following error
"- [418/420] Repairing table 'vpp_user_accounts'
- [419/420] Repairing table 'wallpaper_auto_management_settings'
- [420/420] Repairing table 'webhook_display_fields'
- Applying database settings
- Restarting database
failed to restart the database
Error: pre-conversion step failed: unable to restart database: fork/exec /bin/systemctl: no such file or directory"

anyone?

I'm using a Linux server BTW

@joe.bloom

Hi Jope,
Any Ideas on this?
Running RHEL

"Error: pre-conversion step failed: unable to restart database: fork/exec /bin/systemctl: no such file or directory"

@kerouak Try posting this in the beta forums...I’m guessing you may get a faster response

@kerouak I'll share this with our dev team but I would suggest opening a support case too if you haven't already. Our team will need to know what you've shared above and probably things like what Jamf Pro version you're running. Maybe more.

Hello @kerouak

I work with the team developing the Jamf Pro Server Tools, and shared this error with them last night.

Chatting with them again this morning, would you be able to let us know the following?

• OS name and version. Our initial thought, is this error may be related to the distro you are using.


• Output of jamf-pro version.


• Jamf Pro version installed

Thanks, and look forward to hearing back from you!

Now that it’s been released I will note I faced the same issue as @kerouak today. The conversion process failed to restart MySQL on Windows

I solved it in my case, but it was one of two things that did it.

The first was that I renamed the standard Mysql57 service name to make scripting easier originally. When studying the issue, I uninstalled and reinstalled MySQL this time accepting the default name. I also added the C:Program FilesMySQLMySQL Server 5.7in Folder as a system variable in Windows.

One of those two actions fixed my issue FWIW.

We Have a RHEL Server JUST for our MySQL database, Went to InnoDB Yesterday and I HIGHLY Recommend it. Load times increased BIG TIME!!! GO JAMF!

@ChrisLeeSSD

https://www.jamf.com/jamf-nation/articles/531/converting-the-mysql-database-storage-engine-from-myisam-to-innodb-using-the-jamf-pro-server-tools-command-line-interface

heres the MySQL Commands I was advised to do that got the job done ..in order..i think this is all of them...I would recommend contacting JAMF if unsure as I am not proficient in MySQL

#this command shows your tables, will show all MyISAM, after you convert, run again, should reflect all Innodb

select table_name,engine from information_schema.tables where tables.table_schema="jamfsoftware";



<DefaultStorageEngine>InnoDB</DefaultStorageEngine>



#this will convert MyISAM to Innodb

*MYSQL PATH HERE* -u root -p PASSWORDHERE -N -e "select concat('alter table ', table_name, ' engine =InnoDB;') from information_schema.tables where table_schema = 'jamfsoftware' and engine = 'MyISAM' and table_name != 'downloadable_file_chunk_data'" > jamfsoftware_innodb.sql



#This Will Import After Conversion (Thank @bdelamarche ) - FORGOT THIS PART

MYSQL PATH HERE -u root -p PASSWORDHERE < jamfsoftware_innodb.sql



#again, this will show the newly converted MyISAM tables are now Innodb

select table_name,engine from information_schema.tables where tables.table_schema="jamfsoftware";

ADD THE FOLLOWING to /etc/my.cnf on RHEL Sql Server
NOTE * innodb_buffer_pool_size=#G --> The # value "#G" reflects 75% of your SQL servers RAM, in my case we have 16GB of ram so our value is 12G.

please see my comment in this post for further detail of why this is going here

###***This is a comment in the /etc/my.cnf file 

# Added innodb values September 20th after Update to Jamf 10.7 & MySQL Conversion from MyiSAM to Innodb

innodb_buffer_pool_size=12G

innodb_file_per_table=1

key_buffer_size = 16M

innodb_flush_log_at_trx_commit = 0

drhoten

RHEL 7.5 running on an independent server.

JamfPro V 6.2

Error: pre-conversion step failed: unable to restart database: fork/exec /bin/systemctl: no such file or directory"

If someone can shed a light on the file that it's trying to access, that may make things slightly easier to resolve???

ta

@kerouak I filed a bug for this... basically it's assuming you are starting and stopping your Linux services with systemctl however that's not always the case, you might find that your Linux distro is using service instead

So try restarting your database this way...

Make sure your Tomcat instance(s) have stopped first:

sudo service jamf.tomcat8 stop

Now restart the databse:

sudo service mysql restart

Now start up Tomcat:

sudo service jamf.tomcat8 start

YMMV

@brunerd did that actually work for you as far as conversion? I had the same issue, and after restarting mysqld and checking most of the tables were still myisam...

@chris.kemp The current version of the jamf-pro tool fails to complete the InnoDB conversion on RHEL systems, so you have to do a manual conversion. Contact your TAM/Jamf Buddy/Customer Success Specialist/Whatever they're called today for the procedure.

@Hugonaut
Thanks for the very useful article
I think it missed only in your process the reimport of the dump

this will import the sql dump

MYSQL PATH HERE -u root -p PASSWORDHERE < jamfsoftware_innodb.sql

Best and many thanks
Benoit

Thank you @bdelamarche for correcting the post! I updated my post..its only the most crucial part of the conversion haha. & You're welcome. Glad to help