Over the past year or so, I've collected several errors that some I have found the solution for, others, like the one below are quite befuddling. I get this one every week when /etc/cron.weekly runs. What the heck is the "S" or what it is looking for? Also, I've checked with cpan, and according to cpan, it says it doesn't know what NET::DNS is, yet if I do an i NET::DNS, it returns 150-some odd net::dns entries. I'm not totally familiar with cpan, and just started using it a short time ago. Still the man3/s is really screwey for some reason. There's not a package called "s" n the repositories is there?
This is an x86_64 box updated as of yesterday after removing the httpd.1 stuff someone told me was the fix.
Thanks again all..
Sam
--- On Sun, 7/26/09, Sam Drinkard sam@wa4phy.net wrote:
From: Sam Drinkard sam@wa4phy.net Subject: [CentOS] Cleaning up some problems To: CentOS@centos.org Date: Sunday, July 26, 2009, 6:16 PM Over the past year or so, I've collected several errors that some I have found the solution for, others, like the one below are quite befuddling. I get this one every week when /etc/cron.weekly runs. What the heck is the "S" or what it is looking for? Also, I've checked with cpan, and according to cpan, it says it doesn't know what NET::DNS is,
NET::DNS is a core perl module. You don't want to get any version from CPAN.
$locate DNS.pm /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS.pm
Mr. X wrote:
--- On Sun, 7/26/09, Sam Drinkard sam@wa4phy.net wrote:
From: Sam Drinkard sam@wa4phy.net Subject: [CentOS] Cleaning up some problems To: CentOS@centos.org Date: Sunday, July 26, 2009, 6:16 PM Over the past year or so, I've collected several errors that some I have found the solution for, others, like the one below are quite befuddling. I get this one every week when /etc/cron.weekly runs. What the heck is the "S" or what it is looking for? Also, I've checked with cpan, and according to cpan, it says it doesn't know what NET::DNS is,
NET::DNS is a core perl module. You don't want to get any version from CPAN.
$locate DNS.pm /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS.pm
Hmmm... I don't have a perl version installed at that location. I've only added a few modules from cpan. What should I do to resolve this? yum erase perl, then reinstall or rpm -e whatever version of perl is installed? I can understand there are some packages that are of the i386 flavor instaled on the system from initial install, and probably some updates, but are they really necessary? LIke I have both versions of thunderbird, and I believe firefox as well, not to mention some I can't remember, but remember seeing them as dependencies or standalones. If it weren't for the LDM data streaming in 24/7, I'd blow it all away and start fresh, but I can't afford to lose the LDM data... too much to confiigure in the setup and scripts. Patching and or removing offending stuff is my game plan. BTW, what is wrong with using cpan? I thought they were the most up to date of the perl modules available, but I rarely ever see anything perl related in a yum update... maybe I just missed it. <sigh>
Sam
Sam Drinkard wrote:
NET::DNS is a core perl module. You don't want to get any version from CPAN.
$locate DNS.pm /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS.pm
I don't believe on CentOS this is a "core" module. Try a Yum install of perl-Net-DNS (in the base repository). -Alan
Alan Sparks wrote:
Sam Drinkard wrote:
NET::DNS is a core perl module. You don't want to get any version from CPAN.
$locate DNS.pm /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS.pm
I don't believe on CentOS this is a "core" module. Try a Yum install of perl-Net-DNS (in the base repository). -Alan
Alan,
The package perl-Net-DNS is already installed and is up do date. I'm wondering if that command coming from cron.weekly about the "s" file has anything to do with it? There does not seem to be any ill effects from the cron job, but it irritates me to see errors and not know why or how to fix stuff, especially when the keyword is "s" :( Perhaps I should just remove that particular command from the cron.weekly and see what happens, or at least comment it out.
Sam
Sam Drinkard wrote:
Alan Sparks wrote:
Sam Drinkard wrote:
NET::DNS is a core perl module. You don't want to get any version from CPAN.
$locate DNS.pm /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS.pm
I don't believe on CentOS this is a "core" module. Try a Yum install of perl-Net-DNS (in the base repository). -Alan
Alan,
The package perl-Net-DNS is already installed and is up do date.I'm wondering if that command coming from cron.weekly about the "s" file has anything to do with it? There does not seem to be any ill effects from the cron job, but it irritates me to see errors and not know why or how to fix stuff, especially when the keyword is "s" :( Perhaps I should just remove that particular command from the cron.weekly and see what happens, or at least comment it out.
Sam
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
As others have noted, please let us know any details about whatever error you are seeing, we've seen no details yet. -Alan
Sam Drinkard wrote on Sun, 26 Jul 2009 22:32:54 -0400:
I don't have a perl version installed at that location. I've only added a few modules from cpan.
You have no Perl, but installed modules via CPAN? Digest that. What are you telling us? And, btw, you didn't even tell what your actual problem is. Can you please work on the phrasing of your questions to this list? You seem to be very reluctant to learn from replies to your earlier questions.
TW, what is wrong with using cpan?
You have been using an rpm-based Linux installation long enough to know that by yourself or to google it up by yourself.
Kai
Hello everyone,
I compiled the linux kernel 2.6.18.8 in CentOS 5.3, but when make install, the system says:
WARNING: No module sata_nv found for kernel 2.6.18.8, continuing anyway WARNING: No module sata_nv found for kernel 2.6.18.8, continuing anyway
Just if I installed RHEL 5 version's nforce driver, it still shows these warning message. When reboot, it cannot load the system. The linux kernel package is downloaded from kernel.org directory.
I tried and google it, but I could not find the answer, does anyone can help me?
Hanmo wrote on Mon, 27 Jul 2009 17:35:56 +0800:
Hello everyone,
Please stop hijacking threads. If you want to ask something then hit the button "new message". Thanks!
Kai
On Mon, Jul 27, 2009 at 10:35 AM, HanmoHanmoChine@gmail.com wrote:
Hello everyone,
I compiled the linux kernel 2.6.18.8 in CentOS 5.3, but when make install, the system says:
WARNING: No module sata_nv found for kernel 2.6.18.8, continuing anyway WARNING: No module sata_nv found for kernel 2.6.18.8, continuing anyway
Just if I installed RHEL 5 version's nforce driver, it still shows these warning message. When reboot, it cannot load the system. The linux kernel package is downloaded from kernel.org directory.
I tried and google it, but I could not find the answer, does anyone can help me? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Please visit this page: http://wiki.centos.org/HowTos#head-c4dbf9ecb355694c78175c7eaad46a2472a3849b
Kai Schaetzl wrote:
Sam Drinkard wrote on Sun, 26 Jul 2009 22:32:54 -0400:
I don't have a perl version installed at that location. I've only added a few modules from cpan.
You have no Perl, but installed modules via CPAN? Digest that. What are you telling us? And, btw, you didn't even tell what your actual problem is. Can you please work on the phrasing of your questions to this list? You seem to be very reluctant to learn from replies to your earlier questions.
TW, what is wrong with using cpan?
You have been using an rpm-based Linux installation long enough to know that by yourself or to google it up by yourself.
Kai
Kai,
Yes, I've been using Centos plenty long enough to pickup a few tid-bits of information that have been useful, but a lot of the info passed on the mailing list is either way over my head, or I have no use for it now or in the future. As for the "exact problem" -- it's an error message, and I don't like seeing error messages when I have no clue where to even begin looking besides the source that is causing them. As for learning from earlier questions, yes, as a matter of a fact, I do learn from them, and archive a LOT of threads that deal with things I've seen before or something I feel I might need/use later on. There's nothing wrong with being curious about error messages, I just don't like to see them as I don't know what else might be being affected. As for the cpan, the modules were not available via any repository, hence cpan. All of the modules I grabbbed were for one package and only one package that deals with my weather data and its software. Ever heard of LDM or Gempak.. both required some modules before it would even install, and they were NOT available anywhere else. This software does not get updated but once in a blue moon, and has nothing to do with Centos itself, other than being hosted on it. One last thing.. I don't appreciate one bit you taking jabs at me and my methods. You don't know me, and know even less about how I used my computers. I follow instructions that come with packages I install, not any kind of maybe this or maybe that. So in the future, I'd appreciate it if you'd leave off the jabs and stabs about my knowledge of what I'm doing. I'm no guru by any sort, but if I can't figure something out, I thought the mailing list was where to ask, unless you think every problem ever occured is covered under some form of google... I assure you -- IT"S NOT.
Sam
Sam Drinkard wrote on Mon, 27 Jul 2009 10:03:39 -0400:
As for the "exact problem" -- it's an error message
You may not have noticed that you didn't quote that error message. At least not in the messages I got.
Kai
BTW, what is wrong with using cpan? I thought they were the most up to date of the perl modules available, but I rarely ever see anything perl related in a yum update... maybe I just missed it. <sigh>
Hello Sam: I can't answer the parent question, but I do use CPAN modules quite often. The main difference is that I always convert them to RPM first using the cpan2rpm utility. It takes a few extra steps, but I've found that it makes upgrades and troubleshooting a lot easier.
Hi,
On Sun, Jul 26, 2009 at 22:32, Sam Drinkardsam@wa4phy.net wrote:
BTW, what is wrong with using cpan?
It does not work along with RPM very well... if you mix CPAN with RPM (and you can't avoid RPM considering you need the OS Perl that comes in RPM) a future update of the RPMs might break CPAN-installed packages, or might even break the whole Perl install.
If you need Perl modules, I recommend you look into RPMforge, their collection of RPM-packaged Perl modules is great, and if there is anything else you need that is not there you may request it on their mailing list.
HTH, Filipe
Hi,
On Sun, Jul 26, 2009 at 21:16, Sam Drinkardsam@wa4phy.net wrote:
I get this one every week when /etc/cron.weekly runs.
Which one? You never included the error message you actually have... Please re-read your original e-mail, and post the exact error message you have, and also where you get it (e-mail from cron?).
HTH, Filipe
Filipe Brandenburger wrote:
Hi,
On Sun, Jul 26, 2009 at 21:16, Sam Drinkardsam@wa4phy.net wrote:
I get this one every week when /etc/cron.weekly runs.
Which one? You never included the error message you actually have... Please re-read your original e-mail, and post the exact error message you have, and also where you get it (e-mail from cron?).
HTH, Filipe _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
If I recall, but I'll look back, I quoted the exact message output from the run of cron.weekly, but here it is again::
# ./makewhatis.cron cat: /usr/share/man/man3/s: No such file or directory Read file error: /usr/share/man/man3/s No such file or directory cat: Net::DNS: No such file or directory Read file error: Net::DNS No such file or directory
And the other cron job in that subdir is: 0anacron.
cat 0anacron #!/bin/sh # anacron's script # This script updates anacron time stamps. It is called through run-parts either by anacron itself or by cron # The scrips is called "0anacron" to assure that is will be executed # _before_ all other scripts. # Don't run anacron if this script is called by anacron. if [ ! -e /var/run/anacron.pid]; then anacron -u cron.weekly. fi
The error message is logged within the daily log file, but of course, only once a week. Two problems: Net::DNS IS installed, and what the hell is the "s". Try googling for "s" or even the error message.... zilch for me. As I mentioned earlier, I know of no other effects this failure has, but knowing something has run amok does not make happy.
Ok.. maybe have fixed it on my own. Under the man page for makewhatis, there are some options that can be passed. The server had an "s" and my desktop has a "w" as the option. I changed them to opposites, so if one works and the desktop gives the same error message, then I guess the problem is solved. we'll see...
Sam
Sam Drinkard wrote:
# ./makewhatis.cron cat: /usr/share/man/man3/s: No such file or directory Read file error: /usr/share/man/man3/s No such file or directory cat: Net::DNS: No such file or directory Read file error: Net::DNS No such file or directory
Look what's in /usr/share/man/man3/
See if there are any files or directories in there with spaces in them that start with a lower case s ?
Just a guess..
I disable makewhatis on my systems, I don't use the database, and I don't need the I/O bogging down on my VMs when it runs(I also disable it on physical systems for consistency)
nate
If I recall, but I'll look back, I quoted the exact message output from the run of cron.weekly, but here it is again::
# ./makewhatis.cron cat: /usr/share/man/man3/s: No such file or directory Read file error: /usr/share/man/man3/s No such file or directory cat: Net::DNS: No such file or directory Read file error: Net::DNS No such file or directory
And the other cron job in that subdir is: 0anacron.
This looks suspiciously like you're trying to run a crontab file as a script. Can you post the output of:
cat makewhatis.cron
Kwan Lowe wrote:
If I recall, but I'll look back, I quoted the exact message output from the run of cron.weekly, but here it is again::
# ./makewhatis.cron cat: /usr/share/man/man3/s: No such file or directory Read file error: /usr/share/man/man3/s No such file or directory cat: Net::DNS: No such file or directory Read file error: Net::DNS No such file or directory
And the other cron job in that subdir is: 0anacron.
This looks suspiciously like you're trying to run a crontab file as a script. Can you post the output of:
cat makewhatis.cron _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
That is the exact cron entry "makewhatis.cron, and all below that is the output from the command.
Sam
-
Alan Sparks -
Filipe Brandenburger -
Hanmo -
Kai Schaetzl -
Kwan Lowe -
Lucian＠lastdot.org -
Mr. X -
nate -
Sam Drinkard