NovemberRain

Well-Known Member
Sep 24, 2003
112
3
168
İstanbul
cPanel Access Level
Root Administrator
I also get something like this:

Cron <[email protected]> /usr/local/bandmin/bandmin

modprobe: QM_MODULES: Function not implemented

modprobe: QM_MODULES: Function not implemented

modprobe: Can't locate module ip_tables
iptables v1.2.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
modprobe: QM_MODULES: Function not implemented
 

nurseryboy

Well-Known Member
Mar 3, 2003
78
0
156
NovemberRain said:
I also get something like this:

Cron <[email protected]> /usr/local/bandmin/bandmin

modprobe: QM_MODULES: Function not implemented

modprobe: QM_MODULES: Function not implemented

modprobe: Can't locate module ip_tables
iptables v1.2.8: can't initialize iptables table `filter': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded.
modprobe: QM_MODULES: Function not implemented
I am getting this too.
 

claudio

Well-Known Member
Jul 31, 2004
201
0
166
first time weekly cron error on RH9 and STABLE 65

Hi Guys

Well yesterday my server after cron rotines stoped with Kernel Bug and today it performed early crons pretty fine except by this bellow:


/etc/cron.weekly/makewhatis.cron:

awk: cmd. line:121: (FILENAME=- FNR=1068) fatal error: internal error
/usr/sbin/makewhatis: line 360: 8891 Broken pipe find . -name '*' $findarg -print
8892 Aborted | $AWK '

function readline() {
if (use_zcat) {
result = (pipe_cmd | getline);
if (result < 0) {
print "Pipe error: " pipe_cmd " " ERRNO > "/dev/stderr";
}
} else {
result = (getline < filename);
if (result < 0) {
print "Read file error: " filename " " ERRNO > "/dev/stderr";
}
}
return result;
}

function closeline() {
if (use_zcat) {
return close(pipe_cmd);
} else {
return close(filename);
}
}

function do_one() {
insh = 0; thisjoin = 1; done = 0;
entire_line = "";

if (verbose) {
print "adding " filename > "/dev/stderr"
}

use_zcat = match(filename,"\\.Z$") ||
match(filename,"\\.z$") || match(filename,"\\.gz$");
if(use_zcat) {
filename_no_gz = substr(filename, 0, RSTART - 1);
} else {
filename_no_gz = filename;
}

i cutted many lines because they dont fit in this submit reply :eek:

as soon as i discover something about it will post here

regards

claudio
 

mhbrands

Member
Apr 12, 2003
17
0
151
Kansas
at the same time I got the broken pipe message, my cpanel had this written on it in WHM.

You are running an insecure apache setup. You should run /scripts/easyapache or if you are running cPanel 7.1.9 or later (click here) to upgrade to a newer version as soon as possible to avoid your system being compromised.

Am updating apache now and will check the logfile again tomorrow to see if this fixes it. :)
 

mhbrands

Member
Apr 12, 2003
17
0
151
Kansas
This seems to have solved the problem, at least for me. No more broken pips comments! :D
 

Habikki

Member
Jun 16, 2003
11
0
151
I know this is a little late, but I was getting the zcat: stdout: Broken pipe errors for about 20 days and what fixed mine was that the registration with RHE up2date had expired. Got reregistered and viola! Hope this helps anyone else.

Cheers,
Robby
 

flipper

Member
Sep 14, 2002
20
0
151
The server that we had this problem on had a makewhatis cronjob in both daily and weekly. Since the cronjob has a lock file, if the cron.daily hasn't finished before it runs under cron.weekly, it gives the error. It's a problem with the script not reading the lock file as it should.
 

myusername

Well-Known Member
PartnerNOC
Mar 6, 2003
693
1
168
chown -R us.*yourbase*
cPanel Access Level
DataCenter Provider
Twitter
After CentOS 3.5 I have makwhatis.cron in /etc/cron.daily and /etc/cron.weekly

What's the point? It seems to be fairly useless. If it should not be abondoned for good, maybe make it a weekly only cronjob.

Daily seems a bit unlikely to be ever updated on a "daily need to get it now!" basis.

Anyone else think to the contrary? Seems not worth the support requests to have both tying up the lock file and producing errors.
 

RavenSoul_

Well-Known Member
Nov 2, 2004
95
2
156
Belgium
Any solutions on this one yet?


Daily cron:

Code:
/etc/cron.daily/logrotate:

error: Ignoring samba.rpmnew, because of .rpmnew ending

Weekly cron:

Code:
/etc/cron.weekly/makewhatis.cron:


zcat: stdout: Broken pipe

zcat: stdout: Broken pipe

...
p.s. It seems like Centos (3.5) has more issues with cPanel :(
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,466
31
473
Go on, have a guess
You can remove that /etc/logrotate.d/samba.rpmnew file as it's not needed.

As for the zcat errors from makewhatis, I'd suggest that you simply ignore them. If you cannot bear to do that, you'll need to go through all the man pages and look for broken symlinks which is the usual cause of those errors and is not a real problem.
 

RavenSoul_

Well-Known Member
Nov 2, 2004
95
2
156
Belgium
chirpy said:
You can remove that /etc/logrotate.d/samba.rpmnew file as it's not needed
Ok, tnx.

I will delete it as soon as I gained shell back...

--

The other one, I gonna put "on hold" as it's not important, like you said :p
 

sexshun

Active Member
Sep 28, 2005
26
0
151
I'm not going to read the man pages for anything new I install so I guess i'm going to remove it for now...haha
 

jwiens

Member
Mar 8, 2004
16
0
151
My usual fix is to just to either shut down the scripts entirely (remove them from the cron.daily and cron.weekly directories, or add exit 0 to the top of the script. If you'd rather leave them running but just not get the emails regardless of whether they work or not, add "2>/dev/null" to the end of the makewhatis commands in both scripts:

Code:
#!/bin/bash

LOCKFILE=/var/lock/makewhatis.lock

# the lockfile is not meant to be perfect, it's just in case the
# two makewhatis cron scripts get run close to each other to keep
# them from stepping on each other's toes.  The worst that will
# happen is that they will temporarily corrupt the database...
[ -f $LOCKFILE ] && exit 0
trap "{ rm -f $LOCKFILE ; exit 255; }" EXIT
touch $LOCKFILE
makewhatis -u -w 2>/dev/null
#^^^^^^^^^^^^^^^^^^^^^^^^^^^
#   Change is above here
#^^^^^^^^^^^^^^^^^^^^^^^^^^^
exit 0
That should make those errors not get sent back to you as emails.
 

Radio_Head

Well-Known Member
Verifed Vendor
Feb 15, 2002
2,051
1
343
my solution is

execute

#makewhatis -v -u -w

from command line (note the -v with Verbose output)

then execute
#makewhatis -v -w

take note of the errors and correct the symlink if required.