Hey guys, I'd love to backup a remote filesystem. In the FAQs Roland advices

you should when possible not add any directories with mounts in them, but rather add the mount itself.

http://docs.jottacloud.com/jottacloud-command-line-tool/jottacloud-command-line-tool-faq-s/what-file-systems-are-supported-by-jottacloud-cli

Is it even possible with Linux/Ubuntu? I need a directory where I mount the filesystem. When adding this I will get the error message from the FAQ page.

Can anyone explain further on this topic?
Thanks a lot
Daniél

Thank you for this tool, it looks to be a really good tool.

jotta-cli release (jotta-cli version):

  jotta-cli     version 0.4.4986
  jottad        version 0.4.4986
  jottad        host    raman
  jottad        path    /usr/bin/jottad
  jottad        appdata /var/lib/jottad

Description of problem:
I've got two folders called work, located on two different partitions.
I do not want to add the whole partitions to the backup, only the folders. Currently the files end up in the same folder.

Expected:
For archive the --remote options works. It would be nice if it also worked for add, i.e.
jotta-cli add work --remote workb

One of the most INterresting Parts of the Community Package Jottalib(-ng) which I used for a couple of Years now.Was the FuseFS Implementation,
so that you had the hole filestructure of the JHottacloud and you hadn't have to download everything again.

Is it possible to integrate such a feature in the future?

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version): 0.4.4986

Description of problem:
I want to backup my server files (configuration, db-dumps...). However, jotta-cli now acts as a continuous sync service and fails when trying to sync files that have shared access (permission denied error).
In case of a DB-dump, I don't know when the dump is synced so I'm unable to restart the server unless personally/manually verified.

Expected:
to be able to use a (scripted) one-shot backup: stop my server, dump DB, backup dumps (wait until backup is completed) and restart server

What are the terms of redistribution of the deb/rpm packages. Currently there are no information regarding this, and i'd like to package this for Arch Linux.

jotta-cli release (jotta-cli version):
jotta-cli version 0.3.4269
jottad version 0.3.4269
jottad host ...
jottad path /usr/bin/jottad
jottad appdata /root/.jottad

Description of problem:
I am wondering if the current config method introduces some security issues? It seems that I am able to both log in, log out and add any directory to Jottacloud for backup. The jottad process runs as root and can therefore backup all files, also root-only files.

So I guess that a user of a multi user system then could log out the current Jottacloud user, log in an someone else and add otherwise inaccessible files to the backup? And later read those files through the web interface.

Expected:
Not a problem for most private users, I suppose, and not a problem for me. But the setup (login, logout, add files, etc) should possibly only be accessible through sudo?

Additional info:
Ubuntu 16.04.3 LTS. Installed as instructed through apt. No special setup.

First of all : NICLY DONE!

Now I have a little feature request:

The possebillity to move hole Folderstructures to the Archive.

Wen i try to do this i get the following error:

jotta-cli archive /backup/zips/
Interpretting [/backup/zips/] as [/backup/zips]
Error: [2] read /backup/zips: is a directory

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version): 0.4.4986

Description of problem: From my understanding, this tool only allows [local] to [jottacloud] backup / archiving. I am desperately trying to achieve the opposite: I want to sync [jottacloud] to [local] and back to [jottacloud] (like Sync for Desktop/Mobile clients).

I use Jotta in three ways:
-Sync of important docs/pictures ~20GB
-Backup/Sync of mobile pictures ~10GB
-Backup/Archive of local machines ~15TB

Jotta-Cli currently only allows access to the last of three valuable parts of the service.

I want to keep my jottacloud sync-files [only a few dozen GB of important documents] in sync on a headless backup server.

Expected:
Another option (much like backup) to access the sync folder (to keep it in sync between Desktop/Mobile/Headless).

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):
Any
Description of problem:
No restore command
Expected:
Restore works

jotta-cli status (jotta-cli status):

Not relevant

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Not relevant

Traceback

Not relevant

Additional info:

There has been talk about adding restore to the jotta-cli, which is critical, for some time, months, actually. Can this really be so hard to figure out?

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):

0.3.4269

Description of problem:

jotta-cli add /home/alexander/Jotta

21:14 [alexander@foobar /home/alexander/]$ jotta-cli add Jotta
Interpretting [Jotta] as [/home/alexander/Jotta]
Error: [2] Could not add path to backup: Unsupported filesystem [ECRYPTFS_SUPER_MAGIC] for key [0xf15f]

