Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: inn curious misbehavior

  1. #1
    jdd NNTP User

    Default inn curious misbehavior

    Hello,

    I don't know why it seems to be only me, but it looks like I have some problem with inn.

    In short, I have to reinstall inn each time I reboot my server!

    The only error I see in inn logs is:

    Code:
    cant bind /var/run/news/control No such file or directory
    and doing
    Code:
    zypper in --force inn
    fixes the problem.

    The Inn problem symptom is that nobody can connect to the inn server (connection refused).

    I already discussed similar problem in the openSUSE mailins list ([opensuse] inn problem) long time ago.

    I made a bad mistake two days ago (deleting my virtual server) and had to reinstall backups, so the coming of the problem. But in the past the problem did not appear again after it was fixed following the openSUSE list advices. Notice that after reinstalling backups I made a zypper dup so my system is up to date

    notice that not all the old bugs come again:

    Code:
    /usr/lib/news/bin/ctlinnd mode
    Server running
    Allowing remote connections
    Parameters c 10 i 50 (0) l 5000000 o 1011 t 300 H 2 T 60 X 0 normal specified
    Not reserved
    Readers follow enabled
    Perl filtering enabled
    my question is why reinstalling can fix a problem after a clean reboot?

    thanks
    jdd

  2. #2
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: inn curious misbehavior

    jdd wrote:
    > cant bind /var/run/news/control No such file or directory


    Without any knowledge about inn, /var/run is a tmpfs so it goes away with
    every reboot since it exists onyl in RAM as far as i understand. I can only
    guess that the reinstall recreates /var/run/news/control until your next
    reboot destroys it again.

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.5 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  3. #3
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: inn curious misbehavior

    Martin Helm wrote:

    > jdd wrote:
    >> cant bind /var/run/news/control No such file or directory

    >
    > Without any knowledge about inn, /var/run is a tmpfs so it goes away with
    > every reboot since it exists onyl in RAM as far as i understand. I can
    > only guess that the reinstall recreates /var/run/news/control until your
    > next reboot destroys it again.
    >

    Downloading the inn rpm and looking inside shows that the directory
    /var/run/news is installed by the rpm, it seems when inn starts it cannot
    create control since the directoy in which it lives does not exist.

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.5 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  4. #4
    jdd NNTP User

    Default Re: inn curious misbehavior

    great idea, but not the final answer. there is right now no /var/run/control folder in my server and the inn newsserver works as expected.

    that said I see a repeated error message (12 in a minute and still running):

    Code:
    Aug 26 19:05:45 savage-reborn innd: controlchan! exit 2 elapsed 0 pid 19239
    and more completely:

    Code:
    Aug 26 19:09:51 savage-reborn innd: controlchan! exit 2 elapsed 0 pid 25106
    Aug 26 19:09:51 savage-reborn innd: controlchan!:19:proc:25106 closed
    Aug 26 19:09:51 savage-reborn innd: controlchan! spawned controlchan!:19:proc:25108
    Aug 26 19:09:51 savage-reborn innd: controlchan! restarted
    the server is news.culte.org and free access so every body can use the test group

    thanks
    jdd

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,723

    Default Re: inn curious misbehavior

    Do we know already about which version of openSUSE all this talking is?
    Henk van Velden

  6. #6
    jdd NNTP User

    Default Re: inn curious misbehavior

    Quote Originally Posted by hcvv View Post
    Do we know already about which version of openSUSE all this talking is?
    with as many tempfs, it's 12.1 :-)

    jdd

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,723

    Default Re: inn curious misbehavior

    Yes, but you forgot to tell, then Martin made an intelligent guess without saying something like "if this is ... then ....".

    These threads are also to be understandable and by less clairvoyant people.
    Henk van Velden

  8. #8
    jdd NNTP User

    Default Re: inn curious misbehavior

    Quote Originally Posted by hcvv View Post
    Yes, but you forgot to tell, then Martin made an intelligent guess without saying something like "if this is ... then ....".

    These threads are also to be understandable and by less clairvoyant people.
    you are right. The guess was very clever (ands may be part of the solution) as /var/run *is* tmpfs. Simply don't seems to have been recreated by the new install.

    so your question was perfectly necessary

    thanks
    jdd

  9. #9
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: inn curious misbehavior

    hcvv wrote:
    > These threads are also to be understandable and by less clairvoyant
    > people.
    >

    Oh I am not clairvoyant either, from the discussion linked in the first post
    I see the OP uses systemd which shows the use of 12.x, but I also would be
    happier with a bit more system information given.

    @jdd:
    On the other way with the new error messages given I can anyway not help,
    since as I said I have no knowledge about inn itself.
    At least you should say what version of openSUSE, 32 or 64 bit, which
    version of inn and from which repo, if there was a recent update to the
    package compared to what worked on your previous server and if you use
    sysvinit or systemd and if you applied again what you discussed in your
    thread from march to solve the problem.
    And everything else which can help someone to help you.

    --
    PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
    ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.5 | HD 3000
    eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10

  10. #10
    jdd NNTP User

    Default Re: inn curious misbehavior

    yes...

    It's a 32 bits system, standard openSUSE repos

    Code:
    zypper lr
    # | Alias                  | Nom                        | Activé | Rafraîchir
    --+------------------------+----------------------------+--------+-----------
    1 | openSUSE-12.1-12.1-1.4 | openSUSE-12.1-12.1-1.4     | Oui    | Non       
    2 | repo-debug             | openSUSE-12.1-Debug        | Non    | Oui       
    3 | repo-debug-update      | openSUSE-12.1-Update-Debug | Non    | Oui       
    4 | repo-non-oss           | openSUSE-12.1-Non-Oss      | Oui    | Oui       
    5 | repo-oss               | openSUSE-12.1-Oss          | Oui    | Oui       
    6 | repo-source            | openSUSE-12.1-Source       | Non    | Oui       
    7 | repo-update            | openSUSE-12.1-Update       | Oui    | Oui
    virtual server under VirtualBox

    I made a zypper dup just after the restore, removed the spools for test and linux-31 then it worked. I had to do a powerdown to backup the virtual disk, and then restarted VirtualBox and the server. All started (apache, mailman...), even inn was started, but refused connections.

    zypper in --force inn fixed the install (it works). So the question is why did I have to reinstall to make it work. I can't restart a server too frequently and if it resart accidentally I would better like not to have to reinstall inn :-)

    thanks
    jdd

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •