Custombuild is out of beta.

Is custombuild working fine on your system?


  • Total voters
    110
jlasman, apache configs are backed up when doing a conversation. I was talking about using old configs for the full functionality of custombuild, it's not very easy to do that ;) Because as I said everything is done in the other way (not using the one file). I would take me an hour to tell you how everything is done, if you want - you can browse its source :) E.g. take a look at doPhp() function, it would be quite difficult to do everything in the httpd.conf file.
 
I'm not a php programmer; browsing the source would make me even more confused :) .

I guess I need to somehow revisit what someone called the problem and attempt to understand it better. If you'd be so kind as to do that for me I'll appreciate it. I'd love a full custombuild system rather than just customapache which we have now ... but I want to be sure my employees in different timezones can update systems without having to awaken me in the middle of the night... so I want something that just works.

I guess what I'd like to see is a How-To on how to upgrade to CustomBuild, and another How-To on how to use it once it's installed.

And, as long as I'm asking ... Does CustomBuild include some kind of configuration file to keep track of what was installed last time, so if we only desire to update what we did last time and not install anything new, we can just type one thing that'll work on all servers?

Thanks!

And, oh ...

I've reset the poll results as you requested; hopefully people will now re-vote.

Jeff
 
zziblib

Error:
//
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error exit delayed from previous errors
Done.
./build: line 2264: cd: zziplib-: No such file or directory
Configuring zziplib-...
./build: line 2267: ./configure: is a directory
Done. Making zziplib-...
Trying to make zZip...
make: *** No targets specified and no makefile found. Stop.
server:/usr/local/directadmin/custombuild#
//
Found: Zerobyte zziblib
..
Possible Reason: wrong Link to "zziblib-.tar.gz" somewhere after build update data in the script, instead of "zziplib-0.13.49.tar.gz" (if latter one should be here, i dont know).

johannes
 
And, as long as I'm asking ... Does CustomBuild include some kind of configuration file to keep track of what was installed last time, so if we only desire to update what we did last time and not install anything new, we can just type one thing that'll work on all servers?

You're always welcome. CustomBuild just changes /etc/httpd/conf directory (nothing more is changed), if it has old configs (without extra dir) (you need to do the changes to the httpd.conf file if you have modified something on it, and you only need to do that one time, because when the script detects /etc/httpd/conf/extra - it doesn't overwrite any configs anymore).
 
Error:
//
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error exit delayed from previous errors
Done.
./build: line 2264: cd: zziplib-: No such file or directory
Configuring zziplib-...
./build: line 2267: ./configure: is a directory
Done. Making zziplib-...
Trying to make zZip...
make: *** No targets specified and no makefile found. Stop.
server:/usr/local/directadmin/custombuild#
//
Found: Zerobyte zziblib
..
Possible Reason: wrong Link to "zziblib-.tar.gz" somewhere after build update data in the script, instead of "zziplib-0.13.49.tar.gz" (if latter one should be here, i dont know).

johannes

Do you use Debian 3.1?
 
Please change this:
Code:
elif [ -e /etc/debian_version ]; then
        if [ "`cat /etc/debian_version`" = "4.0" ]; then
                ZZIP_VER=0.13.47        
        fi

To:
Code:
elif [ -e /etc/debian_version ]; then
        if [ "`cat /etc/debian_version`" = "4.0" ]; then
                ZZIP_VER=0.13.47
        else
                ZZIP_VER=0.10.82
        fi
Thank you :) It will be changed into the custombuild script soon.

P.S. if you use PHP5 - it doesn't require zziplib, because it has it own zip extension. It's just needed for PHP4.
 
great, thank you, it works now, but i have still troubles with sshd ..
DA says "An error has occurred", https give blank site (sshd is running, have pids, but not serves via https and not react via DA)
 
Last edited:
johannes, it has nothing to do with ssh daemon, so it's not a problem of custombuild.
 
Sorry, forgot to say that it has been fixed (issue with Debian 3.1 & zzip library) :)
 
keep having problems when use 64bit CentOS 4.5(updated from 4.4)
when building php4:
Code:
/usr/bin/ld: /usr/local/lib/libltdl.a(ltdl.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libltdl.a(ltdl.o): could not read symbols: Bad value
collect2: ld returned 1 exit status
make: *** [libphp4.la] Error 1
 
Do I can delete "customapache" dir after install from "custombuild"?
Thank you.
 
keep having problems when use 64bit CentOS 4.5(updated from 4.4)
when building php4:
Code:
/usr/bin/ld: /usr/local/lib/libltdl.a(ltdl.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libltdl.a(ltdl.o): could not read symbols: Bad value
collect2: ld returned 1 exit status
make: *** [libphp4.la] Error 1

Not a bug of the custombuild script.
 
You're always welcome. CustomBuild just changes /etc/httpd/conf directory (nothing more is changed), if it has old configs (without extra dir) (you need to do the changes to the httpd.conf file if you have modified something on it, and you only need to do that one time, because when the script detects /etc/httpd/conf/extra - it doesn't overwrite any configs anymore).

Ok I think we had a misunderstanding :) you thought I meant the old customapache configs?

I meant on a server where custombuild is already installed and the extra dir exists and all the configs, but then running the build script again to upgrade apache for new version or something.
 
Yes, I thought that you meant the old customapache configs. It's not rewriting configs, when it's not needed. The configs that are rewritten: extra/httpd-suphp.conf, extra/httpd-php-handlers.conf. Nothing more :) You need to use "./build rewrite_confs" if you will ever need to rewrite configs :)
 
"mail-header-patch=yes" has been added to the options.conf file. Just remove options.conf file with "rm -f /usr/local/directadmin/custombuild/options.conf" after the update and options.conf file will be rewritten, you can also just add "mail-header-patch=yes" to the file.
 
Back
Top