I recently made some changes to the rinetd configuration on the linux development server here. Everything seemed to work fine, but a few days later I noticed the follow wharrgarbl in my syslog:
Jul 27 14:28:11 easserv rinetd[14712]: accept(0): Socket operation on non-socket
Jul 27 14:28:42 easserv last message repeated 546042 times
Jul 27 14:29:43 easserv last message repeated 1077719 times
Jul 27 14:30:21 easserv last message repeated 680478 times
After searching around, it turns out I had made a typo in one of my rules. Instead of using the currentl 10.10.10.254 address, I had this new entry:
0.0.0.0 38254 10.10.10.255 80
So having an invalid IP address in those rules, causes rinetd to have a fit. Changing the 255 to a 254 and restarting rinetd solved my problem.
Tuesday, July 27, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment