Problem with tomcatstats
pserrano opened this issue · 11 comments
Hi, I have a problem with this module, i try to work on a machine which tomcat7 ssl system, with all cfg ok, munin-node log print me this :
Service 'tomcatstats' exited with status 1/0.
Error output from tomcatstats:
EXCEPTION: %d format: a number is required, not str
Service 'tomcatstats' exited with status 1/0.
The config it's ok, all with env. on plugin dir, i had try make changes on cfg without ssl and comment this, also comment more parameters and all prompt same error.
Thanks
Pablo
Hi Pablo,
I've done some testing with Tomcat 6 and Tomcat 7 and both worked without problems. What I could not test was using SSL to access the manager page and the configuration of user permissions is a bit different in Tomcat 7, so I added sample configuration file text for Tomcat 7 to the plugin script.
I would be needing your assistance to diagnose the problem:
- The error message seems to indicate that you might be running an older version of the plugin. Could you update to a newer version of PyMunin for testing?
- Could you please follow the Troubleshooting instructions and run the plugin with munin-run and --pidebug option and send the detailed error output.
Thanks in advance for helping improve this plugin,
Cheers,
Ali
Hi Ali,
Thx for your quick reply, i try to explain 2 questions that you asked me
First, i have last version from epel on CentOS 6:
Installed Packages
Name : PyMunin
Arch : noarch
Version : 0.9.4
Release : 2.el6
Size : 694 k
Repo : installed
From repo : epel
And second,
munin-run --pidebug tomcatstats
Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl5/vendor_perl/Munin/Node/Service.pm line 215.
And, thx you to make this great plugin :)
Regards
Pablo
Hi Pablo,
With munin-run it seems like the plugin is failing even before it is run; make sure you are running the plugin with the root user? On CentOS6, I've had some nasty problems with SELINUX in the past and I would recommend you to test the plugin after disabling SELINUX.
And then you are running a quite old version of PyMunin (0.9.4), and I clealy remember fixing some bugs in port number handling and the error messages have become much more informative in the newer versions, so I would recommend you to uninstall the RPM version of PyMunin and install the most recent version from PyPI:
# pip install PyMunin
You might have to install the python-pip RPM first.
Please inform me of the results of your testing, either to close the issue or to analyze new debugging output for fixing the problem.
Thanks for helping improve PyMunin,
Ali
Hi Ali,
I was searching more info for this error and that it isn't problem from your app
http://munin-monitoring.org/ticket/863
Epel is very old versions for all programs, i am very angry that last CentOS versions, all old releases and with a lot of bugs.
I will test to install a most recent version of munin :)
thx for all
Pablo
Hi Pablo
The problem is not EPEL, actually Fedora has a much more recent version, but the Enterprise distributions like RHEL, which forms the basis of CentOS favor stability over bleeding-edge versions and PyMunin being a quite a young project has had many updates in a short period of time.
Then it is also, because this is still unfortunately a one-man project and I cannot test each all the different configuration options of each plugin, but hopefully a larger user pool will be more efficient at identifying the bugs and I might have a automatic testing system some day.
And I have contacted the maintainer of the RPM package for Fedora and RHEL; he is actually quite helpful and he is willing to push a newer version to EPEL, but I would like to get the last version tested a bit more, to avoid bugging him with another update request soon.
Let me know, when you have an opportunity to test the new version; I've already done some testing of my own and as soon as you give an approval too, I will place a update request with the maintainer.
Thanks for improving PyMunin,
Ali
Hi Pablo,
Any update on this one? Could you do some testing with the new version?
Cheers,
Ali
hi Ali,
Nothing new, i had test with last version, update epel and i have same error :S i suppose that there is a system problem :S because now all plug-ins prompt same error that pymunin.
I am very confused, i hate perl :)
Cheers,
Pablo
Hi Pablo,
The error message from Munin seems to indicate a problem with directory permissions. I would recommend you to test Munin in another box. Then you can also try some RPM commands to verify permissions of the directories.
If, there is anything else I can help you with, just let me know. Unless you could do some testing on other box, I will have to close the issue soon.
Bye,
Ali
Hi Ali, i try to test in another box, and reply you with results
Cheers,
Pablo
Closing issue. If you could replicate the problem, you can reopen the issue.
This thread is dealing with the issue the wrong way. You are facing
http://munin-monitoring.org/ticket/1162
which had been solved
http://munin-monitoring.org/ticket/1128
several days before this thread was open.
You would have found that if you had QUOTED your google keywords:
https://www.google.fr/search?newwindow=1&dcr=0&source=hp&ei=MpAdWqzkIYr6wAKtnayYBw&q=%22Insecure+directory+in+%24ENV%7BPATH%7D+while+running+with+-T+switch+at+%2Fusr%2Fshare%2Fperl5%2FMunin%2FNode%2FService.pm+line+215.%22&oq=%22Insecure+directory+in+%24ENV%7BPATH%7D+while+running+with+-T+switch+at+%2Fusr%2Fshare%2Fperl5%2FMunin%2FNode%2FService.pm+line+215.%22&gs_l=psy-ab.3...2062.3025.0.3366.4.3.0.0.0.0.136.136.0j1.1.0....0...1c.1.64.psy-ab..3.1.135.0..35i39k1.0.m1GXTYyFDkk
Solution proposed in http://munin-monitoring.org/ticket/863 worked for me; but is not the proper way to deal with this: it was a munin bug, and it ought to be reported upstream ...