search for: 9246

...power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since vie 2016-06-03 12:10:05 ART; 7s ago Process: 7511 ExecStop=/usr/sbin/upsdrvctl stop (code=exited, status=0/SUCCESS) Process: 9246 ExecStart=/usr/sbin/upsdrvctl start (code=exited, status=1/FAILURE) Process: 9245 ExecStartPre=/usr/bin/systemd-tmpfiles --create /etc/tmpfiles.d/nut-run.conf (code=exited, status=1/FAILURE) jun 03 12:10:03 nut-vm.infoestructura.local upsdrvctl[9246]: [APC_edificio_1] Warning: excessive poll fai...

https://bugzilla.samba.org/show_bug.cgi?id=9246 Summary: Add chroot enablement option to rsync client Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samb...

On Jun 3, 2016, at 11:13 AM, Sergio Belkin <sebelk at gmail.com> wrote: > > jun 03 12:10:05 nut-vm.infoestructura.local upsdrvctl[9246]: No supported device detected > jun 03 12:10:05 nut-vm.infoestructura.local upsdrvctl[9246]: Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) > jun 03 12:10:05 nut-vm.infoestructura.local systemd[1]: nut-driver.service: control process exited, code=exited status=1 > jun 03 12:10:0...

Sds, Paulo Henrique Cardoso Administrador de Redes - T.I. NHS Sistemas Eletr?nicos Ltda Av. Juscelino Kubitschek de Oliveira, 5270 Cidade Industrial, Curitiba - PR Fone/Fax: (41) 2141-9246/9247 www.nhs.com.br IMPORTANTE: Esta mensagem, incluindo quaisquer anexos, ? endere?ada exclusivamente ao seu destinat?rio e poder? conter informa??es confidenciais. A revis?o, distribui??o, divulga??o e o uso n?o autorizado de tais informa??es ? proibido e estar? sujeita a penalidade cab?vel....

...unning a KVM/libvirt host in a datacenter and got a fancy IPv4 subnet from my provider. I'm able to assign IPs from that subnet via dhcp to my VMs: host01 ~ # virsh net-dumpxml internet <network connections='3'> <name>internet</name> <uuid>37b888cc-510f-46f1-9246-346da96222ed</uuid> <forward dev='enp5s0f0' mode='route'> <interface dev='enp5s0f0'/> </forward> <bridge name='virbr1' stp='on' delay='0'/> <mac address='52:54:00:13:39:d5'/> <ip address=...

...ain Controllers,DC=ad,DC=lasthome,DC=solace,DC=krynn' [ldap://dc00] 'CN=DC01,OU=Domain Controllers,DC=ad,DC=lasthome,DC=solace,DC=krynn' [ldap://dc01] Difference in attribute values: servicePrincipalName => ['E3514235-4B06-11D1-AB04-00C04FC2DCD2/9075aec2-bbc6-4f87-9246-aa75689b86d4/ad.lasthome.solace.krynn', 'GC/dc01.ad.lasthome.solace.krynn/ad.lasthome.solace.krynn', 'HOST/DC01', 'HOST/dc01.ad.lasthome.solace.krynn'] ['E3514235-4B06-11D1-AB04-00C04FC2DCD2/9075aec2-bbc6-4f87-9246-aa75689b86d4/ad.lasthome.solace.krynn', '...

Hi all, I'm running in circles trying to debug replication failures on samba 4.7.6: dc00 : is a VM on KVM host (attached to a bridge on local LAN) dc01 : is a similarly configured VM on another KVM host. I've forcibly demoted and re-promoted dc01 but I still cannot get automatic replication to work: root at dc00 ~]# samba-tool drs showrepl Krynn\DC00 DSA Options: 0x00000001 DSA

...ata/myvolume/brick/.glusterfs/indices/xattrop total 76180 10 drw------- 2 root root 4 Jul 29 12:15 . 9 drw------- 5 root root 5 Apr 28 22:15 .. 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. So my question here is, is it possible that this is a stale file which just forgot to get...

