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:
/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?
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
> 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
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.
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
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
On 2012-08-26 19:16, jdd wrote:
>
> 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.
All the same, you should create a script somewhere that creates the directory on every boot before
inn is started. And then report the issue in bugzilla. I’m not fluent with systemd to tell you how.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
On 2012-08-31 13:46, jdd wrote:
>
> thanks Carlos
>
> But in fact this folder problem do not seems to be related to the main
> problem I have. So it may be unnecessary to report it.
>
> The problem is seemingly permanent - I had to recover my server from
> backups and get the same thing anytime I have to reboot:
>
> * at reboot the inn server is launched but do not accept connections
> * “zypper in --force inn” and the server works
You said that the installation creates that directory, perhaps more. You have to instead create
those directories manually or create a service script that creates those directories on every boot.
This is something YOU have to do.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
no, I didn’t say so. I said that an error message complained this directory being non existent. It’s an other anwswer that said that thr rpm was creating the folder.
by the way I have to work on this. If I found someting more, I will report
> as a reminder the error message is in “news.crit”:
>
> Code:
> --------------------
>
> Aug 29 17:47:32 savage-reborn innd: SERVER cant bind /var/run/news/control No such file or directory
>
>
> --------------------
Why don’t you simply create THAT directory in the error message? /var/run/news? It is complaining
about it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))
That is also what I think and what I hoped to make clear (maybe not clear enough) from the very beginning.
Looking at the spec file’s post install step
It creates not only the directory but also a lot of files in it.
And since that package is delievered by the oss repository and seems not to work out of the box, the OP should file a bug report and I wonder if that has not been done since the first discussion from jdd on the mailing list dates back to March.
