Custombuild is out of beta.

Is custombuild working fine on your system?


  • Total voters
    110
I finally got a chance to give this a try and for the most part things went smoothly. There are a few minor issues that still need to be taken care of as far as configuration goes. When I tried to downgrade to PHP4 it pulled the configuration file out of the ap1 directory even though apache2 was running.

There were one or two other glitches but I didn't have time to document them, but they were also configuration based and fixed with a little bit of manual tweaking.
 
You just needed to set apache_ver=2.2, instead of 1.3 in options.conf.
 
It was already set to that, the only thing I did was change the php version to 4 and moved the yes for the CLI thing.
 
Code:
elif [ "${APACHE_OPT}" = "2.0" ] || [ "${APACHE_OPT}" = "2.2" ]; then
    PHP4_CONFIGURE=configure/ap2/configure.php4
    PHP5_CONFIGURE=configure/ap2/configure.php5
It's impossible to use file from ap1 directory while apache_ver 2.2 or 2.0 set.
 
You're right. I went back to see if I could reproduce it but couldn't. Ah well, maybe I'll stumble on it at another time.
 
Installed at clean system.
When a domain name created in the user's file httpd.conf writes Port 80, which prevents starts Apache.
I have found nothing in templates.
Solving the problem with scripts domain_create(destroy)_post.sh
Code:
#!/bin/sh
/usr/bin/perl -p -i -e 's/Port/#Port/g' /usr/local/directadmin/data/users/$username/httpd.conf
/usr/bin/perl -p -i -e 's/##Port/#Port/g' /usr/local/directadmin/data/users/$username/httpd.conf
 
Installed at clean system.
When a domain name created in the user's file httpd.conf writes Port 80, which prevents starts Apache.
I have found nothing in templates.
Solving the problem with scripts domain_create(destroy)_post.sh
Code:
#!/bin/sh
/usr/bin/perl -p -i -e 's/Port/#Port/g' /usr/local/directadmin/data/users/$username/httpd.conf
/usr/bin/perl -p -i -e 's/##Port/#Port/g' /usr/local/directadmin/data/users/$username/httpd.conf
Problem not solved.
My scripts don't start when I restore a backup.
Please, help.
 
Make sure that all virtual hosts files has been rewriten and you have apache_ver=2.0 set in /usr/local/directadmin/directadmin.conf. If it's set, run:
Code:
echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq
 
Make sure that all virtual hosts files has been rewriten and you have apache_ver=2.0 set in /usr/local/directadmin/directadmin.conf. If it's set, run:
Code:
echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq
There is no apache_ver=2.0 in conf file.
It works! Thanks.
 
Make sure that all virtual hosts files has been rewriten and you have apache_ver=2.0 set in /usr/local/directadmin/directadmin.conf. If it's set, run:
Code:
echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq
I have this problem. I have do this and now i have this error:
Code:
Stopping httpd:
Starting httpd: [Mon Jun 11 11:55:11 2007] [warn] module php5_module is already loaded, skipping
httpd: Syntax error on line 152 of /etc/httpd/conf/httpd.conf: Syntax error on line 4 of /etc/httpd/conf/extra/directadmin-vhosts.conf: Could not open configuration file /usr/local/directadmin/data/users/httpd.conf/httpd.conf: Not a directory
 
Apache displaying php4 source

Hopefully someone can shed some light on this.

About a week ago I decided to upgrade our server to php5-cli from php4. At the same time I also went from Apache 1.3 > 2.3. End the end, due to a script not working with PHP5, we decided to revert to php4 again.

Unfortunately this is where it got messy. We just could not get it running, so in the end dropped back to php4/apache 1.3 using customapache. Took a while to get it working.

The first problem here, is that from what I can see, DA is still using the new config file format, which means add a subdomain for example, and it will fail, add a domain, and it will tell you it cant write to httpd.conf. I have checked all the permissions and they are spot on.

Now I have tried to recompile to php4 on apache 1.3 or 2.3 using custombuild, so as to use the new config file structure.

Problem when I do this, is even though php is working fine, the php is displayed on screen as source. I have checked, the modules appear to be loading correctly, handlers are in the config correctly too. If I recompile as a test using php5-cli instead, it works perfect first time, back to php4-cli and it dies.

I have tried every combination of rewriting config files, deleting the existing httpd config etc etc... really stuck on what to try next.

If anyone has some pointers I would really appreciate it!

Cheers
 
Send me your server details and I will take a look at it.
 
how is it possible to use php 5.1.6 with this? because I never have been able to get php 5.2 working with ioncube sites and remote includes.
 
how is it possible to use php 5.1.6 with this? because I never have been able to get php 5.2 working with ioncube sites and remote includes.

Firstly, this would be something of a hack to make it work, but if you have a non production server to test it on, give it a try, I'm fairly confident it will work. I wouldn't try it on a production machine first though... not without smtalks advice first.

I have not tested this myself, but I believe you can change the version within the build script. Just look for the "User Variable" section within the build script. In there you will see PH5_VER=

In theory you could change this to the version you want. You would then need to download that version and place it within the custombuild directory. The script will look for a file named php-{version}.tar.gz.

The version number would change to the most recent everytime you update though.
 
yeah I seen where you can do it in build. I just ended uip going for 5.2.3 in regular customapache.
I dont like this suphp, Im not sure how it exactl works but if its anything like suexec or php-suexec then when a hacker uploads a shell to a users site its just like a user logging in ssh and they can delete the entire site if they want, be able to compile exploits, run binaries, etc.
Sure you can do it as apache to but you can only write to where world can you dont own the files.
I had a big debate at WHT over this once and was called an idiot and everything but its true, try yourself. They was saying over there that its the same and actually more secure.
the only benefit of suphp is the abilty to track scripts and mail scripts better in my opinion
 
For someone who had any problems I suggest to update to 1.0.10 version of custombuild. It's not released yet, but I'm attaching it here. It has all the fixes and it has one (new) great feature - it doesn't allow 2nd instance of the custombild script, so when you're building php - you won't be able to build it on the other ssh screen at the same time :)
 

Attachments

  • build.txt
    119.2 KB · Views: 292
It's uploaded on DirectAdmin servers now :) So, "./build update" will get the latest version of custombuild. Report any issues You have. Thank You!
 
the last version got an big bug !

if i want to recompile php it says


./build php
cURL is already installed. Do you want to build it again? (y/n) :n

LibJPEG is already installed. Do you want to build it again? (y/n) :n

LibZ is already installed. Do you want to build it again? (y/n) :n

LibPng is already installed. Do you want to build it again? (y/n) :n

GD is already installed. Do you want to build it again? (y/n) :n

mCrypt is already installed. Do you want to build it again? (y/n) :n

mHash is already installed. Do you want to build it again? (y/n) :n

Another instance of custombild is running, please delete the .custombuild file if you want to use custombuild.


And that file isn't on my server

Hope this can be fixt soon
 
Back
Top