Help! Hilfe! How to restore mysql after upgrade to core 141

How to restore/reinstall mysql (or restore version 138 of ipfire, where all was OK) on core version 141? In our LAN we have only ipfire firewall and [prior to 141 uopdate] mysql database with lan user login name and password table. All users were authorised against that database to log in into their windows workstations. After update 141 users cannot login into computers because mysql not working [is gone from system]. We have no other servers in LAN where store/restore that database.

You just install your backup, which you have definitally downloaded of your installation before the update, because you run other mandatory services on it.

Already tried, but Backup contains only settings, not removed mysql files/folders

If your databases aren’t saved with the backup and they are gone with the update you’re stuck.

Database is saved, but how restore/reinstall mysql addon (no more in pakfire)

You’re right mysql addon is gone. It’s not listed anymore:

This will be a little problem since addons are not saved with ipfire backups (which I totally can’t understand why that’s the case).

@arne_f where are you?

Mysql was droped two years ago.;a=commit;h=2d5940daca7ccdf94796979a247d645a14191a11

I know, but it worked without problems until today i decided update from 138 to 141. What old version i must restore to get addon back? I use none of ipfire todays improwements.

Stange. IPFire 2.19 core119 should remove mysql. And its a bad idea to use such old version. It was years outdated at time of remove.

The pakfire trees for 2.19 contain no addons anymore. Only the files needed for upgrade.

1 Like

But I have no other option but to get the version that still has this addon no matter how old - 90 users cannot login into computers. And we have no other server computers (and no need such untill now) where i can install mysql for only two tables.

For login only, there are other possibilities ( within IPFire also ).
These could have been installed in the time since mysql was dropped.

Then you can only try to copy a static linked binary from here:
But im not sure if this work.

I have mysql installation files, but what commands for manual installation (ipfire is debian, redhat, ubuntu or what like?)

Hi all,
Marcel do have actual versions of MariaDB but since he build it in a whole environment like the Mailproxy --> and the Mailserver --> this version might be highly adapted to his needs, not sure if this is therefore a help for you.
You can fin in here -->;a=blob;f=lfs/mariadb;h=b65518be7b520ff958d895deb59b2322fa2cfc08;hb=70b6affe0dcfa42997ee5fac7141bdd7f0bfe4d3 the building instructions (LFS file) and in here the packages --> .

Take care if you use them, write him may in one of the topics.

As an idea,



Thanks for ideas!
Found a temporary solution - import my database into external server mysql database of another organisation and redirect ipfire’s mysql port to that external server (as ipfire is firewall).
But however, let me express my thoughts about that situation here.
Why do software authors feel it is imperative to eliminate old things that work well (especially if they are open source). Even though security risks are theoretically open, I am aware of them, and maybe I have a configuration that does not matter. I started using ipfire 2.15 with only 4 services, so I still do it, I don’t need any more. Now, overnight, I have to figure out how to throw out ipfire and install something else (firewall+DNS+DHCP+mysql) there.
When I started working on PCs, for example, the Autocad program came on a single 1.44MB floppy disk and ran hundreds of kilobytes of RAM. Today, it takes up a few gigabytes of computer, requires large amounts of computer memory, but in essence, it has not increased in speed, nor has basic functionality changed. Just a variety of beauties, some of which don’t require anything. The software, unlike cars, does not rust and should be allowed to run for as long as the user likes it.
And ipfire likes me!

Twentytwo open CVE is not a theoretical risk.

The other thing it that it was incompatible with gcc/glibc updates and has not build anymore…

1 Like

Please do not recommend installing any third party software on your firewall.

It is not maintained, and I personally find it very questionable where this is all coming from and how it is being published. It is simply unsafe software.

About software ( and other things made by humans ): There never a complete and error free version!
In contrast to solid state products ( cars, houses, … ) errors and incomplete functions can be easily corrected, when they are known. But these deficiencies can also be abused.
Thus it is recommended not to use unsupported software longer than necessary.

That is why we have package managers that simply update packages. Those packages are signed and you can trust that they are coming from a source you trust.

Those there are not, and once people installed them, they will run them until they break. Let’s be honest.

1 Like

Sorry, if my last sentence wasn’t exact enough.

Deficiencies in software can be abused much easier because of the nature of the product.
Especially in a security application one should minimize these!!

Hope, this clears my opinion.