Cron jobs not running

Discussion in 'Installation/Configuration' started by Rescue9, Nov 3, 2011.

  1. Rescue9

    Rescue9 Member

    As the topic says, the cron jobs won't run for a specific user. I have a test environment that is a close mirror to my production environment. The test environment has 1 job setup to run on @reboot that works fine, but the production server is giving me problems. As near as I can tell it has something to do with jailkit, but I'm so lost in my troubleshooting right now my head is spinning.

    Here's what I have so far.

    command to run is:
    Chroot Shell for ssh user is set to none

    When I add the cron job I get this in the /var/log/ispconfig/cron.log
    ERROR: /var/www/clients/client1/web5/etc is not owned by root:root!
    ERROR: /var/www/clients/client1/web5/etc is not owned by root:root!
    usermod: no changes
    PHP Warning:  mkdir(): File exists in /usr/local/ispconfig/server/plugins-available/ on line 293
    usermod: unlocking the user's password would result in a passwordless account.
    You should set a password with usermod -p to unlock this user's password.
    From there, I'm lost. What say you oh powerful ISPConfig developers.


    I looked in /etc/cron.d and there is only one ispc job: ispc_chrooted_web5
    the contents of that file are as such:
    @reboot web5    /teamspeak3-server_linux-x86/
    Last edited: Nov 3, 2011
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The cronjob is chrooted, so it can not run any commands outside of the chroot jail.

    Change the line:




    In the ispc_chrooted_web5 file and restart cron.
  3. Rescue9

    Rescue9 Member

    I changed the configuration file as noted and rebooted the machine. There are no errors in the cron.log file now, but the process still didn't start as expected.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    But you are able to execute ths cript when you run the two commands:

    su web5
    on the shell? If this is a server daemon, then I doubt that a normal shell user that is not the root user might start it at all.

Share This Page