Re: Cron Job since InterWorx Upgrade

[int]

Hi,

I've had some nightly Cronjobs running since I got my server in February, without any problems. Ever since the latest Interworx update though (to be specific, since September 8, 2005), the emails which I receive for these jobs all contain errors:


./iworx.pex: line 5: /home/interworx/bin/php: Permission denied
./iworx.pex: line 5: exec: /home/interworx/bin/php: cannot execute: Permission denied


and


Stopping httpd: /sbin/service: line 68: 2297 Terminated env -i LANG=$LANG PATH=$PATH TERM=$TERM "${SERVICEDIR}/${SERVICE}" ${OPTIONS}


The actual content of my CRONTAB is the following:

10 0 * * * /usr/local/bin/rkhunter --update > /dev/null 2>&1
25 0 * * * /usr/local/bin/rkhunter -c --nocolors --cronjob --report-mode --createlogfile --skip-keypress --quiet
25 3 * * * /sbin/service httpd restart
26 3 * * * /sbin/service mysqld restart


Any ideas?

Thanks.

[IWorx-Paul]

Just based on those messages it looks like permissions are messed up. I'd try running

home/interworx/bin/cvspermsfix.pex

as root.

I'd also check RPM versions and make sure nothing is out of whack -
rpm -qa | grep interworx

normal output for this would be:

interworx-2.1.1-6.iworx
interworx-nodeworx-2.1.1-6.iworx
interworx-siteworx-2.1.1-6.iworx

Paul

[int]

Just based on those messages it looks like permissions are messed up. I'd try running

home/interworx/bin/cvspermsfix.pex

as root.

I'd also check RPM versions and make sure nothing is out of whack -
rpm -qa | grep interworx

normal output for this would be:

interworx-2.1.1-6.iworx
interworx-nodeworx-2.1.1-6.iworx
interworx-siteworx-2.1.1-6.iworx

Paul

[root@server bin]# ./cvspermsfix.pex
[root@server bin]#
[root@server bin]# rpm -qa | grep interworx
interworx-2.1.1-6.iworx
interworx-siteworx-2.1.1-6.iworx
interworx-nodeworx-2.1.1-6.iworx


I'll update this tonight so see if that fixed my Crontab problem. Thanks for the quick reply!

[int]

I'll update this tonight so see if that fixed my Crontab problem. Thanks for the quick reply!

Didn't receive the iworx.pex error at 3:05am like I used to, but I received the following still:

Stopping httpd: /sbin/service: line 68: 30792 Terminated env -i LANG=$LANG PATH=$PATH TERM=$TERM "${SERVICEDIR}/${SERVICE}" ${OPTIONS}



Looking at old Crontab emails (keep in mind i haven't changed anything at all manually), they used to look like the following, for the restart of the httpd process:

Stopping httpd: [ OK ] Flushing IPC Semaphores[ OK ] Starting httpd: [ OK ]

[int]

I'm still receiving the same error for the restart of the HTTPD service.

Also, something new now:


ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)
ERROR: illegal attempt to update using time 1127970482 when last update time is 1127970484 (minimum one second step)


Looks like something is majorly wrong?!

[timryberg]

Have you tried killing the httpd service (killall httpd) and then starting it again (service httpd start).

Also, I 'm really relucatnt to suggest it but a server reboot does tend to fix wierd things like this.

[int]

Have you tried killing the httpd service (killall httpd) and then starting it again (service httpd start).

Also, I 'm really relucatnt to suggest it but a server reboot does tend to fix wierd things like this. Rebooted the server already - way before I posted - that's my solution to everything as i don't care for my server uptime ;) The thing is, if i do a "service httpd restart", it works just fine. It's the httpd cron job that I get emailed about which is messing up lately. I know someone's going to say to remove the cron job and re-add it, but this all started since the Interworx upgrade so i'd like to know what caused it and I wanted to make the Interworx team aware of it as it appears to be a bug. Please let me know if you guys have any suggestions on how I can fix this problem easily. Thanks for the reply / for the effort timryberg.

[timryberg]

Not a problem but let me point out that killing, stopping and then starting, and restarting the service are three different things and sometimes have different effects.
Good luck. :-)

[IWorx-Socheat]

Have you tried re-syncing the server's clock? Those errors are complaining about updating using a time that has already passed.

As root run:
ntpdate bitsy.mit.edu

See if that helps.