search for: 2018

...@node1 datapool]# qemu-x86_64 --version qemu-x86_64 version 2.9.0 Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers [root@node1 datapool]# uname -a Linux node1 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Here are some log fragments: 2018-11-13 14:21:39.942+0000: 95205: debug : virEventPollRunOnce:650 : Poll got 0 event(s) 2018-11-13 14:21:39.942+0000: 95205: debug : virEventPollDispatchTimeouts:432 : Dispatch 2 2018-11-13 14:21:39.942+0000: 95205: info : virEventPollDispatchTimeouts:455 : EVENT_POLL_DISPATCH_TIMEOUT: timer=2 2018-1...

...gainst that component, you’ll get notified automatically through email. For components with few reported bugs, a single triager may suffice. For the high-traffic components, we’ll probably need multiple volunteers. I’ve provided the list of product/components below that had bugs reported against in 2018, together with how many bugs were reported against them this year so far, as an indication for which components may need more volunteers. I do want to highlight the “new-bugs/new bugs”, “clang/-New Bugs” components as those tend to be components people file bugs against if they don’t have a clue w...

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 ctdb-recoverd[9437]: ../ctdb/server/ctdb_recoverd....

...;/directory> <directory> <yp-url-timeout>15</yp-url-timeout> <yp-url>http://icecast-yp.internet-radio.com</yp-url> </directory> yp in my error.log in the attached file -------------- next part -------------- [2018-01-14 18:46:22] DBUG yp/send_to_yp YP touch at http://icecast-yp.internet-radio.com succeeded [2018-01-14 18:46:22] DBUG yp/send_to_yp YP touch at http://icecast-yp.internet-radio.com succeeded [2018-01-14 18:46:22] DBUG yp/send_to_yp YP touch at http://icecast-yp.internet-radio.com succeeded [2...

------------------原始邮件------------------ 发件人：朱尚忠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 following the ctdb logs: 2018/...

Time stamps are correct and my system time is correct. I am now tried to use Sys.setFileTime() to update time stamps as proposed. This does not help. The windows and debian builds give different reports on the time stamp issue. https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.8_20180920_122655/Windows/00check.log https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.8_20180920_122655/Debian/00check.log I attached the time stamp listing below. Leo lei at kone:~/Rpackages/eurostat/inst/extras$ tar zvtf eurostat_3.2.8.tar.gz drwxr-xr-x lei/lei 0 2018-09-2...

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 ctdbd[6602]: Created PID file /run/ctdb/ctdbd.pid 2018/02/12 19:38:51.529120 ctdbd[6602]: Listening to ctdb socket /var/run/ctdb/c...

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 - con...

...components. If we merge components later on, we can merge cc lists, or asks the volunteers for the relevant components If they want to remain on the default-cc list for the merged component. * My opinion is the we should define components based on areas of expertise. Thanks, Kristof On 8 Nov 2018, at 20:39, Zachary Turner <zturner at google.com<mailto:zturner at google.com>> wrote: Just so I'm clear, are we going to attempt to clean up and/or merge the components? If we are, it makes sense to do that before we start putting ourselves as default CC's on the various comp...

...dmin") anymore. This happens even without any snapshots (it's the same when there are snapshots). Why? I tried disabling SELinux, no avail. I'm attaching some "log level = 9" logs and hope someone can enlighten me. Thanks Matthias -------------- next part -------------- [2018/02/21 14:26:38.414299, 5] ../lib/dbwrap/dbwrap.c:159(dbwrap_check_lock_order) check lock order 2 for /var/lib/samba/lock/serverid.tdb [2018/02/21 14:26:38.414404, 5] ../lib/dbwrap/dbwrap.c:127(dbwrap_lock_order_state_destructor) release lock order 2 for /var/lib/samba/lock/serverid.tdb [2018/...

Hi Zach, Thanks for elaborating. I like your proposal. I agree it still groups per area of expertise. And it makes the set of components we have easier to manage. Before making changes though I hope to hear opinions from others on this. What do others think? Thanks, Kristof On 9 Nov 2018, at 18:05, Zachary Turner <zturner at google.com<mailto:zturner at google.com>> wrote: To elaborate, I didn't mean to group all components with less than 10 bugs into one massive component. Rather, to do it separately for each subcomponent. Grouping by expertise is fine, but I wo...

...; { type master; file "master/localhost.zone"; }; # 127.0.0. zone. zone "0.0.127.in-addr.arpa" { type master; file "master/0.0.127.zone"; }; These zones are also in DC=RootDNSServers,CN=MicrosoftDNS,DC=DomainDnsZones,DC=<domain>,DC=corp The log parts. 31-Oct-2018 13:26:56.585 processing statistics channel 127.0.0.1#8653 31-Oct-2018 13:26:56.585 statistics channel listening on 127.0.0.1#8653 31-Oct-2018 13:26:56.585 using default UDP/IPv4 port range: [1024, 65535] 31-Oct-2018 13:26:56.585 using default UDP/IPv6 port range: [1024, 65535] 31-Oct-2018 13:26:56....

