FireFly Media Server › Firefly Media Server Forums › Firefly Media Server › Nightlies Feedback › Repeated crashes with "Out of pseudo file handles. See
- This topic has 7 replies, 3 voices, and was last updated 17 years, 1 month ago by dantidote.
-
AuthorPosts
-
21/10/2006 at 12:30 AM #701HorizonXGuest
I started using firefly about 3 weeks ago (Win32 nightlies on XP SP2) and have been getting the nightlies as they come out, and I’ve had a problem with this error for nearly the entire time I’ve been running the server. I think I’ve found the culprit by upping the debug level and looking at the logs — any user running the program “myTunes Redux” seems to open a MASSIVE amount of connections to my machine when copying a signfigant amount of music. I’m running svn-1400 atm, and the server has exited unexpectedly with “Out of pseudo file handles. See ya” 16 times already this week. >_< edit: I took a look at the traffic using a bw monitor… when I looked firefly had what looked like 100s(!) of sockets open to only 3 IPs! Is this a documented problem? :/ edit again: I discovered all the notices it puts in the event log at higher debug levels. Every single time, the error occurred after opening Socket #511. I guess something about trying to open socket #512 is what is causing it to crash. Could you code in a fix for this behaivor? I’m sure it’s due to sloppy coding in myTunes redux, but still… >_>
21/10/2006 at 7:04 PM #6943rpeddeParticipant@HorizonX wrote:
edit: I took a look at the traffic using a bw monitor… when I looked firefly had what looked like 100s(!) of sockets open to only 3 IPs! Is this a documented problem? :/
Not really… but yeah, there are only so many sockets it can have open. There must be something going on where the sockets aren’t getting closed.
edit again: I discovered all the notices it puts in the event log at higher debug levels. Every single time, the error occurred after opening Socket #511. I guess something about trying to open socket #512 is what is causing it to crash. Could you code in a fix for this behaivor? I’m sure it’s due to sloppy coding in myTunes redux, but still… >_>
Won’t fix it. The underlying problem is I’m not closing some sockets. Unless you have a *ton* of users connecting to this server. Is that the case? If so, I could crank up the socket limit, but I never figured there would be that many connections to the server simultaneously.
22/10/2006 at 1:41 AM #6944HorizonXGuestThere’s not a LOT of users (maybe 1-4 a time, something like 5-15 unique in a day), the main problem is that there can be in excess of 200 sockets open to a single IP. I don’t think increasing the socket limit would fix it, just delay the crash a little. I could get you any information on the problem you want since I’ll have the crash around every hour when someone uses myTunes redux to get music from my server, and somewhat infrequently otherwise. I set the service up to restart itself and the crash happened 16 times today >_>. I think the problem is something like when a client fails to open a proper connection, a socket is left open on my machine for some reason and it adds up since they never go away. :/
23/10/2006 at 2:58 AM #6945rpeddeParticipant@HorizonX wrote:
There’s not a LOT of users (maybe 1-4 a time, something like 5-15 unique in a day), the main problem is that there can be in excess of 200 sockets open to a single IP. I don’t think increasing the socket limit would fix it, just delay the crash a little. I could get you any information on the problem you want since I’ll have the crash around every hour when someone uses myTunes redux to get music from my server, and somewhat infrequently otherwise. I set the service up to restart itself and the crash happened 16 times today >_>. I think the problem is something like when a client fails to open a proper connection, a socket is left open on my machine for some reason and it adds up since they never go away. :/
Yeah. I’m just wondering what it is that mtunesredux is doing that differently than iTunes that I’m not closing the socket on my end.
I’ll look into it though — I have mytunesredux installed here somewhere.
— Ron
28/10/2006 at 5:33 AM #6946HorizonXGuestI got some info that might be useful out of this week’s logs (debug lvl 7)… it seems the following 2 messages are popping up a lot:
“Write error: An existing connection was forcibly closed by the remote host.”
and
“Thread xxx: could not read: An existing connection was forcibly closed by the remote host.”
I can also tell you that myTunes seems to be able to attempt connections VERY quickly so it wouldn’t surprise me if that had something to do with it. 😯
19/10/2007 at 5:01 AM #6947dantidoteParticipantWhatever this is, I’m getting it now too. All the sockets open at the same time. Weird. This happened all the way back on 1586 and is still a problem for me on the latest 1676.
2007-10-18 22:05:08 (688f3533): Socket 504 (1016): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 505 (1017): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 506 (1018): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 507 (1019): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 508 (1020): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 509 (1021): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 510 (1022): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 511 (1023): State Open/Listening
2007-10-18 22:05:08 (688f3533): Out of pseudo file handles. See ya
2007-10-18 22:05:08: Aborting20/10/2007 at 11:30 PM #6948rpeddeParticipant@dantidote wrote:
Whatever this is, I’m getting it now too. All the sockets open at the same time. Weird. This happened all the way back on 1586 and is still a problem for me on the latest 1676.
2007-10-18 22:05:08 (688f3533): Socket 504 (1016): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 505 (1017): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 506 (1018): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 507 (1019): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 508 (1020): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 509 (1021): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 510 (1022): State Open/Listening
2007-10-18 22:05:08 (688f3533): Socket 511 (1023): State Open/Listening
2007-10-18 22:05:08 (688f3533): Out of pseudo file handles. See ya
2007-10-18 22:05:08: AbortingWhaaa? Since > 1589, the pseudo handle thing isn’t used anymore. The code isn’t even in there.
Are you *sure* you are running a new version?
21/10/2007 at 12:51 AM #6949dantidoteParticipantwhoops, ha yep you’re right. I’ve been switching back and forth between the latest nightlies and 1586. forgot which one was installed.
-
AuthorPosts
- The forum ‘Nightlies Feedback’ is closed to new topics and replies.