Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 485
    • Issues 485
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4759

Closed
Open
Opened 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
3.3
Milestone
3.3
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#4759