Expected:

Expected to work.

jotta-cli status (jotta-cli status):

---------------------------------------------------------
 Account   : ****************
 Usage     : 0bytes / 5.00GiB
 Backups   :
---------------------------------------------------------
   Path      : /opt/alexander/jotta
   Files     : 1 files / 12bytes
   Status    : Up to date!
---------------------------------------------------------
OK

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Don't seem to have this folder and file.

I wanted to ask if you can implement a function like mkls-lR (make ls-lR) of the entire archive that a user has with you (Synced files, Backed up files, Archive, Shared files ... it would be useful to have / be able to download a list of all files)

Make it possible to configure and run background sync using jotta-cli.

A command "jotta-cli pause" would be convenient to pause the upload/backup.

Make sure you are running the latest version of jotta-cli before reporting an issue.

Hi, I think I have found a bug in jotta-cli.

jotta-cli release (jotta-cli version):
0.4.4986

Description of problem:

If the file is already present, it causes a 404 error.

That happens for apparently every file already online. status

Expected:

success

jotta-cli status (jotta-cli status):

Path : .../RAWs
Files : 3066 files / 80.28GiB
Status : 3066 files (80.28GiB) could not be backed up

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

pid:10422 2018/07/07 09:32:08 Running scan of .../RAWs
pid:10422 2018/07/07 09:32:08 Error uploading

{
"Name": "x.sh",
"Path": ".../RAWs/x.sh",
"Size": 395,
"Modified": "2018-06-09T17:48:42.549072988Z",
"Created": "2018-06-10T08:55:12.196051496Z",
"Checksum": "",
"State": "Added"
}

=> Invalid statuscode 404
pid:10422 2018/07/07 09:32:10 Deferring scan of .../RAWs while waiting for previous queue to finish

Additional info:
extra systemd section:

[Service]
CPUShares=100
MemoryLimit=150M
BlockIOWeight=50
Nice=19
IOSchedulingClass=idle
CPUSchedulingPolicy=idle

I guess this is a feature request, but hey.

If jotta were to open up the code of the client, I'm positive they will receive not only good bug reports, but also programming help and sufficient amounts of creds from the OSS society to allow the customer count to grow substantially. I can hardly see a reason for keeping something as simple as a backup client under closed source…

Just wanted to thank you for providing this! 😄

It would be very convenient to be able to schedule jottad to run within specified time intervals. I know that it is possible to set scan interval. However I would like to set a start time and end time for when the backup should run. A typical use case would be to only backup during night hours.

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):
jotta-cli version 0.4.4986
jottad version 0.4.4986

Description of problem:
When adding webhooks to discord it returns an error stating that receiving server is missing expected definition of Content-Type in the http header.

Discord, using webhooks, documentation:
https://support.discordapp.com/hc/sv/articles/228383668

Expected:
Possibility to send webhooks to discord.

jotta-cli status (jotta-cli status):

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Data sent in webhook, example welcome confirmation captured with netcat:

POST / HTTP/1.1
Host: 192.168.1.132:1234
User-Agent: Go-http-client/1.1
Content-Length: 104
Accept-Encoding: gzip

{"username":"Jottacloud Command-line Tool","text":"Hello from jottad on the_moon!\nYour webhook is working!"}

Error in log

pid:2793 2018/05/17 20:32:04 Invalid status code for webhook[400] {"_misc": ["Expected \"Content-Type\" header to be one of set(['application/json', 'multipart/form-data', 'application/x-www-form-urlencoded'])."]}

Traceback

Additional info:
Yay, keep it up 😄

I was missing a bash completion script for this, so I wrote one:

