Bug 196544
| Summary: | Latest rrdtool stucks after some time using | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Scheck <redhat-bugzilla> |
| Component: | rrdtool | Assignee: | Jarod Wilson <jarod> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | extras-qa |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.2.13-3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-06-25 16:09:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Ah and rrdtool-perl *is* installed... Hrm, the error output isn't being particularly helpful, since its simply saying it can't find RRDs.pm, which does indeed exist in @INC (specifically, in /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi, same place the 1.0.50 build put it). Any way to increase verbosity of what gets logged to maybe get some more useful info? I'm having a hard time thinking how this could be a build issue, since RRDs.pm is essentially nothing more than a text file that gets copied into place straight out of the source tarball... But the failure versus your build certainly is interesting. For comparison, can you attach the spec you're using for your own build? As far as I can see, the naming misery perl-rrdtool vs. rrdtool-perl caused some strange yum confusion which was the reason this problem. Maybe other factors also were involved, too, because I'm not able to reproduce the same situation now, when upgrading from an older rrdtool to the latest one. |
Description of problem: Unfortunately latest rrdtool for Fedora Core 5 stucks after some time using, from HotSaNIC logfile: --- snipp --- Uncaught exception from user code: Can't locate RRDs.pm in @INC (@INC contains: ../../lib /usr/lib/perl5/ site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386- linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/ lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8. 4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/ site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 / usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/ vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386- linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi / usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/ vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386- linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/ 5.8.7 /usr/lib/perl/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/ perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/ vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ../../lib/HotSaNICmod.pm line 9. BEGIN failed--compilation aborted at ../../lib/HotSaNICmod.pm line 9. Compilation failed in require at ./read-data.pl line 8. BEGIN failed--compilation aborted at ./read-data.pl line 8. at ./read-data.pl line 8 [Fri 2006-06-23 23:51:02] - rrdtimer [5842]: waiting for module's PID-file --- snapp --- The older rrdtool-1.0.50-4.fc5 works without any problem. Interesting is, that I still can't reproduce the whole problem for months now when using my own RPM package of rrdtool for this. This results IMHO that it is a packaging problem as my own 1.2.13 package works... Version-Release number of selected component (if applicable): rrdtool-1.2.13-3.fc5 How reproducible: Very often. Actual results: Latest rrdtool stucks after some time using... Expected results: No stucks and strange error messages in logfiles like above.