EFA 3.0.7 update

[yaboc]

Hi,

I tried to update 3.0.6 and executed the

sudo /usr/local/sbin/EFA-Update -update in shell but the update log shows only

Thu Feb 26 23:46:25 2015

[EFA] Good you are root

Thu Feb 26 23:46:25 2015


nothing is happening. any ideas ?

Thanks

yaboc

[DaN]

Hi

same here

console:

Code: Select all

/usr/local/sbin/EFA-Update -update
[EFA] Good you are root
[EFA] Starting update to EFA-3.0.0.7
[EFA] Good you are root

Script close at this point
EFA-Backup.log:

Code: Select all

[...]
Backup Completed at 02272015 040805
[EFA] Good you are root
Purging Backups older than 5...
Old backups purged.

update-2015-02-27-08:59:24.log:

Code: Select all

Log of /var/EFA/update/EFA-update-script 
Fri Feb 27 08:59:24 2015

[EFA] Good you are root

Fri Feb 27 08:59:24 2015
----------------

I miss "Update to EFA-3.0.0.7" in my "EFA-update-script". Oh the file ist from last year. Same on http://dl.efa-project.org/update/EFA-update-script.
Could anyone update that script please?

[darky83]

Updated the script, I guess we forgot to upload it to the production server :S

[DaN]

Now i've got an update-success-mail, but the updatelog shows:

Code: Select all

zoom: rule __FOR_SALE_NET will loop on SpamAssassin older than 3.3.2 running under Perl 5.12 or older, Bug 6558

 91% [==================================================================================                ]  60.13 rules/sec 00m02s LEFT
 93% [==================================================================================           ]  70.39 rules/sec 00m01s LEFT
 96% [==================================================================================      ]  73.70 rules/sec 00m00s LEFT
 98% [==================================================================================   ]  63.56 rules/sec 00m00s LEFT
100% [==================================================================================]  62.09 rules/sec 00m23s DONE
//no text here, what is the script downloading?
  0% [                                                                                                                                                  ]   0.00 bases/sec --m--s LEFT

[...]
 73% ==================================================================================     ]  28.90 bases/sec 00m40s LEFT
 73% [================================================================================                              
Fri Feb 27 09:57:32 2015
----------------

After 73% there is no log. How can i be shure the update is realy successful?

Console output from PuTTY (SSH):

[shawniverson]

After 73% there is no log. How can i be shure the update is realy successful?

That is the last thing that happens in the script. I am thinking you are fine.

Run a lint test in MailWatch to verify that Spamassassin and MailScanner are ok

[shawniverson]

Updated the script, I guess we forgot to upload it to the production server :S

lol that is my bad. Learning my way around prod

[DaN]

SA Lint show one orange:
"dbg: rules: __HAS_LIST_ID merged duplicates: __ML2" with "1.23709" seconds

"total" with "11.92213"

MailScanner Lint show one red:
"SpamAssassin reported no errors." with "9.38914" (second test: "4.30646") seconds

"total" with" (6.12967)

All other are green.

Thanks

[shawniverson]

Those color codes reflect the relative processing times.

If you do not see any errors then you are good.

[toddh]

We are getting the same error.

MailScanner shows pass but SA is Red.

SA Lint show one orange:
"dbg: rules: __HAS_LIST_ID merged duplicates: __ML2" with "1.1xxx" seconds

"total" with "5.3xxxx"

This seems to me like a long time for SA to process a message?

[pdwalker]

Spamassassin is doing a heck of a lot of checks, so yes, it appears to take a fair amount of realtime to consult all the RBLs, check all the rules, etc, etc, etc.

It appears to be perfectly normal.

[darky83]

My servers are normaly below the 2seconds:
Total: 1.59137

Keep in mind that the performance of your system might also be an issue.
one other (slower) system: Total 3.52634

And on my little intel Atom test server it can take over 10s.

Performance of your DNS lookups and the available bandwidth and connection times might also slow things down.

[pdwalker]

4.84301s on my machine.

It's nighttime now. During the day it takes about 1.5 seconds longer.

I run the VM on a machine hosting 10 other active VMs