Cloudlinux breaks cpbackup ability to mount drive?

ThinIce

• April 04, 2017 08:58

I appear to have just run into the bug discussed at The backup drive will not mount, nor-unmount. A very strange issue. In brief, legacy cpbackup set to mount / unmount its backup disk can no longer do so, and further the drive will now not mount despite not appearing to be in use, or currently mounted. What exactly is the underlying issue please? Given the timing I ran into the problem (after adding more users to CageFS and CageFS getting an update via upcp) after CL and legacy cpbackup had been working fine for a while, I'm guessing it has something to with CageFS, but I don't see how this would interfere with basic mounting behaviour as root outside of CageFS. Thanks

• 

  cPanelMichael

  • April 04, 2017 15:27

  Hello, Could you verify which version of CloudLinux is installed on your system? EX:
  cat /etc/redhat-release
  Thank you.

  0
• 

  ThinIce

  • April 04, 2017 15:34

  Thanks Michael. cat /etc/redhat-release CloudLinux Server release 6.8 (Oleg Makarov)

  0
• 

  cPanelMichael

  • April 04, 2017 16:48

  Hello, The thread you linked to references a CloudLinux issue with CL 5.x systems that should not affect your server. Could you open a support ticket using the link in my signature so we can take a closer look at the affected system and see what's happening? You can post the ticket number here so we can update this thread with the outcome. Thank you.

  0
• 

  ThinIce

  • April 04, 2017 17:44

  Thanks Michael, that's interesting. I've already had a similar conversation with Cloudlinux support, it's not policy to grant access to production machines, however by running
  cagefsctl --remount-all
  The problem disappears and the drive can again be mounted. This could be a coincidence I suppose, will continue to monitor it and update the thread if it occurs again. During last nights upcp (before the problem occurred) I did get some cron emails while CL performed its updates, again can't see how that would be related, but mentioning for completeness.
  Cron /usr/bin/cl-quota -YC ERROR: Can't open lock file for reading
  

  0
• 

  cPanelMichael

  • April 04, 2017 19:02

  During last nights upcp (before the problem occurred) I did get some cron emails while CL performed its updates, again can't see how that would be related, but mentioning for completeness.
  Cron /usr/bin/cl-quota -YC ERROR: Can't open lock file for reading
  

  
  Hello, To note, this is a known bug that CloudLinux is aware of: Error with cl-quota Thank you.

  0

Please sign in to leave a comment.