Issue ERROR: Dr.Web Updater: failed to download files ! return code 105

[chris-design]

@Sebahat.hadzhi I adjusted the /etc/hosts file on several servers and switched to this IP:

195.161.158.50  update.geo.drweb.com

But this doesn't seem to help: I received this error again this morning:

/etc/cron.daily/drweb-update:
ERROR: Dr.Web Updater: failed to download files !
run-parts: /etc/cron.daily/drweb-update exited with return code 105

@SleepTri how can I adjust the time period of the daily cronjob for drweb? I checked crontab - but there are no entries.

 

[Sebahat.hadzhi]

Can everyone who is still experiencing the issue on a daily basis confirm what's the time zone set for their servers? As well as the schedule of the cron.daily task:

cat /etc/crontab  | grep daily

Thanks in advance.

 

[mow]

@SleepTri how can I adjust the time period of the daily cronjob for drweb? I checked crontab - but there are no entries.

You're looking in the wrong place. cron has two ways to start things: The per-user crontab and the system-wide /etc/crontab, which in turn runs the scripts in /etc/cron.hourly, daily, weekly and monthly.
At the start of the line for cron.daily, I changed 25 6 to 40 5 for 5:40. Please do not use the same time
(CET DST btw)

 

[chris-design]

Can everyone who is still experiencing the issue on a daily basis confirm what's the time zone set for their servers? As well as the schedule of the cron.daily task:

cat /etc/crontab  | grep daily

Thanks in advance.

25 6 * * * root test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; }

 

[chris-design]

You're looking in the wrong place. cron has two ways to start things: The per-user crontab and the system-wide /etc/crontab, which in turn runs the scripts in /etc/cron.hourly, daily, weekly and monthly.
At the start of the line for cron.daily, I changed 25 6 to 40 5 for 5:40. Please do not use the same time
(CET DST btw)

Thank you very much @mow - I switxh to 25 5 now - I hope that will fix the problem.

 

[mow]

Thank you very much @mow - I switxh to 25 5 now - I hope that will fix the problem.

Unfortunately it didn't for me - but now I got return code 103 which, according to /opt/drweb/update.pl, is EXIT_STATUS_CONNECT_ERROR => 103,
Worse is that I keep getting this error even now running /etc/cron.daily/drweb-update manually.

Update: I checked all the round-robin IPs of update.geo.drweb.com:
update.geo.drweb.com has address 85.10.234.30
update.geo.drweb.com has address 195.161.158.50
update.geo.drweb.com has address 195.133.219.93
update.geo.drweb.com has address 195.133.219.91
update.geo.drweb.com has address 81.176.67.172
update.geo.drweb.com has address 213.59.3.178

All but the first one of these are in Russia. That might have something to do with it.

The first one is actually at hetzner, just a few hops away from our server.
So I put that IP in /etc/hosts and was able to update manually.

 

[chris-design]

Unfortunately it didn't for me - but now I got return code 103 which, according to /opt/drweb/update.pl, is EXIT_STATUS_CONNECT_ERROR => 103,
Worse is that I keep getting this error even now running /etc/cron.daily/drweb-update manually.

Update: I checked all the round-robin IPs of update.geo.drweb.com:
update.geo.drweb.com has address 85.10.234.30
update.geo.drweb.com has address 195.161.158.50
update.geo.drweb.com has address 195.133.219.93
update.geo.drweb.com has address 195.133.219.91
update.geo.drweb.com has address 81.176.67.172
update.geo.drweb.com has address 213.59.3.178

All but the first one of these are in Russia. That might have something to do with it.

The first one is actually at hetzner, just a few hops away from our server.
So I put that IP in /etc/hosts and was able to update manually.

I also received this message from a server where I switched the execution time for the daily cronjob from 6:25 to 5:25:

/etc/cron.daily/drweb-update:
ERROR: Dr.Web Updater: failed to download files !
run-parts: /etc/cron.daily/drweb-update exited with return code 103

So same result with return code 103.

@Sebahat.hadzhi any update/support from Plesk on this? I would like to fix this issue finally because it is annoying me every day for several weeks now.

 

