search for: xids

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

Hello, I have a problem which is that some of my VMs are loosing there IP addresses from time to time. What I saw in the log is when this VM loose its IP address there are DHCPREQUEST send from the VM by dhclient and the server responded only 50 minutes later ! Any help, advise on how to debug would be welcome. Thanks in advance Patrick Here after is an extract from the log July 1st 2016,

The issue of I/O stopping may also be with glusterfsd not being properly killed before rebooting the server. For example in RHEL 7.4 with official Gluster 3.8.4, the glusterd service does *not* stop glusterfsd when you run systemctl stop glusterd So give this a try on the nose you wish to reboot: 1. Stop glusterd 2. Check if glusterfsd processes are still running. If they are, use: killall

Hi Diego, indeed glusterfsd processes are runnin and it is the reason I do server reboot instead of systemctl glusterd stop. Is killall different from reboot in a way glusterfsd processes are terminated in CentOS (init 1?)? However I will try this and let you know. -ps On Fri, Sep 8, 2017 at 12:19 PM, Diego Remolina <dijuremo at gmail.com> wrote: > The issue of I/O stopping may also

This is exactly the problem, Systemctl stop glusterd does *not* kill the brick processes. On CentOS with gluster 3.10.x there is also a service, meant to only stop glusterfsd (brick processes). I think the reboot process may not be properly stopping glusterfsd or network or firewall may be stopped before glusterfsd and so the nodes go into the long timeout. Once again , in my case a simple

If your VMs use ext4 also check this: https://joejulian.name/blog/keeping-your-vms-from-going- read-only-when-encountering-a-ping-timeout-in-glusterfs/ I asked him what to do for VMs using XFS and he said he could not find a fix (setting to change) for those. HTH, Diego On Sep 8, 2017 6:19 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: > The issue of I/O stopping may

This is the qemu log of instance: [2017-09-08 09:31:48.381077] C [rpc-clnt-ping.c:160:rpc_clnt_ping_timer_expired] 0-gv_openstack_1-client-1: server 10.0.1.202:49152 has not responded in the last 1 seconds, disconnecting. [2017-09-08 09:31:48.382411] E [rpc-clnt.c:365:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x13b)[0x7fbcadb09e8b] (-->

I think this should be considered a bug If you have a server crash, glusterfsd process obviously doesn't exit properly and thus this could least to IO stop ? And server crashes are the main reason to use a redundant filesystem like gluster Il 8 set 2017 12:43 PM, "Diego Remolina" <dijuremo at gmail.com> ha scritto: This is exactly the problem, Systemctl stop glusterd does

Oh, you really don't want to go below 30s, I was told. I'm using 30 seconds for the timeout, and indeed when a node goes down the VM freez for 30 seconds, but I've never seen them go read only for that. I _only_ use virtio though, maybe it's that. What are you using ? On Fri, Sep 08, 2017 at 11:41:13AM +0200, Pavel Szalbot wrote: > Back to replica 3 w/o arbiter. Two fio jobs

Hi, I got the same problem as Juergen, My volume is a simple replicated volume with 2 host and GlusterFS 3.2.0 Volume Name: poolsave Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: ylal2950:/soft/gluster-data Brick2: ylal2960:/soft/gluster-data Options Reconfigured: diagnostics.brick-log-level: DEBUG network.ping-timeout: 20 performance.cache-size: 512MB

...loaded kccsrv_partition[CN=Schema,CN=Configuration,DC=mymymy,DC=local] loaded kccsrv_partition[DC=DomainDnsZones,DC=mymymy,DC=local] loaded kccsrv_partition[DC=ForestDnsZones,DC=mymymy,DC=local] loaded Loading new DNS update grant rules /usr/local/samba/sbin/smbd: ldb_wrap open of idmap.ldb Out of xids to allocate. idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED /usr/local/samba/sbin/smbd: Out of xids to allocate. /usr/local/samba/sbin/smbd: idmapping sid_to_xid failed for id[0]=S-1-5-32-544: NT_STATUS_NONE_MAPPED /usr/local/samba/sbin/smbd: Out of xids to allocate. /us...

Hello, I'm having problems when write-behind is enabled on Gluster 3.8.4. I have 2 Gluster servers each with a single brick that is mirrored between them. The code causing these issues reads two data files each approx. 128G in size. It opens a third file, mmap()'s that file, and subsequently reads and writes to it. The third file, on sucessful runs (without write-behind enabled)

During the build (via a serial console) we get input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 running install... running /sbin/loader Sending request for IP information for eth0... Determining host name and domain... Sending request for IP information for eth0... Determining host name and domain... And there it hangs. On the 6.3 host: Feb 8 08:28:55 penfold dhcpd:

I'm currently struggeling with a cifs mount from a windows 2003 server. The share can be mounted with mount.cifs, but despite using the rw mount option, the mountpoint can only be accessed read-only. Trying to write on the share results in a permission denied error. This happens on a 2.4.21 kernel with the shipped CIFS kernel module. The mount command used is: mount.cifs

Hello, if ipconfig is run as ipconfig :::::: (i.e. long spec with all fields empty) and the computer has multiple network interfaces and only one of them is connected to dhcp managed network, ipconfig ends up in an infinite loop (see the log bellow). The following patch solved this for me. According to README, if the <device> in the long spec is empty, the first interface should be

Hi CentOS users, I have install CentOS 7 in VirtualBox, and want the guest CentOS using dynamic IP address (The network type is bridged). I find the guest CentOS can works OK when using ethernet cable, but can't get IP address via wireless network. I also posted this issue on stackoverflow

On 2019-02-25 at 11:32 +0000 Rowland Penny via samba sent off: > > (I take it xid stands for both uid and gid?) > > No, I think it was chosen to differentiate them from uidNumber & > gidNumber attributes, they are similar but not the same. They also only > exist on DC's in Windows the owner of a file can be a group. In the unix world the main owner is always a user.

This is on 32 bit x86 on a Dell 1950 After mouting a cifs share we have 5 second hiccups. Typical log output when doing a simple "ls /mnt": Sep 4 16:21:43 rd-spare kernel: fs/cifs/transport.c: For smb_command 50 Sep 4 16:21:43 rd-spare kernel: fs/cifs/transport.c: Sending smb: total_len 118 Sep 4 16:21:43 rd-spare kernel: fs/cifs/inode.c: CIFS VFS: leaving cifs_revalidate (xid =