Alternate devmon SNMP
list Bruno Manzoni
Hello, I created a repo with "devmon" github/bonomani and included all patches/contrib and resolved all bugs I can. (I try to integrate all patches, bugs and features from SF) see the REAMDE for details This is not an official update of current "devmon" but I have difficulties to have an answer on current sourceforge repo, so I decided to publish what I have done. (I did not have any answer on my patches after myn years!?) As i am working on Centos, there are some specific things for systemd. I trying also to contact devmon admins to merge this work or part of it, so if you have a clue... If you want to test this work, you should simply take the files in the "modules" dir and it should work...with your current installation And of course any suggestions are welcome! Bruno
list Bruce Ferrell
▸
On 5/9/19 3:47 AM, Bruno Manzoni wrote:
Hello, I created a repo with "devmon" github/bonomani and included all patches/contrib and resolved all bugs I can. (I try to integrate all patches, bugs and features from SF) see the REAMDE for details This is not an official update of current "devmon" but I have difficulties to have an answer on current sourceforge repo, so I decided to publish what I have done. (I did not have any answer on my patches after myn years!?) As i am working on Centos, there are some specific things for systemd. I trying also to contact devmon admins to merge this work or part of it, so if you have a clue... If you want to test this work, you should simply take the files in the "modules" dir and it should work...with your current installation And of course any suggestions are welcome! Bruno
Bruno, As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo. One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd. Personally, I'll avoid systemd like the plague, however I'd think those modifications should be called out and isolated as well... Especially considering devmon normally runs as a perl based daemon... At least on my Scientific linux 6.10 system.
list Bruno Manzoni
Bruce,
▸
As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo.
Di you have a look te the README?
▸
One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd.
I have the same problem: I suspect a problem with the snmp polling lib or decoding process....*.Can you create an issue for that point on github ?*
▸
Personally, I'll avoid systemd like the plague, however I'd think those modifications should be called out and isolated as well...
I dont like Systemd very much, but I decided to work by now with centos....and these modifications are isolated scripts (devmon/extra/centos folder), but it is just to inform that something exists as Xymon as a Terabithia version hah to work with linux dsitrib that use systemd: But devmon should continue to work with any linux distrib. And thanks for this feedback!
▸
Le 09.05.2019 à 16:17, Bruce Ferrell a écrit :
Bruno,
As a long time user of devmon, I'd be fascinated to see an enumeration
of the bugs, features, patches etc in your repo.
One of the biggest "bugs" I've seen, and I haven't had time to chase it
down is that over time devmon seems to leak memory like a sieve,
becoming quite bloated. I run a cron job to kill (yes kill -9 ) and
restart it every four hours... Not under systemd.
Personally, I'll avoid systemd like the plague, however I'd think those
modifications should be called out and isolated as well... Especially
considering devmon normally runs as a perl based daemon... At least on
my Scientific linux 6.10 system. Bruno, As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo. One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd. Personally, I'll avoid systemd like the plague, however I'd think those modifications should be called out and isolated as well... Especially considering devmon normally runs as a perl based daemon... At least on my Scientific linux 6.10 system. On 5/9/19 3:47 AM, Bruno Manzoni wrote:Hello, I created a repo with "devmon" github/bonomani and included all patches/contrib and resolved all bugs I can. (I try to integrate all patches, bugs and features from SF) see the REAMDE for details This is not an official update of current "devmon" but I have difficulties to have an answer on current sourceforge repo, so I decided to publish what I have done. (I did not have any answer on my patches after myn years!?) As i am working on Centos, there are some specific things for systemd. I trying also to contact devmon admins to merge this work or part of it, so if you have a clue... If you want to test this work, you should simply take the files in the "modules" dir and it should work...with your current installation And of course any suggestions are welcome! Bruno
list W.J.M. Nelis
Hi,
At NLR, devmon is running on a RHEL 6.10. There is a slight memory
leak, probably in xymon or devmon, which requires a restart once
every 2 or 3 months. Normally, a kernel update is issued by RedHat
well before the memory utilisation becomes an issue.
Regards,
Wim Nelis.
▸
As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo.
One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd.
Regards,
Wim Nelis.
list Bruce Ferrell
▸
On 5/9/19 11:50 PM, W.J.M. Nelis wrote:
Hi,As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo. One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd.At NLR, devmon is running on a RHEL 6.10. There is a slight memory leak, probably in xymon or devmon, which requires a restart once every 2 or 3 months. Normally, a kernel update is issued by RedHat well before the memory utilisation becomes an issue. Regards, Wim Nelis.
All I can tell you Wim, that's not my experience. 24 hours is enough that xymon starts sending memory use alerts and the fatcat on researching the cause IS devmon (from sourceforge) not xymon. I'll also add that I inadvertently ran across Bruno's github repo about a year back, thinking it was a migration from sourceforge to github and not the fork that it seems to be. I used it in an install... Then fell back very rapidly to the sourceforge release tarballs. The git clone had issues running in the most basic setup. The templates... Let's just say I didn't have the time to figure out what all was wrong with them. Suffice to say, that install (a clone/rebuild of an existing install) using the github repo failed in so many ways it was faster and easier to revert to the SF release packages. No Bruno, I will NOT be opening issues on the github repo. The maintainers and users on the very low volume devmon list deserve better than that and they do respond there and to issues on SF. Which sort of begs the question as to why this announcement was made on the xymon list and not on the devmon list. While the SF code has some issues, that code works out of the box... To the extent SNMP works. I need to be clear on my comment regarding SNMP; I love the concept of SNMP and it DOES work in 98% of the cases, and it's shame it's only 98%. BSD based systems (PfSense and OS X are the players I've worked with here... OS X even using ucd net-snmp from the Mac Ports Project) have... Interesting implementations with interesting quirks. SNMP on OpenWRT is interesting too. I've even seen Cisco do odd things. Devmon turned ALL the quirks up and while it's fascinating sometimes to figure out "Why does it do THAT?", it also points up why SNMP has never really taken solid hold in over 30 years.
list Stef Coene
▸
On 10/05/19 08:50, W.J.M. Nelis wrote:
Hi,As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo. One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd.At NLR, devmon is running on a RHEL 6.10. There is a slight memory leak, probably in xymon or devmon, which requires a restart once every 2 or 3 months. Normally, a kernel update is issued by RedHat well before the memory utilisation becomes an issue.
We have multiple xymon servers running with uptimes ranging from weeks to months. One of them is running sinds june 2015! If there is a memory increase, it's in xymon_rrd. xymon_rrd uses 3.054.896K on that server that's running since 2015. I sometimes kill all xymon_rrd processes if we are getting low on memory. Stef
list Bruno Manzoni
Hi Bruce, Many thanks for your answer and I shared your point of view: if you use the version of sourceforge, you should put a ticket on it. Also I dont want to deserve nor Devmon on sourceforge nor Xymon: I just try to make my best (The road to hell is paved with good intentions) My goal of this proposition was just to move this discussion elsewhere: to not bother people of this mailing list And thanks for the info about memory leaks: just to document this problem: your are polling BSD OS, from a BSD OS or from a linux OS?
▸
Le 09.05.2019 à 16:17, Bruce Ferrell a écrit :On 5/9/19 3:47 AM, Bruno Manzoni wrote:Hello, I created a repo with "devmon" github/bonomani and included all patches/contrib and resolved all bugs I can. (I try to integrate all patches, bugs and features from SF) see the REAMDE for details This is not an official update of current "devmon" but I have difficulties to have an answer on current sourceforge repo, so I decided to publish what I have done. (I did not have any answer on my patches after myn years!?) As i am working on Centos, there are some specific things for systemd. I trying also to contact devmon admins to merge this work or part of it, so if you have a clue... If you want to test this work, you should simply take the files in the "modules" dir and it should work...with your current installation And of course any suggestions are welcome! BrunoBruno, As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo. One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd. Personally, I'll avoid systemd like the plague, however I'd think those modifications should be called out and isolated as well... Especially considering devmon normally runs as a perl based daemon... At least on my Scientific linux 6.10 system.
list Bruce Ferrell
Hi Bruno, I actually poll Linux (net-snmp), OS X (net-snmp from Mac Ports), Windows 2008r2, 7 and 10, PfSense 2.2.6/FreeBSD 10.1R25(bsnmpd) and Cisco; all of those from a Linux system
▸
On 5/10/19 9:31 AM, Bruno Manzoni wrote:Hi Bruce, Many thanks for your answer and I shared your point of view: if you use the version of sourceforge, you should put a ticket on it. Also I dont want to deserve nor Devmon on sourceforge nor Xymon: I just try to make my best (The road to hell is paved with good intentions) My goal of this proposition was just to move this discussion elsewhere: to not bother people of this mailing list And thanks for the info about memory leaks: just to document this problem: your are polling BSD OS, from a BSD OS or from a linux OS? Le 09.05.2019 à 16:17, Bruce Ferrell a écrit :On 5/9/19 3:47 AM, Bruno Manzoni wrote:Hello, I created a repo with "devmon" github/bonomani and included all patches/contrib and resolved all bugs I can. (I try to integrate all patches, bugs and features from SF) see the REAMDE for details This is not an official update of current "devmon" but I have difficulties to have an answer on current sourceforge repo, so I decided to publish what I have done. (I did not have any answer on my patches after myn years!?) As i am working on Centos, there are some specific things for systemd. I trying also to contact devmon admins to merge this work or part of it, so if you have a clue... If you want to test this work, you should simply take the files in the "modules" dir and it should work...with your current installation And of course any suggestions are welcome! BrunoBruno, As a long time user of devmon, I'd be fascinated to see an enumeration of the bugs, features, patches etc in your repo. One of the biggest "bugs" I've seen, and I haven't had time to chase it down is that over time devmon seems to leak memory like a sieve, becoming quite bloated. I run a cron job to kill (yes kill -9 ) and restart it every four hours... Not under systemd. Personally, I'll avoid systemd like the plague, however I'd think those modifications should be called out and isolated as well... Especially considering devmon normally runs as a perl based daemon... At least on my Scientific linux 6.10 system.
list Colin Coe
Hi, I've created a github issue as requested. https://github.com/bonomani/devmon/issues/10 Thanks
▸
On Sat, May 11, 2019 at 1:12 AM Bruce Ferrell <user-24fbf1912cfe@xymon.invalid> wrote:
Hi Bruno, I actually poll Linux (net-snmp), OS X (net-snmp from Mac Ports), Windows 2008r2, 7 and 10, PfSense 2.2.6/FreeBSD 10.1R25(bsnmpd) and Cisco; all of those from a Linux system On 5/10/19 9:31 AM, Bruno Manzoni wrote: Hi Bruce, Many thanks for your answer and I shared your point of view: if you use the version of sourceforge, you should put a ticket on it. Also I dont want to deserve nor Devmon on sourceforge nor Xymon: I just try to make my best (The road to hell is paved with good intentions) My goal of this proposition was just to move this discussion elsewhere: to not bother people of this mailing list And thanks for the info about memory leaks: just to document this problem: your are polling BSD OS, from a BSD OS or from a linux OS? Le 09.05.2019 à 16:17, Bruce Ferrell a écrit : On 5/9/19 3:47 AM, Bruno Manzoni wrote: Hello, I created a repo with "devmon" github/bonomani and included all patches/contrib and resolved all bugs I can. (I try to integrate all patches, bugs and features from SF) see the REAMDE for details This is not an official update of current "devmon" but I have difficulties to have an answer on current sourceforge repo, so I decided to publish what I have done. (I did not have any answer on my patches after myn years!?) As i am working on Centos, there are some specific things for systemd. I trying also to contact devmon admins to merge this work or part of it, so if you have a clue... If you want to test this work, you should simply take the files in the "modules" dir and it should work...with your current installation And of course any suggestions are welcome! Bruno
Xymon mailing user-d459c9d661b6@xymon.invalid
▸
Bruno,
As a long time user of devmon, I'd be fascinated to see an enumeration of
the bugs, features, patches etc in your repo.
One of the biggest "bugs" I've seen, and I haven't had time to chase it
down is that over time devmon seems to leak memory like a sieve, becoming
quite bloated. I run a cron job to kill (yes kill -9 ) and restart it
every four hours... Not under systemd.
Personally, I'll avoid systemd like the plague, however I'd think those
modifications should be called out and isolated as well... Especially
considering devmon normally runs as a perl based daemon... At least on my
Scientific linux 6.10 system.
Xymon mailing user-d459c9d661b6@xymon.invalid
Xymon mailing user-d459c9d661b6@xymon.invalid