DevOps, CI/CD and Automation

MySQL 8.0 supports Solaris 11.4 and higher
https://dev.mysql.com/doc/mysql-solaris-excerpt/8.0/en/solaris-installation.html

Thanks for your reply, however it does not point me at an x86 version, or when it will be available.
If I go to https://dev.mysql.com/downloads/mysql/ , select Solaris there are only SPARC binarys available.

Use the standard tar binary installation. Generic binaries should get installed on x86. https://dev.mysql.com/doc/mysql-linuxunix-excerpt/8.0/en/binary-installation.html

Linux binaries should run on Solaris x86.
"Solaris also supports the Linux platform application binary interface (ABI), allowing Solaris to run native Linux binaries on x86 systems. This feature is called Solaris Containers for Linux Applications (SCLA)..."

Select OS as Linux-Generic, and Version as x86, 64-bit.

ok, I'll have an experiment with that.
But generally a Linux binary will not work with Solaris, it needs compliling. And I can't see a compile stage in that link.

I run apps natively in S11.4, I'm not going to start playing with the LX brand now (that never made it into S11).
What I am not grasping is why the binaries are available for SPARC and not Solaris x86.
My requiremnt is to be able to upgrade my NextCloud instances to NC21, which requires MySQL 8.

why the binaries are available for SPARC and not Solaris x86.
Probably because x86 is not as commonly used as Sparc.

I am in exactly the same situation. Upgrading our Nextcloud instances to version 21 and later is currently blocked as it requires MySQL 8.
MySQL 8.0.21 seems to have been the latest version, which was available for Solaris x86. After then, the MySQL people seem to have silently dropped Solaris-x86 support. At least I have not found any form of discussion about it neither in the forums nor on the MySQL website. It might very well be related to the commonness of Solaris-x86 compared to Solaris-SPARC, but nevertheless, I miss a discussion or at least an announcement about it.
I have asked Oracle whether they plan to include it in their Solaris 11.4 SRU repository, but I have not got any commitment, yet. Interestingly, Oracle has become very up-to-date with a lot of OSS tools in Solaris 11.4, e.g. PHP, Node.js, Apache, Python, and so on. For this reason, I do not grasp why the discontinuation of MySQL 5.6 did not lead to the inclusion of MySQL 8 into Solaris' SRU repository, I've been watching the OSS userland build repository on Github from time to time, but have not seen any signs, yet.
If I knew for sure that Oracle will never (or at least not in the next months) be going to include it, I would immediately start to join Thomas from https://sfe.opencsw.org/ in order to build packages. As my available time is very limited, I still hope for a sign from Oracle. As we run about 12 instances of MySQL on Solaris-x86, having packages (instead of tarballs) would be really a great advantage when it comes to maintaining the tool.
Kind regards,
Steffen

The Linux-branded zones are, unfortunately, not available in Solaris 11.4, anymore. So we cannot execute Linux binaries in Solaris. The only possibility would be to run them in a VirtualBox guest.
Kind regards,
Steffen

Just spotted this about MySQL v8 and Solaris x86.
Looks like this is exactly the same as they did for Java. Drop Solaris x86 first and then drop SPARC 6 months later...
Oracle MySQL people like to reply and tell me I am wrong?
Andrew

You can always build from the source code but I vaguely remember something about the tools like C++ also being needed to be built from source too.
Sadly the demand for Solaris version has dropped. And I am a long time user of SunOS/Solaris.

Way back in June AlanC mentioned on twitter that the Solaris Userland team are planning to get it in the IPS repo.
But I've not worked out how to contact that team yet :-(

I forgot about that and we both "Liked" the tweet.. Memory way better than mine...
undefined (0 Bytes)I hope he is right, but if MySQL have dropped it I find it hard to believe they can kick it into life...
Guess there may have been some inhouse discussion...
Thanks,
Andrew

