Successfully completed playbook, but fusermount3 still not exist

[mihalt]

Hi! I use play like this

- name: Install and configure rclone to backup values
      ansible.builtin.include_role:
        name: stefangweichinger.ansible_rclone
      vars:
        rclone_configs:
          - name: GoogleDriveRemote
            properties:
              type: drive
              client_id: "{{ client_id }}"
              client_secret: "{{ client_secret }}"
              token: " {{ generated_token }}"

        rclone_mounts:
          - name: GoogleDriveRemote
            remote_name: GoogleDriveRemote
            remote_path: "/values"
            local_path: "/values/file"
            auto_mount: true
            extra_args: "--allow-other --allow-non-empty --log-level INFO"

But in fact I don't have anything mounted to /values/file and I get error after command journalctl -u [email protected]

Jan 02 20:37:15 b3-8-waw1 rclone[194079]: CRITICAL: Fatal error: failed to mount FUSE fs: fusermount: exec: "fusermount3": executable file not found in $PATH
Jan 02 20:37:15 b3-8-waw1 systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Jan 02 20:37:15 b3-8-waw1 systemd[1]: [email protected]: Failed with result 'exit-code'.
Jan 02 20:37:15 b3-8-waw1 systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
Jan 02 20:37:15 b3-8-waw1 systemd[1]: [email protected]: Start request repeated too quickly.
Jan 02 20:37:15 b3-8-waw1 systemd[1]: [email protected]: Failed with result 'exit-code'.
Jan 02 20:37:15 b3-8-waw1 systemd[1]: Failed to start [email protected] - RClone Mount Service for GoogleDriveRemote.

Looks like, that fusermount3 wasn't installed during your tasks?

[mihalt]

@stefangweichinger I've found an interesting problem. And still don't know why it happened and how better to resolve and to prevent it in the future. All my servers before worked fine with my this playbook. But this problem is specific for my current cloud server.

So, looks like, that it created a lot of not related to a fuse links.

$ fusermount3
-sh: 7: fusermount3: Too many levels of symbolic links
$ ls -l $(which fusermount3)
total 16
-rw-r--r-- 1 root root 3496 Jan  2 20:10 nginx.conf
-rw-r--r-- 1 root root 2189 Jan  2 20:29 docker-compose.yml
drwxr-xr-x 3 root root 4096 Jan  2 20:38 grafana
-rw-r--r-- 1 root root  649 Jan  2 20:35 prometheus.yml

I could think that all this staff about docker volumes. But docker-compose.yml? I didn't mount it to any containers.

[stefangweichinger]

Thanks for using the role and reporting this issue. I am on the road and not in office till next week.

Aside from that I think that installing fusermount3 is out of scope for this role. In my opinion you should install this with some other role or some task in a playbook. This role installs rclone, period. I am open to discussion, though.

Your 2nd posting: I don't see any relation to the role ansible-rclone here. Maybe it gets understandable after you installed fusermount3 and retest things (and provide more detail here). The rclone-role doesn't do any links, afaik (I don't use those rclone mounts myself, so I might be wrong here).

[mihalt]

@stefangweichinger I've found a problem. Probably this is my hoster error. I has circle linking:

$ ls -l /usr/bin/fusermount3
lrwxrwxrwx 1 root root 19 Jan  2 19:56 /usr/bin/fusermount3 -> /usr/bin/fusermount

$ ls -l /usr/bin/fusermount
lrwxrwxrwx 1 root root 11 Sep 15 06:00 /usr/bin/fusermount -> fusermount3

So, this command helped:

sudo apt remove --purge fuse3
sudo apt install fuse3