search for: a733

...osts and /etc/resolv.conf . > > Send the output of "ping -c5 fs1" command from your machine? [gruss at ws1 ~]$ cat /etc/resolv.conf # Generated by NetworkManager domain tss-engineering.com search tss-engineering.com tss-engineering.com. nameserver 192.168.1.1 nameserver fd78:beb4:a733::1 [gruss at ws1 ~]$ cat /etc/hosts 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 [gruss at ws1 ~]$ ping -c5 fs1 PING fs1.tss-engineering.com (192.168.1.10) 56(84) bytes of data. 64 bytes from FS1.tss-engineering.com (192.168.1.10): icmp_seq=1 ttl=64 time=0.4...

I'm guessing there's something wrong w.r.t address resolution on node 1. >From the logs it's quite clear to me that node 1 is unable to resolve the address configured in /etc/hosts where as the other nodes do. Could you paste the gluster peer status output from all the nodes? Also can you please check if you're able to ping "pri.ostechnix.lan" from node1 only? Does

I have encountered a need for float-to-int casts that saturate to min/max when the value is out of the range of the target type. It seems that there is no intrinsic to do this, currently, but on IRC it was pointed out that a patch [1] has been proposed to implement this functionality in exactly the way that I was looking for. It looks like the discussion has died out but I was hoping maybe to

...the output of "ping -c5 fs1" command from your machine? >> > > [gruss at ws1 ~]$ cat /etc/resolv.conf > # Generated by NetworkManager > domain tss-engineering.com > search tss-engineering.com tss-engineering.com. > nameserver 192.168.1.1 > nameserver fd78:beb4:a733::1 > > [gruss at ws1 ~]$ cat /etc/hosts > 127.0.0.1 localhost.localdomain localhost > ::1 localhost6.localdomain6 localhost6 > > [gruss at ws1 ~]$ ping -c5 fs1 > PING fs1.tss-engineering.com (192.168.1.10) 56(84) bytes of data. > 64 bytes from FS1.t...

Hello, i installed glusterfs 3.11.3 version 3 nodes ubuntu 16.04 machine. All machines have same /etc/hosts. node1 hostname pri.ostechnix.lan node2 hostname sec.ostechnix.lan node2 hostname third.ostechnix.lan 51.15.77.14 pri.ostechnix.lan pri 51.15.90.60 sec.ostechnix.lan sec 163.172.151.120 third.ostechnix.lan third volume create command is root at

...ek-laptop _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs IN SRV 0 100 3268 przemek-laptop ; ; ldap servers _ldap._tcp IN SRV 0 100 389 przemek-laptop _ldap._tcp.dc._msdcs IN SRV 0 100 389 przemek-laptop _ldap._tcp.pdc._msdcs IN SRV 0 100 389 przemek-laptop _ldap._tcp.90715785-ce5d-4420-a733-9c8e1c828cc8.domains._msdcs IN SRV 0 100 389 przemek-laptop _ldap._tcp.Default-First-Site-Name._sites IN SRV 0 100 389 przemek-laptop _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs IN SRV 0 100 389 przemek-laptop ; ; krb5 servers _kerberos._tcp IN SRV 0 100 88 przemek-laptop _kerberos....

Hi All, I've configured a Fedora 20 server with samba to share a few user directories and a printer. From a Windows 8 laptop, I am able to address the samba server by it's name (fs1) From a Fedora 20 client (ws1), I am able to address the samba server by IP address, but not by name. [gruss at ws1 ~]$ smbclient --version Version 4.1.15 [gruss at ws1 ~]$ smbclient -L 192.168.1.10

As soon as the application starts, a window pops up that (normally under windows) would say "this is a trial version demo, click okay to start the trial", or something along those lines. The window is blank and clicking randomly on it (to find the "ok") does not work either. The following output from wine during this test is as follows : err:iphlpapi:getRouteTable Received