Just spotted your link to the last known working MySQL8 version for x86, so I have grabbed a copy of that.

Has the Solaris PKG format been used?
https://dev.mysql.com/doc/refman/8.0/en/solaris-installation-pkg.html

Yes, up to 8.0.21, binaries in a "tar" and in a "pkg" format have been made available, for example:
https://downloads.mysql.com/archives/get/p/23/file/mysql-8.0.21-solaris11-x86_64.tar.gz
https://downloads.mysql.com/archives/get/p/23/file/mysql-8.0.21-solaris11-x86_64.pkg.gz
Integration of MySQL 8.x into Solaris' IPS has never been available, though.
Kind regards,
Steffen

Still have not got round to building it yet, so running a possible unsecure MySQL 8.0.21 systems at the moment on x86.
30+ CVEs reported for MySQL < 8.0.26 Oracle Critical Patch Update Advisory - July 2021

I guess the people who did that documentation have just done a global replacement of the version numbers and no one has notified them mysql-8.0.26-solaris11-x86_64.pkg.gz does not exist.
Bet the page will be altered soon to show SPARC version and not the x86 version. Then 6 months later the pages will disappear...

I'm begining to think that people don't know the difference between x86 and SPARC and how an OS can run on more than one chip.

Didn't know "mysql-8.0.26-solaris11-x86_64.pkg.gz does not exist".

