NS7 cron daily problem

NethServer Version: NethServer release 7.9.2009 (final)

Hi,

For a month now I have been receiving the following error message from cron:

/etc/cron.daily/0yum-daily.cron:
Could not retrieve mirrorlist http://mirrorlist.de-labrusse.fr/mirror error was
12: Timeout on http://mirrorlist.de-labrusse.fr/mirror: (28, 'Connection timed out after 30004 milliseconds')

What could be the reason for this?

Thank you for your help

The mirror isn’t available anymore.

I’m sad. I’ve used several applications from stephdl’s repo and still haven’t been able to solve all the problems for the NS7 and NS8 migration. We probably need to find a solution quickly because this isn’t going to be good…

point to the correct url

[root@firewall ~]# cat /etc/yum.repos.d/stephdl.repo
[stephdl]
name=Stephdl (Stephane de Labrusse) repository for nethserver $releasever - $basearch
baseurl=http://mirror.de-labrusse.fr/NethServer/$releasever
#mirrorlist=http://mirrorlist.de-labrusse.fr/mirror
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-stephdl

1 Like

but it is going to be removed one day or completely obsoleted

2 Likes

Can you open a new thread specifically to your migration issues, and outline them there please?

I don’t see it as justified, because we’re trying to solve each problem in multiple threads. I hope they all lead to results, because without them I’ll be in serious trouble…

We’ve been trying to find solutions for a year now, but unfortunately there are some things we haven’t been able to solve…

1 Like

Thank you @stephdl

I’ll find out tomorrow if the setup was successful…

Right, same applies for time of devs inteligence you are seeking for and volunteers time here.

I suggest you look here.

Don’t forget, YOU and YOUR company have a problem and are seeking for FREE help. NS7 is obsolete, you deliberately chose to NOT migrate in time to NS8. The Cron Contrib is not available on NS8.

The issues and problems and difficulties you are flooding these forums with are yours. Not ours.

I think you misunderstood. I opened a separate thread for every problem that arose or joined the appropriate thread. I’m currently doing the same thing, but I’m only dealing with one problem at a time, so I don’t think it’s appropriate to open a new topic at the moment.

The main reason for this is that the problems are interdependent and it only becomes clear that there is a solution once we have solved each one individually.

In any case, thank you for your advice and suggestions.

Point taken, appologies.

1 Like

Thank you, this solved the error message problem. I hope I can switch to NS8 by the time it is removed.

Just attaching this info to this thread. A way to use cron on NS8 containers at this time.

Thanks, but the problem occurred under NS7 and @stephdl’s answer solved it. Unfortunately, NS8 cron management is not relevant to this problem…

Correct; this was a very poor topic title.