Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

Veeam Agent for Linux Becomes Unresponsive on Debian

$
0
0

Challenge

When starting any backup job or log export, Veeam Agent  for Linux UI freezes and becomes unresponsive. The /var/log/veeam/Backup folder contains no log files for your configured backup jobs, the related folders are empty.  It may also be observed that veeamservice takes too much time to start/stop and becomes unresponsive.

Cause

It is possible that some of the dependent libraries are missing. The /usr/sbin/veeamjobman binary may not work properly if any dependent library missing. The example below contains the command that can be used to verify the root cause and the output generated in case a dependent library is missing.
 
root@debian:~# veeamjobman
veeamjobman: error while loading shared libraries: libmagic.so.1: cannot open shared object file: No such file or directory
root@debian:~#

The described behavior has been reproduced on Debian 7 and 8. For the most part, the minimal installations are affected.

Solution

The following workarounds are available at the moment.
  • Try to install a package that contains the missing library.
  • Upgrade the current system to the most recent update.
A package that contains the missing library can be found like this:
 
root@debian:~# apt-file find libmagic.so.1
libmagic1: /usr/lib/x86_64-linux-gnu/libmagic.so.1
libmagic1: /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0
root@debian:~#

Here is an example of installing a package that contains the missing library:

root@debian:~# apt-get install libmagic1

More Information

If you need assistance, you are welcome to open a support case with us. It will help if you can provide us with the following additional information.

Log in to shell as root and save the output ofthese commands:
 
dpkg -l
cat /etc/*release

 

Viewing all articles
Browse latest Browse all 4362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>