Since upgrading to Leap 15.1, I cannot get to my MariahDB.
NMAP on localhost says port is open, but my connecting client (Leap 42.3) can’t find route to database and
NMAP says port is closed. My router is a Linksys Smartrouter.
I am assuming that both client and server hosts are on a private (non-routable) local network (e.g. 192.168.x.0/24) and that Firewalld is running on the host. Make sure that SuSEfirwall2 is not running.
On the server:
YaST > Security and Users > Firewall
the default default zone is “public”
Select the “public” zone.
Scroll down the list of services to “mysql” and add it to Allowed
> Accept
There is also a firewalld-applet in the standard repository that provides a (in my opinion) confusung graphical interface.
NMAP issue resolved, thanks.
I still have some issues with the client app which I may have to report.
By the way, I had filewalld configured as trusted, but changing to public was the answer.
Unless your machine is somehow unusual,
That would mean that however you opened port(s) for access, those rules were applied to the Public zone.
That might make sense if you were using an automated tool to open the port since the Public zone is default, but if you opened the port manually then you would want to open the port in whatever zone is active.
Or, if you think that the port should have been opened for not just the default zone but also for all zones which are less restrictive, you might want to submit a bug report to https://bugzilla.org. If others agree, others who follow you might not find the same problem.
TSU
I will refrain from reporting a bug, because I’m not all that familiar with firewall, I may have been doing something amiss.
My client issue, I have fixed. Seems the new my.cnf didn’t carry over my previous settings and MySQL was only accepting
connections on “localhost”.
My total experience with migration from 42.3 has been less than satisfactory. I still have unresolved issues with 1) Libreoffice and
2) general printing.
Thanks for your help.
Jumping multiple version is not really supported. Sometime it works with little problem but sometimes it is a mess depends on setting you made. IMHO it is best to simply keep home and do a new install the time to reinstall some programs you need is usually much less then the time trouble shooting an upgrade. Keep a copy of /etc as a reference if you have a complex setup.
If this is your first upgrade,
Then this may just be your first exposure to what an upgrade involves.
The openSUSE upgrade SDBs only apply to the OS which of course is important, but that’s really only the bare minimum and start to a series of procedures which requires careful inspection and often research.
You describe MariaDB which is one server application.
That could require a whole plan for itself, and the tables sometimes need to be exported and then imported into a newly installed latest version.
If your MariaDB is part of a LAMP pattern, then you might also need to investigate the new Apache version plus any web technologies such as running PHP. Website code may need to be updated to the new PHP, and maybe database connections need to be re-made. Maybe it’s not just PHP but you might halve deployed a website using a PHP framework like Wordpress, perhaps that might need to also be upgraded which could involve a number of widgets no longer supported and would need replacing.
And, so on.
Not just server apps, if your machine is a User Workstation, perhaps numerous personal apps will also be upgraded and need to be addressed. You mentioned LibreOffice. Yes, and there could be others. Just remain optimistic as you do what is necessary… There’s help in these Forums and in the end your apps should have a much brighter future with more functionality and hopefully fewer issues moving forward.
TSU