[tools] update.script

Do you like use update.script ?

  • yes, all time

    Votes: 221 69.1%

  • no, some time

    Votes: 44 13.8%

  • some time

    Votes: 55 17.2%
  • Total voters
    320
update.script and custombuild use differents path on installation, ive stopped to use the update.script one since it was added in custombuil (nice cause now i got email when there is an update).

Regarding your problem, seems just that clamav is not started, so:

Code: 
/etc/init.d/clamd restart
netstat -ant | grep :3310

Post output.

Regards
 
Thanks Sellerone for the explanation.

I'm sure it's started and that also shows when I give the grep command, out put is:
Code: 
tcp        0      0 127.0.0.1:3310              0.0.0.0:*                   LISTEN
So it's started.
However, last time the error notice showed in the log was this afternoon. So maybe the problem is over.

Since custombuild 1.2 only uses different paths... what's the best way to uninstall/remove the Clamav from update.script?
And do I also need to remove the line in exim.conf then, before using the custombuild Clamav?

I did not trust the custombuild version at first, because yesterday I used spamassassin from the options.conf on a new server but it did not show up in DA itself. Maybe I did something wrong.
But if possible I would rather use clamav from options.conf.
 
well, last time if i dont remember bad i had to manually remove every clam* file than install the custombuild one.

So, stop clamd and do

Code: 
find / -name clam* /

You should find executables and manuals, remove all those related files and install it from custombuild

Code: 
cd /usr/local/directadmin/custombuild
./build set clamav yes
./build update
./build clamav

Regards
 
I tried to install mod_security2 with your script but when I try to restart the apache I get this error:

Code: 
Starting httpd: httpd: Syntax error on line 133 of /etc/httpd/conf/httpd.conf: Syntax error on line 10 of /etc/httpd/conf/extra/httpd-includes.conf: Syntax error on line 337 of /etc/modsecurity2/modsecurity-rules-selected-by-web4host.net.conf: No matches for the wildcard '*.conf' in '/etc/modsecurity2/activated_rules', failing (use IncludeOptional if required)

I also tried install rules with ./update.script MODsecurity2Apache2Rules but without success...

For now I commented the line 337 and apache started without errors, but I would figure out what to do to get it to work properly.

Thank in advance
 
very new to DA

only had it few days but it seems this is something I should at least install.
have to admit I am a bit scared of stuff like this though :)
just wanted to say thank you for preparing this, going to read through the pages to prepare for any pitfalls.
 
Is the problem not solved then?

I installed update.script on july 21st. So that's 2 days ago and I installed mod_antiloris from it.
There was no problem getting the files.

Working like a charm at the moment too:
--2012-07-23 20:07:18-- http://tools.web4host.net/licenses.tmp
Resolving tools.web4host.net... 108.162.198.157, 108.162.198.57
Connecting to tools.web4host.net|108.162.198.157|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17981 (18K)
Saving to: `/usr/local/updatescript/licenses'

100%[==========================================================================================>] 17,981 --.-K/s in 0.09s

2012-07-23 20:07:19 (190 KB/s) - `/usr/local/updatescript/licenses' saved [17981/17981]
Click to expand...
 
Your link came up for me now, but after a long delay. Maybe simply routing issues.

Jeff
 
That could indeed be the case because it's working very vast on my side, residing in Europe, the Netherlands.
 
chronic said:
I tried to install mod_security2 with your script but when I try to restart the apache I get this error:

Code: 
Starting httpd: httpd: Syntax error on line 133 of /etc/httpd/conf/httpd.conf: Syntax error on line 10 of /etc/httpd/conf/extra/httpd-includes.conf: Syntax error on line 337 of /etc/modsecurity2/modsecurity-rules-selected-by-web4host.net.conf: No matches for the wildcard '*.conf' in '/etc/modsecurity2/activated_rules', failing (use IncludeOptional if required)

I also tried install rules with ./update.script MODsecurity2Apache2Rules but without success...

For now I commented the line 337 and apache started without errors, but I would figure out what to do to get it to work properly.

Thank in advance
Click to expand...

I am experiencing the same problem on a new installation.
 
Suurbier, tries to show me the contents of this file /etc/httpd/conf/extra/httpd-includes.conf
 
The mod_security download does not work at all. Any idea how to sort out this or any other working tutorial on it?

[root@server1 updatescript]# ./update.script MODsecurity2Apache2

Only one mirror to download modsecurity-apache_2.7.1.tar.gz

--2013-02-05 08:53:22-- http://www.modsecurity.org/download/modsecurity-apache_2.7.1.tar.gz
Resolving www.modsecurity.org... 204.13.200.240
Connecting to www.modsecurity.org|204.13.200.240|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://downloads.sourceforge.net/mod-security/modsecurity-apache_2.7.1.tar.gz?use_mirror= [following]
--2013-02-05 08:53:23-- http://downloads.sourceforge.net/mod-security/modsecurity-apache_2.7.1.tar.gz?use_mirror=
Resolving downloads.sourceforge.net... 216.34.181.59
Connecting to downloads.sourceforge.net|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-02-05 08:53:23 ERROR 404: Not Found.

Catastrophe! Mirror failed.
 
You must log in or register to reply here.
Back
Top