Hi, On Sun, Jan 29, 2006 at 01:18:06AM -0500, Daniel Jacobowitz wrote: > Package: nbd-server > Version: 1:2.8.3-1 > Severity: important > > Jan 28 14:34:06 caradoc nbd_server[28890]: connect from 192.168.1.139, > assigned file is /space/chroot/mips-nbd.img > Jan 28 14:34:06 caradoc nbd_server[28890]: Can't open authorization file > (null) (Bad address). > Jan 28 14:34:06 caradoc nbd_server[28890]: Authorized client > Jan 28 14:34:06 caradoc nbd_server[14840]: Starting to serve > Jan 28 14:34:06 caradoc nbd_server[14840]: size of exported file/device is > 536870912 > Jan 28 14:42:21 caradoc nbd_server[14840]: Disconnect request received. > Jan 28 14:42:21 caradoc nbd_server[14840]: accept: Socket operation on > non-socket
Hmm. That shouldn't happen; this is the child process which was forked off to serve the client, which at that point should quit rather than try to run accept() on the server socket (nbd-server is written with fork-per-client semantics). Since that server socket has been closed at that point for the child, obviously we get an error. > Jan 28 14:42:27 caradoc last message repeated 230299 times ... and an infinite loop. Awtch. > Jan 28 14:42:27 caradoc mountd[10629]: authenticated unmount request from > bcm.them.org:1009 for /space (/space) > Jan 28 14:42:27 caradoc nbd_server[14840]: accept: Socket operation on > non-socket > Jan 28 14:42:58 caradoc last message repeated 1190456 times > Jan 28 14:43:59 caradoc last message repeated 2478818 times > Jan 28 14:45:00 caradoc last message repeated 2424694 times > Jan 28 14:46:01 caradoc last message repeated 2406191 times > > Then two nbd server processes somehow started fighting over syslog > (not sure why, the board that was powered on only uses one nbd > device). One would be the server which is listening to the socket we got from socket() and did bind() on; the other would be the child process that was forked off after the parent did accept() and which is spawned to handle a client. It would be interesting to know what message, exactly, the other process was sending out. Was this the same "Socket operation on non-socket" message, or did you see something else? -- .../ -/ ---/ .--./ / .--/ .-/ .../ -/ ../ -./ --./ / -.--/ ---/ ..-/ .-./ / -/ ../ --/ ./ / .--/ ../ -/ ..../ / -../ ./ -.-./ ---/ -../ ../ -./ --./ / --/ -.--/ / .../ ../ --./ -./ .-/ -/ ..-/ .-./ ./ .-.-.-/ / --/ ---/ .-./ .../ ./ / ../ .../ / ---/ ..-/ -/ -../ .-/ -/ ./ -../ / -/ ./ -.-./ ..../ -./ ---/ .-../ ---/ --./ -.--/ / .-/ -./ -.--/ .--/ .-/ -.--/ .-.-.-/ / ...-.-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
