dm-vdo / vdo

Userspace tools for managing VDO volumes.
GNU General Public License v2.0
192 stars 31 forks source link

ModuleNotFoundError: No module named 'vdo' #31

Closed jwest75674 closed 4 years ago

jwest75674 commented 4 years ago

Hello!

I am having trouble getting VDO and KVDO working on a debian based machine (proxmox). Here are the steps I followed initially:

apt-get install -y git sudo
sudo apt-get upgrade -y
sudo apt-get install -y build-essential libdevmapper-dev libz-dev uuid-dev python-yaml python3-yaml
sudo apt install  pve-headers-$(uname -r)
mkdir /src
cd /src
git clone https://github.com/dm-vdo/vdo.git
git clone https://github.com/dm-vdo/kvdo.git
cd /src/vdo
make
make install
cd /src/kvdo
make -C /usr/src/linux-headers-`uname -r` M=`pwd`
cp vdo/kvdo.ko /lib/modules/`uname -r`/
cp uds/uds.ko /lib/modules/`uname -r`/
depmod
modprobe kvdo
modprobe uds
systemctl start vdo

Which leads to: (journalctl -xe)

May 20 22:09:01 dl380g7 systemd[1]: Starting VDO volume services...
-- Subject: A start job for unit vdo.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit vdo.service has begun execution.
--
-- The job identifier is 6046.
May 20 22:09:01 dl380g7 vdo[5672]: Traceback (most recent call last):
May 20 22:09:01 dl380g7 vdo[5672]:   File "/usr/bin/vdo", line 46, in <module>
May 20 22:09:01 dl380g7 vdo[5672]:     from vdo.utils import Command
May 20 22:09:01 dl380g7 vdo[5672]: ModuleNotFoundError: No module named 'vdo'
May 20 22:09:01 dl380g7 systemd[1]: vdo.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit vdo.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
May 20 22:09:01 dl380g7 systemd[1]: vdo.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit vdo.service has entered the 'failed' state with result 'exit-code'.
May 20 22:09:01 dl380g7 systemd[1]: Failed to start VDO volume services.
-- Subject: A start job for unit vdo.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit vdo.service has finished with a failure.
--
-- The job identifier is 6046 and the job result is failed.

I've searched the tickets here, and even Google didn't help shed any light on the situation. I do apologize if, as is likely, the issue is on my end, but after retrying a few times and being unable to otherwise track down a solution, this seemed an appropriate next step.

jwest75674 commented 4 years ago

Figured this out after waaaaaaay too long. The issue was related to the use of anaconda by default. deactivated anaconda and worked as expected.