Description of problem: I ran system-config-services and my messages log filled with about 4GB of this: Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set Mar 15 13:44:45 arturo xinetd[1689]: 1 descriptors still set system-config-services-0.99.42-1.fc12.noarch
This is xinetd spamming the log file, not system-config-services. Changing the component accordingly.
Could you please post here what version of xinetd are you using? Also config files of active services would be useful. And of course, some steps to reproduce the issue would be welcomed. You just ran system-config-services, with no other activity? And how long before the log was this big?
I am using xinetd-2.3.14-29.fc12.x86_64 I managed to reproduce this. I started up system-config-services, then chose a service that runs from xinetd, in this case daytime-dgram. It doesn't matter which I choose. I enabled it, then disabled it, and after that the messages file had grown from 213436 bytes to 207013412, all full with this same message.
Created attachment 400844 [details] xinetd configuration files
..And xinetd continues to spam the log file after system-config-services is closed... Once it gets going it doesn't stop until I restart xinetd. Here's where it starts: Mar 17 14:03:28 arturo xinetd[1646]: Starting reconfiguration Mar 17 14:03:28 arturo xinetd[1646]: Swapping defaults Mar 17 14:03:28 arturo xinetd[1646]: readjusting service ntalk Mar 17 14:03:28 arturo xinetd[1646]: readjusting service shell Mar 17 14:03:28 arturo xinetd[1646]: readjusting service rsync Mar 17 14:03:28 arturo xinetd[1646]: readjusting service sagewake Mar 17 14:03:28 arturo xinetd[1646]: readjusting service talk Mar 17 14:03:28 arturo xinetd[1646]: readjusting service telnet Mar 17 14:03:28 arturo xinetd[1646]: readjusting service tftp Mar 17 14:03:28 arturo xinetd[1646]: readjusting service time-dgram Mar 17 14:03:28 arturo xinetd[1646]: readjusting service time-stream Mar 17 14:03:28 arturo xinetd[1646]: readjusting service uucp Mar 17 14:03:28 arturo xinetd[1646]: Reconfigured: new=0 old=10 dropped=0 (services) Mar 17 14:03:28 arturo xinetd[1646]: Starting reconfiguration Mar 17 14:03:28 arturo xinetd[1646]: Swapping defaults Mar 17 14:03:28 arturo xinetd[1646]: readjusting service ntalk Mar 17 14:03:28 arturo xinetd[1646]: readjusting service shell Mar 17 14:03:28 arturo xinetd[1646]: readjusting service rsync Mar 17 14:03:28 arturo xinetd[1646]: readjusting service sagewake Mar 17 14:03:28 arturo xinetd[1646]: readjusting service talk Mar 17 14:03:28 arturo xinetd[1646]: readjusting service telnet Mar 17 14:03:28 arturo xinetd[1646]: readjusting service tftp Mar 17 14:03:28 arturo xinetd[1646]: readjusting service time-dgram Mar 17 14:03:28 arturo xinetd[1646]: readjusting service time-stream Mar 17 14:03:28 arturo xinetd[1646]: readjusting service uucp Mar 17 14:03:28 arturo xinetd[1646]: Reconfigured: new=0 old=10 dropped=0 (services) Mar 17 14:03:28 arturo xinetd[1646]: Starting reconfiguration Mar 17 14:03:28 arturo xinetd[1646]: Swapping defaults Mar 17 14:03:28 arturo xinetd[1646]: readjusting service ntalk Mar 17 14:03:28 arturo xinetd[1646]: readjusting service shell Mar 17 14:03:28 arturo xinetd[1646]: readjusting service rsync Mar 17 14:03:28 arturo xinetd[1646]: readjusting service sagewake Mar 17 14:03:28 arturo xinetd[1646]: readjusting service talk Mar 17 14:03:28 arturo xinetd[1646]: readjusting service telnet Mar 17 14:03:28 arturo xinetd[1646]: readjusting service tftp Mar 17 14:03:28 arturo xinetd[1646]: readjusting service time-dgram Mar 17 14:03:28 arturo xinetd[1646]: readjusting service time-stream Mar 17 14:03:28 arturo xinetd[1646]: readjusting service uucp Mar 17 14:03:28 arturo xinetd[1646]: Reconfigured: new=0 old=10 dropped=0 (services) ... Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set Mar 17 14:06:53 arturo xinetd[1646]: 1 descriptors still set ...
Thanks for the information. I'm working on it. One more thing - could you please try to install an older version of xinetd (link is below) and try to reproduce the issue? This was the last version before some major changes in xinetd, which might have brought a regression, so I'd like to check it. http://koji.fedoraproject.org/koji/buildinfo?buildID=124215
I installed the older version and the problem went away.
There is a new build of the package. In my tests it seems to fix this issue. Can you please confirm? http://koji.fedoraproject.org/koji/taskinfo?taskID=2061425
(In reply to comment #8) > There is a new build of the package. In my tests it seems to fix this issue. > Can you please confirm? > > http://koji.fedoraproject.org/koji/taskinfo?taskID=2061425 Confirmed, looks good here.
xinetd-2.3.14-30.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/xinetd-2.3.14-30.fc12
xinetd-2.3.14-30.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/xinetd-2.3.14-30.fc13
xinetd-2.3.14-30.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xinetd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/xinetd-2.3.14-30.fc12
xinetd-2.3.14-30.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xinetd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/xinetd-2.3.14-30.fc13
xinetd-2.3.14-30.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
xinetd-2.3.14-30.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.