...l]# ls ls: cannot access 111: No such file or directory 111 [root at f08n25test_vol]# touch file touch: setting times of ?file?: No such file or directory Using other nodes also can not write data normally this is some log [root at f08n25glusterfs]# tail -n 100 test_vol-quota-crawl.log [2018-02-02 11:23:31.419152] W [MSGID: 122056] [ec-combine.c:873:ec_combine_check] 0-test_vol-disperse-0: Mismatching xdata in answers of 'LOOKUP' [2018-02-02 11:23:31.419274] W [MSGID: 122053] [ec-common.c:116:ec_check_status] 0-test_vol-disperse-0: Operation failed on some subvolumes (up=7, mas...

And here is mine. All dates are todays! # doveadm -f tab fetch -u test at example.org "uid date.saved" mailbox Trash uid date.saved 6829 2018-07-18 06:04:50 6830 2018-07-18 11:10:13 6831 2018-07-18 16:16:15 6832 2018-07-18 16:16:15 6833 2018-07-18 08:22:55 6834 2018-07-18 16:16:15 6835 2018-07-18 08:47:10 6836 2018-07-18 09:12:11 6837 2018-07-18 09:53:31 6838 2018-07-18 11:03:31 SNIP a lot of lines... 6873 2018-07-18 18:54:07 6874 2018-0...

On Thu, Sep 20, 2018 at 11:46 AM Leo Lahti <leo.lahti at iki.fi> wrote: > > Time stamps are correct and my system time is correct. > > I am now tried to use Sys.setFileTime() to update time stamps as proposed. > This does not help. > > The windows and debian builds give different reports on t...

...t is the last version that I could log successfully on. The test ADs have exactly the same configuration, that was created during the AD provisioning. Here are the log excerpts running on -d3: Working logon: ==================================Version 4.5.8-Ubuntu================================== [2018/03/26 16:32:38.889960, 3] ../lib/ldb-samba/ldb_wrap.c:325(ldb_wrap_connect) ldb_wrap open of secrets.ldb [2018/03/26 16:32:38.896147, 3] ../auth/ntlmssp/ntlmssp_util.c:69(debug_ntlmssp_flags) Got NTLMSSP neg_flags=0xe2088297 [2018/03/26 16:32:38.897060, 3] ../auth/ntlmssp/ntlmssp_server.c:45...

...example.com/DC=ForestDnsZones,DC=samba4p8,DC=example,DC=com # returned 4 records # 1 entries # 3 referrals named -V produces the relevant build options: '--with-dlopen' and '--with-gssapi' I ran named with the debug option "-d 7" and it produced this log output: 15-Mar-2018 12:29:13.562 starting BIND 9.11.2-P1 <id:2c2bc60> 15-Mar-2018 12:29:13.563 running on Linux x86_64 4.9.76-gentoo-r1 #1 SMP Wed Mar 14 23:34:12 GMT 2018 15-Mar-2018 12:29:13.563 built with '--prefix=/usr' '--build=x86_64-pc-linux-gnu' '--host=x86_64-pc-linux-gnu' '-...

...onfig * : base_tdb = 0 enable core files = false syslog = 0 log file = /var/log/samba/log.%m log level = 3 max log size = 50 [data] comment = Local data path = /opt/test/data/ valid users = userx public = no writeable = yes browseable = yes smb error: [2018/09/14 10:42:45.698030, 3] ../auth/ntlmssp/ntlmssp_util.c:69(debug_ntlmssp_flags) Got NTLMSSP neg_flags=0x62888215 [2018/09/14 10:42:45.722429, 3] ../auth/ntlmssp/ntlmssp_server.c:452(ntlmssp_server_preauth) Got user=[user1] domain=[DOMAIN] workstation=[USER1-2VFVH5-2] len1=24 len2=238 [2018/0...

...nt-io-threads: on performance.io-thread-count: 24 performance.write-behind-window-size: 8MB server.event-threads: 32 performance.write-behind: off performance.stat-prefetch: on performance.resync-failed-syncs-after-fsync: on server.outstanding-rpc-limit: 512 -------------- next part -------------- [2018-02-22 18:07:45.241970] W [rpcsvc.c:265:rpcsvc_program_actor] 0-rpc-service: RPC program not available (req 1298437 330) for 172.17.1.61:1022 [2018-02-22 18:07:45.242018] E [rpcsvc.c:560:rpcsvc_check_and_reply_error] 0-rpcsvc: rpc actor failed to complete successfully [2018-02-22 18:07:45.242681] W...

...sion 2.9.0 Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers [root@node1 datapool]# uname -a Linux node1 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux There are too many debug logs. I paste the log of thread 99225 below: Line 58679: 2018-11-13 14:22:30.129+0000: 95225: debug : qemuProcessLaunch:5614 : vm=0x7f822c002fe0 name=6efd749c-3162-4ac4-90e6-b3fca6fde9bc id=1 asyncJob=6 incoming.launchURI=<null> incoming.deferredURI=<null> incoming.fd=-1 incoming.path=<null> snapshot=(nil) vmop=0 flags=0x11 Line 58680: 2018-...