While trying to build an IPS package of MySQL 8.x for Solaris x64, I've always been working on MySQL 8.0.26. I use GCC 10 and I seem to get along without the Developer Studio compiler. Currently, I've been stuck in testing, but I am confident to get this resolved.
Today, I discovered by accident that MySQL 8.0.27 has been released to the public in the meantime. So, I've changed "8.0.26" to "8.0.27" in the Makefile which downloads, unpacks and patches the sources.
The end of the story: 8.0.27 did not compile anymore... :-(
But why?
Obviously, the MySQL developers used the release of 8.0.27 to actively prohibit compilation on Solaris x64. The following patch fixed it:

steffen@solaris:~/solaris-userland/components/mysql-8-0$ cat patches/allowIntel.patch  
--- mysql-8.0.27/cmake/os/SunOS.cmake      2021-09-28 13:46:34.000000000 +0000
+++ mysql-8.0.27/cmake/os/SunOS.cmake   2021-10-24 10:32:59.300620257 +0000
@@ -28,7 +28,7 @@
IF(CMAKE_SYSTEM_PROCESSOR MATCHES "sparc")
  SET(SOLARIS_SPARC 1)
ELSE()
-  MESSAGE(FATAL_ERROR "Solaris on Intel is not supported.")
+  SET(SOLARIS_INTEL 1)
ENDIF()
 
IF("${CMAKE_C_FLAGS}${CMAKE_CXX_FLAGS}" MATCHES "-m32")

Has anyone reading here found what their objectives are? It seems that -for now(!)- this little patch seems to enable the compilation again. But it reminds me quite strongly to JDK 15 where https://openjdk.java.net/jeps/381 removed the Solaris support... :-(
Kind regards,
Steffen

Thanks for all that Steffen, you appear to have confirmed that x86 is dropping off the radar (not for the first time in its life).
I presume illumos and smartos will have the same issues.

At least in the OpenIndiana repositories, there doesn't seem to be MySQL at all:
https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/database
They seem to rely on PostgreSQL and MariaDB (instead of MySQL). For this reason, we (internally at Ulm University) are currently evaluating whether switching from MySQL to MariaDB should be the way to go. My plan is to provide the packages we build to http://sfe.opencsw.org/localhosts12/en/index.shtml.

I'll keep an eye on progress and start looking at converting my nextcloud to MariaDB.
Thanks for your efforts.

We will move our teaching from MySQL and guess towards Microsoft SQL Server and then we will be ready for when Oracle drops Oracle DB for Solaris. Microsoft products are near enough free for Universities...
Sad days....

x86 architecture could get outdated and obsolete because of the power consumption and RAM limit.

So, you are dropping all intel chip versions soon then?
If oracle are dropping Solaris compilations of software, then they need to pull up their girl pants and just say it.
Fannying about with silent drops does themselves no credit whatsoever.
They have few enough friends or clients that actually like them as it is.

Actually, when comparing the largest SPARC M8-8 servers to the largest x86 X8-8 servers offered by Oracle, I don't see this huge difference in the maximum supported RAM. Oracle's largest x86 servers (which are optional, by the way, still being sold together with Solaris!) support up to 6 TB, their biggest SPARC machines up to 8 TB. So I don't think that this is the main reason for having dropped support for a platform/OS combination while supporting the other one.
When it comes to power consumption, I don't have a comparison of large applications for x86 vs SPARC. If it really was about power efficiency, should we not have seen any Solaris for ARM coming up? ;-)
Kind regards,
Steffen

What are you trying to say? How does this statement relate to the topic being discussed, namely MySQL 8 support being axed for Solaris on x86-64? Are you trying to justify the decision? Most would not see x86 going away anytime in the lifetime of anyone posting in here, whose architecture, by the way, permits a memory limit of 2^64.

MySQL 8.0.27 for Solaris 11.4 x86_64 is now available as an early testing package. The daemon mysqld works and I was able to initialize the database and login with mysql client.
For now the package it is good enough for testing, and testing is needed! Any volunteers out thre?
Next steps on the packaging side will be:
* split into separate IPS pkgs as for mysql 5.7
* add tags for IPS mediator mysql
* provide a SMF manifest
* add initial config file and supporting directory structure
* add Solaris role and mysql user-id
* documentation to assist in very first steps with MySQL 8.0.27 on Solaris (database init, user-password, SMF instance ...)
At the moment I don't think that I'll make a mysql-8.0.27-solaris11-x86_64.pkg.gz available, unless there is a demand for it. I believe people could make better use of a Online IPS repo or use a stanalone IPS p5i package.
Thomas

I should have time in a couple of weeks, my requirement is for use with Nextcloud, so I could run up a new one (ahh, the joy of zones) and try the package there.

MySQL 8.0.27 for Solaris 11.4 x86_64 is now available as an early testing package. The daemon mysqld works and I was able to initialize the database and login with mysql client.
Available from where?
Thanks

Note: The package https://sfe.opencsw.org/localhosts12/info/0/database%2Fmysql-80%408.0.27%2C5.11-0.11.4.0.0.1.15.0%3A20211102T200201Z is not yet split into doc / test / lib and so on, therefore the size is a little bit big :)
The supporting stuff is not yet there, so you need a bit good mysql knowledge to get the mysqld daemon happy and run. Later update to the package will make it very similar to what the old version 5.7 is, including IPS mediators.
e.g.
mkdir /var/lib/mysql-files                                                      
chown mysql:mysql /var/lib/mysql-files
chmod 700 /var/lib/mysql-files

mkdir -p /var/mysql/8.0/data
chown -R mysql:mysql /var/mysql/8.0
chmod 700 /var/mysql/8.0/data
#maybe add a config file
mkdir -p /etc/mysql/8.0/
touch /etc/mysql/8.0/my.cnf
then run it:
/usr/mysql/8.0/bin/mysqld --initialize --user=mysql. &  #(write down the temporary root password!)
/usr/mysql/8.0/bin/mysql mysql -u root -p -

Ok, I don't have a "bit good mysql" knowledge, so may well wait until the later updates.
Also, I am want to be able to migrate from 5.7 to 8, not initialise a new DB.

I've just successfully tried upgrading from Oracle's version (5.7.35) to Thomas' version (8.0.27) on a test zone running Solaris 11.4 SRU 38 (x86-64). It worked well. I had to…
* …clone the SMF scripts,
* …copy my /etc/mysql/5.7 to /etc/mysql/8.0,
* …comment out these three lines which seem to be default now:

innodb_file_format = Barracuda
innodb_file_per_table = 1
innodb_large_prefix

* …copy my DB files from /var/mysql/5.7 to /var/mysql/8.0 and set the according ownership.
Currently, I am testing my web apps (Nextcloud, Moodle, Mahara, and so on).
Kind regards
Steffen

For those waiting on MySQL 8 for OmniOS, Solaris 11.3 and OpenIndiana.
Currently I'm working on the mysql 8.0 package for Solaris 11.4 to have the same layout and fine-tuning then the OS provided mysql 5.7. That is a bunch of work to do and will take a few days. Once this is done, I'll start compiling packages for the other OS Version. I'll keep you posted here and on the blog of the SFE project: https://sfe.opencsw.org.
Thomas

A quick Saturday morning test, and failed with the following.
---8<
[ 2021 Nov 6 11:44:24 Executing start method ("/lib/svc/method/mysql_80 start"). ]
+ /usr/mysql/8.0/bin/mysqld --initialize '--user=mysql' '--datadir=/var/mysql/8.0/data' '--log-error=/var/mysql/8.0/data/ytc-halls-nc.err'
ld.so.1: mysqld: fatal: libstdc++.so.6: version 'GLIBCXX_3.4.29' not found (required by file /usr/mysql/8.0/bin/mysqld)
ld.so.1: mysqld: fatal: /usr/mysql/8.0/bin/mysqld: mismatched ELF symbol versioning
/lib/svc/method/mysql_80: line 52: 6438: Killed
ld.so.1: my_print_defaults: fatal: libstdc++.so.6: t foundversion 'GLIBCXX_3.4.29' no (required by file /usr/mysql/8.0/bin/my_print_defaults)
ld.so.1: my_print_defaults: fatal: /usr/mysql/8.0/bin/my_print_defaults: mismatched ELF symbol versioning
ld.so.1: my_print_defaults: fatal: libstdc++.so.6: version 'GLIBCXX_3.4.29' not found (required by file /usr/mysql/8.0/bin/my_print_defaults)
ld.so.1: my_print_defaults: fatal: /usr/mysql/8.0/bin/my_print_defaults: mismatched ELF symbol versioning
ld.so.1: my_print_defaults: fatal: libstdc++.so.6: version 'GLIBCXX_3.4.29' not found (required by file /usr/mysql/8.0/bin/my_print_defaults)
ld.so.1: my_print_defaults: fatal: /usr/mysql/8.0/bin/my_print_defaults: mismatched ELF symbol versioning
ld.so.1: my_print_defaults: fatal: libstdc++.so.6: version 'GLIBCXX_3.4.29' not found (required by file /usr/mysql/8.0/bin/my_print_defaults)
ld.so.1: my_print_defaults: fatal: /usr/mysql/8.0/bin/my_print_defaults: mismatched ELF symbol versioning
/usr/mysql/8.0/bin/mysqld_safe: line 199: 6566 Killed                 env MYSQLD_PARENT_PID=6449 nohup /usr/mysql/8.0/bin/mysqld --defaults-file=/etc/mysql/8.0/my.cnf --basedir=/usr/mysql/8.0 --datadir=/var/mysql/8.0/data --plugin-dir=/usr/mysql/8.0/lib/amd64/plugin --log-error=ytc-halls-nc.err --pid-file=/var/mysql/8.0/data/ytc-halls-nc.pid < /dev/null >> /var/mysql/8.0/data/ytc-halls-nc.err 2>&1
Failed to start service MySQL
[ 2021 Nov 6 11:44:25 Method "start" exited with status 0. ]
[ 2021 Nov 6 11:44:25 Stopping because all processes in service exited. ]
[ 2021 Nov 6 11:44:25 Executing stop method (:kill). ]
---8<
I'm guessing that I need some more packages from SFE? A search of the repo does not give me much clue to which one(s) are missing.
This is a zone, whch I have just added the SFE publisher to
---8<
PUBLISHER                  TYPE    STATUS P LOCATION
solaris       (syspub)    origin  online T <system-repository>
localhosts12                origin   online F https://sfe.opencsw.org/localhosts12/
---8<

I've installed "sfe/developer/gcc-11", but most probably "sfe/system/library/gcc-11-runtime" should suffice.

If more users were actually using Solaris on x86-64, it (Solaris on x86-64) would definitely be available.

True, but would more people use it if Oracle were still truly behind it?
Oracle Java dropped Oracle Solaris support
Oracle DB dropped Oracle Solaris x86-64 (guess SPARC dropped next)
Oracle MySQL dropped Oracle Solaris x86-64 (guess SPARC dropped next)
Would a company purchase Oracle Solaris (The best o/s) when Oracle don't invest in it.

The question is answered at Oracle Support >
Questions about Java Support on Solaris X86 64Bit (Doc ID 2325957.1)

Question 4: Why is Solaris x86 no longer going to be a supported platform?

Could someone with a support contract summarize 2325957.1? Not asking for it to be posted verbatim here.

Purpose
This FAQ aims to clear up any confusion regarding Java SE support on the Solaris OS.
(It doesn't really IMO).

And Q4 answer is " Oracle is focused on products and platforms that make it easier for developers to create and deploy applications for the cloud."
I note that it says delelopers, not end-clients. So basically the end-client gets fed what they are told they need, not what they would like.

Go on, I'll play the game.
Can you tell me exactly how many instances of Solaris x86 ae installed and in use?
Also, the same for SPARC?
(We played this game back in the early 2000s, when Solaris x86 was dropped. It ws amazing how many customers wanted it and the position had to be reveresed, but by then the damage was too late. Now I suspect the customers just go "Oh FFS, lets just stick it on Linux".

Ta, added runtime and made some progress
---8<
mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2 - No such file or directory)
2021-11-08T09:29:12.201094Z 0 [ERROR] [MY-010095] [Server] Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /var/lib/mysql-files
2021-11-08T09:29:12.201145Z 0 [ERROR] [MY-010187] [Server] Could not open file './ytc-halls-nc.err' for error logging: Read-only file system
---8<
I created the dir, but made no difference. More reading needed I presume :-(

Bruce, did the error message change slightly?
In my previous post (type out of memory) I had as well this:
chown mysql:mysql /var/lib/mysql-files
chmod 700 /var/lib/mysql-files
HTH
Thomas
PS: mysql package make some progress, will take maybe until end of the week as I have a full shedule this week. OpenZFS summit, doing some paid work and so on :)

Yes, sorry, I should noted the change.
---8<
2021-11-08T09:29:12.287984Z mysqld_safe mysqld from pid file /var/mysql/8.0/data/ytc-halls-nc.pid ended
2021-11-08T09:33:11.725353Z 0 [System] [MY-013169] [Server] /usr/mysql/8.0/bin/mysqld (mysqld 8.0.27) initializing of server in progress as process 14828
2021-11-08T09:33:11.728273Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
2021-11-08T09:33:11.728420Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/mysql/8.0/data/ is unusable. You can remove all files that the server added to it.
2021-11-08T09:33:11.728597Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-11-08T09:33:11.729116Z 0 [System] [MY-010910] [Server] /usr/mysql/8.0/bin/mysqld: Shutdown complete (mysqld 8.0.27) Source distribution.
---8<
So I deleted the files in "data" and restarted it.
That cleared the issue and MySQL 8 has started ok.
I'll carry on later, thanks for the efforts.

Watching VirtualBox very carefully because I think unfortunately it will be the next victim of the Solaris purge within Oracle, along with a corresponding , vague Oracle Support Doc Id containing the usual weasel words.