[Sebahat.hadzhi]

@chris-design , can you and @mow confirm the location of the server you are experiencing the issue? Also, can you please edit the logging verbosity in /etc/drweb/drweb32.ini and set it to Debug:

# grep -i loglevel /etc/drweb/drweb32.ini
# LogLevel = {Quiet|Error|Warning|Info|Verbose|Debug}
LogLevel = Info

@chris-design If I remember correctly you already tried adjusting the hosts file and that didn't work for you, but have you tried with another IP address other than the first one? If not, could you please try rotating the IP address on a daily basis and confirm if there's any scenario in which you do not encounter the error?

 

[mow]

@chris-design , can you and @mow confirm the location of the server you are experiencing the issue? Also, can you please edit the logging verbosity in /etc/drweb/drweb32.ini and set it to Debug:

The server is at hetzner's datacenter in Falkenstein, Germany. The working drweb server 85.10.234.30 is in hetzner's datacenter in Nuremberg.
I don't think increasing the log level will be of much help since 103 is a connection issue where the connection already fails at the TCP level - some of the other servers don't even ping.

 

[hexx_network]

Will Plesk provide a solution for that issue?

 

[Tjerk Visser]

It would be nice if there will be a solution! I am experience the same error already for some time now. First with code 105 and now code 103.
Server is a strato server located in germany. Maybe that helps.

Regards Tjerk

 

[hebeyer]

It's been the same for me for several weeks. Partly error 105, partly error 103. On average, I get these emails 2 to 3 times a week.

 

[mow]

Since I changed the IP to 85.10.234.30, I didn't get any further errors.

 

[trialotto]

@Sebahat.hadzhi and @AlL,

It seems to be the case that, in addition to the odd error notifications, there are some connectivity issues.

I can refer to the following link where I have add some information and some STR that can help to minimize the connectivity issues.

Kind regards....

 

[Tjerk Visser]

A bit confusing, this thread is marked resolved. Maybe I missed something? I still recieve the 105 error.
Maybe someone can tell me what to do?

Regards
Tjerk Visser

 

[trialotto]

@Tjerk Visser

Please try to add

85.10.234.30 update.geo.drweb.com

to the /etc/hosts file.

In most cases, that you should do the trick.

Kind regards....

 

[Tjerk Visser]

@trialotto

Thank you for the reply.

I will give it a try

Regards

 

[Bitpalast]

A bit confusing, this thread is marked resolved. Maybe I missed something? I still recieve the 105 error.

You are right. It's not resolved. I changed the status back to "issue". We are seeing the issue here on many servers, too, since months. It is thinkable that it is a banned subnet or several banned subnets that Hetzner is using for their dedicated servers. It would be nice if Plesk could ask the antivirus manufacturer if their systems have banned some Hetzner IP blocks.

 

[Tjerk Visser]

@trialotto @Bitpalast
Updated the etc hosts file as suggested.
This morning again recieved the error message.

Would be nice, since I am paying a monthly subscription for Plesk, that this issue gets a bit more attention from Plesk.

 

[trialotto]

@Tjerk Visser

I agree with your statement

Would be nice, since I am paying a monthly subscription for Plesk, that this issue gets a bit more attention from Plesk.

but, at the same time, I have to emphasize that the whole issue is on the side of DrWeb (and not Plesk).


DrWeb simply has servers that are really unresponsive - you can ping the servers and then you will see how "slow" they are.

As a result, there will be connectivity issues - the "slow" DrWeb servers will not respond in time and/or will not respond properly.

As a result, the connectivity issues are more present when the updates become larger.


Plesk could easily provide a solution by creating a mirror that can be used to update from.

Nevertheless, that would only mitigate some of the issues on the DrWeb side - it is a workaround solution, not a proper solution.


Plesk admins, at least in theory, could also try to run the daily update on a later time of the day.

After all, all updates are more or less executed on the same time, so the DrWeb servers get many requests during a small period of time - that is why we all get notifications of update failures in the morning hours.


I hope the above helps a bit.

Kind regards....