Install CloudEndure agent fail - Unexpected error while making agent driver!

English Applications
#1

I’m trying to install CloudEndure agent and when I try to run install_agent, I get the following error:

running: 'make SUSE_KERNEL=1'
make -C /lib/modules/4.4.74-92.38-default/build M=/tmp/tmp.0UEd7q5Xob/AgentDriver modules
make[1]: Entering directory '/usr/src/linux-4.4.74-92.38-obj/x86_64/default'
  CC [M]  /tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.o
/tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.c: In function ‘get_bio_chain_callback_pointer’:
/tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.c:172:5: error: too many arguments to function ‘bio_init’
     bio_init(&parent, NULL, 0);
     ^
In file included from /usr/src/linux-4.4.74-92.38/include/linux/writeback.h:192:0,
                 from /usr/src/linux-4.4.74-92.38/include/linux/memcontrol.h:30,
                 from /usr/src/linux-4.4.74-92.38/include/linux/swap.h:8,
                 from /usr/src/linux-4.4.74-92.38/include/linux/pagemap.h:15,
                 from /usr/src/linux-4.4.74-92.38/include/linux/blkdev.h:14,
                 from /tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.c:33:
/usr/src/linux-4.4.74-92.38/include/linux/bio.h:479:13: note: declared here
 extern void bio_init(struct bio *);
             ^
/tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.c:173:5: error: too many arguments to function ‘bio_init’
     bio_init(&child, NULL, 0);
     ^
In file included from /usr/src/linux-4.4.74-92.38/include/linux/writeback.h:192:0,
                 from /usr/src/linux-4.4.74-92.38/include/linux/memcontrol.h:30,
                 from /usr/src/linux-4.4.74-92.38/include/linux/swap.h:8,
                 from /usr/src/linux-4.4.74-92.38/include/linux/pagemap.h:15,
                 from /usr/src/linux-4.4.74-92.38/include/linux/blkdev.h:14,
                 from /tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.c:33:
/usr/src/linux-4.4.74-92.38/include/linux/bio.h:479:13: note: declared here
 extern void bio_init(struct bio *);
             ^
/usr/src/linux-4.4.74-92.38/scripts/Makefile.build:259: recipe for target '/tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.o' failed
make[4]: *** [/tmp/tmp.0UEd7q5Xob/AgentDriver/src/linux/KernelTracer.o] Error 1
/usr/src/linux-4.4.74-92.38/Makefile:1428: recipe for target '_module_/tmp/tmp.0UEd7q5Xob/AgentDriver' failed
make[3]: *** [_module_/tmp/tmp.0UEd7q5Xob/AgentDriver] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[1]: *** [__sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-4.4.74-92.38-obj/x86_64/default'
Makefile:38: recipe for target 'AgentDriver' failed
make: *** [AgentDriver] Error 2
retcode: 512

Unexpected error while making agent driver! Are kernel linux headers installed correctly?

My kernel info:

:~ # uname -r
4.4.121-92.141-default
:~ # rpm -qa | grep kernel
kernel-default-devel-4.4.121-92.135.1.x86_64
nfs-kernel-server-1.3.0-34.22.1.x86_64
kernel-source-4.4.121-92.141.1.noarch
kernel-source-4.4.121-92.135.1.noarch
kernel-devel-4.4.121-92.135.1.noarch
kernel-macros-4.4.121-92.141.1.noarch
kernel-default-devel-4.4.121-92.141.1.x86_64
kernel-default-4.4.121-92.135.1.x86_64
kernel-firmware-20170530-21.31.1.noarch
kernel-devel-4.4.121-92.141.1.noarch
kernel-default-4.4.121-92.141.1.x86_64

How can I solve this problem?
Any help Appreciated

#2

Hi and welcome to the Forum :slight_smile:
I see you selected Leap 15.2 as the prefix, but your output indicates an unsupported release, openSUSE Leap 42?

I imagine that kernel is too old for the driver hence your error…

#3

Looks like you’re building /lib/modules/4.4.74-92.38-default
While your kernel is 4.4.121-92.141-default

IMO you’ll need to figure out why you’re building for a different kernel,
Maybe you didn’t run the make and make configure commands?

BTW -
You should remove your kernel source packages and leave only the “devel” packages… Assuming you only want to build kernel modules and not build a new kernel itself, those source packages are just going to confuse things and never be used.

TSU

#4

Thank you for your help.
But I’m sorry, I’m sent kernel information is another testing machine.
There is the error message machine kernel information:

:~ # uname -r
4.4.74-92.38-default
:~ # rpm -qa | grep kernel
kernel-devel-4.4.74-92.38.1.noarch
kernel-default-4.4.59-92.20.2.x86_64
kernel-default-4.4.74-92.38.1.x86_64
kernel-source-4.4.59-92.20.2.noarch
kernel-source-4.4.74-92.38.1.noarch
kernel-default-devel-4.4.74-92.38.1.x86_64
kernel-devel-4.4.59-92.20.2.noarch
kernel-firmware-20170530-21.10.1.noarch
kernel-default-devel-4.4.59-92.20.2.x86_64
nfs-kernel-server-1.3.0-33.7.x86_64
kernel-macros-4.4.74-92.38.1.noarch

By the way, I also try in kernel 4.4.121-92.141 machines get the similar error.

#5

I don’t know if it makes a difference, but your kernel and kernel headers are still slightly different… Your kernel headers (the devel files) have a minor version of “.1” that is not in your reported kernel.

Run a system update and then reboot to see if you can get those versions to match exactly

zypper up

And,
As I mentioned earlier, unless you intend to build the kernel itself and not just build a kernel module, you should remove the kernel source packages from your system. It shouldn’t cause problems but would confuse and add info to your output that is irrelevant.

TSU

#6

Thanks for the suggestion.
I try with command ‘zypper up’ and reboot, but the problem remains.

#7

What malcolmlewis is saying:
Your system is maybe too old.

Kernel 4.4 was delivered with Leap 42.x which is out of support.

Try a newer Leap 15.2

#8

Thanks for your help.

But in CloudEndure documentation, they said “Kernel versions earlier than 2.6.18-164 are not supported”.
CloudEndure should be supporting my kernel version.

#9

But in CloudEndure documentation, they said “Kernel versions earlier than 2.6.18-164 are not supported”.

This is minimum version…

Kernels gets developed and changed…

I build drivers and have often making a patch.

I can not confirm it, because I have to add a acoount, so maybe ask them.