Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 552
    • Issues 552
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4759
Closed
Open
Created Aug 10, 2017 by Sergi@sse

On client change cron.d paths to logs not changed

If a site is changed to a new client, paths on already created cron entries are not updated.

For example : 00 2 * * * web19 /usr/bin/wget --user-agent='Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0' -q -t 1 -T 7200 -O /var/www/clients/client8/web19/private/cron_wget.log 'http://example.com/modules/cron_products_full.php' >>/var/www/clients/client8/web19/private/cron.log 2>>/var/www/clients/client8/web19/private/cron_error.log #example.com

if client8 is changed to client9 using the panel, paths won't be updated here and command 'wget' will fail because it won't find the old path.

Maybe, on client change, cron entries related to the updated site should be reprocessed for paths to be rediscovered.

Assignee
Assign to
Time tracking