Re: Syncache problem in FreeBSD 7.3-PRERELEASE
On 05/07/10 07:40, Zhenkai Zhu wrote: Hi, I'm experiencing some problem of syncache (probably). We have a NFS server which exports everyone's home directory, and I'm developing my Qualnet code on another machine (NFS client) under my home directory. However, when I make my code, linking takes extremely long time (it takes more than 5 minutes while on my laptop it only takes 15 seconds). I examed the /var/log/messages on the NFS server and it was like this: May 6 19:51:49 raptors kernel: TCP: [131.179.96.24]:985 to [131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) The above message appears every time I make my code ( and only when I make my code). I turned on linux binary compatiblity on the NFS client because Qualnet needs to be run in that mode. Here are some more details: both the NFS server and client are amd64 machines. The server has 8 cpus and the client has 16 cpus. Any one can help me out? Thanks!!! What does your net.inet.tcp.syncache.count show? Actually, sending the output of sysctl net.inet.tcp | grep syn would probably help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Syncache problem in FreeBSD 7.3-PRERELEASE
Hi,
I'm experiencing some problem of syncache (probably).
We have a NFS server which exports everyone's home directory, and I'm
developing my Qualnet code on another machine (NFS client) under my home
directory. However, when I make my code, linking takes extremely long
time (it takes more than 5 minutes while on my laptop it only takes 15
seconds). I examed the /var/log/messages on the NFS server and it was
like this:
May 6 19:51:49 raptors kernel: TCP: [131.179.96.24]:985 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
The above message appears every time I make my code ( and only when I
make my code). I turned on linux binary compatiblity on the NFS client
because Qualnet needs to be run in that mode.
Here are some more details: both the NFS server and client are amd64
machines. The server has 8 cpus and the client has 16 cpus.
Any one can help me out? Thanks!!!
Zhenkai
For detail info for the NFS server is as following:
kern.ostype: FreeBSD
kern.osrelease: 7.3-PRERELEASE
kern.osrevision: 199506
kern.version: FreeBSD 7.3-PRERELEASE #0: Tue Feb 9 12:59:50 PST 2010
r...@raptors.cs.ucla.edu:/usr/obj/usr/src/sys/RAPTORS
kern.maxvnodes: 10
kern.maxproc: 6164
kern.maxfiles: 12328
kern.argmax: 262144
kern.securelevel: 2
kern.hostname: raptors.cs.ucla.edu
kern.hostid: 2180312168
kern.clockrate: { hz = 1000, tick = 1000, profhz = 2000, stathz = 133 }
kern.posix1version: 200112
kern.ngroups: 16
kern.job_control: 1
kern.saved_ids: 0
kern.boottime: { sec = 1267039765, usec = 441091 } Wed Feb 24 11:29:25 2010
kern.domainname: uclairlnew
kern.osreldate: 702106
kern.bootfile: /boot/kernel/kernel
kern.maxfilesperproc: 11095
"~/info" 2185L, 121063C
kern.bootfile: /boot/kernel/kernel
kern.maxfilesperproc: 11095
kern.maxprocperuid: 5547
kern.ipc.maxsockbuf: 262144
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.somaxconn: 128
kern.ipc.max_linkhdr: 16
kern.ipc.max_protohdr: 60
kern.ipc.max_hdr: 76
kern.ipc.max_datalen: 100
kern.ipc.nmbjumbo16: 3200
kern.ipc.nmbjumbo9: 6400
kern.ipc.nmbjumbop: 12800
kern.ipc.nmbclusters: 25600
kern.ipc.piperesizeallowed: 1
kern.ipc.piperesizefail: 0
kern.ipc.pipeallocfail: 0
kern.ipc.pipefragretry: 0
kern.ipc.pipekva: 16384
kern.ipc.maxpipekva: 103321600
kern.ipc.msgseg: 2048
kern.ipc.msgssz: 8
kern.ipc.msgtql: 40
kern.ipc.msgssz: 8
kern.ipc.msgtql: 40
kern.ipc.msgmnb: 2048
kern.ipc.msgmni: 40
kern.ipc.msgmax: 16384
kern.ipc.semaem: 16384
kern.ipc.semvmx: 32767
kern.ipc.semusz: 152
kern.ipc.semume: 10
kern.ipc.semopm: 100
kern.ipc.semmsl: 60
kern.ipc.semmnu: 30
kern.ipc.semmns: 60
kern.ipc.semmni: 10
kern.ipc.semmap: 30
kern.ipc.shm_allow_removed: 0
kern.ipc.shm_use_phys: 0
kern.ipc.shmall: 8192
kern.ipc.shmseg: 128
kern.ipc.shmmni: 192
kern.ipc.shmmin: 1
kern.ipc.shmmax: 33554432
kern.ipc.maxsockets: 25600
kern.ipc.shmmax: 33554432
kern.ipc.maxsockets: 25600
kern.ipc.numopensockets: 74
kern.ipc.nsfbufsused: 0
kern.ipc.nsfbufspeak: 0
kern.ipc.nsfbufs: 0
kern.dummy: 0
kern.ps_strings: 140737488355296
kern.usrstack: 140737488355328
kern.logsigexit: 1
kern.iov_max: 1024
kern.hostuuid: 00020003-0004-0005-0006-000700080009
kern.cam.cam_srch_hi: 0
kern.cam.scsi_delay: 5000
kern.cam.cd.retry_count: 4
kern.cam.cd.changer.max_busy_seconds: 15
kern.cam.cd.changer.min_busy_seconds: 5
kern.cam.da.da_send_ordered: 1
kern.cam.da.default_timeout: 60
kern.cam.da.retry_count: 4
kern.cam.da.0.minimum_cmd_size: 6
kern.cam.da.1.minimum_cmd_size: 6
kern.cam.da.2.minimum_cmd_size: 6
kern.cam.da.1.minimum_cmd_size: 6
kern.cam.da.2.minimum_cmd_size: 6
kern.cam.da.3.minimum_cmd_size: 6
kern.cam.da.4.minimum_cmd_size: 6
kern.cam.da.5.minimum_cmd_size: 6
kern.cam.da.6.minimum_cmd_size: 6
kern.cam.da.7.minimum_cmd_size: 6
kern.cam.da.8.minimum_cmd_size: 6
kern.cam.da.9.minimum_cmd_size: 6
kern.cam.da.10.minimum_cmd_size: 6
kern.cam.da.11.minimum_cmd_size: 6
kern.dcons.poll_hz: 100
kern.disks: da11 da10 da9 da8 da7 da6 da5 da4 da3 da2 da1 da0
kern.geom.collectstats: 1
kern.geom.debugflags: 0
kern.geom.label.debug: 0
kern.elf64.fallback_brand: -1
kern.init_shutdown_timeout: 120
kern.init_path:
/sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall
kern.acct_suspended: 0
kern.acct_configured: 0
kern.acct_chkfreq: 15
kern.acct_configured: 0
kern.acct_chkfreq: 15
kern.acct_resume: 4
kern.acct_suspend: 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Syncache problem in FreeBSD 7.3-PRERELEASE
Sorry for the spam. A correction: the message does NOT only appear when
I make my code. I copied several here:
May 6 21:50:06 raptors kernel: TCP: [131.179.96.24]:660 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
May 6 21:59:00 raptors ntpd[876]: kernel time sync status change 6001
May 6 22:06:48 raptors kernel: TCP: [131.179.96.24]:669 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
May 6 22:10:26 raptors kernel: TCP: [131.179.96.24]:743 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
May 6 22:11:48 raptors kernel: TCP: [131.179.96.24]:611 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
May 6 22:26:03 raptors kernel: TCP: [131.179.96.24]:665 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
May 6 22:35:46 raptors kernel: TCP: [131.179.96.24]:708 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment failed
SYNCOOKIE authentication, segment rejected (probably spoofed)
Zhenkai
On 05/06/2010 10:40 PM, Zhenkai Zhu wrote:
Hi,
I'm experiencing some problem of syncache (probably).
We have a NFS server which exports everyone's home directory, and I'm
developing my Qualnet code on another machine (NFS client) under my
home directory. However, when I make my code, linking takes extremely
long time (it takes more than 5 minutes while on my laptop it only
takes 15 seconds). I examed the /var/log/messages on the NFS server
and it was like this:
May 6 19:51:49 raptors kernel: TCP: [131.179.96.24]:985 to
[131.179.96.25]:2049 tcpflags 0x10; syncache_expand: Segment
failed SYNCOOKIE authentication, segment rejected (probably spoofed)
The above message appears every time I make my code ( and only when I
make my code). I turned on linux binary compatiblity on the NFS client
because Qualnet needs to be run in that mode.
Here are some more details: both the NFS server and client are amd64
machines. The server has 8 cpus and the client has 16 cpus.
Any one can help me out? Thanks!!!
Zhenkai
For detail info for the NFS server is as following:
kern.ostype: FreeBSD
kern.osrelease: 7.3-PRERELEASE
kern.osrevision: 199506
kern.version: FreeBSD 7.3-PRERELEASE #0: Tue Feb 9 12:59:50 PST 2010
r...@raptors.cs.ucla.edu:/usr/obj/usr/src/sys/RAPTORS
kern.maxvnodes: 10
kern.maxproc: 6164
kern.maxfiles: 12328
kern.argmax: 262144
kern.securelevel: 2
kern.hostname: raptors.cs.ucla.edu
kern.hostid: 2180312168
kern.clockrate: { hz = 1000, tick = 1000, profhz = 2000, stathz = 133 }
kern.posix1version: 200112
kern.ngroups: 16
kern.job_control: 1
kern.saved_ids: 0
kern.boottime: { sec = 1267039765, usec = 441091 } Wed Feb 24 11:29:25
2010
kern.domainname: uclairlnew
kern.osreldate: 702106
kern.bootfile: /boot/kernel/kernel
kern.maxfilesperproc: 11095
"~/info" 2185L, 121063C
kern.bootfile: /boot/kernel/kernel
kern.maxfilesperproc: 11095
kern.maxprocperuid: 5547
kern.ipc.maxsockbuf: 262144
kern.ipc.sockbuf_waste_factor: 8
kern.ipc.somaxconn: 128
kern.ipc.max_linkhdr: 16
kern.ipc.max_protohdr: 60
kern.ipc.max_hdr: 76
kern.ipc.max_datalen: 100
kern.ipc.nmbjumbo16: 3200
kern.ipc.nmbjumbo9: 6400
kern.ipc.nmbjumbop: 12800
kern.ipc.nmbclusters: 25600
kern.ipc.piperesizeallowed: 1
kern.ipc.piperesizefail: 0
kern.ipc.pipeallocfail: 0
kern.ipc.pipefragretry: 0
kern.ipc.pipekva: 16384
kern.ipc.maxpipekva: 103321600
kern.ipc.msgseg: 2048
kern.ipc.msgssz: 8
kern.ipc.msgtql: 40
kern.ipc.msgssz: 8
kern.ipc.msgtql: 40
kern.ipc.msgmnb: 2048
kern.ipc.msgmni: 40
kern.ipc.msgmax: 16384
kern.ipc.semaem: 16384
kern.ipc.semvmx: 32767
kern.ipc.semusz: 152
kern.ipc.semume: 10
kern.ipc.semopm: 100
kern.ipc.semmsl: 60
kern.ipc.semmnu: 30
kern.ipc.semmns: 60
kern.ipc.semmni: 10
kern.ipc.semmap: 30
kern.ipc.shm_allow_removed: 0
kern.ipc.shm_use_phys: 0
kern.ipc.shmall: 8192
kern.ipc.shmseg: 128
kern.ipc.shmmni: 192
kern.ipc.shmmin: 1
kern.ipc.shmmax: 33554432
kern.ipc.maxsockets: 25600
kern.ipc.shmmax: 33554432
kern.ipc.maxsockets: 25600
kern.ipc.numopensockets: 74
kern.ipc.nsfbufsused: 0
kern.ipc.nsfbufspeak: 0
kern.ipc.nsfbufs: 0
kern.dummy: 0
kern.ps_strings: 140737488355296
kern.usrstack: 140737488355328
kern.logsigexit: 1
kern.iov_max: 1024
kern.hostuuid: 00020003-0004-0005-0006-000700080009
kern.cam.cam_srch_hi: 0
kern.cam.scsi_delay: 5000
kern.cam.cd.retry_count: 4
kern.cam.cd.changer.max_busy_seconds: 15
kern.cam.cd.changer.min_busy_seconds: 5
kern.cam.da.da_send_ordered: 1
kern.cam.da.default_timeout: 60
kern.cam.da.retry_count: 4
kern.cam.da.0.minimum_cmd_size: 6
kern.cam.da.1.minimum_cmd_size: 6
kern.cam.da.2.minimum_cmd_size: 6
kern.cam.da.1.minimum_cmd_size: 6
kern.cam.da
