Changes

From SME Server
Jump to navigationJump to search
m
headings amended
Line 1: Line 1: −
==Freshclam update==
+
==Method 1 - Freshclam update==
    +
=== '''Problem''' ===
 
On occasion there can be errors with clamav which can relate to the download of update files as shown below. In some instances, the admin account can be flooded by emails when clamav tries to update its database, this can occur several times a day.
 
On occasion there can be errors with clamav which can relate to the download of update files as shown below. In some instances, the admin account can be flooded by emails when clamav tries to update its database, this can occur several times a day.
   Line 13: Line 14:  
  2013-03-02 22:58:52.561968500 Update failed. Your network may be down or none of the mirrors listed in /etc/freshclam.conf is working. Check http://www.clamav.net/support/mirror-problem for possible reasons.
 
  2013-03-02 22:58:52.561968500 Update failed. Your network may be down or none of the mirrors listed in /etc/freshclam.conf is working. Check http://www.clamav.net/support/mirror-problem for possible reasons.
    +
=== '''Solution''' ===
 
{{Tip box|msg= As a result of [[bugzilla:8107]] and [[bugzilla:8108]] a script to  refresh clamav is now included in your SME Server}}
 
{{Tip box|msg= As a result of [[bugzilla:8107]] and [[bugzilla:8108]] a script to  refresh clamav is now included in your SME Server}}
   −
To run this script and refresh clamav, open a terminal (logged as root) and issue the following command: /usr/bin/refreshclam - then press "enter" .  The script will take a few minutes to complete. All steps will be displayed, ending up with the following WARNING : "Clamd was NOT notified : Can't connect to clamd through /var/clamav/clamd.socket connect(): No such file or directory.  This warning can be ignored, it is expected as a number of processes were stopped during execution of the script.
+
To run this script and refresh clamav, open a terminal (logged as root) and issue the following command:  
 +
/usr/bin/refreshclam  
 +
then press "enter" .  The script will take a few minutes to complete. All steps will be displayed, ending up with the following WARNING : "Clamd was NOT notified : Can't connect to clamd through /var/clamav/clamd.socket connect(): No such file or directory.  This warning can be ignored, it is expected as a number of processes were stopped during execution of the script.
    
'''All other scripts below are deprecated. They are here for documentation purposes only.'''
 
'''All other scripts below are deprecated. They are here for documentation purposes only.'''
   −
== Method 0 ==
+
== Method 2 - Deprecated ==
 +
{{Note box|This method is deprecated.
 +
Please use the Freshclam update default script ie refreshclam - see Freshclam update - https://wiki.contribs.org/Clamav:freshclam_update#Freshclam_update}}
    
See http://bugs.contribs.org/show_bug.cgi?id=7406#c32 for the source of this script, thanks chris.
 
See http://bugs.contribs.org/show_bug.cgi?id=7406#c32 for the source of this script, thanks chris.
Line 90: Line 96:  
  refreshclam
 
  refreshclam
   −
== Method 1 ==
+
== Method 3 - Deprecated ==
 +
{{Note box|This method is deprecated.
 +
Please use the Freshclam update default script ie refreshclam - see Freshclam update - https://wiki.contribs.org/Clamav:freshclam_update#Freshclam_update}}
 +
 
 
{{Tip box|This is a workaround to create a new database solving the error condition of clamav. Use a root terminal to perform these commands.}}
 
{{Tip box|This is a workaround to create a new database solving the error condition of clamav. Use a root terminal to perform these commands.}}
   Line 142: Line 151:  
  bytecode.cvd version from DNS: 214
 
  bytecode.cvd version from DNS: 214
 
  bytecode.cvd is up to date (version: 214, sigs: 41, f-level: 63, builder: neo)
 
  bytecode.cvd is up to date (version: 214, sigs: 41, f-level: 63, builder: neo)
      
Finally & to be absolutely sure signal-event post-update; signal-event reboot, then go through the logs post reboot to make sure everything started correctly.  This is not necessary for this procedure but doesn't hurt.
 
Finally & to be absolutely sure signal-event post-update; signal-event reboot, then go through the logs post reboot to make sure everything started correctly.  This is not necessary for this procedure but doesn't hurt.
   −
== Method 2==
+
== Method 4 - Deprecated==
 +
{{Note box|This method is deprecated.
 +
Please use the Freshclam update default script ie refreshclam - see Freshclam update - https://wiki.contribs.org/Clamav:freshclam_update#Freshclam_update}}
    
This is another method that you can find in [[bugzilla:7406]]
 
This is another method that you can find in [[bugzilla:7406]]
Line 205: Line 215:  
  tail -5 /var/log/freshclam/current | tai64nlocal
 
  tail -5 /var/log/freshclam/current | tai64nlocal
   −
== Method 3==
+
== Method 5 - Deprecated==
 +
{{Note box|This method is deprecated.
 +
Please use the Freshclam update default script ie refreshclam - see Freshclam update - https://wiki.contribs.org/Clamav:freshclam_update#Freshclam_update}}
    
===a script to launch===
 
===a script to launch===
Line 225: Line 237:  
If you want to launch it
 
If you want to launch it
 
  /root/clamav-update
 
  /root/clamav-update
 
+
[[Category:Howto]]
+
[[Category:Howto]]
624

edits

Navigation menu