Thursday, July 24, 2008
confd and Element support matrix
Q: I'm trying to figure out which version of confd goes with my Element release. This doesn't seem to be documented in the Element 2.3.x docs I have.
A: Correct that it's not documented. Here is the matrix for what is officially supported for confd.
Element 2.3.0 - confd 2.3.0
Element 2.3.1 - confd 2.3.0
Element 2.3.2 - confd 2.3.0, 2.3.1, 2.3.2,and 2.3.3 .
Element 3.0.0 - confd 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.4.0, 2.4.1, 2.4.2.
The 2.3.x and 2.4.x releases of ConfD are not API compatible, consequently Element starting in release 3.0.0 is built differently for each. There are two reference platforms for confd in the newer release, generic_confd_2.3.3 generic_confd_2.4.2 .
A: Correct that it's not documented. Here is the matrix for what is officially supported for confd.
Element 2.3.0 - confd 2.3.0
Element 2.3.1 - confd 2.3.0
Element 2.3.2 - confd 2.3.0, 2.3.1, 2.3.2,and 2.3.3 .
Element 3.0.0 - confd 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.4.0, 2.4.1, 2.4.2.
The 2.3.x and 2.4.x releases of ConfD are not API compatible, consequently Element starting in release 3.0.0 is built differently for each. There are two reference platforms for confd in the newer release, generic_confd_2.3.3 generic_confd_2.4.2 .
Labels: confd, Element, tail-f
Tuesday, July 08, 2008
"error: too arguments to function 'confd_init' "
Q: When I put confd-2.4.1 into action with this release, I get this build error in generic_confd:
make[3]: Entering directory `/home/jmir/Element/Releases/2.3.0/element_2.3.0/src/northbound/confd_proxy'
+++ Compiling confd_proxy.c
confd_proxy.c: In function `elemConfdInitConfdHa':
confd_proxy.c:1101: warning: implicit declaration of function `confd_ha_init'
confd_proxy.c: In function `confdProxy':
confd_proxy.c:3067: error: too few arguments to function `confd_init'
A: confd-2.4.x is not supported with this release of Element. Go back to confd-2.3.0.
Q: ...and... if I want to use confd-2.4.x instead?
A: You must upgrade to Element 2.3.2 or higher.
make[3]: Entering directory `/home/jmir/Element/Releases/2.3.0/element_2.3.0/src/northbound/confd_proxy'
+++ Compiling confd_proxy.c
confd_proxy.c: In function `elemConfdInitConfdHa':
confd_proxy.c:1101: warning: implicit declaration of function `confd_ha_init'
confd_proxy.c: In function `confdProxy':
confd_proxy.c:3067: error: too few arguments to function `confd_init'
A: confd-2.4.x is not supported with this release of Element. Go back to confd-2.3.0.
Q: ...and... if I want to use confd-2.4.x instead?
A: You must upgrade to Element 2.3.2 or higher.
Labels: confd, Element, tail-f
Wednesday, July 02, 2008
elemLoader does not start after migrating to Element 3.0
Q: I upgraded from Element 2.3.x to Element 3.0. Everything in 3.0 seemed to build okay, but the elemLoader won't start.
A: The problem is the upgrade itself - 2.3.x isn't actually upgradable to 3.0, due to backward incompatibilities in LINX and other areas. The only procedure that is known to work consistently is to delete or rename /usr/local/element from your 2.3.x installation to something else, then configure and install Element 3.0.
A: The problem is the upgrade itself - 2.3.x isn't actually upgradable to 3.0, due to backward incompatibilities in LINX and other areas. The only procedure that is known to work consistently is to delete or rename /usr/local/element from your 2.3.x installation to something else, then configure and install Element 3.0.
Labels: Element
generic_confd make error: confd.h: No such file or directory
Q: I'm trying my first attempt at building the Element reference platform for confd. In ref_platforms/generic_confd, I get instead:
+++ Compiling confd_proxy.c
confd_proxy.c:81:19: confd.h: No such file or directory
make[3]: *** [obj/linux-x86/confd_proxy.o] Error 1
make[3]: Leaving directory `/home/jmir/Element/Releases/2.3.1/element_2.3.1/src/northbound/confd_proxy'
make[2]: *** [libs] Error 1
A: You must first install confd software on your system, then set up a softlink to the confd root within your Element tree. This is described in the ConfD Support Guide in the section Building Element with ConfD Support.
Q: Okay, I did all that, but I still get the same error...
A: Note that the "arch" designation for your softlink may confuse some who are used to seeing linux-x86 directories all over their build. While this is normal for Element object directories, the ones under confd (and the one required for this softlink) should be x86 instead. E.g. he command to set up the softlink within element_2.3.0 pointing to confd-2.4.1 looks like:
ln -s /home/jmir/tail-f/Releases/2.4.1/confd-2.4.1 /home/jmir/Element/Releases/2.3.0/element_2.3.0/confd/x86
+++ Compiling confd_proxy.c
confd_proxy.c:81:19: confd.h: No such file or directory
make[3]: *** [obj/linux-x86/confd_proxy.o] Error 1
make[3]: Leaving directory `/home/jmir/Element/Releases/2.3.1/element_2.3.1/src/northbound/confd_proxy'
make[2]: *** [libs] Error 1
A: You must first install confd software on your system, then set up a softlink to the confd root within your Element tree. This is described in the ConfD Support Guide in the section Building Element with ConfD Support.
Q: Okay, I did all that, but I still get the same error...
A: Note that the "arch" designation for your softlink may confuse some who are used to seeing linux-x86 directories all over their build. While this is normal for Element object directories, the ones under confd (and the one required for this softlink) should be x86 instead. E.g. he command to set up the softlink within element_2.3.0 pointing to confd-2.4.1 looks like:
ln -s /home/jmir/tail-f/Releases/2.4.1/confd-2.4.1 /home/jmir/Element/Releases/2.3.0/element_2.3.0/confd/x86
Labels: confd, Element, tail-f
free invisible web counter
