Ever thought it might be a smart idea to test a new release if you plan on deploying it in a production environment?? .. mikrotik aren't perfect you know.. everyone makes mistakes.Who are you?
Member of the mikrotik developer team?
Or just another mikrotik user?
Don't you think this announcement is a little bit late?
I loose all my trust to mikrotik. All - every bit of it.
And today I will be installing vyatta on my router machine right after my customers goes to sleep.
Thank you mikrotik! For the worst day of my life..
uncompressing linux ...
is it the election day today ??Congratulations to mikrotik for this excellent and democratic forum.
I know have 1 working + 2 spare routers on my shelf + 5 different copies of backups in different locations
While it is best practice to do so it says a lot when you release a full version (not alpha, beta, etc) and it doesn't even work (at all?) on a certain architecture that your product is sold on.I have to say, it serves you right for putting this onto production boxes.
You should always test a new release from ANY vendor on spare hardware in a non-production environment. It's called "best practice"
IMO this is in no way Mikrotik's fault, it is your own.
Oh , i feel fine now , thanks , cause Vmware makes mistakes too !!!Haha you guys are obviously not aware of the VMWare issues in the last day. Basically they released a patch that had a build expiry on the 12th of August and it caused VMotion and all VM startups to stop on ALL boxes running the latest version of VMWare it was only fixed this morning. So even the BIG boys have major patching issues.
Stop bagging on Mikrotik, they make an excellent product at an excellent price.
/system hardware set multi-cpu=yes
Strongly disagree to that.I have to say, it serves you right for putting this onto production boxes.
You should always test a new release from ANY vendor on spare hardware in a non-production environment. It's called "best practice"
IMO this is in no way Mikrotik's fault, it is your own.
+10 to the mail quote.Oh, and another quick suggestion:
As a Sys Admin like all of you I don't have time to check this forum so often. The release of 3.12 was announced to me via e-mail, so I think this should be the way to warn users about problems like these. Release notices via e-mail and complete crash notices only trough forums seems a little like sweeping dirt under the carpet to me...
Be more transparent. It takes courage but pays off in the long term.
You know there are old saying: "Only God can create perfect things!" in this case "Only God can add a feature without future fixes required!"It's an alarm sign for me that in the changelog has from 3.x releases, more and more lines appear to be starting with "fixed" than starting with "added".
How did you managed to find that only multi-core with smp enabled are having this problem ?You know there are old saying: "Only God can create perfect things!" in this case "Only God can add a feature without future fixes required!"It's an alarm sign for me that in the changelog has from 3.x releases, more and more lines appear to be starting with "fixed" than starting with "added".
..............
BTW: all routers in my network except multi-core core routers are running 3.12 - and I am having a good night sleep. Cheers!
Careful!How did you managed to find that only multi-core with smp enabled are having this problem ?
Guess i'll find out.
"I'm going in."
(and I still think about that alarm sign.)
Good work. And also for notification. I'm trying to reproduce it on an intel celeron 733, with 3.12, right now.Careful!
Not "multi-core with smp enabled", but "any x86 with smp enabled"
Hot I did find out? I was messing around with my dead core router - trying to revive it and find what exactly was causing the problem, then I noticed that MT guys wrote that simpe queues was the problematic place - but i at that moment was able to add simple queues without any problems - my multi-cpu was no
I trust releases with most "fixed" lines in changelog. Currently, latest trusted (so-so:) release for me is 3.10, because I realised there is no need for me to upgrade every production router to 3.11.It's an alarm sign for me that in the changelog has from 3.x releases, more and more lines appear to be starting with "fixed" than starting with "added".
If 3.12 went through any test department I believe someone needs fired....It happens to the best test department, even with a bazillion dollars to throw at testing.
Regardless of best practice something as trivial as a SIMPLE QUEUE causing a crash on x86 that requires a complete reinstall of the OS points out how recklessly inadequate the QA is on "releases".Ever thought it might be a smart idea to test a new release if you plan on deploying it in a production environment?? .. mikrotik aren't perfect you know.. everyone makes mistakes.