Search found 6 matches

by Pukkeltje
01 May 2020 07:50
Forum: 4.x Bugs
Topic: Cron job are not running
Replies: 16
Views: 701

Re: Cron job are not running

I have an equal problem:
/etc/cron.hourly/0yum-hourly.cron:

Could not get metalink https://mirrors.fedoraproject.org/metal ... ent=centos error was
14: curl
by Pukkeltje
25 Feb 2020 08:30
Forum: 4.x Bugs
Topic: ERROR: eFa4 failed to install
Replies: 9
Views: 1213

Re: ERROR: eFa4 failed to install

I have the same error from the cron update job:
/etc/cron.daily/0yum-daily.cron:

Failed to check for updates with the following error message:
Failed to build transaction: 1:eFa-4.0.2-7.eFa.el7.x86_64 requires clamav-server >= 0.101.0-1
by Pukkeltje
05 Oct 2017 20:30
Forum: 3.x Bugs
Topic: Learn+Report - Razor2 Error (Resolved?)
Replies: 2
Views: 2482

Re: Learn+Report - Razor2 Error (Resolved?)

Yes, yes, after trying a lot of other things, this finally did help!
I also have a hyper-v iso.
by Pukkeltje
09 Feb 2017 13:52
Forum: 3.x Bugs
Topic: GEOIP download problem sice update to 3.0.1.8
Replies: 4
Views: 2552

GEOIP download problem sice update to 3.0.1.8

Since the upgrade to 3.0.1.8, I get this error while updating de GEOIP databases: Downloading file, please wait... Error occurred while downloading GeoIP IPv4 data file: cURL error 7: Failed to connect to 2400:cb00:2048:1::6810:262f: Network is unreachable Error occurred while downloading GeoIP IPv6...
by Pukkeltje
10 Sep 2016 13:24
Forum: 3.x Bugs
Topic: UNTRUSTED NETWORK: Message not reported as Spam
Replies: 9
Views: 4802

Re: UNTRUSTED NETWORK: Message not reported as Spam

I deleted the whole list and was playing with it. After some time I noticed that this is working: 172.16.0.6255.255.255.255 172.16.0.38 IP DOES NOT MATCH SUBNET 192.168.2.254 255.255.255.255 172.16.0.38 IP DOES NOT MATCH SUBNET 172.16.0.0 255.255.255.0 172.16.0.38 IP MATCHES SUBNET 192.168.2.0 255.2...
by Pukkeltje
08 Sep 2016 08:35
Forum: 3.x Bugs
Topic: UNTRUSTED NETWORK: Message not reported as Spam
Replies: 9
Views: 4802

Re: UNTRUSTED NETWORK: Message not reported as Spam

I have the same problem and run the script:

172.16.0.0 255.255.0.0
172.16.0.38
IP DOES NOT MATCH SUBNET

This looks like a bug: it should be trusted but it isn't!