Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S server-side-backups-client
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Turris
  • server-side-backups-client
  • Issues
  • #8

Closed
Open
Created May 17, 2018 by Vojtech Myslivec@vmyslivec2 of 3 tasks completed2/3 tasks

Return apropriate error and exit code when backup file is too large

There is a backup size limit on the server side. When the backup is too large, ssbackups client exits with 255 error code and print json to stdout:

root@omnia: ~ # ssbackups create bigfile.bak
Password for backup: 
Password for backup (again): 
{"type": "ClientException", "detail": "Command << ['/usr/bin/curl', '--fail', '-X', 'POST', '-m', '10', '-H', 'Accept:application/json', '-H', 'Authorization:Token 01234DEADBEEF', '-F', 'payload=@bigfile.bak', 'https://rb.turris.cz/backups/'] >> ended with << return code = 22 >> and with output <<  >>.", "exit_code": -1}

Foris wrongly reports "Failed to connect to the ssbackup server." then (see screenshot).

  • ssbackups cli client should report some apropriate message on stderr and return defined exit code
  • Foris should report similar error message instead of general "Failed to connect..."
  • A notification message should be raised when (regular timed) backup was not finished successfully, so the user get noticed that the backups are not created periodically

screenshot

cc: @mmladek @shenek

Edited May 30, 2018 by Michal Mladek
Assignee
Assign to
Time tracking