proxmox-backup-client mount not work on centos 7

marwen

Member
Mar 3, 2021
1
0
6
54
Hey guys.

I try to mount a snapshot/backup

Code:
proxmox-backup-client mount host/backuppc/2021-03-12T06:26:16Z root.pxar /mnt/mountpoint --repository filebackup@pbs@10.124.0.195:8007:QNAP-PBS-NFS
on debian 10 it works perfect (fuse-lib 3.4.1)

on centos 7 i get an error message with the same command.

Code:
proxmox-backup-client mount host/backuppc/2021-03-12T06:26:16Z root.pxar /mnt/mountpoint --repository filebackup@pbs@10.124.0.195:8007:QNAP-PBS-NFS
FUSE library version: 3.6.1
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /root/proxmox-backup-client/proxmox-backup/vendor/tokio/src/runtime/context.rs:18:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

any idea to fix that ?

Code:
FUSE library version: 3.6.1
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /root/proxmox-backup-client/proxmox-backup/vendor/tokio/src/runtime/context.rs:18:26
stack backtrace:
   0: rust_begin_unwind
             at /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/core/src/panicking.rs:92:14
   2: core::option::expect_failed
             at /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/core/src/option.rs:1260:5
   3: std::thread::local::LocalKey<T>::with
   4: tokio::io::driver::Handle::current
   5: proxmox_fuse::session::FuseSession::mount
   6: proxmox_backup::pxar::fuse::Session::mount
   7: proxmox_backup_client::proxmox_backup_client::mount::mount_do::{{closure}}
   8: proxmox_backup::tools::runtime::block_on_local_future
   9: tokio::runtime::context::enter
  10: proxmox_backup::tools::runtime::main
  11: proxmox_backup_client::proxmox_backup_client::mount::mount
  12: core::ops::function::Fn::call
  13: proxmox::api::cli::command::handle_simple_command
  14: proxmox::api::cli::command::handle_command
  15: proxmox::api::cli::command::run_cli_command
  16: proxmox_backup_client::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Centos 7 proxmox-backup-client was build from the howto:

https://github.com/sg4r/proxmox-backup-client
 
Last edited:
Hey guys.

I try to mount a snapshot/backup

Code:
proxmox-backup-client mount host/backuppc/2021-03-12T06:26:16Z root.pxar /mnt/mountpoint --repository filebackup@pbs@10.124.0.195:8007:QNAP-PBS-NFS
on debian 10 it works perfect (fuse-lib 3.4.1)

on centos 7 i get an error message with the same command.

Code:
proxmox-backup-client mount host/backuppc/2021-03-12T06:26:16Z root.pxar /mnt/mountpoint --repository filebackup@pbs@10.124.0.195:8007:QNAP-PBS-NFS
FUSE library version: 3.6.1
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /root/proxmox-backup-client/proxmox-backup/vendor/tokio/src/runtime/context.rs:18:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

any idea to fix that ?

Code:
FUSE library version: 3.6.1
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /root/proxmox-backup-client/proxmox-backup/vendor/tokio/src/runtime/context.rs:18:26
stack backtrace:
   0: rust_begin_unwind
             at /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/core/src/panicking.rs:92:14
   2: core::option::expect_failed
             at /rustc/cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/core/src/option.rs:1260:5
   3: std::thread::local::LocalKey<T>::with
   4: tokio::io::driver::Handle::current
   5: proxmox_fuse::session::FuseSession::mount
   6: proxmox_backup::pxar::fuse::Session::mount
   7: proxmox_backup_client::proxmox_backup_client::mount::mount_do::{{closure}}
   8: proxmox_backup::tools::runtime::block_on_local_future
   9: tokio::runtime::context::enter
  10: proxmox_backup::tools::runtime::main
  11: proxmox_backup_client::proxmox_backup_client::mount::mount
  12: core::ops::function::Fn::call
  13: proxmox::api::cli::command::handle_simple_command
  14: proxmox::api::cli::command::handle_command
  15: proxmox::api::cli::command::run_cli_command
  16: proxmox_backup_client::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Centos 7 proxmox-backup-client was build from the howto:

https://github.com/sg4r/proxmox-backup-client
Hi,
this is probably not related to the fuse library as I have an ArchLinux system with Fuse 3.10.2 and proxmox-backup-client 1.0.10 and mounts are working just fine.
This seems more like a bug of the outdated version of the proxmox-backup-client in the github repo.
The error is related to the tokio runtime. You could try to build a newer version of the client, have a look at the AUR package in order to understand what steps need to be taken to compile the client by yourself.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!