Hi admins,

I apologize to all administrators for the chaotic server change and the associated effort.

I think, since 11th of March, there are no more erroneous feeds coming
to you.

In the last few days I have analyzed why a simple server change can go
wrong.

1. We realized too late that the old hard disks had more and more
typographical errors and throughput problems, which meant that we had to
change the system at short notice.

2. Administrators with little experience in using inn2 and news servers.
Since I had to go out during the server change and to install new
systems with a customer. For this reason, the inexperienced team was temporarily on its own and had only a short list of instructions from
me. There the note was deposited that they should think of the DNS and
this was wrong. The DNS entries of the domain news.freedyn.net should
remain unchanged. Only the reverse DNS of the new server should be
adapted and the IP addresses of the old server should be redirected to
the new one.

3. I was temporarily unavailable to my admins because I was in a poor
mobile location.

We learned from this mistake and planned some changes for the future. So
that we will train our young administrators even more in the technology
of news servers.

In addition, I internally started the discussion, whether it makes sense
to step down as project manager of FreeDYN.de in the summer of 2019,
since I have to bear the full responsibility for this mess.

Sorry

Timo

--
FreeDYN.de / DNS-Netz.com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/15/19 9:03 PM, Timo wrote:

Hi admins,

I apologize to all administrators for the chaotic server change and the associated effort.

I think, since 11th of March, there are no more erroneous feeds coming
to you.

In the last few days I have analyzed why a simple server change can go
wrong.

1. We realized too late that the old hard disks had more and more typographical errors and throughput problems, which meant that we had to change the system at short notice.

2. Administrators with little experience in using inn2 and news servers. Since I had to go out during the server change and to install new
systems with a customer. For this reason, the inexperienced team was temporarily on its own and had only a short list of instructions from
me. There the note was deposited that they should think of the DNS and
this was wrong. The DNS entries of the domain news.freedyn.net should
remain unchanged. Only the reverse DNS of the new server should be
adapted and the IP addresses of the old server should be redirected to
the new one.

3. I was temporarily unavailable to my admins because I was in a poor
mobile location.

We learned from this mistake and planned some changes for the future. So
that we will train our young administrators even more in the technology
of news servers.

In addition, I internally started the discussion, whether it makes sense
to step down as project manager of FreeDYN.de in the summer of 2019,
since I have to bear the full responsibility for this mess.

Sorry

Timo

I'm mostly interested in how one can afford a team to run NNTP services
in this decade <g>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I'm mostly interested in how one can afford a team to run NNTP services
in this decade <g>

We do not earn anything with the nntp servers. We run webhosting and
other services, so the guys have little experience with nntp.

--
FreeDYN.de / DNS-Netz.com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)