[campsite-support] crontab error
  • I'm thinking this is a fairly common problem as i've run into it everytime i've installed on any os. I'm getting an error during the automation step. 'Error: could not save cron job files. Could not run the crontab executable.' this is easily side stepped by a replacement file for CampInstallationBase.php found here http://www.nabble.com/list-articles-pages-td20771187.html at the bottom of the page. this script is not up to date or just written incorrectly and does not know where the demo data is. i've manually corrected the script several times but now find it easier to simply wait until the automation step to replace that script. my question is why is this error appearing? my crontab is set up with a cron.deny file with nothing in it. this allows every user to access crontab. apache does have access to crontab and i've tested this with my own simple php script. why is it erroring and is there a fix that could be documented for frustrated users? i'd much rather just get all
    my permissions correct, if that is indeed the problem, than use some replacement CampInstallationBase.php file.
  • 8 Comments sorted by
  • Hi,

    this usually appears if php runs in safe_mode, and/or have some functions
    disabled in php.ini (search for disable_functions). Is this the case?

    We should change the installer to continue, even the cron binary cannot
    executed. Instead, can prompt how to solve this on command line. Should I
    do, or any veto?

    Sebastian



    > -----Original Message-----
    > From: cbell@falconsys.com [mailto:cbell@falconsys.com]
    > Sent: Wednesday, March 25, 2009 10:08 PM
    > To: campsite-support@campware.org
    > Subject: [campsite-support] crontab error
    >
    >
    > I'm thinking this is a fairly common problem as i've run into it
    > everytime i've installed on any os. I'm getting an error during
    > the automation step. 'Error: could not save cron job files. Could
    > not run the crontab executable.' this is easily side stepped by a
    > replacement file for CampInstallationBase.php found here
    > http://www.nabble.com/list-articles-pages-td20771187.html at the
    > bottom of the page. this script is not up to date or just written
    > incorrectly and does not know where the demo data is. i've
    > manually corrected the script several times but now find it
    > easier to simply wait until the automation step to replace that
    > script. my question is why is this error appearing? my crontab is
    > set up with a cron.deny file with nothing in it. this allows
    > every user to access crontab. apache does have access to crontab
    > and i've tested this with my own simple php script. why is it
    > erroring and is there a fix that could be documented for
    > frustrated users? i'd much rather just get all
    > my permissions correct, if that is indeed the problem, than use
    > some replacement CampInstallationBase.php file.
  • Hi Sebastian,

    Please don't do anything yet, the problem may have been caused by an
    obsolete version of the file.

    Mugur

    On Thu, Mar 26, 2009 at 3:32 PM, Sebastian Goebel
    wrote:

    > Hi,
    >
    > this usually appears if php runs in safe_mode, and/or have some functions
    > disabled in php.ini (search for disable_functions). Is this the case?
    >
    > We should change the installer to continue, even the cron binary cannot
    > executed. Instead, can prompt how to solve this on command line. Should I
    > do, or any veto?
    >
    > Sebastian
    >
    >
    >
    > > -----Original Message-----
    > > From: cbell@falconsys.com [mailto:cbell@falconsys.com]
    > > Sent: Wednesday, March 25, 2009 10:08 PM
    > > To: campsite-support@campware.org
    > > Subject: [campsite-support] crontab error
    > >
    > >
    > > I'm thinking this is a fairly common problem as i've run into it
    > > everytime i've installed on any os. I'm getting an error during
    > > the automation step. 'Error: could not save cron job files. Could
    > > not run the crontab executable.' this is easily side stepped by a
    > > replacement file for CampInstallationBase.php found here
    > > http://www.nabble.com/list-articles-pages-td20771187.html at the
    > > bottom of the page. this script is not up to date or just written
    > > incorrectly and does not know where the demo data is. i've
    > > manually corrected the script several times but now find it
    > > easier to simply wait until the automation step to replace that
    > > script. my question is why is this error appearing? my crontab is
    > > set up with a cron.deny file with nothing in it. this allows
    > > every user to access crontab. apache does have access to crontab
    > > and i've tested this with my own simple php script. why is it
    > > erroring and is there a fix that could be documented for
    > > frustrated users? i'd much rather just get all
    > > my permissions correct, if that is indeed the problem, than use
    > > some replacement CampInstallationBase.php file.
    >
    >
  • Sebastian Goebel wrote:
    > Hi,
    >
    > this usually appears if php runs in safe_mode, and/or have some functions
    > disabled in php.ini (search for disable_functions). Is this the case?
    >
    > We should change the installer to continue, even the cron binary cannot
    > executed. Instead, can prompt how to solve this on command line. Should I
    > do, or any veto?
    >
    > Sebastian
    >
    >
    >
    >
    >> -----Original Message-----
    >> From: cbell@falconsys.com [mailto:cbell@falconsys.com]
    >> Sent: Wednesday, March 25, 2009 10:08 PM
    >> To: campsite-support@campware.org
    >> Subject: [campsite-support] crontab error
    >>
    >>
    >> I'm thinking this is a fairly common problem as i've run into it
    >> everytime i've installed on any os. I'm getting an error during
    >> the automation step. 'Error: could not save cron job files. Could
    >> not run the crontab executable.' this is easily side stepped by a
    >> replacement file for CampInstallationBase.php found here
    >> http://www.nabble.com/list-articles-pages-td20771187.html at the
    >> bottom of the page. this script is not up to date or just written
    >> incorrectly and does not know where the demo data is. i've
    >> manually corrected the script several times but now find it
    >> easier to simply wait until the automation step to replace that
    >> script. my question is why is this error appearing? my crontab is
    >> set up with a cron.deny file with nothing in it. this allows
    >> every user to access crontab. apache does have access to crontab
    >> and i've tested this with my own simple php script. why is it
    >> erroring and is there a fix that could be documented for
    >> frustrated users? i'd much rather just get all
    >> my permissions correct, if that is indeed the problem, than use
    >> some replacement CampInstallationBase.php file.
    >>
    >
    >
    My safe_mode = off. The user on nabble also suggested this. Are there
    specific functions that you speak of that need to be turned on?
  • Mugur Rus wrote:
    > Hi Sebastian,
    >
    > Please don't do anything yet, the problem may have been caused by an
    > obsolete version of the file.
    >
    > Mugur
    >
    > On Thu, Mar 26, 2009 at 3:32 PM, Sebastian Goebel
    > > wrote:
    >
    > Hi,
    >
    > this usually appears if php runs in safe_mode, and/or have some
    > functions
    > disabled in php.ini (search for disable_functions). Is this the case?
    >
    > We should change the installer to continue, even the cron binary
    > cannot
    > executed. Instead, can prompt how to solve this on command line.
    > Should I
    > do, or any veto?
    >
    > Sebastian
    >
    >
    >
    > > -----Original Message-----
    > > From: cbell@falconsys.com
    > [mailto:cbell@falconsys.com ]
    > > Sent: Wednesday, March 25, 2009 10:08 PM
    > > To: campsite-support@campware.org
    >
    > > Subject: [campsite-support] crontab error
    > >
    > >
    > > I'm thinking this is a fairly common problem as i've run into it
    > > everytime i've installed on any os. I'm getting an error during
    > > the automation step. 'Error: could not save cron job files. Could
    > > not run the crontab executable.' this is easily side stepped by a
    > > replacement file for CampInstallationBase.php found here
    > > http://www.nabble.com/list-articles-pages-td20771187.html at the
    > > bottom of the page. this script is not up to date or just written
    > > incorrectly and does not know where the demo data is. i've
    > > manually corrected the script several times but now find it
    > > easier to simply wait until the automation step to replace that
    > > script. my question is why is this error appearing? my crontab is
    > > set up with a cron.deny file with nothing in it. this allows
    > > every user to access crontab. apache does have access to crontab
    > > and i've tested this with my own simple php script. why is it
    > > erroring and is there a fix that could be documented for
    > > frustrated users? i'd much rather just get all
    > > my permissions correct, if that is indeed the problem, than use
    > > some replacement CampInstallationBase.php file.
    >
    >
    found line disable_functions and is emtpy.
    disable_functions =
    still wondering why i'm getting this error. also i can run crontab from
    exec in my own scripts. doesn't seem like a permissions issue.
  • Did you install the file I sent you before trying again?

    Mugur

    On Thu, Mar 26, 2009 at 11:47 PM, Chelsea Bell wrote:

    > Mugur Rus wrote:
    >
    >> Hi Sebastian,
    >>
    >> Please don't do anything yet, the problem may have been caused by an
    >> obsolete version of the file.
    >>
    >> Mugur
    >>
    >> On Thu, Mar 26, 2009 at 3:32 PM, Sebastian Goebel <
    >> devel@yellowsunshine.de > wrote:
    >>
    >> Hi,
    >>
    >> this usually appears if php runs in safe_mode, and/or have some
    >> functions
    >> disabled in php.ini (search for disable_functions). Is this the case?
    >>
    >> We should change the installer to continue, even the cron binary
    >> cannot
    >> executed. Instead, can prompt how to solve this on command line.
    >> Should I
    >> do, or any veto?
    >>
    >> Sebastian
    >>
    >>
    >>
    >> > -----Original Message-----
    >> > From: cbell@falconsys.com
    >> [mailto:cbell@falconsys.com ]
    >> > Sent: Wednesday, March 25, 2009 10:08 PM
    >> > To: campsite-support@campware.org
    >>
    >> > Subject: [campsite-support] crontab error
    >> >
    >> >
    >> > I'm thinking this is a fairly common problem as i've run into it
    >> > everytime i've installed on any os. I'm getting an error during
    >> > the automation step. 'Error: could not save cron job files. Could
    >> > not run the crontab executable.' this is easily side stepped by a
    >> > replacement file for CampInstallationBase.php found here
    >> > http://www.nabble.com/list-articles-pages-td20771187.html at the
    >> > bottom of the page. this script is not up to date or just written
    >> > incorrectly and does not know where the demo data is. i've
    >> > manually corrected the script several times but now find it
    >> > easier to simply wait until the automation step to replace that
    >> > script. my question is why is this error appearing? my crontab is
    >> > set up with a cron.deny file with nothing in it. this allows
    >> > every user to access crontab. apache does have access to crontab
    >> > and i've tested this with my own simple php script. why is it
    >> > erroring and is there a fix that could be documented for
    >> > frustrated users? i'd much rather just get all
    >> > my permissions correct, if that is indeed the problem, than use
    >> > some replacement CampInstallationBase.php file.
    >>
    >>
    >> found line disable_functions and is emtpy.
    > disable_functions =
    > still wondering why i'm getting this error. also i can run crontab from
    > exec in my own scripts. doesn't seem like a permissions issue.
    >
  • I just had a chance today to try your new file. Unfortunatly it failed.
    It gives the crontab error without anyway to continue. Had to go back to
    the other version downloaded from that website.

    -Chelsea

    Mugur Rus wrote:
    > Did you install the file I sent you before trying again?
    >
    > Mugur
    >
    > On Thu, Mar 26, 2009 at 11:47 PM, Chelsea Bell > > wrote:
    >
    > Mugur Rus wrote:
    >
    > Hi Sebastian,
    >
    > Please don't do anything yet, the problem may have been caused
    > by an obsolete version of the file.
    >
    > Mugur
    >
    > On Thu, Mar 26, 2009 at 3:32 PM, Sebastian Goebel
    >
    > > >> wrote:
    >
    > Hi,
    >
    > this usually appears if php runs in safe_mode, and/or have some
    > functions
    > disabled in php.ini (search for disable_functions). Is this
    > the case?
    >
    > We should change the installer to continue, even the cron
    > binary
    > cannot
    > executed. Instead, can prompt how to solve this on command
    > line.
    > Should I
    > do, or any veto?
    >
    > Sebastian
    >
    >
    >
    > > -----Original Message-----
    > > From: cbell@falconsys.com
    > >
    > [mailto:cbell@falconsys.com
    > >]
    > > Sent: Wednesday, March 25, 2009 10:08 PM
    > > To: campsite-support@campware.org
    >
    > > >
    > > Subject: [campsite-support] crontab error
    > >
    > >
    > > I'm thinking this is a fairly common problem as i've run
    > into it
    > > everytime i've installed on any os. I'm getting an error
    > during
    > > the automation step. 'Error: could not save cron job
    > files. Could
    > > not run the crontab executable.' this is easily side
    > stepped by a
    > > replacement file for CampInstallationBase.php found here
    > > http://www.nabble.com/list-articles-pages-td20771187.html
    > at the
    > > bottom of the page. this script is not up to date or just
    > written
    > > incorrectly and does not know where the demo data is. i've
    > > manually corrected the script several times but now find it
    > > easier to simply wait until the automation step to
    > replace that
    > > script. my question is why is this error appearing? my
    > crontab is
    > > set up with a cron.deny file with nothing in it. this allows
    > > every user to access crontab. apache does have access to
    > crontab
    > > and i've tested this with my own simple php script. why is it
    > > erroring and is there a fix that could be documented for
    > > frustrated users? i'd much rather just get all
    > > my permissions correct, if that is indeed the problem,
    > than use
    > > some replacement CampInstallationBase.php file.
    >
    >
    > found line disable_functions and is emtpy.
    > disable_functions =
    > still wondering why i'm getting this error. also i can run crontab
    > from exec in my own scripts. doesn't seem like a permissions issue.
    >
    >
  • Please check if your apache crontab file was writable by the apache user.
    Try to insert text to you from your PHP scripts.

    Mugur

    On Sat, Mar 28, 2009 at 3:45 AM, Chelsea Bell wrote:

    > I just had a chance today to try your new file. Unfortunatly it failed. It
    > gives the crontab error without anyway to continue. Had to go back to the
    > other version downloaded from that website.
    >
    > -Chelsea
    >
    > Mugur Rus wrote:
    >
    >> Did you install the file I sent you before trying again?
    >>
    >> Mugur
    >>
    >> On Thu, Mar 26, 2009 at 11:47 PM, Chelsea Bell >> cbell@falconsys.com>> wrote:
    >>
    >> Mugur Rus wrote:
    >>
    >> Hi Sebastian,
    >>
    >> Please don't do anything yet, the problem may have been caused
    >> by an obsolete version of the file.
    >>
    >> Mugur
    >>
    >> On Thu, Mar 26, 2009 at 3:32 PM, Sebastian Goebel
    >>
    >> >> >> wrote:
    >>
    >> Hi,
    >>
    >> this usually appears if php runs in safe_mode, and/or have some
    >> functions
    >> disabled in php.ini (search for disable_functions). Is this
    >> the case?
    >>
    >> We should change the installer to continue, even the cron
    >> binary
    >> cannot
    >> executed. Instead, can prompt how to solve this on command
    >> line.
    >> Should I
    >> do, or any veto?
    >>
    >> Sebastian
    >>
    >>
    >>
    >> > -----Original Message-----
    >> > From: cbell@falconsys.com
    >> >
    >> [mailto:cbell@falconsys.com
    >> >]
    >> > Sent: Wednesday, March 25, 2009 10:08 PM
    >> > To: campsite-support@campware.org
    >>
    >> >> >
    >> > Subject: [campsite-support] crontab error
    >> >
    >> >
    >> > I'm thinking this is a fairly common problem as i've run
    >> into it
    >> > everytime i've installed on any os. I'm getting an error
    >> during
    >> > the automation step. 'Error: could not save cron job
    >> files. Could
    >> > not run the crontab executable.' this is easily side
    >> stepped by a
    >> > replacement file for CampInstallationBase.php found here
    >> > http://www.nabble.com/list-articles-pages-td20771187.html
    >> at the
    >> > bottom of the page. this script is not up to date or just
    >> written
    >> > incorrectly and does not know where the demo data is. i've
    >> > manually corrected the script several times but now find it
    >> > easier to simply wait until the automation step to
    >> replace that
    >> > script. my question is why is this error appearing? my
    >> crontab is
    >> > set up with a cron.deny file with nothing in it. this allows
    >> > every user to access crontab. apache does have access to
    >> crontab
    >> > and i've tested this with my own simple php script. why is it
    >> > erroring and is there a fix that could be documented for
    >> > frustrated users? i'd much rather just get all
    >> > my permissions correct, if that is indeed the problem,
    >> than use
    >> > some replacement CampInstallationBase.php file.
    >>
    >>
    >> found line disable_functions and is emtpy.
    >> disable_functions =
    >> still wondering why i'm getting this error. also i can run crontab
    >> from exec in my own scripts. doesn't seem like a permissions issue.
    >>
    >>
    >>
    >