...;, "SW-5", "SW-6", "SW-7", "SW-8", "SW-9"), class = "factor"), sampdate = structure(c(8421, 8442, 8477, 8503, 8537, 8567, 8595, 8596, 8636, 8666, 8686, 8713, 8741, 8782, 8810, 8833, 8861, 8889, 8924, 8957, 8988, 9022, 9049, 9114, 9142, 9246, 9274, 9295, 9407, 8573, 8693, 8573, 8693, 8363, 8390, 8421, 8442, 8476, 8505, 8532, 8567, 8604, 8638, 8665, 8686, 8717, 8741, 8778, 8805, 8833, 8860, 8887, 8924, 8959, 8987, 9022, 9050, 9113, 9141, 9169, 9205, 9244, 9274, 9296, 9408, 8364, 8391, 8421, 8441, 8476, 8505, 8531, 8566, 8594, 8636,...

...D_DIRECTORIES_IN_BETWEEN>/fileKey node2: 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 arbirternode: NOTHING As you requested I have tried to run on node1 a getfattr on the fileKey file by using the following command: getfattr -m . -d -e hex fileKey but there is no output. I am not familiar with the getfattr command so maybe I am using the wrong parameters, could you hel...

...---------- 2 root root 0 Apr 28 22:51 > /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 > 2798404 1 ---------- 2 root root 0 Apr 28 22:51 > /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 > > arbirternode: > > NOTHING > > As you requested I have tried to run on node1 a getfattr on the > fileKey file by using the following command: > > getfattr -m . -d -e hex fileKey > > but there is no output. I am not familiar with the getfattr command...

...t; total 76180 > 10 drw------- 2 root root 4 Jul 29 12:15 . > 9 drw------- 5 root root 5 Apr 28 22:15 .. > 2798404 ---------- 2 root root 0 Apr 28 22:51 > 29e0d13e-1217-41cc-9bda-1fbbf781c397 > 2798404 ---------- 2 root root 0 Apr 28 22:51 > xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 > > > > I tried to find the real file on my brick where this xattrop file > points to using its inode number (command: find > /data/myvolume/brick/data -inum 8394642) but it does not find any > associated file. > > So my question here is, is it possible th...

...;/fileKey >> node2: >> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >> arbirternode: >> NOTHING >> As you requested I have tried to run on node1 a getfattr on the fileKey file by using the following command: >> getfattr -m . -d -e hex fileKey >> but there is no output. I am not familiar with the getfattr command so maybe I...

...t;> 10 drw------- 2 root root 4 Jul 29 12:15 . >>>> 9 drw------- 5 root root 5 Apr 28 22:15 .. >>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 >>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >>>> So my question here is, is it possible that this is a s...

...>> 9 drw------- 5 root root 5 Apr 28 22:15 .. >>>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>>>> 29e0d13e-1217-41cc-9bda-1fbbf781c397 >>>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>>>> xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>>> >>>>> >>>>> >>>>> I tried to find the real file on my brick where this xattrop file >>>>> points to using its inode number (command: find >>>>> /data/myvolume/brick/data -inum 8394642) but...

...>> total 76180 >> 10 drw------- 2 root root 4 Jul 29 12:15 . >> 9 drw------- 5 root root 5 Apr 28 22:15 .. >> 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 >> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >> So my question here is, is it possible that this is a stale file which...

...root 0 Apr 28 22:51 >>> /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >>> 2798404 1 ---------- 2 root root 0 Apr 28 22:51 >>> /data/myvolume/brick/.glusterfs/indices/xattrop/xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>> >>> arbirternode: >>> >>> NOTHING >>> >>> As you requested I have tried to run on node1 a getfattr on the >>> fileKey file by using the following command: >>> >>> getfattr -m . -d -e hex fileKey >&...

...root root 4 Jul 29 12:15 . >>> 9 drw------- 5 root root 5 Apr 28 22:15 .. >>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>> 29e0d13e-1217-41cc-9bda-1fbbf781c397 >>> 2798404 ---------- 2 root root 0 Apr 28 22:51 >>> xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>> >>> >>> >>> I tried to find the real file on my brick where this xattrop file >>> points to using its inode number (command: find >>> /data/myvolume/brick/data -inum 8394642) but it does not find any >>> associated f...

...acenter and got a fancy IPv4 > subnet from my provider. I'm able to assign IPs from that subnet via > dhcp to my VMs: > > host01 ~ # virsh net-dumpxml internet > <network connections='3'> > <name>internet</name> > <uuid>37b888cc-510f-46f1-9246-346da96222ed</uuid> > <forward dev='enp5s0f0' mode='route'> > <interface dev='enp5s0f0'/> > </forward> > <bridge name='virbr1' stp='on' delay='0'/> > <mac address='52:54:00:13:39:d5'/...

...>> subnet from my provider. I'm able to assign IPs from that subnet via >> dhcp to my VMs: >> >> host01 ~ # virsh net-dumpxml internet >> <network connections='3'> >> <name>internet</name> >> <uuid>37b888cc-510f-46f1-9246-346da96222ed</uuid> >> <forward dev='enp5s0f0' mode='route'> >> <interface dev='enp5s0f0'/> >> </forward> >> <bridge name='virbr1' stp='on' delay='0'/> >> <mac address='52:...