function _jottacli() {
  local config_params cmds cur first params prev second

  COMPREPLY=()
  cur=${COMP_WORDS[COMP_CWORD]}
  first=${COMP_WORDS[1]}
  second=${COMP_WORDS[2]}
  prev=${COMP_WORDS[COMP_CWORD-1]}

  cmds="add archive config help ignores login logout rem scan status tailf web webhook"
  params="-help -host --remote --nogui --share"
  config_params="logscanignores scaninterval webhookstatusinterval"

  case "$first" in
    add|archive)
      COMPREPLY=($(compgen -W "$(ls -1)" -- $cur))
      ;;
    config|ignores)
      case "$second" in
        get|set)
          if [[ "$first" == "config" ]]; then
            COMPREPLY=($(compgen -W "$config_params" -- $cur))
          elif [[ "$first" == "ignores" ]] && [[ "$second" == "set" ]]; then
            COMPREPLY=($(compgen -W "$(ls -1)" -- $cur))
          fi
          ;;
        *)
          COMPREPLY=($(compgen -W 'get set' -- $cur))
          ;;
      esac
      ;;
    help|login|logout|status|tailf|web) ;;
    rem)
      COMPREPLY=($(compgen -W "$(ls -1)" -- $cur))
      ;;
    scan)
      COMPREPLY=($(compgen -W "$(ls -1)" -- $cur))
      ;;
    webhook)
      COMPREPLY=($(compgen -W 'add rem' -- $cur))
      ;;
    *)
      COMPREPLY=($(compgen -W "$cmds" -- $cur))
      ;;
  esac

  if [[ "$cur" == -* ]]; then
    COMPREPLY=($(compgen -W '$params' -- $cur))
  fi
}
complete -F _jottacli jotta-cli

Having some problems adding folders to my newly installed Jottacli.
Have tried different steps, including changing the user the jottad runs as as well as the services user for the .msi package.

Trying to add "any" folder or path to Jotta, gives me "Error: [2] Invalid path"
C:>jotta-cli add d:
Interpretting [d:] as [D:]
Error: [2] Invalid path

(Have also tried to add folder on C: with the same result)

Can't find anything useful in my log either regarding the error.

OS Information
MS Server 2016 (Core) part of a domain.

Jotta Information

C:>jotta-cli version
jotta-cli version 0.3.4269
jottad version 0.3.4269
jottad host TCBACK01
jottad path C:\Program Files (x86)\JottaCli\jottad.exe
jottad appdata C:\Users\s_jottacloud/.jottad

jotta-cli release (jotta-cli version):
0.3.4195

Description of problem:
No manual pages installed for jottad or jotta-cli. This is on debian.

Expected:

jotta-cli status (jotta-cli status):

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Traceback

Additional info:

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):

jotta-cli version 0.4.4986

Description of problem:

jotta-cli lacks the ability to provide setup configuration options in a scripted manner.

Expected:

jotta-cli login -u username -p password -d device.name --acceptlicense

jotta-cli release (jotta-cli version):

jotta-cli version 0.4.4914
jottad version 0.4.4914
jottad host Sandwich
jottad path /usr/bin/jottad
jottad appdata /var/lib/jottad

Description of problem:
I have the following .jottaignore file in my home folder on Linux:

.*
Dropbox/
Nedlastinger/

# include .jottaignore
!.jottaignore

The jottad user has not access to some dotfiles and Dropbox folder both which should be ignored. However jotta-cli status reports

Path      : /home/daghenning
Files     : 25804 files / 262.37MiB
Status    : 2 files (24.38KiB) could not be backed up
---- The following paths could not be backed up ----
/home/daghenning/Dropbox => open /home/daghenning/Dropbox: permission denied
/home/daghenning/.adobe => open /home/daghenning/.adobe: permission denied
/home/daghenning/.dbus => open /home/daghenning/.dbus: permission denied
/home/daghenning/.dropbox => open /home/daghenning/.dropbox: permission denied
/home/daghenning/.gconf => open /home/daghenning/.gconf: permission denied
/home/daghenning/.gnome => open /home/daghenning/.gnome: permission denied
/home/daghenning/.gnupg => open /home/daghenning/.gnupg: permission denied

Expected:
I would expect that when files are ignored jotta-cli should not try to access the files.

Dear Devs,

Probably something went wrong during the updating.
I am getting this error:

Could not connect to jottad

The only working things now are the command jotta-cli -help

There is any way to completely remove it and fix it?
I try to remove the jotta-cli and reinstall, but nothing changed.
I have also tried to remove all the file associated with jotta-cli and jottad but, again, nothing changed.

Do you have any clue I might use for fixing it?

Thanks in advance,

Cheers,
Fabio

jotta-cli release (jotta-cli version): 0.4.4986

Description of problem: There is no problem, I just have a question. I'm running jotta-cli on Ubuntu 16.04, where is the log file located? Thanks in advance.

Expected: -

jotta-cli status (jotta-cli status): -

Relevant logs for the issue (cat ~/.jottad/jottabackup.log) -

Traceback -

