×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Nagios-Plugins Web Site Taken Over By Nagios

Soulskill posted about 3 months ago | from the bad-behavior dept.

The Internet 119

New submitter hymie! writes "Nagios is a commonly used IT tool that monitors computers, networks, and websites. It supports the use of plug-ins, many of which were developed independently by the community. Holger Weiß, formerly of nagios-plugins.org, announced that 'Yesterday, the DNS records [of nagios-plugins.org] were modified to point to web space controlled by Nagios Enterprises instead. This change was done without prior notice. To make things worse, large parts of our web site were copied and are now served (with slight modifications) by Nagios. Again, this was done without contacting us, and without our permission. This means we cannot use the name 'Nagios Plugins' any longer.' Further discussion is available in a Bugzilla thread."

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered

119 comments

IT IS HAPPENING ALL OVER !! (-1)

Anonymous Coward | about 3 months ago | (#46004135)

Website are copied and being impersonated by Russuans.

Shitting all over your most supportive users (5, Insightful)

Anonymous Coward | about 3 months ago | (#46004157)

is not a viable long term strategy.

Re:Shitting all over your most supportive users (0)

VortexCortex (1117377) | about 3 months ago | (#46004279)

is not a viable long term strategy.

Get back to your own damn universe Bizzaro Mark Shuttleworth.

Re:Shitting all over your most supportive users (5, Informative)

Anonymous Coward | about 3 months ago | (#46004449)

No, but Nagios hasn't cared much about it's users for some time now. It worked when they were the only game in town[1], but these days you can choose to use Icinga or even Sensu; both of which are far better products than Nagios and support Nagios plugins.

[1]: Well O.K, there's OpenNMS, but that's network oriented rather than infrastructure so it's not a direct comparison.

Re:Shitting all over your most supportive users (3, Insightful)

Anonymous Coward | about 3 months ago | (#46005887)

Give Zabbix a try, you'll be surprised. Much better flexibilty and easier to tie into active directory for authentication.

http://www.zabbix.com/

Re:Shitting all over your most supportive users (3, Informative)

jon3k (691256) | about 3 months ago | (#46009241)

http://www.zabbix.com/license.php [zabbix.com]

If you use ZABBIX in a commercial context such that you profit by its use, we ask that you further the development of ZABBIX by purchasing some level of support.

Just fair warning.

Re:Shitting all over your most supportive users (2)

deadeye766 (1104515) | about 3 months ago | (#46009921)

IMHO stay away from Zabbix for anything but small-ish environments. For what it's worth, our experience hasn't been great running zabbix in a distributed configuration. Plus, there isn't much flexibility in terms of configuring checks on hosts due to the way templates work.

Also, their "enterprise support" is a fucking joke. Our support experiences are "chatting" back and forth in a Notepad while a guy fucks around in the mysql DB for a few hours. Total waste of money. =(

Re: Shitting all over your most supportive users (0)

Anonymous Coward | about 3 months ago | (#46006079)

You may not be aware but OpenNMS supports direct interfacing/collection from National plug-ins (NPRE, NSclient & NSclient++)
There are many more features that allow application monitoring, beyond SNMP, WMI and syslog/eventlog parsing/alerting.

More details here http://www.opennms.org/wiki/Features_List
IT certainly is one of the most powerful monitoring systems available that just happens to be open source (especially since they now generate elegant Jasper reports).
Before knocking it, I encourage you to try it (before spending a ton on something else).

-Kurt

Re: Shitting all over your most supportive users (0)

Anonymous Coward | about 3 months ago | (#46007975)

I didn't knock OpenNMS, I just said it was aimed more towards network monitoring rather than infrastructure monitoring. Sure, OpenNMS can be used for infrastructure monitoring, but then Nagios/Icinga/Sensu can be used for network monitoring. Whether they're the best solution for the job is a different matter.

This may be why they are doing this. (1)

Arker (91948) | about 3 months ago | (#46006897)

"It worked when they were the only game in town[1], but these days you can choose to use Icinga or even Sensu; both of which are far better products than Nagios and support Nagios plugins."

So it appears their business strategy moving forward was to leverage the domain registration to allow them to present their fork as the original product, then alter the plugins to be incompatible with the competition.

Sure the original project will keep going at mobility-plugins, but the 'big fish' customers might not be able to see past the name/domain.

Re:Shitting all over your most supportive users (2, Funny)

aliquis (678370) | about 3 months ago | (#46004525)

Shitting all over your most supportive users (Score:5, Insightful)
is not a viable long term strategy.

Apple: - What?

Re:Shitting all over your most supportive users (2, Funny)

Anonymous Coward | about 3 months ago | (#46004599)

Shitting all over your most supportive users (Score:5, Insightful) is not a viable long term strategy.

Apple: - What?

You're holding it wrong.

Re:Shitting all over your most supportive users (0)

Anonymous Coward | about 3 months ago | (#46005061)

Shitting all over your most supportive users (Score:5, Insightful)
is not a viable long term strategy.

Apple: - What?

You're holding it wrong.

That's what she said

Re:Shitting all over your most supportive users (1, Interesting)

kelemvor4 (1980226) | about 3 months ago | (#46006303)

Shitting all over your most supportive users (Score:5, Insightful) is not a viable long term strategy.

Apple: - What?

I don't think that was apple's strategy specifically. More of a consequence of being so successful. They just don't care. Apple's strategy is to be fashionable and cool rather than functional. Things seem to be on the decline for the fruity company in my estimation. This behavior will help drive them back into obscurity once again.

Copyright violation. (2, Interesting)

Anonymous Coward | about 3 months ago | (#46004163)

This sounds like a plain and simple copyright violation in many ways.

Sue Nagios.

Re:Copyright violation. (5, Funny)

Anonymous Coward | about 3 months ago | (#46004177)

Sue Nagios.

Are you related to Sally Nagios?

Re:Copyright violation. (0)

Anonymous Coward | about 3 months ago | (#46004237)

Hmmm...
This site https://www.monitoring-plugins.org/news/index.html [monitoring-plugins.org]

announced that the domain name would be transferring to Nagios in SEPTEMBER 2011.

perhaps the domain registras have just actioned it?

Re:Copyright violation. (2)

gl4ss (559668) | about 3 months ago | (#46004259)

well yeah but the understanding was that the domain would point to the monitoring plugins...

now nagios altered the deal.

Re:Copyright violation. (5, Interesting)

xQx (5744) | about 3 months ago | (#46004325)

This battle was lost years ago when this volunteer organisation gave control of their domain to Nagios Enterprises to avoid trademark issues.

So they've been able to continue in their priviliaged position paying Nagios Enterprises SFA for theses years, until finally some mid-level bureaucrat decided that the money they were getting ($0) from nagios-plugins.org community group doesn't outweigh the brand-risk that they pose, and they brought the website back inhouse.

Wow, I would never have seen that coming!!

Sounds to me like Nagios Enterprises is readying its self for sale.

This is the open source business model. Cisco have been at it for years. Get used to it.

Re:Copyright violation. (1)

mysidia (191772) | about 3 months ago | (#46004761)

This battle was lost years ago when this volunteer organisation gave control of their domain to Nagios Enterprises to avoid trademark issues.

Yes... it would of been prudent for them to at that time begin the immediate process of transitioning releases to a domain that they retained control over.

Re:Copyright violation. (1)

number11 (129686) | about 3 months ago | (#46005727)

So, Nagios copied the nagios-plugins website. What's the statutory penalty for copyright violation? And does each page view by an outside party count as a new violation?

Re:Copyright violation. (1)

Anonymous Coward | about 3 months ago | (#46004263)

https://www.monitoring-plugins.org/archive/devel/2014-January/009417.html [monitoring-plugins.org]

"In the past, the domain "nagios-plugins.org" pointed to a server
maintained by us, the Nagios Plugins Development Team. The domain
itself had been transferred to Nagios Enterprises a few years ago, but
we had an agreement that the project would continue to be independently
run by the actual plugin maintainers. Yesterday, the DNS records were
modified to point to web space controlled by Nagios Enterprises instead.
This change was done without prior notice."

Re:Copyright violation. (2)

xQx (5744) | about 3 months ago | (#46004301)

Yeah, and that would hold weight if you weren't using their trademark all over your site.

Seems to me this is just an occupational hazard of using somebody else's name for your site.

Re:Copyright violation. (-1)

Anonymous Coward | about 3 months ago | (#46004341)

I'm aware that intellectual property and IP laws are quite murky concepts for many slashdotters, but I assure you that "trademark" and "copyright" are two distinct concepts, and using somebody's trademark in a copyrightable work doesn't entail automatic transfer of your copyright to the owner of that trademark.

Re:Copyright violation. (5, Insightful)

tverbeek (457094) | about 3 months ago | (#46004543)

You seem to be completely overlooking the issue of copyright. Re-appropriating the domain was apparently within Nagios' rights, but copying the contents of the web site was not. Trademark rights are not virally transmissible to copyright.

Re:Copyright violation. (1)

mysidia (191772) | about 3 months ago | (#46004765)

You seem to be completely overlooking the issue of copyright. Re-appropriating the domain was apparently within Nagios' rights, but copying the contents of the web site was not. Trademark rights are not virally transmissible to copyright.

They are if the potential claimant/entity whose rights you are stepping on does not have lawyers, or is otherwise prevented from suing you over the copying.

Re:Copyright violation. (0)

Anonymous Coward | about 3 months ago | (#46004787)

It's a common mistake- namely because many lawyers have munged up the notions in the minds of many to serve purely the interests of their profession.

Re:Copyright violation. (0)

Anonymous Coward | about 3 months ago | (#46006399)

You seem to be completely overlooking the issue of copyright. Re-appropriating the domain was apparently within Nagios' rights, but copying the contents of the web site was not. Trademark rights are not virally transmissible to copyright.

I'd guess that it depends on the nature of the domain transfer. As I understand it, Nagios-plugins transferred the domain name, albeit under threat of trademark violation legal action. Nagios may very well have an agreement in place that says they own the copyright to the website whose domain they own.

Re:Copyright violation. (4, Informative)

mysidia (191772) | about 3 months ago | (#46005277)

Yeah, and that would hold weight if you weren't using their trademark all over your site.

I think you don't get it... the Nagios Plugins project pre-dated Nagios. The Nagios Plugins Project was renamed from The NetSaint plugins project due to trademark issues. Nagios was an acronym for "Nagios Aint gonna insist on Sainthood"
The open source project was using the name before Nagios Enterprises was founded, and these development teams, therefore have prior use of the name Nagios.

They were apparently tricked into handing over control of the domain to the guy who founded Nagios enterprises later.

Re:Copyright violation. (1)

Anonymous Coward | about 3 months ago | (#46004321)

I agree. While the source code of the plugins is licensed GPLv3, and as such may be legally 'forked' (keeping open which project is the forked one), the content of the web site is not. Even though it was always hosted by Nagios Enterprises, it has now been copied to a physically different server (and modified the DNS accordingly). That is a clear copyright violation.
IMO, Nagios Enterprises could have handled this more elegantly. Reminds me a little of the Mambo / Joomla debacle 9 years ago.

Re:Copyright violation. (0)

Anonymous Coward | about 3 months ago | (#46004797)

That's because entirely too many businessmen listen to and believe incompetent IP rights attornies with very wrong and bad notions and advice.

Re:Copyright violation. (1)

coats (1068) | about 3 months ago | (#46005315)

If the original plugins-team follow the Scientology copyright-action precedent and show up with an ex parte seizure order, a Federal Marshall, and an 18-wheeler to seize the evidence of copyright infringement (i.e., every computer in the place), it might serve as an example pour les autres.

companies love trademarks (-1)

Anonymous Coward | about 3 months ago | (#46004165)

Trademarks ensure brand loyalty. By leveraging brand loyalty people can be told what to do and buy and vote for, and they'll do it too.

Vote Slashdot!!!

Switched to Icinga a long time ago (3, Informative)

Anonymous Coward | about 3 months ago | (#46004203)

So far I have not looked back once.

Re:Switched to Icinga a long time ago (2, Insightful)

Anonymous Coward | about 3 months ago | (#46004927)

+1

The switch is trivially easy and all plugins are backwards-compatible. The "classic" UI has every annoyance of Nagios UI fixed. There is a sensible release cycle and authors that accept feedback in their bugtracker.

Every time I hear people complain about their Nagios love/hate relationship I tell them to switch.

Re:Switched to Icinga a long time ago (0)

Anonymous Coward | about 3 months ago | (#46004979)

You're probably using nagios-plugins which means this affects you.

Re:Switched to Icinga a long time ago (1)

Pinky's Brain (1158667) | about 3 months ago | (#46006491)

I doubt there are many distributions which will go with what Nagios Enterprises want, I assume most of them will just make nagios-plugins some type of transitional to monitoring-plugins and force a name change on Nagios Enterprises's package ... if they include it at all. At Redhat you have employees just coming forward (thank you DJ Delorie) and calling them on their bullshit copying of the website.

Re:Switched to Icinga a long time ago (1)

houstonbofh (602064) | about 3 months ago | (#46008561)

Yep, it does, and I am freezing the nagios plugins package on all the monitoring servers I manage until it gets resolved. And when it does, I will be upgrading to the monitoring-plugins groups stuff. When Icinga and Nagios forked, there was a lot of "he said" "she said" crap. I guess we now know who was telling the truth.

similar (1)

Threni (635302) | about 3 months ago | (#46004217)

You have to admit, the two names are rather similar. One might reasonably assume they're run by the same people.

Re:similar (5, Informative)

Richard_at_work (517087) | about 3 months ago | (#46004233)

Looks like Nagios Plugins was a community project to provide plugins for Nagios, with little to no input by Nagios themselves. At some point in the past, the website name was transferred to Nagios to avoid trademark issues but the project continued to be community driven and led. Now, Nagios has redirected the DNS to its own plugins website, forked the community codebase, setup an entirely new developer base and taken the company line that "monitoring plugins (the name chosen by the original nagios-plugins project leads) is the fork, not us".

Reading the propaganda by the Nagios rep on the bugzilla thread is highly amusing, smacks of Eurasia and East Asia from 1984.

If all of this is even mildly true, its quite an evil thing by Nagios to do.

Re:similar (1)

Anonymous Coward | about 3 months ago | (#46004295)

Looks like Nagios Plugins was a community project to provide plugins for Nagios, with little to no input by Nagios themselves. At some point in the past, the website name was transferred to Nagios to avoid trademark issues but the project continued to be community driven and led. Now, Nagios has redirected the DNS to its own plugins website, forked the community codebase, setup an entirely new developer base and taken the company line that "monitoring plugins (the name chosen by the original nagios-plugins project leads) is the fork, not us".

Reading the propaganda by the Nagios rep on the bugzilla thread is highly amusing, smacks of Eurasia and East Asia from 1984.

If all of this is even mildly true, its quite an evil thing by Nagios to do.

A representative of Nagios Enterprise was available to comment on this issue [youtube.com].

Re:similar (2)

Splab (574204) | about 3 months ago | (#46004367)

It's quite a mess they have made, they expect us (the users) to just accept a new team under same name.

Well fuck that. Hope package maintainers are on top of this and make sure users are forced to make a choice of which plugin distribution to use.

Re:similar (1)

alphatel (1450715) | about 3 months ago | (#46004393)

At some point in the past, the website name was transferred to Nagios to avoid trademark issues but the project continued to be community driven and led.

If all of this is even mildly true, its quite an evil thing by Nagios to do.

A part of this is foolishness. You can never trust a corp that has been litigious over its brand with ownership of your project or its hosting. Everything should have been copied elsewhere to a domain or hosted url with no TMs, and the old site should have been slowly deprecated and forked.

Re:similar (1)

mysidia (191772) | about 3 months ago | (#46005365)

Looks like Nagios Plugins was a community project to provide plugins for Nagios, with little to no input by Nagios themselves.

They were a community project to develop plugins. The guy who originally developed the Nagios core software, eventually went on to create Nagios enterprises.

The NetSaint plugins project was renamed to the Nagios plugins [linuxtoday.com] project in ~2001; The nagios-plugins repo has content going back 9 years.

Nagios Enterprises company was first founded in 2007. The Nagios Trademark was registered in 2007.

The Nagios plugins project pre-dated the existence of the corporate entity or any trademark registrations, by at least 5 years.

Re:similar (1)

stoborrobots (577882) | about 3 months ago | (#46009461)

I agree with your perspective. Unfortunately, the other details muddy the water:

The Nagios project on sourceforge was set up in May 2001.

The Nagios Plugins project on sourceforge was set up in June 2001.

The owner of the Nagios project later went on to create Nagios Enterprises and register the trademark.

So while the enterprise didn't exist back then, it is the successor of the project which was using the name first...

Re:similar (2)

houstonbofh (602064) | about 3 months ago | (#46008569)

If all of this is even mildly true, its quite an evil thing by Nagios to do.

It sure puts a new spin on the Nagios Enterprises side of the Icinga fork... So, who still thinks Icinga was making stuff up?

Suprise, not really (0)

Anonymous Coward | about 3 months ago | (#46004225)

So why did you give Nagios control of your domain again?

Re:Suprise, not really (3, Informative)

paziek (1329929) | about 3 months ago | (#46004235)

They (Nagios Enterprises) requested it. I didn't see mention of why they did, but I would guess it was trademark issue. They were supposed to let them use it independent of Nagios Enterprises, but seems like 3 years was all they could get on this deal. From what I read in their discussion, reason for takeover are mentions of compatible competition on main site of old Nagios Plugins.

Not a registrar problem. (1, Interesting)

imunfair (877689) | about 3 months ago | (#46004247)

The summary made it sound like a domain registrar just transferred the name without their permission, but that totally is not the case according to the article:

In the past, the domain "nagios-plugins.org" pointed to a server maintained by us, the Nagios Plugins Development Team. The domain itself had been transferred to Nagios Enterprises a few years ago, but we had an agreement that the project would continue to be independently run by the actual plugin maintainers.

So really the company just decided they want control of the server now instead of pointing their domain to a third party. Nonstory.

Re:Not a registrar problem. (3, Informative)

Anonymous Coward | about 3 months ago | (#46004261)

So really the company just decided they want control of the server now instead of pointing their domain to a third party. Nonstory.

You apparently decided to read the article on this occasion, but inexplicably stopped after the second link.

3.3/10 for effort but could try harder.

Re:Not a registrar problem. (5, Informative)

Richard_at_work (517087) | about 3 months ago | (#46004265)

The story is a but more than that - they took the website almost as-is, forked the codebase and are portraying themselves as the original project with a new developer base, insisting the original developers are the fork.

If they had switched the domain to a brand new website and started from scratch, that would be your non-story...

The real question is why. (2)

leuk_he (194174) | about 3 months ago | (#46004375)

Why did nagios take out the server out the hands of the community. Was there a fight in the community? Is this just a "it is named nagios, so it is ours"? Want do to some subscribtion? Sombody in the community took to big consulting fees?

At first it looks like that nagios has a name to loose, and more work to do by maintaining a lot of plugins and a extra site.

Re:The real question is why. (0)

Anonymous Coward | about 3 months ago | (#46004529)

The bugzilla thread alleged that it was because the original plugins hompage talked about nagios competitors; but, that was not confirmed. (And doesn't seem to explain "firing" the whole plugins team.)

Re:The real question is why. (1)

Michael Friedrich (2971005) | about 3 months ago | (#46005397)

I guess Nagios Enterprises will never confirm that. It's left to the user, opening http://www.nagios-plugins.org/ [nagios-plugins.org] and https://www.monitoring-plugins.org/ [monitoring-plugins.org] and compare their content. https://plus.google.com/101435336006767659040/posts/W2HUysCafyD [google.com] That's also mentioned in Holger's announcement here: https://www.monitoring-plugins.org/archive/devel/2014-January/009417.html [monitoring-plugins.org]

Re:The real question is why. (1, Funny)

Anonymous Coward | about 3 months ago | (#46004619)

At first it looks like that nagios has a name to loose

Loose: your slut of a mother's vagina.
Lose: no longer in possession of something.

How fucking hard can this be?

Re:The real question is why. (0)

Anonymous Coward | about 3 months ago | (#46004771)

Seems that you too have some problems being polite to others. Do you need some advice with that?

Re:The real question is why. (2)

rnturn (11092) | about 3 months ago | (#46006005)

While I hate to comment on a grammatical post... I, too, am getting more than a little tired of seeing this misuse in a comment by someone who, otherwise, seems to have a good grasp of the English language. Whenever I see it, my respect for that poster's argument/comment drops by about 10dB. They may as well have posted in all caps.

Re:Not a registrar problem. (1)

Anonymous Coward | about 3 months ago | (#46004443)

The story is a but more than that - they took the website almost as-is, forked the codebase and are portraying themselves as the original project with a new developer base, insisting the original developers are the fork.

And if the entire intent was to bring the project under the control of Nagios Enterprises, how exactly would you go about doing that without using your own employees?!?

Seems the FOSS community, regardless of how many of them actually get up every day and go to work as an employee, have forgotten all about all those legal issues that corporations tend to have to do. And if I was in charge as the project manager to bring this in-house, I'd probably do the exact same thing with a fork of my own people that a corporation can control and manage.

To be honest, the FOSS community should probably feel lucky they felt nice enough to offer up the "archive" code base after they converted over. Again, remember your corporate roots. They have zero obligation to provide this. They're only obligated to provide and maintain their official code base.

Dick move? You better believe it. Piss off a sizable community? Hell yes. Perfectly legal? Yup. The right way to do it to avoid future liability? Unfortunately, most likely.

Re:Not a registrar problem. (2)

causality (777677) | about 3 months ago | (#46004625)

Dick move? You better believe it. Piss off a sizable community? Hell yes. Perfectly legal? Yup. The right way to do it to avoid future liability? Unfortunately, most likely.

That reminds me of a saying I once heard: "we will have world peace when the last lawyer is strangled with the entrails of the last banker."

Re:Not a registrar problem. (0)

Anonymous Coward | about 3 months ago | (#46005403)

They have zero obligation to provide this. They're only obligated to provide and maintain their official code base.

Dick move? You better believe it. Piss off a sizable community? Hell yes. Perfectly legal? Yup. The right way to do it to avoid future liability? Unfortunately, most likely.

In which world do you live? They only own the name. They didn't maintain anything. Claiming other people's work as your own? Perfectly legal? Nowhere. The right way to do it to avoid future liability? Not a chance.

The right way:
Claim the webpage, do your own design of it, fork the project (name it nagios-nagios-plugins, or official-nagios-plugins or whatever), at least mention the origins of the software and tell the free project to stop using the name nagios.

Re:Not a registrar problem. (1)

jones_supa (887896) | about 3 months ago | (#46004705)

The story is a but more than that - they took the website almost as-is, forked the codebase and are portraying themselves as the original project with a new developer base, insisting the original developers are the fork.

What the fuck man, you are correct. It's almost creepy to watch the /team.html page both at nagios-plugins.org [nagios-plugins.org] and monitoring-plugins.org [monitoring-plugins.org]. The sites look identical but the names on the lists are different.

Re:Not a registrar problem. (1)

pr0fessor (1940368) | about 3 months ago | (#46005637)

The way on nagios-plugin all of the names have been moved to previous team members and all the current team members happen to be employed by nagios. The way they have removed mention of other solutions. It makes me think there might be more going on than what is in the post as if they are planing to refocus the project on nagios because of something that happened but we are not privy to.

Re: Creepy? (2)

rnturn (11092) | about 3 months ago | (#46006133)

Creepy? Howzabout "disgusting"?

IANAL but I doubt there's anything in trademark law that would allow the Nagios team to appropriate the work of the Nagios Plugin team wholesale the way they did and merely change the name of the team members. While I hate the term, this looks like it could be a blatant example of ``intellectual property'' theft. Was the Nagios team unable to come up with their own wen site? Really? Rights to the domain name don't give you rights to the work that went into creating the plugin web site.

After having used it for 6-7 years, Nagios just went off my list of recommended monitoring tools. Icinga just moved to the top.

Re: Creepy? (1)

Redmancometh (2676319) | about 3 months ago | (#46006261)

Holy shit we have a new argument in the IP debate! IP laws cause IP theft it's fucking bulletproof!

Really though this is an instance of IP laws causing IP theft which is just...deliciously ironic.

Re:Not a registrar problem. (0)

Anonymous Coward | about 3 months ago | (#46009741)

the names on the /news page are entertaining

Distro packaging mess (4, Interesting)

paziek (1329929) | about 3 months ago | (#46004249)

It will be interesting to see who will provide source for packages used by various distros. Those plugins can be used by other monitoring applications and I guess that new maintainers on the old domain could release version of their plugins that would not work with competition, while at the same time old maintainers probably shouldn't use nagios-plugins for their packages.

Re:Distro packaging mess (0)

Anonymous Coward | about 3 months ago | (#46005013)

It seems from the bugzilla thread that Redhat is leaning towards the "Nagios takeover" fork, rather than the original team's version.

I think that's a big mistake. If someone has decided to trust the original maintainers and project, silently substituting a version that's been taken-over in a corporate-sleeze maneuver isn't very trustworthy. Until the new team establishes both technical and community levels of trust, they should not be silently substituted under the same package name.

Awe, that's disappointing. (1)

VortexCortex (1117377) | about 3 months ago | (#46004293)

Naigio-Plugins Web Site Taken Over By Nagios
"Nagios is a commonly used IT tool that monitors computers, networks, and websites."
...
"Again, this was done without contacting us, and without our permission."

It would have been a better story if the takeover was done using the Nagios tool itself.

Alternatives... (2, Informative)

ptudor (22537) | about 3 months ago | (#46004395)

After having the good fortune to spend a few weeks testing everything free, I've got to spend a minute evangelizing for Zabbix.

It took me a week to understand the concepts, but the clone button and templates make Zabbix my favorite tool. The local Zabbix agent on each host gives detailed metrics and the screens of graphs are great.

Check out the appaloosa-zabbix-templates for more MySQL and Memcache charts than you ever thought might work out of the box.

Zabbix is ridiculously powerful, from auto discovery on subnets, to simple ping and snmp, up through more advanced tools.

Re:Alternatives... (1)

Zarhan (415465) | about 3 months ago | (#46004453)

We are currently monitoring six distributed sites using http://mathias-kettner.com/checkmk.html [mathias-kettner.com]. It still relies on Nagios 3.x core, but they are going to replace that soon ("micro-core"). From what I've heard, Nagios development started really going downhill at Nagios 4.0, and this plugin issue is yet one more such symptom.

Re:Alternatives... (2, Interesting)

Anonymous Coward | about 3 months ago | (#46004483)

Nah - it was way before 4.0.

The core Nagios guys pissed off enough people that various forks had appeared (e.g. Icinga, Shinken etc), and the new forks provided an outlet for years of repressed development/feature ideas that were squelched in Nagios as 'not part of the core of what we do'.

And as these other projects gained steam and became more popular, the core Nagios folk realised they had some major catch-up work to do, which (iirc) is where 4.0 came from, and seemed to take a bunch more major contributors on board around then as well.

(But they also had a bit of a kerfuffle a yeear or two back over a similar thing - the project going a bit too far in the direction of comercial control (aka stranglehold)).

Re:Alternatives... (5, Informative)

Michael Friedrich (2971005) | about 3 months ago | (#46005293)

The funny thing is, that Nagios Enterprises didn't write Nagios 4.0 - that work was done by Andreas Ericsson who works for op5. So instead, you should call "Nagios 4 Core" "op5 Core" if you're looking for the who-did-write-it. The sad thing is, that Nagios Enterprises kicked out Andreas Ericsson out of the Nagios core development after recognizing that people actually knew that Andreas was the only core developer at that time - working for a competitor. Andreas forked Nagios 4 into Naemon abandoning the dictatorship by Nagios Enterprises. You may find their website interesting but there more interesting read is located here in terms of the Nagios Plugins project: https://www.monitoring-plugins.org/archive/devel/2014-January/009432.html [monitoring-plugins.org] If you're interested in more details, the announcement happened on last years OSMC http://www.youtube.com/watch?v=YgbbyyNIiHc [youtube.com] So other than the clusterfuck by Nagios Enterprises in regards of lying to the community again, they've lost their last core developer and there are fellow forks around the corner filling the gap. If you're questioning yourself - I am the lead core dev of Icinga, but what's written here is my sole personal opinion.

Somone had to plug icinga (3, Interesting)

Anonymous Coward | about 3 months ago | (#46004553)

Someone had to plug the better open source monitor. Icinga (https://www.icinga.org/) is either a fork from nagios 2 or a rebuilt but either way has config file level compatibility with your nagios configs. A way saner architecture for writing add-ons and a better web ui.

Re:Somone had to plug icinga (3, Informative)

Michael Friedrich (2971005) | about 3 months ago | (#46005321)

Actually Icinga was forked off Nagios 3.2.1 and some patches ahead. Meanwhile we've ported plenty of Nagios patches, but also sent them Icinga patches. At some point, they've removed the Icinga copyright on those patches, and banned me from their bug tracker. But since people had been asking quite often, which patches and features are exclusive to Icinga, I had compiled a periodically updated table with all details exposed. https://www.icinga.org/2011/11/03/icinga-vs-nagios-a-developers-comparison/ [icinga.org] And while we're still working on the 1.x branch, we're preparing Icinga 2 and Icinga Web 2 for their first final releases, overcoming long lasting problems (such as an integrated cluster stack, or recurring downtimes).

Just eastablish a new fork (2)

mlwmohawk (801821) | about 3 months ago | (#46004577)

Nagios is a stupid name, and now they are acting like a stupid company. You can't buy good will, but you can certainly spend it out of existence. Create an entity sys-monitoring.org, or something, pull a GPL nagios, change trademarks, and point to monitoring-plugins.org. That really is the only way to deal with companies that behave this way.

Then contact Debian, RedHat et. al. they will probably deal with the new fork after this crap.

Nagios - rhymes with (1)

Anonymous Coward | about 3 months ago | (#46004833)

adios

Let's not take sides.. (0)

Anonymous Coward | about 3 months ago | (#46004959)

They all seem pretty despicable at this point.

The drama with the parent and its forks seems to have a long and jaded history:

http://www.freesoftwaremagazine.com/comment/79247#comment-79247

The best thing we slashdotters can do is treat them all like trolls - no soup for you, trolls!

Plugin developers (2)

MouseTheLuckyDog (2752443) | about 3 months ago | (#46005303)

In the future plugin developers should make their plugins compatible with alternatives but incompatible with Nagios. Then Naagios can either live with the old plugins or hire people to port the new plugins. Then Nagios can see what the community meant to them. This is a typical business approach which says that the enemy is not your competitors but your user community and the community of people who add value to your product. Time these users got a clue.

Re:Plugin developers (0)

Anonymous Coward | about 3 months ago | (#46007159)

It's always profitable for one guy, to make a whole company bite the hands that feed it. Just got to break loose before the shitstorm from the fans does.

But does it have FUD? Check! (...check...check) (1)

Anonymous Coward | about 3 months ago | (#46005339)

Holy cow...
http://assets.nagios.com/datasheets/compare/How_Nagios_Compares_To_Icinga.pdf

That's a lot of checkmarks! And we all know how much IT managers LOVE those checkmarks (and hate "legal risks" and "high developer turnover". I like how the icinga checkmarks are light gray and the nagios checks are "blazin' blue".

Lessons learned:
You know a product is the most awesome of them all when it gets a check mark for every single point compared.

Re:But does it have FUD? Check! (...check...check) (0)

Anonymous Coward | about 3 months ago | (#46006029)

Some of those comparison are... Odd at best. Very specific ones that really only work for 1 of the two. I was expecting a 'Company named Nagios' checkmark at the bottom of the list.

From the bugzilla thread (4, Insightful)

rk (6314) | about 3 months ago | (#46007139)

"nagios-plugins is not a fork, but a rebase with new team members. monitoring-plugins is indeed a fork, as their new name suggests."

That is rich.

How to kill a project! (0)

Anonymous Coward | about 3 months ago | (#46007481)

Open source developers support projects for many reasons, money is obvious not one of them. Reasons like giving back to the community, working with a community with like mindsets, the status of working on an open source project, etc.. While there is loyalty to a project, it is a mutual two way street. When b.s. like this happens, the open source developers leave and go to competitive projects. I don't understand how companies figure that people are just assets that are easily replaced. There's years of knowledge and understanding of why code was developed in a certain way and method. That is lost when your core developers leave.

Good Point (1)

darkpixel2k (623900) | about 3 months ago | (#46009677)

The article makes a good point. We need to ditch the threaded slashdot UI in favor of news articles being posted to a Bugzilla instance for comment (Or at the very least adding a moderation 'WORKSFORME')
Load More Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account

Loading...