SolusVM 'Cannot change to source directory' error








SolusVM 'Cannot change to source directory' error generally happens when the FTP destination directory is wrong in AutoFTP backup settings.

Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to perform related SolusVM queries.

In this context, we shall look into how we can fix this SolusVM error quickly.


Nature of SolusVM 'Cannot change to source directory' error

SolusVM is known for its built-in feature to take regular snapshots of virtual servers. These Snapshots act exactly as a restore point in the Windows PC.

For instance, the software can take an image of the VPS server whilst it is still online then store that image in a separate location.

With the AutoFTP restore commands, we can always restore the SolusVM AutoFTP backups from the command line.

However, it is not a success every time. We have customers who were unable to run the SolusVM AutoFTP backup.

The log page in the SolusVM > Nodes > the_node > Auto FTP Backup > Log may show the error below:

Cannot change to source directory


Method to resolve SolusVM 'Cannot change to source directory' error

In order to fix this error easily, we change the FTP destination directory in the AutoFTP backup settings.

To do so, we follow the below steps:

  • Initially, we log in to the SolusVM interface.
  • Then we navigate to SolusVM > Nodes > the_node > Auto FTP Backup.
  • Here, we edit the AutoFTP backup settings. In the Directory field, we mention the FTP user’s home directory.
  • Finally, we run the backup manually on Node where the Backup is configured: # php /usr/local/solusvm/includes/autoftpbackup.php –mode=all –debug=1


[Need help with fixing Plesk errors? We'd be happy to assist. ]



Conclusion

This article covers how to fix SolusVM 'Cannot change to source directory' error which happens when the FTP destination directory is wrong in AutoFTP backup settings. It can also be caused  as a result of Permissions / ownership of /usr/local/solusvm/tmp/ directory on source and target servers are incorrect.

To fix SolusVM not accessible: No such file or directory error, Set correct ownership and permissions:

$ chown solusvm:solusvm /usr/local/solusvm/tmp/ && chmod 755 /usr/local/solusvm/tmp/

For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com