Additional info: -

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):
jotta-cli_0.3.4269_amd64.deb

Description of problem:
Got the following error when installing ( sudo apt-get install jotta-cli):

/var/lib/dpkg/info/jotta-cli.postinst: 18: /var/lib/dpkg/info/jotta-cli.postinst: systemctl: not found
/var/lib/dpkg/info/jotta-cli.postinst: 19: /var/lib/dpkg/info/jotta-cli.postinst: systemctl: not found
/var/lib/dpkg/info/jotta-cli.postinst: 20: /var/lib/dpkg/info/jotta-cli.postinst: systemctl: not found

Ideally, this would be handled without throwing an error, but more importantly to me - Can I work around this? I guess I have to set up service start manually?

Expected:
No error

Additional info:
Ubuntu 12.04.5 LTS

The macOS instructions notes brew services start jotta-cli as optional, but without it the cli reports:

❯ jotta-cli login
Error: Could not connect to jottad

http://docs.jottacloud.com/jottacloud-command-line-tool/installing-the-command-line-tool/jottacloud-cli-for-macos

Probably requires a bit more granular cli API, with get/put/list/query, or possibly exposing parts of the cli as a (go?) library.

jotta-cli release (jotta-cli version):

---------------------------
  jotta-cli     version 0.4.4986

  jottad        version 0.4.4986
  jottad        host    shack
  jottad        path    /usr/bin/jottad
  jottad        appdata /var/lib/jottad
---------------------------

Description of problem:
jotta-cli seems to ignore symlinks. I have added several symlinks to various other directories to a backup directory. This directory is added to jotta-cli. These directories do not appear in my backup. There is no mention of these directories in my log.

Expected:
It would be nice if jotta-cli would also follow symlinks, or at least have an option to do (or not do) so, if that would be required.

Additional info:

Distributor ID: Ubuntu
Description:    Ubuntu 16.04.4 LTS
Release:        16.04
Codename:       xenial

jotta-cli release (jotta-cli version):
0.3.4195

Description of problem:
I have a machine with some disks, and I try to separate services as good as possible to increase system security and stability. Now, jottad runs as root, meaning if a bad bug or security breach can be disasterous. So I've setup a small virtual machine to do the job. To this VM, I have exported the data filesystem read-only and no_root_squash, meaning root can read everything on it, but never write. Now jotta-clli refuses to add NFS-mounted filesystem:

jotta-cli add /somefs

Error: [2] Could not add path to backup: Unsupported filesystem [NFS_SUPER_MAGIC] for key [0x6969]

Expected:
That it works…

jotta-cli status (jotta-cli status):

Nothing relevant

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Nothing in the logs

Traceback

Nada

Additional info:

Please add filters for files and folders.

As far as I can see, the existing data on jotta can't be seen from jotta-cli. Is this intentional or perhaps just something to be added later? A fuse driver would be brilliant. I've tried jottalib, but I have pretty much problems with it…

jotta-cli release (jotta-cli version):

Description of problem:

Expected:

jotta-cli status (jotta-cli status):

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Traceback

Additional info:

Currently jotta-cli utilizes the whole upload bandwidth capacity which has the effect that other uses of the Internet connection are very slow/useless until jotta-cli is done backing up.

It would be very useful to set that jotta-cli should only use e.g. 50% of the available bandwidth capacity.

According to http://docs.jottacloud.com/jottacloud-command-line-tool/using-the-command-line-tool/archiving-files-with-jottacloud-cli

Note: Files are stored in a subfolder of the Archive with the same name as the device name.

Having previously used https://github.com/Fjodor42/jottalib-ng (thank you for providing something yourselves - the speed especially seems to indicate multithreading that I never got around to and, hence, looks vastly superior), I have some directory structure in Archive, that I would very much like to keep, and, hence, I would very much like to be able to specify more directly, where the files should go.

Looking at http://docs.jottacloud.com/jottacloud-command-line-tool/using-the-command-line-tool/login-and-basic-use , there is a slight chance that --remote facilitates this, but from the description ("Where you want it?"), it's a bit hard to tell...

Seeing you have Linux and Darwin support, adding FreeBSD to the list of supported platforms should be trivial.
FreeBSD support would also allow FreeNAS users to use this utility.

jotta-cli release (0.3.4269):

Publish the app as a docker image

Running the service in a docker container to backup stuff might be usefull.

