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 494
    • Issues 494
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 32
    • Merge Requests 32
  • 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
  • #5001

Closed
Open
Opened Mar 27, 2018 by umaxx@umaxx

changing web->client association leaves traces behind

short description

After editing/switching a simple wordpress(+db) website (web4) from one client (client1) to another (client3), ISPConfig adjust things in background for me (nice!), but seem to leave the following traces behind (not cleaned up correctly):

  1. Left a folder: /var/www/clients/client3/web4_bak_2018_03_22_21_32_08/
  2. mount command shows 2 (!) times the same active mount: /dev/mapper/vg_host-var on /var/www/clients/client3/web4_bak_2018_03_22_21_32_08/log type xfs (rw,relatime,attr2,inode64,usrquota,grpquota)
  3. Also a doubled mount for the "new" client3/web4, two times instead of once: /dev/mapper/vg_host-var on /var/www/clients/client3/web4/log type xfs (rw,relatime,attr2,inode64,usrquota,grpquota)
  4. Additional "nofail" entry in /etc/fstab /var/log/ispconfig/httpd/example.tld /var/www/clients/client3/web4/log none bind,nofail 0 0

Item 2. is probably effect due to 1. still there.

Not sure about 4. where it comes from exactly and if maybe needed despite my client association switch, but I don't have it with other similar websites.

correct behaviour

These traces should be cleaned up correctly.

environment

Server OS: centos Server OS version: centos7 ISPConfig version: 3.1.11

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#5001