similar to: Apple cannot connect to RHLinux Samba

I am sharing out ZFS ISCSI luns to my Mac. When copying large files, the network will hang in the middle of the transfer and the LUN will become unavailable until I plumb the NIC. This issue appears to only occur only when I am reading files (ie..syncing an ipod) and not writing (I''m not 100% sure though). When I snoop the interface I notice a bunch of ARP lookups. Any ideas? Thanks in

Hi, I have problems installing RMySQL under R1.8.1 and RHlinux (kernel2.4.7). During compilation I get: ** libs gcc -I/usr/lib/R/include -I/usr/include/mysql -I/usr/local/include -D__NO_MATH_INLINES -mieee-fp -fPIC -O2 -m486 -fno-strength-reduce -g -c RS-DBI.c -o RS-DBI.o gcc -I/usr/lib/R/include -I/usr/include/mysql -I/usr/local/include -D__NO_MATH_INLINES -mieee-fp -fPIC -O2 -m486

Todd, I experienced a similar problem. I know it sounds trivial... I used the version of Samba that came with the install CD of RHLinux 7.3, and got it running well. Then I read about the bugs and so I upgraded to Samba 2.2.8a. Afterwards, whenever I would make any changes to /etc/samba/smb.conf, I would not see any difference in Samba's behavior. Then I ran testparm and I noticed

I have been chasing a reliability problem that seems to boil down to this: sshd needs a certain amount of time delay between opening a forwarded connection and receiving the first data packet for the connection. Otherwise it never forwards the data. Anyone heard of such a thing, or have an idea where to look for the problem? I see a possibly-related bug report in the archives:

root ~ # ip route ls default 10.0.9.200 dev eth1 scope link 10.0.1.200 dev eth2 scope link 10.0.3.200 dev eth4 scope link 10.0.2.200 dev eth3 scope link default dev eth3 scope link root ~ # ip route ls table http default equalize nexthop dev eth1 weight 1 nexthop dev eth2 weight 1 root ~ # ip route ls table ssh default equalize nexthop dev eth1 weight 1

Hi. I''m migrating to shorewall(6) mgmt of my various firewalls. Simple configs have been easy with the great docs. I''ve got a slightly more convoluted config, and have gotten ''lost'' in config''ing a SNAT/DNAT/NAT + DMZ + Xen Host/Guest set up with Static IP/29. Having some challenges wrapping my head around the ''best'' Shorewall

https://bugzilla.mindrot.org/show_bug.cgi?id=1904 Summary: sshd refuses certificate-based authentication if password has expired Product: Portable OpenSSH Version: 4.3p2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

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

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

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] (-->

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

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

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'm new to R and would like to know, how one can populate the list with array data. I'm reading a tab separated table in R. The data in the table looks something like this. #Table Data Comp    A    B    C Extracellular    103    268    535759 Nucleus    45603    47783    442744 #R code myData <- read.table("table.data",                 header=T,