are you sure its '--witn-tirpc'? as with it i am getting
WARNING: QA Issue: glusterfs: configure was passed unrecognised options:
--with-tirpc [unknown-configure-option]
also I tried with '--with-libtirpc' but result was same.
Regards,
Abhishek
On Wed, Mar 13, 2019 at 11:56 AM Amar Tumballi Sur
We recommend to use 'tirpc' in the later releases. use '--with-tirpc' while
running ./configure
On Wed, Mar 13, 2019 at 10:55 AM ABHISHEK PALIWAL
wrote:
> Hi Amar,
>
> this problem seems to be configuration issue due to librpc.
>
> Could you please let me know what should be configuration I need
Hi Amar,
this problem seems to be configuration issue due to librpc.
Could you please let me know what should be configuration I need to use?
Regards,
Abhishek
On Wed, Mar 13, 2019 at 10:42 AM ABHISHEK PALIWAL
wrote:
> logs for libgfrpc.so
>
> pabhishe@arn-build3$ldd
> ./5.4-r0/packages-split
logs for libgfrpc.so
pabhishe@arn-build3$ldd
./5.4-r0/packages-split/glusterfs/usr/lib64/libgfrpc.so.*
./5.4-r0/packages-split/glusterfs/usr/lib64/libgfrpc.so.0:
not a dynamic executable
./5.4-r0/packages-split/glusterfs/usr/lib64/libgfrpc.so.0.0.1:
not a dynamic executable
On Wed, Mar 13, 2019
Hi Abhishek,
Few more questions,
> On Tue, Mar 12, 2019 at 10:58 AM ABHISHEK PALIWAL
> wrote:
>
>> Hi Amar,
>>
>> Below are the requested logs
>>
>> pabhishe@arn-build3$ldd ./sysroot-destdir/usr/lib64/libglusterfs.so
>> not a dynamic executable
>>
>> pabhishe@arn-build3$ldd ./sysroot-destdir/us
Hi Amar,
did you get time to check the logs?
Regards,
Abhishek
On Tue, Mar 12, 2019 at 10:58 AM ABHISHEK PALIWAL
wrote:
> Hi Amar,
>
> Below are the requested logs
>
> pabhishe@arn-build3$ldd ./sysroot-destdir/usr/lib64/libglusterfs.so
> not a dynamic executable
>
> pabhishe@arn-build3$ldd ./s
Hi Amar,
Below are the requested logs
pabhishe@arn-build3$ldd ./sysroot-destdir/usr/lib64/libglusterfs.so
not a dynamic executable
pabhishe@arn-build3$ldd ./sysroot-destdir/usr/lib64/libgfrpc.so
not a dynamic executable
root@128:/# gdb /usr/sbin/glusterd core.1099
GNU gdb (GDB) 7.10.1
Copyright
Hi Abhishek,
Can you check and get back to us?
```
bash# ldd /usr/lib64/libglusterfs.so
bash# ldd /usr/lib64/libgfrpc.so
```
Also considering you have the core, can you do `(gdb) thr apply all bt
full` and pass it on?
Thanks & Regards,
Amar
On Mon, Mar 11, 2019 at 3:41 PM ABHISHEK PALIWAL
w
Hi Team,
COuld you please provide some pointer to debug it further.
Regards,
Abhishek
On Fri, Mar 8, 2019 at 2:19 PM ABHISHEK PALIWAL
wrote:
> Hi Team,
>
> I am using Glusterfs 5.4, where after setting the gluster mount point when
> trying to access it, glusterfsd is getting crashed and mount
Hi Team,
I am using Glusterfs 5.4, where after setting the gluster mount point when
trying to access it, glusterfsd is getting crashed and mount point through
the "Transport endpoint is not connected error.
Here I are the gdb log for the core file
warning: Could not load shared library symbols f
Anand Avati a écrit :
This bug is being fixed in the repository. You can disable
flush-behind on the server spec file to not trigger the bug, till the
next release is made available.
Ok, I confirm, it didn't crash with flush-behind disabled.
--
Greg
___
This bug is being fixed in the repository. You can disable
flush-behind on the server spec file to not trigger the bug, till the
next release is made available.
Avati
On Thu, Apr 2, 2009 at 2:41 PM, Greg wrote:
> Shehjar Tikoo a écrit :
>>
>> Hi Greg
>>
>> Can you try running a test with the sam
Shehjar Tikoo a écrit :
Hi Greg
Can you try running a test with the same config but without the
io-threads translator? It has undergone some changes lately that might
be the cause here. However, cursory look at the code suggests something
else. Still, no harm in eliminating one potential reason.
Hi Greg
Can you try running a test with the same config but without the
io-threads translator? It has undergone some changes lately that might
be the cause here. However, cursory look at the code suggests something
else. Still, no harm in eliminating one potential reason.
Thanks
Shehjar
Greg wr
Can you please get us a backtrace of the core dump?
Thanks,
Avati
On Wed, Apr 1, 2009 at 9:45 PM, Greg wrote:
> Anand Avati a écrit :
>>
>> Greg,
>> can you describe the sequence of operations performed on the
>> mountpoint before you faced this?
>>
>>
>
___
Can you please get us a backtrace of the core dump?
Thanks,
Avati
On Wed, Apr 1, 2009 at 9:45 PM, Greg wrote:
> Anand Avati a écrit :
>>
>> Greg,
>> can you describe the sequence of operations performed on the
>> mountpoint before you faced this?
>>
>>
>
> Avati,
>
> I have restarted both serve
Anand Avati a écrit :
Greg,
can you describe the sequence of operations performed on the
mountpoint before you faced this?
Avati,
I have restarted both servers, then mount on 10 clients, then put some
load on only 1 client, using mount bind.
Regards,
--
Greg
___
Greg,
can you describe the sequence of operations performed on the
mountpoint before you faced this?
Avati
On Wed, Apr 1, 2009 at 9:06 PM, Greg wrote:
> Hi,
>
> I've just upgraded to 2.0.0-rc7, and add read-ahead + io-cache translators
> on server side, and got this error on both servers :
>
>
Hi,
I've just upgraded to 2.0.0-rc7, and add read-ahead + io-cache
translators on server side, and got this error on both servers :
2009-04-01 17:26:21 N [server-protocol.c:7513:mop_setvolume] server:
accepted client from 10.0.8.3:954
2009-04-01 17:26:21 N [server-protocol.c:7513:mop_setvolum
19 matches
Mail list logo
