[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
Try to rebuild again or send your server info to fix (pm)
Thank you for your generous offer of assistance. I have sent you a PM. Could you please tell me the commands I for uninstalling/rolling back to my older versions of OpenSSL and OpenSSH?

I don't understand all the nuances of the differences between the latest update.script versions and the alternate file paths. (/usr vs. /usr/local) I would like to revert back to my previous standard CentOS 4.x versions of OpenSSL and OpenSSH to keep things simple.

My FTP has been broken for a week and I'm not sure what else is broken or will break if I make any more mistakes with the update process.

Please let me know if you need me to run any commands to give you more information about my configuration before you explain how to revert to my old versions of OpenSSL and OpenSSH (from before I ran update.script).

I am running CentOS 4.4 64 bit, now with ProFTPD 1.3.1 (broken), PHP 4.4.8 (will not rebuild) and Apache 2.2.9.


Thank you very much for your help.
 
Last edited:
hi wael

i've used ./update.script UPDATEME and it is showing older product versions, and when i use ./update.script DATE

it shows:

Version: 1.1
# Release Date: 1 / 9 / 2006
# Update Date : 11 / 7 / 2007

is it an older script on your server by mistake?

thanks in advance
 
hi wael

i've used ./update.script UPDATEME and it is showing older product versions, and when i use ./update.script DATE

it shows:

Version: 1.1
# Release Date: 1 / 9 / 2006
# Update Date : 11 / 7 / 2007

is it an older script on your server by mistake?

thanks in advance

delete old update.script and download it again.
 
Hi,

Update to mysql 5.0 doesn't work here on a centos 4.4.

It says:
PHP:
A MySQL server package (MySQL-server-4.1.21-0) is installed.

Upgrading directly from MySQL 4.1 to MySQL 5.0 may not
be safe in all cases.  A manual dump and restore using mysqldump is
recommended.  It is important to review the MySQL manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

- Ensure that you have a complete, working backup of your data and my.cnf
  files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages.  Usually this command will
  list the packages you should remove:
  rpm -qa | grep -i '^mysql-'

  You may choose to use 'rpm --nodeps -ev <package-name>' to remove
  the package which contains the mysqlclient shared library.  The
  library will be reinstalled by the MySQL-shared-compat package.
- Install the new MySQL packages supplied by MySQL AB
- Ensure that the MySQL server is started
- Run the 'mysql_upgrade' program

Maby its a good idea to make some changes to the update script so it will deleted first the old packages?

(i already have deleted the packages manualy, and update mysql sucesfuly)
 
Last edited:
Hi,

Update to mysql 5.0 doesn't work here on a centos 4.4.

It says:
PHP:
A MySQL server package (MySQL-server-4.1.21-0) is installed.

Upgrading directly from MySQL 4.1 to MySQL 5.0 may not
be safe in all cases.  A manual dump and restore using mysqldump is
recommended.  It is important to review the MySQL manual's Upgrading
section for version-specific incompatibilities.

A manual upgrade is required.

- Ensure that you have a complete, working backup of your data and my.cnf
  files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages.  Usually this command will
  list the packages you should remove:
  rpm -qa | grep -i '^mysql-'

  You may choose to use 'rpm --nodeps -ev <package-name>' to remove
  the package which contains the mysqlclient shared library.  The
  library will be reinstalled by the MySQL-shared-compat package.
- Install the new MySQL packages supplied by MySQL AB
- Ensure that the MySQL server is started
- Run the 'mysql_upgrade' program

Maby its a good idea to make some changes to the update script so it will deleted first the old packages?

(i already have deleted the packages manualy, and update mysql sucesfuly)

Update work fine & you can use ELS script

Wael
 
I 've got this error when I run ./update.script NOBODYCHECK
--------------------
mkdir: cannot create directory `/usr/local/updatescript': File exists
--15:59:53-- http://www.webhostgear.com/projects/nobodycheck/install.sh
=> `install.sh'
Resolving www.webhostgear.com... 70.86.41.194
Connecting to www.webhostgear.com|70.86.41.194|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
15:59:53 ERROR 500: Internal Server Error.

chmod: cannot access `install.sh': No such file or directory
./update.script: line 1111: ./install.sh: No such file or directory
----------------------
I've tried to re-install updatescript but it didn't help to solve that problems!
 
I am trying to block some IPs and subnets adding them in BLOCK_LIST but when I check the chains is not added. Do I have to enable something else in the script?

If I run manually the part of the script that adds the ip for input/output it adds the ip so something is not running within the script?
 
MRTG - Install Error

Hi!

i have new server (Centos 5, apache 2)

And if install MRTG, i have this error message:

[root@srv - /usr/local/updatescript # ./update.script MRTG
Checking for previous MRTG installation...
The directory /var/www/html/mrtg does not exist. I will create it...
Creating necessary directories and preparing for installation...
Preparations complete...
Downloading the most recent MRTG and installing it...
--11:59:02-- http://oss.oetiker.ch/mrtg/pub/mrtg-2.16.2.tar.gz
Resolving oss.oetiker.ch... 213.144.138.195
Connecting to oss.oetiker.ch|213.144.138.195|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1078423 (1.0M) [application/x-tar]
Saving to: `mrtg-2.16.2.tar.gz'

100%[=========================================>] 1,078,423 796K/s in 1.3s

11:59:04 (796 KB/s) - `mrtg-2.16.2.tar.gz' saved [1078423/1078423]

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for perl... /usr/bin/perl
checking for groff... /usr/bin/groff
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for inttypes.h... (cached) yes
checking for unsigned long long... yes
checking for long long... yes
checking for strtoll... yes
checking for printf long long format specifier... %lld
checking for pow in -lm... yes
checking for gdImageGif in -lgd... no
checking for gdImagePng in -lgd... no
checking for gdImagePng_jpg in -lgd... no
checking for gdImagePng_jpg_ft in -lgd... no
checking for gdImageGd in -lgd... no
checking gd.h usability... yes
checking gd.h presence... yes
checking for gd.h... yes

** Ooops, one of many bad things happened:

a) You don't have the GD library installed.
Get it from http://www.boutell.com, compile it and
use either --with-gd-lib=DIR and --with-gd-inc=DIR to specify
its location. You might also have to use --with-z-inc,
--with-z-lib and --with-png-inc, --with-png-lib for gd
versions 1.6 and higher. Check config.log for more
information on the problem.

b) You have the GD library installed, but not the gd.h
header file. Download the source (see above) and use
--with-gd-inc=DIR to specify where the file can be found.

c) You have the library and the header file installed, but
you also have a shared GD library in the same directory.
Remove the shared library files and/or links (e.g.
libgd.so.2.0.0, libgd.so and libgd.so.2). This is especially
likely if you're using a recent (post 1.8.4) version of GD
and didn't configure it with --disable-shared.

d) You have gd library installed and also it's headers, but you are
missing libpng (and headers) or freetype (and headers)
(mrtg does not use freetype, but if your copy of gd is precompiled
against it, you have to install it ...

Consider following the instructions in doc/mrtg-unix-guide.txt
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
MRTG has been installed...
Updating MRTG config and template...
--11:59:06-- http://tools.web4host.net/mrtgcfg.tar.gz
Resolving tools.web4host.net... 67.205.76.198
Connecting to tools.web4host.net|67.205.76.198|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2056 (2.0K) [application/x-gzip]
Saving to: `mrtgcfg.tar.gz'

100%[=========================================>] 2,056 --.-K/s in 0s

11:59:06 (4.75 MB/s) - `mrtgcfg.tar.gz' saved [2056/2056]

Adding MRTG to /etc/crontab...
env: /usr/local/mrtg-2/bin/mrtg: No such file or directory
env: /usr/local/mrtg-2/bin/mrtg: No such file or directory
env: /usr/local/mrtg-2/bin/mrtg: No such file or directory
env: /usr/local/mrtg-2/bin/mrtg: No such file or directory
Cleaning up installation...


MRTG install done

How this fix it?

Thanks!
 
Hi!

i have new server (Centos 5, apache 2)

And if install MRTG, i have this error message:



How this fix it?

Thanks!
Use custombuild to install the GD library. Then redo the installation of MRTG. ^^
 
Getting this error when installing AVG on debian 4.0

./update.script: line 792: yum: command not found
./update.script: line 792: rpm: command not found
./update.script: line 792: /opt/grisoft/avggui/bin/avggui_update_licinfo.sh: No such file or directory
./update.script: line 793: avgupdate: command not found
./update.script: line 793: /etc/init.d/avgd: No such file or directory
./update.script: line 793: /etc/init.d/avgd: No such file or directory
./update.script: line 793: avgscan: command not found
 
This is the only thing I dislike about DA, it restricts you a bit with regard to using your OS to it's full ability.

I am afraid I am going to break it at any moment. DA is a bit of a dictator over my OS and I am not sure if I like that.

These build and update scripts are great but still seem a bit of a strange way to run a business so to speak.

David
 
Back
Top