Here is a dockerfile to create such an image and a instruction how to use it. It maybe useful some day.

ARG ubuntu_version=16.04
FROM ubuntu:${ubuntu_version}

ARG jotta_cli_version=0.3.4269

LABEL maintainer="Your name and email"
LABEL org.label-schema.schema-version="1.0.0-rc.1"
LABEL org.label-schema.name="jottad"
LABEL org.label-schema.description="This image runs the Jottacloud deamon jottad."
LABEL org.label-schema.usage="/usr/doc/app-usage.txt"
LABEL org.label-schema.url="http://docs.jottacloud.com/jottacloud-command-line-tool"
LABEL org.label-schema.version="${jotta_cli_version}"

RUN apt-get clean \
	&& apt-get update -y \
	&& apt-get upgrade -y \
	&& apt-get -y install wget apt-transport-https ca-certificates \
	&& wget -O - https://repo.jotta.us/public.gpg | apt-key add - \
	&& echo "deb https://repo.jotta.us/debian debian main" | tee /etc/apt/sources.list.d/jotta-cli.list \
	&& apt-get update -y \
	&& apt-get install jotta-cli=${jotta_cli_version} -y \
	&& apt-get autoremove -y \
	&& apt-get clean \
	&& rm -rf /var/lib/lists/*

EXPOSE 53

ENTRYPOINT [ "jottad","stdoutlog" ]

Here is how to use it:

How can i create the image?

Install Docker

First remove all old installations of Docker if there are any.

sudo apt-get remove docker-engine docker.io

The Docker package is renamed into docker-ce.

Then update the package cache.

sudo apt-get update

You will need some dependencies to install Docker.

sudo apt-get install apt-transport-https ca-certificates curl software-properties-common

apt must know the gpg key for the Docker repository.

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

Ensure that always the stable version will be installed.

sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

Update the package index again and install docker-ce.

sudo apt-get update
sudo apt-get install docker-ce

You will need an additional component to compose Docker images.

sudo apt-get install docker-compose

Create the image

The image could be build now by changing the directory to the one the dockerfile is located. The dockerfile contains to ARG wich defines the versions of Ubuntu and jotta-cli. You can change them by passing arguments to docker build.

docker build -t jotta-cli:0.3.4183 --build-arg ubuntu_version=18.04 --build-arg jotta_cli_version=0.3.4183 .

If you don't pass any arguments the defaults in the dockerfile will be used.

docker build -t jotta-cli:latest .

How can i use the image?

Prepare the container

First of all you don't want to configure jotta-cli every time you create a jotta-cli-container when you want to update jotta-cli. So you need to create a volume to persist the configuration.

docker volume create jotta-cli

The configuration files will be stored in the volume. On Linux the path is /var/lib/docker/volumes/jotta-cli/_data.

Now you can create the container.

docker run -d --name jotta-cli --mount source=jotta-cli,target=/root/.jottad --mount type=bind,source=/,target=/sync,readonly jotta-cli:latest

You will notice that two mounts are made. The first mounts the created volume to /root/.jottad where the configuration is stored. The second mounts the hosts / into the containers /sync/. This way jottad could access the hosts filesystem to backup files. The hosts filesystem is mounted as readonly so that the container could not change anything on your host.

Keep attention to mount / only in a subfolder in the container!

Login into Jottacloud

To enter you Jottacloud credentials you must open a bash on the container. The output of jotta-cli login could not be displayed with Docker's exec command.

docker exec -it jotta-cli /bin/bash

In the container's bash log into your Jottacloud account.

jotta-cli login

Now you can exit the container with exit. Every other configuration could be made with exec.

The most important command it to add a path to backup.

docker exec jotta-cli jotta-cli add /sync/var/lib/docker/volumes

This adds the path where Docker stores volumes to the observed folders. This way the container saves it's own configuration in the cloud.

jotta-cli release (0.4.4986):

Description of problem:
The log file is created in /var/lib/jottad/jottabackup.log on Ubuntu 16.04 which is not following any conventions.

Expected:
Log file created in /var/log/jottad/

Additional info:
The standard template make me seem strict and angry so I'm throwing in a smiley 😄

jotta-cli release (jotta-cli version): 0.4.4986

Description of problem: Ignores file with negated ignores does not seem to work / taken into account

I am trying to set the following ignore file to jotta:

*~
.fuse_hidden*
.directory
.Trash-*
.nfs*

/home/user/.config/
!/home/user/.config/autostart
/home/user/VirtualBox VMs/

Where the whole .config folder is skipped, while I in fact want the autostart subfolder there to be backed up. Re-ordering it so it looks like below does not work either:

*~
.fuse_hidden*
.directory
.Trash-*
.nfs*

!/home/user/.config/autostart
/home/user/.config/
/home/user/VirtualBox VMs/

Do these not work?

Version of jottad/jotta-cli: 0.4.4986

I am uploading a file using the following command:

jotta-cli.exe archive D:\Backup\subfolder\filename.7z --remote Backup

The file is uploaded to the Backup folder in my Archive as expected, but looking in the Web UI the file has name "\filename.7z" - with an extra backslash prefix. When I enter the file rename function (in Web UI) it presents the current name as \\filename.7z (extra backslash for escaping?). Deleting both backslashes, renaming the file, works from Web UI.

Make sure you are running the latest version of jotta-cli before reporting an issue.

**jotta-cli release (jotta-cli version):0.3.4269

**Description of problem:*Error message when adding new path to the backup repository:

Command: jotta-cli add /home/herk/Backup-CLI-Test/

Result: Error: [2] Could not add path to backup: Unsupported filesystem [ECRYPTFS_SUPER_MAGIC] for key [0xf15f]

Expected:

Path added into the backup list.

jotta-cli status (jotta-cli status):

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Traceback

Additional info:

Is it possible to customize the location of the datadir? If not, can you make a command line argument or something for it?
I'm trying out the Windows version, and would like to use something different than "%USERPROFILE%\.jottad", for instance a local folder in a portable setup (and then a .zip distribution would also be nice, although extracting the binaries from the .msi is no problem).

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):
version 0.4.4986

Description of problem:
The status bytes remaining is reported wrongly:
Status : Transferring 68577 files / -1013417007bytes remaining

There is a minus, and the number is 'growing' the wrong way.

Expected:

jotta-cli status (jotta-cli status):

 ~/code  date
Thu May 17 01:45:55 CEST 2018
 ~/code  jotta-cli status
------------------------------------------------------------------------------
 Account   : XXX
 Usage     : 259.68GiB / ( Unlimited )
 Device    : GLAP
 Backups   :
------------------------------------------------------------------------------
   Path      : /Users/XXX/code
   Files     : 149060 files / 8.13GiB
   Status    : Transferring 69566 files / -1000298053bytes remaining

------------------------------------------------------------------------------
OK
 ~/code  date
Thu May 17 01:46:08 CEST 2018
 ~/code  jotta-cli status
------------------------------------------------------------------------------
 Account   : XXX
 Usage     : 259.68GiB / ( Unlimited )
 Device    : GLAP
 Backups   :
------------------------------------------------------------------------------
   Path      : /Users/XXX/code
   Files     : 149060 files / 8.13GiB
   Status    : Transferring 68577 files / -1013417007bytes remaining

------------------------------------------------------------------------------
OK

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

id:3865 2018/05/17 01:42:31 Error uploading {
 "Name": "RCTCameraRollManager.m",
 "Path": "/Users/XXX/code/scenarios/node_modules/react-native/Libraries/Image/RCTCameraRollManager.m",
 "Size": 6713,
 "Modified": "2015-07-25T00:16:08+02:00",
 "Created": "2018-04-12T01:16:41.284303075+02:00",
 "Checksum": "",
 "State": "Added"
} => open /Users/XXX/code/scenarios/node_modules/react-native/Libraries/Image/RCTCameraRollManager.m: too many open files
pid:3865 2018/05/17 01:46:22 Error uploading {
 "Name": "README.md",
 "Path": "/Users/XXX/code/scenarios/node_modules/is-equal-shallow/README.md",
 "Size": 2775,
 "Modified": "2015-06-23T05:39:48+02:00",
 "Created": "2018-04-12T01:13:38.756761913+02:00",
 "Checksum": "",
 "State": "Added"
} => Invalid statuscode 421
pid:3865 2018/05/17 01:46:22 Error uploading {
 "Name": "README.md",
 "Path": "/Users/XXX/code/scenarios/node_modules/is-equal-shallow/README.md",
 "Size": 2775,
 "Modified": "2015-06-23T05:39:48+02:00",
 "Created": "2018-04-12T01:13:38.756761913+02:00",
 "Checksum": "",
 "State": "Added"
} => Invalid statuscode 421
pid:3865 2018/05/17 01:47:33 Error uploading {
 "Name": "README.md",
 "Path": "/Users/XXX/code/scenarios/node_modules/git-rev/README.md",
 "Size": 2453,
 "Modified": "2012-08-09T13:35:11+02:00",
 "Created": "2018-04-12T00:53:04.373971621+02:00",
 "Checksum": "",
 "State": "Added"
} => Invalid statuscode 421
pid:3865 2018/05/17 01:47:33 Error uploading {
 "Name": "README.md",
 "Path": "/Users/XXX/code/scenarios/node_modules/git-rev/README.md",
 "Size": 2453,
 "Modified": "2012-08-09T13:35:11+02:00",
 "Created": "2018-04-12T00:53:04.373971621+02:00",
 "Checksum": "",
 "State": "Added"
} => Invalid statuscode 421

Traceback

Additional info:
The error log contains a lot of
too many open files
and
Invalid statuscode 421 things....

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):
0.4.4986

Description of problem:
options is not defaulting to localhost if omitted.

The output shows options as optional with brackets around it.
usage: ./jotta-cli [options] command

Typing jotta-cli version makes it timeout, however specifying -host localhost for all commands makes it work. Seems like there is no default fallback to localhost for -host if omitted

Expected:
Default to localhost if omitted since the docs show that options is optional.

jotta-cli status (jotta-cli status):

------------------------------------------------------------------------------
 Account   : [removed]
 Usage     : 0bytes / 5.00GiB
 Device    : [removed]
 No folders added to backup yet
OK

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Nothing relevant in logs regarding this.

Traceback

-

Additional info:
Ubuntu 16.04.3 LTS

Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version): 0.4.4986

Description of problem: A number of files seem to fail with either "Invalid statuscode 420" or
"Invalid statuscode 421"

Expected: More meaningful error description

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

pid:11638 2018/03/09 14:44:53 Error uploading {
"Name": "prefs.js",
"Path": "/home/adrian/.mozilla/firefox/n273f1nh.default/prefs.js",
"Size": 23068,
"Modified": "2018-03-08T18:27:05.871502846Z",
"Created": "2018-03-08T18:27:06.1064936Z",
"Checksum": "",
"State": "Added"
} => Invalid statuscode 421
pid:11638 2018/03/09 14:44:53 Error uploading {
"Name": "places.sqlite-wal",
"Path": "/home/adrian/.mozilla/firefox/n273f1nh.default/places.sqlite-wal",
"Size": 426328,
"Modified": "2018-03-09T08:22:36.233950464Z",
"Created": "2018-03-09T08:22:36.233950464Z",
"Checksum": "",
"State": "Added"
} => Invalid statuscode 420
pid:11638 2018/03/09 14:45:45 Deferring scan of /backup while waiting for previous queue to finish

Additional info: The errors shown in the log above are common and seem to apply to a large number of files, I'm not sure if they will eventually resolve themselves or not. However, the last line regarding the deferring of the scan of the /backup directory seems to be a long term problem, that directory does not appear to have been backed up in weeks. Its not clear if the two issues are related or separate.

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):
Error: Could not connect to jottad

Description of problem:
Hi there!

I have jottacloud installed in somes systems: desktop, portable, raspberry-pi... This last suddenly gives the error that can't connect to jottad.

Having a look at jottabackup.log I can read:

jauth error ciphertext too short

So I thin that was a login errror.

I've purged the installation and resinstalled jotta-cli, but I still can't connect to jottad, and this time even I have no jottabackup.log, so there are the last lines with journalctl -u jottad.service -b:

may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Service hold-off time over, scheduling restart.
may 24 21:06:38 nextcloudplus systemd[1]: Stopped Jottacloud cli.
may 24 21:06:38 nextcloudplus systemd[1]: Started Jottacloud cli.
may 24 21:06:38 nextcloudplus jottad[6481]: pid:6481 2018/05/24 21:06:38 Checking custom datadir /etc/jottad/config.ini
may 24 21:06:38 nextcloudplus jottad[6481]: [6481] creating logger @ /var/lib/jottad/jottabackup.log
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Main process exited, code=exited, status=1/FAILURE
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Unit entered failed state.
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Failed with result 'exit-code'.
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Service hold-off time over, scheduling restart.
may 24 21:06:38 nextcloudplus systemd[1]: Stopped Jottacloud cli.
may 24 21:06:38 nextcloudplus systemd[1]: Started Jottacloud cli.
may 24 21:06:38 nextcloudplus jottad[6488]: pid:6488 2018/05/24 21:06:38 Checking custom datadir /etc/jottad/config.ini
may 24 21:06:38 nextcloudplus jottad[6488]: [6488] creating logger @ /var/lib/jottad/jottabackup.log
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Main process exited, code=exited, status=1/FAILURE
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Unit entered failed state.
may 24 21:06:38 nextcloudplus systemd[1]: jottad.service: Failed with result 'exit-code'.
may 24 21:06:39 nextcloudplus systemd[1]: jottad.service: Service hold-off time over, scheduling restart.
may 24 21:06:39 nextcloudplus systemd[1]: Stopped Jottacloud cli.
may 24 21:06:39 nextcloudplus systemd[1]: jottad.service: Start request repeated too quickly.
may 24 21:06:39 nextcloudplus systemd[1]: Failed to start Jottacloud cli.
may 24 21:06:39 nextcloudplus systemd[1]: jottad.service: Unit entered failed state.
may 24 21:06:39 nextcloudplus systemd[1]: jottad.service: Failed with result 'exit-code'.

Could you help me?

Expected:

jotta-cli status (jotta-cli status):
could not connect to jottad

Relevant logs for the issue (cat ~/.jottad/jottabackup.log)

Traceback

Additional info:

Make sure you are running the latest version of jotta-cli before reporting an issue.

jotta-cli release (jotta-cli version):

jotta-cli     version 0.4.4986
jottad        version 0.4.4914

Description of problem:
When I check status or run any jotta-cli command I get a message:

A new version of Jotta Cli is availiable.
Please update to version 0.4.4986

But I have the latest version.
Expected:
No message about new version since I'm on the new version

jotta-cli status (jotta-cli status):

---------------------------
 A new version of Jotta Cli is availiable.
 Please update to version 0.4.4986
------------------------------------------------------------------------------
 Account   : [email protected]
 Usage     : 2.39TiB / ( Unlimited )
 Device    : Eldaron Server
------------------------------------------------------------------------------
 ###### PAUSED UNTIL Fri Mar 2 23:41:05 (60 hours 15 min) ######
------------------------------------------------------------------------------
 Backups   :
------------------------------------------------------------------------------
   Path      : /media/Backup
   Files     : 6517 files / 255.26GiB
   Status    : Up to date!

------------------------------------------------------------------------------
   Path      : /media/Data500
   Files     : 5147 files / 5.80GiB
   Status    : Up to date!

------------------------------------------------------------------------------
   Path      : /media/Media
   Files     : 31676 files / 510.48GiB
   Status    : 38 files (13.07GiB) could not be backed up

------------------------------------------------------------------------------
   Path      : /var/www
   Files     : 25019 files / 771.13MiB
   Status    : Up to date!

------------------------------------------------------------------------------
OK

I know about the 38 files. I'm in the prosess to replace a disk from BTRS raid1. It's a slow process. That's why I have paused the backup. But anyway. It' dosen''t inflict on the message about a new version available.

apt update gives me the following message:
All packages are up-to-date.

I have an USB Drive which is in exfat formatted, so i cant back it up neither to archive nor via add
I'm getting the following Error:

Error: [2] Could not add path to backup: Unsupported filesystem [FUSE_SUPER_MAGIC] for key [0x65735546]
or
Error: [2] Unsupported filesystem [FUSE_SUPER_MAGIC] for key [0x65735546]

Any Ideas?!

Make sure you are running the latest version of jotta-cli before reporting an issue.

**jotta-cli release (jotta-cli version): all versions

adding "c:" results in "\" being added

"c" as folder in cloud expected

generally: support for whole drives being added

jotta-cli release (jotta-cli version):

jotta-cli version 0.3.4269

Description of problem:

# jotta-cli add /etc/
Error: [2] Invalid path
# jotta-cli add /root/
Error: [2] Invalid path

It's understandable to exclude /usr, full of binaries, but /etc/ and /root/ are pretty important to back up.
Also /var should be allowable, pretty please?

❯ jotta-cli archive /tmp/foo
Interpretting [/tmp/foo] as [/tmp/foo]
Error: [2] read /tmp/foo: is a directory

Would be nice, but not critical.