Bug 652116 - inadyn-mt: missing file /etc/rc.d/init.d/inadyn
Summary: inadyn-mt: missing file /etc/rc.d/init.d/inadyn
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: inadyn-mt
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Jochen Schmitt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 627108 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 02:24 UTC by Tim Taiwanese Liim
Modified: 2010-12-06 03:41 UTC (History)
2 users (show)

Fixed In Version: inadyn-mt-2.18.50-2.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-17 17:01:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tim Taiwanese Liim 2010-11-11 02:24:30 UTC
Description of problem:
    The file /etc/rc.d/init.d/inadyn does not exist, causing inadyn not to
    start at boot time.

Version-Release number of selected component (if applicable):
    inadyn-mt-2.18.36-1.fc14.i686

How reproducible:
    always

Steps to Reproduce:
    1. install inadyn-mt-2.18.36-1.fc14.i686
    2. use system-config-services to enable inadyn.
    3. ls -l /etc/rc.d/rc5.d/S55inadyn /etc/rc.d/init.d/inadyn

Actual results:
    [root@iyam ~]# ls -l /etc/rc.d/rc5.d/S55inadyn /etc/rc.d/init.d/inadyn
    ls: cannot access /etc/rc.d/init.d/inadyn: No such file or directory
    lrwxrwxrwx. 1 root root 16 Nov  9 00:36 /etc/rc.d/rc5.d/S55inadyn -> 
        ../init.d/inadyn

Expected results:
    /etc/rc.d/init.d/inadyn should be in the rpm file, and inadyn should
    be started after reboot.

Additional info:
    Said file exists in inadyn-mt-2.12.24-2.fc11.i586.

Comment 1 Fedora Update System 2010-11-15 20:04:46 UTC
inadyn-mt-2.18.50-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/inadyn-mt-2.18.50-2.fc14

Comment 2 Tim Taiwanese Liim 2010-11-15 20:37:52 UTC
Jochen,
Appreciate your fast action!  I downloaded these 3 rpms:
    inadyn-mt-2.18.50-2.fc14.i686.rpm
    inadyn-mt-sysvinit-2.18.50-2.fc14.noarch.rpm
    inadyn-mt-units-2.18.50-2.fc14.noarch.rpm
Then tried to install them:
    [root@taiwan Downloads]# rpm -U inadyn-mt-*
Got this msg:
    /var/tmp/rpm-tmp.P2kMMK: line 1: [: missing `]'
Is it safe to ignore this msg?  Thanks.

Comment 3 Fedora Update System 2010-11-16 23:18:19 UTC
inadyn-mt-2.18.50-2.fc14 has been pushed to the Fedora 14 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 inadyn-mt'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/inadyn-mt-2.18.50-2.fc14

Comment 4 Tim Taiwanese Liim 2010-11-17 17:01:14 UTC
Found where the scriptlet error came from.  As part of the rpm -U
upgrade, the old inadyn-mt-units would be uninstalled, which
generated said error.
    [root@taiwan ~]# rpm -qa | grep inadyn
    inadyn-mt-2.18.50-2.fc14.x86_64
    inadyn-mt-sysvinit-2.18.50-2.fc14.noarch
    inadyn-mt-units-2.18.50-2.fc14.noarch
    [root@taiwan ~]# rpm -e inadyn-mt-units.noarch
    /var/tmp/rpm-tmp.3cMnuH: line 1: [: missing `]'

As far as this current bug is concerned, the issue is fixed, so I
will close this bug.  Again, thank you for your fast action and
effort.

There seems to be some issue with inadyn not closing files,
though.  After running 1 hour or so, inadyn has >200 file handles
left open, all to the same set of destinations (xxx.dyndns.com).
I will open a separate bug to track this issue.
    lsof -p $(pgrep -f inadyn)
    COMMAND  FD   TYPE NAME
    inadyn  216u  IPv4 qyam:44262->checkip-ewr.dyndns.com:http (ESTABLISHED)
    inadyn  217u  IPv4 qyam:56505->checkip-ams.dyndns.com:http (CLOSE_WAIT)
    inadyn  218u  IPv4 qyam:57066->checkip-ams.dyndns.com:http (ESTABLISHED)
    inadyn  219u  IPv4 qyam:43419->checkip-pao.dyndns.com:http (ESTABLISHED)
    inadyn  220u  IPv4 qyam:56509->checkip-ams.dyndns.com:http (ESTABLISHED)

Comment 5 Fedora Update System 2010-11-24 22:39:19 UTC
inadyn-mt-2.18.50-2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Bryan Hoover 2010-11-29 21:46:19 UTC
*** Bug 627108 has been marked as a duplicate of this bug. ***

Comment 7 Bryan Hoover 2010-11-29 21:50:06 UTC
(In reply to comment #4)
> Found where the scriptlet error came from.  As part of the rpm -U
> upgrade, the old inadyn-mt-units would be uninstalled, which
> generated said error.
>     [root@taiwan ~]# rpm -qa | grep inadyn
>     inadyn-mt-2.18.50-2.fc14.x86_64
>     inadyn-mt-sysvinit-2.18.50-2.fc14.noarch
>     inadyn-mt-units-2.18.50-2.fc14.noarch
>     [root@taiwan ~]# rpm -e inadyn-mt-units.noarch
>     /var/tmp/rpm-tmp.3cMnuH: line 1: [: missing `]'
> 
> As far as this current bug is concerned, the issue is fixed, so I
> will close this bug.  Again, thank you for your fast action and
> effort.
> 
> There seems to be some issue with inadyn not closing files,
> though.  After running 1 hour or so, inadyn has >200 file handles
> left open, all to the same set of destinations (xxx.dyndns.com).
> I will open a separate bug to track this issue.
>     lsof -p $(pgrep -f inadyn)
>     COMMAND  FD   TYPE NAME
>     inadyn  216u  IPv4 qyam:44262->checkip-ewr.dyndns.com:http (ESTABLISHED)
>     inadyn  217u  IPv4 qyam:56505->checkip-ams.dyndns.com:http (CLOSE_WAIT)
>     inadyn  218u  IPv4 qyam:57066->checkip-ams.dyndns.com:http (ESTABLISHED)
>     inadyn  219u  IPv4 qyam:43419->checkip-pao.dyndns.com:http (ESTABLISHED)
>     inadyn  220u  IPv4 qyam:56509->checkip-ams.dyndns.com:http (ESTABLISHED)

This (files leak) is fixed in present version (upstream), 02.20.38.

Comment 8 Tim Taiwanese Liim 2010-12-03 17:06:46 UTC
Great!  I don't need to open a separate bug for this issue (files
leak) then.  Any estimate when we will have this fix in F14?
Thanks!

Comment 9 Tim Taiwanese Liim 2010-12-06 03:41:53 UTC
I opened 
   bug660203 inadyn file leak (>200 fd in 1 hour)
to keep track the file leak issue in Comment #4.


Note You need to log in before you can comment on or make changes to this bug.