New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: The OUTPUT_URL scheme http requires the 'lftp' command, which is missing! #1003
Comments
That error message comes from case $output_scheme in (fish|ftp|ftps|hftp|http|https|sftp) if [[ -z "$(type -p lftp)" ]]; then Error "The OUTPUT_URL scheme $output_scheme requires the 'lftp' command, which is missing!" fi ;; I.e. "type -p lftp" results nothing on your system |
I installed it and then reran, this i got error that put method not mput: Operation not supported: 405 Method Not Allowed (PUT) On Tuesday, 20 September 2016, Johannes Meixner notifications@github.com
Sent from Gmail Mobile |
The "mput: Operation not supported: 405 Method Not Allowed (PUT)" You need to find out why the PUT method is not allowed I.e. check the config of your FTP server so that In general see the section I.e. run "rear -d -D mkbackup" and inspect the rear log file |
The "mput: Operation not supported: 405 Method Not Allowed (PUT)" |
Relax-and-Recover (rear) Issue Template
Please fill in the following items before submitting a new issue:
rear version (/usr/sbin/rear -V):
rear-1.17.2-1
OS version (cat /etc/rear/os.conf or lsb_release -a): RHEL 6.7
rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):
Brief description of the issue
I am trying to setup rear using http. I have already verified http server connectivity from the server with curl download. Let me know settings that are required for using Http for rear backup/iso upload to http server. Can anyone provide a sample local.conf for using http.
Is there any userid/password also need to setup on http server ? what settings will be required from http server side.
I got messages:
ERROR: The OUTPUT_URL scheme http requires the 'lftp' command, which is missing!
None so far.
The text was updated successfully, but these errors were encountered: