running mariadb on current
 

Hey y'all

Is anyone running the latest up to date -current, running in an active way mariadb, successfully?

I've read other threads and googled which is reported it fails, and strangely Pat has never addressed those folk about it, and google shows on mariadb bug tracker mariadb devs pointing finger at slackware being at fault, and well I see the changelog says maybe close to beta - although I'm sure we saw that a year or two ago as well, but anyways, I'm gonna make the plunge this weekend, but first I'm hoping to see people are successfully running it in production, unlike some I dont have 50 servers to play with, I have one, its personal and business mail/web/blog/forums all in one, so you see I cant afford to have it all drop dead on me for 12 hours whilst I reinstall an rsync backup on 14.0 (yeh yeh, my bad for running oldie verz)

anyways, hope you guys can give me some good news or pointers that Pat is trying to fix why it dont work?

Oh please please please dont comment it works, if you do not as I said earlier, run it doing real stuff 24/7 yourself, third party hear say is no good to me, or anyone.

TIA

This what you are referring to https://jira.mariadb.org/browse/MDEV...Y%20due%20DESC ?

MDEV-24922 and MDEV-24745 are this year.

Why don't you try it in a VM before installing it on bare hardware. That will allow you to see for yourself whether mariadb is working properly or not without sacrificing the reliability of your system.

So, it appears you are wanting to know if an issue is fixed, without saying what the actual issue is.
Some info on the specific issue you are asking about would be helpful.


It also sounds like you are planning on doing a major upgrade from a 9 year old distro to a current development branch.
I really recommend you don't upgrade to -current for a production system, especially not an in place upgrade from such an old distro.
I would highly recommend setting up a test system first, and waiting until the stable 15.0 release comes out before attempting your plans.

What is the problem? Yes I am using glibc multilib from AlienBOB, but again, what is the problem?

- mariadb-10.5.9-x86_64-1
- glibc-2.33_multilib-x86_64-2alien

As one of the two jira reporters, I can confirm the issue is not resolved, as the responses in Charlie's ticket eludes to, it appears limited in failure to those using Pentium CPU's, in particular older CPU's, or at least that's all we know about at this time.

I can't recall if I made comment on it on here or not, but others have and have pretty much been ignored, so I might have not for also fear of being labelled a troll like Pat did one already.

In the dev world this results in " I got no clue it only affect X people I can count on one hand so I will pretend I dont see it " in years gone by with projects I was involved in, I too am guilty of such offences :P

looking to increase your post count?

I read that as he was wanting replies from anyone successfully running it, that pretty much leaves a yes or no response, replies like yours are not what OP was asking for.

In the last comment by Marko Mäkelä for MDEV-24745, he offers to debug it if someone with the problem gives him a remote access.

Pat checks the forum so he probably saw problems people have but that doesn't mean he can do anything about them. The only people I've seen Pat have issues with are those that deserved it because of their bad attitude. No one wants to listen to a spoiled entitled brat that is spamming threads. People need to start a thread about their issues and share the information they have on it. If someone comes up with a solution, Pat may incorporate it into Slackware. He may even downgrade a particular piece of software if it can be shown that it is more stable.

I do, I run always the latest version of it on current in production on multiple hosts serving a lot of different stuff since four years with no hiccups.

if this is something CPU-specific personally I cannot see anywhere else than upstream to fix this: the build options that Slackware uses doesn't seem to involve any particular optimization.
In the other report a developer explained that if you don't debug it in the same environment with a build with debug symbols on it's nearly impossible to understand what's happening, so it's no use to blame X or Y.

EDIT: Petri has been faster!

He said multiple things about an issue without specifying what issue he was talking about.
And said he was going to upgrade his server from 14.0 to -current, which I recommended against doing.

great, thank you ponce, sounds like their problem wont be mine, I'll be do a full backup of os and databases are backed up hourly anyway.

I'll take the plunge sunday

my question was as clear as crystal as ponce deduced by replying with yes it works, not 500 questions, nobby6 was right you're just trolling my thread, now go away

another one who did not read my post

this is my first time posting on lq but I have been a long time reader, so I should have expected usual suspects to troll

like most the regular posters here they just cant help themselves, they are incapable of reading properly, nor answering with what a OP was asking. they call that trolling.

maybe its my fault, maybe rather than say "dont reply it works unless you actually running it full time" to dont reply unless your actually running it and it works" /me sighs