Atin Mukherjee wrote on 21/01/2016 10:12:> On 01/21/2016 03:11 PM, Ronny Adsetts wrote: >> >> I'm trying to upgrade our gluster install to 3.7.6 from the >> gluster.org repo for Debian Wheezy. The package installs but >> gluster fails to start with the following logged: >>[...]>> [2016-01-21 09:11:16.477126] W [MSGID: 101095] >> [xlator.c:194:xlator_dynload] 0-xlator: >> /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/mgmt/glusterd.so: >> undefined symbol: rcu_read_lock_bp[...]>> >> Having Googled around, I installed librcu1: >> >> https://packages.debian.org/wheezy/liburcu1 >> >> but this doesn't help. >> >> The function rcu_read_lock_bp does exist in a library >> /usr/lib/liburcu-bp.so.1 installed by the librcu1 package:[...]>> >> Any ideas on how to proceed from here? > > Install liburcu-dev package. That should solve the problem.Hi Atin, Thanks for your reply. That doesn't seem to help. Trying to start gluster after installing liburcu-dev gives the same error as above. Ronny -- Ronny Adsetts Technical Director Amazing Internet Ltd, London t: +44 20 8977 8943 w: www.amazinginternet.com Registered office: 85 Waldegrave Park, Twickenham, TW1 4TJ Registered in England. Company No. 4042957 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160121/9c4225ef/attachment.sig>
Am 2016-01-21 11:22, schrieb Ronny Adsetts:> Atin Mukherjee wrote on 21/01/2016 10:12: >> On 01/21/2016 03:11 PM, Ronny Adsetts wrote: >>> >>> I'm trying to upgrade our gluster install to 3.7.6 from the >>> gluster.org repo for Debian Wheezy. The package installs but >>> gluster fails to start with the following logged: >>> > [...] >>> [2016-01-21 09:11:16.477126] W [MSGID: 101095] >>> [xlator.c:194:xlator_dynload] 0-xlator: >>> /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/mgmt/glusterd.so: >>> undefined symbol: rcu_read_lock_bp > [...] >>> >>> Having Googled around, I installed librcu1: >>> >>> https://packages.debian.org/wheezy/liburcu1 >>> >>> but this doesn't help. >>> >>> The function rcu_read_lock_bp does exist in a library >>> /usr/lib/liburcu-bp.so.1 installed by the librcu1 package: > [...] >>> >>> Any ideas on how to proceed from here? >> >> Install liburcu-dev package. That should solve the problem. > > Hi Atin, > > Thanks for your reply. > > That doesn't seem to help. Trying to start gluster after installing > liburcu-dev gives the same error as above. > > Ronny > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-usersHi, i have installed wheezy too and upgraded glusterfs since 3.5x and got no problems. the mentioned packed is not installed on my system. From which Version you upgraded and do you update wheezy to latest packages? Taste
On Thu, Jan 21, 2016 at 3:52 PM, Ronny Adsetts <ronny.adsetts at amazinginternet.com> wrote:> Atin Mukherjee wrote on 21/01/2016 10:12: >> On 01/21/2016 03:11 PM, Ronny Adsetts wrote: >>> >>> I'm trying to upgrade our gluster install to 3.7.6 from the >>> gluster.org repo for Debian Wheezy. The package installs but >>> gluster fails to start with the following logged: >>> > [...] >>> [2016-01-21 09:11:16.477126] W [MSGID: 101095] >>> [xlator.c:194:xlator_dynload] 0-xlator: >>> /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/mgmt/glusterd.so: >>> undefined symbol: rcu_read_lock_bp > [...] >>> >>> Having Googled around, I installed librcu1: >>> >>> https://packages.debian.org/wheezy/liburcu1 >>> >>> but this doesn't help. >>> >>> The function rcu_read_lock_bp does exist in a library >>> /usr/lib/liburcu-bp.so.1 installed by the librcu1 package: > [...] >>> >>> Any ideas on how to proceed from here? >> >> Install liburcu-dev package. That should solve the problem. > > Hi Atin, > > Thanks for your reply. > > That doesn't seem to help. Trying to start gluster after installing liburcu-dev gives the same error as above.*-dev packages are only required when building, they just provide the header files required. So they wouldn't help. Could you provide a little more details on your system and the packages used (arch, version etc.). Also could you do a `ldd` on glusterd.so to find the exact .so glusterd is trying to find, `ldd /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/mgmt/glusterd.so | grep liburcu`.> > Ronny > -- > Ronny Adsetts > Technical Director > Amazing Internet Ltd, London > t: +44 20 8977 8943 > w: www.amazinginternet.com > > Registered office: 85 Waldegrave Park, Twickenham, TW1 4TJ > Registered in England. Company No. 4042957 > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users