search for: shangzhong

...r failing to log level 1. * BUG 13832: Fix printing via smbspool backend with kerberos auth. * BUG 13847: s4:librpc: Fix installation of Samba. * BUG 13848: s3:lib: Fix the debug message for adding cache entries. * BUG 13853: s3:waf: Fix the detection of makdev() macro on Linux. o Zhu Shangzhong <zhu.shangzhong at zte.com.cn> * BUG 13839: ctdb: Initialize addr struct to zero before reparsing as IPV4. ####################################### Reporting bugs & Development Discussion ####################################### Please discuss this release on the samba-technical maili...

...r failing to log level 1. * BUG 13832: Fix printing via smbspool backend with kerberos auth. * BUG 13847: s4:librpc: Fix installation of Samba. * BUG 13848: s3:lib: Fix the debug message for adding cache entries. * BUG 13853: s3:waf: Fix the detection of makdev() macro on Linux. o Zhu Shangzhong <zhu.shangzhong at zte.com.cn> * BUG 13839: ctdb: Initialize addr struct to zero before reparsing as IPV4. ####################################### Reporting bugs & Development Discussion ####################################### Please discuss this release on the samba-technical maili...

...e debug message for adding cache entries. * BUG 13853: s3:waf: Fix the detection of makdev() macro on Linux. * BUG 13857: docs: Update smbclient manpage for --max-protocol. * BUG 13861: 'net ads join' to child domain fails when using "-U admin at forestroot". o Zhu Shangzhong <zhu.shangzhong at zte.com.cn> * BUG 13839: ctdb: Initialize addr struct to zero before reparsing as IPV4. o Martin Schwenke <martin at meltin.net> * BUG 13838: ctdb package should not own system library directory. * BUG 13860: CTDB restarts failed NFS RPC services by hand, w...

...e debug message for adding cache entries. * BUG 13853: s3:waf: Fix the detection of makdev() macro on Linux. * BUG 13857: docs: Update smbclient manpage for --max-protocol. * BUG 13861: 'net ads join' to child domain fails when using "-U admin at forestroot". o Zhu Shangzhong <zhu.shangzhong at zte.com.cn> * BUG 13839: ctdb: Initialize addr struct to zero before reparsing as IPV4. o Martin Schwenke <martin at meltin.net> * BUG 13838: ctdb package should not own system library directory. * BUG 13860: CTDB restarts failed NFS RPC services by hand, w...

...------------------------- Re: [Samba] [ctdb]Unable to run startrecovery event(if mail contentis encrypted, please see the attached file) Thanks for reporting this. It looks very interesting and we will fix it all as soon as we understand it! :-) On Wed, 5 Sep 2018 16:29:31 +0800 (CST), "zhu.shangzhong--- via samba" <samba at lists.samba.org> wrote: > There is a 3 nodes ctdb cluster is running. When one of 3 nodes is > powered down, lots of logs will be wrote to log.ctdb. Can you please let us know what version of Samba/CTDB you're using? Note that you're referring to...

Thanks Martin. --------------------------------------------------- Re: [Samba] [ctdb]Unable to run startrecovery event On Thu, 6 Sep 2018 14:24:12 +0800 (CST), "zhu.shangzhong--- via samba" <samba at lists.samba.org> wrote: > I have checked more logs. > Before ctdb-eventd went away, system memory utilization is very high, almost 100%. > Is it related to "Bad talloc magic value - wrong talloc version used/mixed"? Definitely. The only time...

When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node 2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602 2018/02/12 19:38:51.529060

...------------------------- Re: [Samba] [ctdb]Unable to run startrecovery event(if mail contentis encrypted, please see the attached file) Thanks for reporting this. It looks very interesting and we will fix it all as soon as we understand it! :-) On Wed, 5 Sep 2018 16:29:31 +0800 (CST), "zhu.shangzhong--- via samba" <samba at lists.samba.org> wrote: > There is a 3 nodes ctdb cluster is running. When one of 3 nodes is > powered down, lots of logs will be wrote to log.ctdb. Can you please let us know what version of Samba/CTDB you're using? Note that you're referring to...

...------------------------- Re: [Samba] [ctdb]Unable to run startrecovery event(if mail contentis encrypted, please see the attached file) Thanks for reporting this. It looks very interesting and we will fix it all as soon as we understand it! :-) On Wed, 5 Sep 2018 16:29:31 +0800 (CST), "zhu.shangzhong--- via samba" wrote: > There is a 3 nodes ctdb cluster is running. When one of 3 nodes is > powered down, lots of logs will be wrote to log.ctdb. Can you please let us know what version of Samba/CTDB you&apos;re using? Note that you&apos;re referring to nodes 1, 2, 3 while CTD...

------------------原始邮件------------------ 发件人：朱尚忠10137461 收件人：samba@lists.samba.org <samba@lists.samba.org> 日 期 ：2018年02月26日 17:10 主 题 ：[ctdb] Unable to take recovery lock - contention When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The

Am Montag, 26. Februar 2018, 17:26:06 CET schrieb zhu.shangzhong--- via samba: Decoded base64 encoded body with some chinese characters: ------------------原始邮件------------------ 发件人：朱尚忠10137461 收件人：samba at lists.samba.org <samba at lists.samba.org> 日 期 ：2018年02月26日 17:10 主 题 ：[ctdb] Unable to take recovery lock - contention When the ctdb is starting, th...

There is a 3 nodes ctdb cluster is running. When one of 3 nodes is powered down, lots of logs will be wrote to log.ctdb. node1: repeat logs: 2018/09/04 04:35:06.414369 ctdbd[10129]: Recovery has started 2018/09/04 04:35:06.414944 ctdbd[10129]: connect() failed, errno=111 2018/09/04 04:35:06.415076 ctdbd[10129]: Unable to run startrecovery event node2: repeat logs: 2018/09/04 04:35:09.412368

When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node 2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602 2018/02/12 19:38:51.529060