search for: piperd

...408 408 0000100 [SLPQ select 0xffffffff80569bf0][SLP] httpd 5174 ffffff005fc7f9c0 1002 408 408 0000100 [SLPQ select 0xffffffff80569bf0][SLP] httpd 3168 ffffff0060afb340 1002 408 408 0000100 [SLPQ accept 0xffffff0060c632c6][SLP] httpd 1796 ffffff004ae0c680 1002 408 408 0000100 [SLPQ piperd 0xffffff005c9b2000][SLP] httpd 566 ffffff00606f59c0 0 1 566 0004002 [SLPQ ttyin 0xffffff00008fb010][SLP] getty 565 ffffff005fd0e9c0 0 1 565 0004002 [SLPQ ttyin 0xffffff00008b2c10][SLP] getty 564 ffffff005fb37340 0 1 564 0004002 [SLPQ ttyin 0xffffff00008f7010][SLP] g...

...run 'df', but I can't run 'df -t ufs', as that too just hangs ... According to ps axl, I have the following in WCHAN states: neptune# ps axl | awk '{print $9}' | sort | uniq -c 6 - 1 WCHAN 207 accept 103 inode 2 kqread 412 lockf 68 nanslp 8 pause 1 piperd 13 poll 3 psleep 58 sbwait 1 sched 626 select 1 syncer 3 ttyin 1 vlruwt 8 wait Thoughts? Does anything above look like its 'hanging' or 'locking' the file system? A few minutes later, there are a few variations: neptune# ps axl | awk '{print $9}' |...

...sleep nanosl 1:09 0.00% svscan 2496 www 2 0 996K 1608K sleep select 0:37 0.00% httpd 29202 root 2 0 728K 1036K sleep select 0:12 0.00% nmbd 10472 root 2 0 272K 220K idle select 0:12 0.00% cron 24271 nobody -6 0 72K 388K sleep piperd 0:10 0.00% unlinkd 28591 root 2 0 312K 520K idle select 0:08 0.00% sshd 17737 www 2 0 1032K 748K sleep netcon 0:06 0.00% httpd 31651 www 2 0 1032K 748K sleep netcon 0:05 0.00% httpd 27726 www 2 0 1032K 748K sleep netcon 0:05...

I'm running a few servers sitting on top of a NetAPP file server ? everything runs great, but periodically I'm getting: nfs_getpages: error 13 vm_fault: pager read error, pid 11355 (https) errors on my screen ? not always same pid ? the annoying part is that it seems to always affect the same jail that is running .. if I shutdown all jails on that physical server, everything shuts down

...ses is handled in Tcl and the C code only gets involved to write the data out (to an FD the Tcl layer keeps). The problem is that every now and then the process gets stuck and becomes unkillable just after forking, ie.. eureka:~>ps -axwwwwl | grep Reco 19999 881 1 12 -8 -5 21716 15984 piperd I<s ?? 128:50.79 /usr/home/radar/skiymet/libexec/Recorder /usr/home/radar/skiymet/libexec/acquisition/sks.tcl /usr/home/radar/skiymet/etc/ud3 19999 80154 881 12 92 -5 21716 16 user m D<L ?? 0:00.00 /usr/home/radar/skiymet/libexec/Recorder /usr/home/radar/skiymet/libexec/acquisi...

We have a reproducible problem with FreeBSD-4.7 which is apparently a deadlock. The system is undergoing a filesystem stress test. The machine is pingable, but console and most other features are unresponsive. The console debugger can be accessed. The following information is available with db's "ps". I suspect the wchan of "inode" to be what everything is waiting on.

I have a FreeBSD 4.8-Release machine that I upgraded from a 4.5 or 4.4 machine. It works just great for about 9 days, then processes will not die. It starts to become a problem when I can't kill processes, restart services, connections hang, and I can't reboot or shutdown, I have to do a hard reset. I can't really find anything in the logs to indicate what is giving me

...005 2 expireover 37656 e95bf0c0 e9abf000 8 37410 37407 000084 3 wait e95bf0c0 sh 37410 e95bd860 e9b40000 8 37407 37407 004084 3 wait e95bd860 sh 37407 e95bfdc0 e991f000 0 37403 37407 004084 3 wait e95bfdc0 sh 37403 e95bd520 e9b5e000 0 103 103 000084 3 piperd e9440540 cron 31158 e95bc680 e9ba8000 8 727 727 004085 2 overchan 31157 e95bcea0 e9b68000 8 727 727 004084 3 sbwait e554e888 perl 31156 e95c0ac0 e95e2000 8 727 727 004484 2 innfeed 30033 e95bc340 e9bc1000 8 30031 30031 004086 3 ttyin...