cron job permission problem after 2.1.3 update

General Interworx Control Panel Info General Inquries
1

Hi,

Since the update to 2.1.3 we recieve errors 1 time a day from the fively and hourly iworx.pex cron job (I think it’s the same time that (yum) runs):

/home/interworx/cron ; ./iworx.pex --hourly

/bin/bash: line 0: cd: /home/interworx/cron: Permission denied
/bin/bash: ./iworx.pex: No such file or directory

/home/interworx/cron ; ./iworx.pex --fively

/bin/bash: line 0: cd: /home/interworx/cron: Permission denied
/bin/bash: ./iworx.pex: No such file or directory

The permissions on the /home/interworx/cron directory is:
drwxr-x— 2 iworx iworx 4096 Apr 18 14:31 cron/

The permissions on /home/interworx/cron/decoder.sh is:

-rwxr-x— 1 root iworx 196 Oct 15 2003 decoder.sh

I’ve tried running cvspermsfix.pex as root but it has not changed any perms in the cron directory.

Anyone with ideas?

Thanks
-tsl-

2

We’ve pushed out a couple different versions of the 2.1.3 release, and these are very likely just caused by the cron running as the update is running. It’s not a cause for concern, and these messages should stop now.

Paul

3

Ok, thanks Paul.

Where is the time actually set for yum to run (automatic updates on)?
It runs on our server at 1pm local time and it would be nice to set this to early morning instead.
We have Iworx-CP on Centos 4.3

rgds
-tsl-

4

It runs at the end of the “daily” iworx cron job. If you go to NodeWorx -> Server -> CRON, it’s the entry that runs:

cd /home/interworx/cron; ./iworx.pex --daily

You can change the time this runs there.

Paul

5

Ah, excellent :slight_smile:

Thanks
-tsl-

6

I’ve been having the same problem, but it wasn’t just once, and it’s only with the fively cron job. It’s been ongoing for a few days, including this morning:

Sunday April 16, 2006:
/bin/bash: line 1: cd: /home/interworx/cron: Permission denied
/bin/bash: line 1: ./iworx.pex: No such file or directory

Monday April 17, 2006:
/bin/bash: line 1: cd: /home/interworx/cron: Permission denied
/bin/bash: line 1: ./iworx.pex: No such file or directory

Tuesday April 18, 2006:
/bin/bash: line 1: cd: /home/interworx/cron: Permission denied
/bin/bash: line 1: ./iworx.pex: No such file or directory

Wednesday April 19, 2006:
tinydns-data: fatal: unable to move data.tmp to data.cdb: file does not exist

I too ran the cvs perm fix (Sunday - after I noticed the first cron error)…

The last error is different from the others. Any ideas? Or should I just wait it out too?

7

Hi it happens again tomorrow, bump this thread and we’ll check it out.

Paul

8

Didn’t happen again the very next day (which I was happy about), but sure enough, it happened again the next day (last night)

Friday morning, April 21, 2006:
tinydns-data: fatal: unable to move data.tmp to data.cdb: file does not exist

9

Open up a support ticket and we’ll look into the tinydns message.

Paul

10

I’m getting the same tinydns cron error once a day around 2am (unable to move data.tmp to data.cdb: file does not exist). I’d really like to know what the resolution is for this.

11

For most people, the problem eventually went away. How many days in a row has this been happening? Is it every day or only happens intermittently?

12

It appears to be every day