WU and PWS send protocols
Posted: Tue 17 Jun 2014 11:00 pm
Cumulus (1.9.4. b1096) quit sending updates to WU and PWS this morning at ~5:50am.
After a lot of fiddling about it turned out to be an update of the ESET NOD32 virus checker that was blocking the sending of the file(s) to these servers.
I understand that WU does not use FTP but an http protocol and assume that PWS is the same. Data to our websites and to CWOP continued normally.
At this time I have disabled the virus checker as I am unable to determine what it is doing to affect these uploads.
We already have the entire Cumulus folder and all its associated files excluded from Nod32 (or so I believed).
Can anyone throw any light on what the actual mechanism is for the sending these updates that may assist in managing how to remove the activity from the attention of NOD32.
Thanks
Update,
have found the place in NOD32 to add http://*.wunderground.com/* to an exclusion list. This appears to have resolved the issue.
After a lot of fiddling about it turned out to be an update of the ESET NOD32 virus checker that was blocking the sending of the file(s) to these servers.
I understand that WU does not use FTP but an http protocol and assume that PWS is the same. Data to our websites and to CWOP continued normally.
At this time I have disabled the virus checker as I am unable to determine what it is doing to affect these uploads.
We already have the entire Cumulus folder and all its associated files excluded from Nod32 (or so I believed).
Can anyone throw any light on what the actual mechanism is for the sending these updates that may assist in managing how to remove the activity from the attention of NOD32.
Thanks
Update,
have found the place in NOD32 to add http://*.wunderground.com/* to an exclusion list. This appears to have resolved the issue.