Discussion about CustomBuild
- Thread starter nobaloney
- Start date
There is no difference, you can do that manually too if you want.
Code:
cd /usr/local/directadmin/custombuild
./build update
perl -pi -e 's/mysql_inst=no/mysql_inst=yes/' options.conf
./build mysql
./build php nCustom build 1.1.15 shows latest MySQL version to be 5.0.x with ./build versions !!
Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
This error stopping me at last! I had to reverted to the older version.
Icheb
Verified User
After upgrading to the new Roundcube, I got into a load of issues.
It seems, by default the custombuild sets the imap root to 'INBOX.', nice and all, but more than 20 'dirs' with mail disappeared from a client. They were still on the imap server, however, Roundcube wasn't able to display them, due to the imap root.
Would it be an idea to change line 1913 of the latest custom builder to just be empty?
I manually patched the config here, and there are no problems with it now.
It seems, by default the custombuild sets the imap root to 'INBOX.', nice and all, but more than 20 'dirs' with mail disappeared from a client. They were still on the imap server, however, Roundcube wasn't able to display them, due to the imap root.
Would it be an idea to change line 1913 of the latest custom builder to just be empty?
I manually patched the config here, and there are no problems with it now.
/etc/cron.daily/custombuild
Running the cron everyday results on Debian in this error:
/etc/cron.daily/custombuild:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Is there an easy way to get this error gone?
Running the cron everyday results on Debian in this error:
/etc/cron.daily/custombuild:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Is there an easy way to get this error gone?
Remove system installed MySQL packages (You can see them on Debian/Ubuntu using: "dpkg --list | grep mysql", CentOS/RHEL/Fedora: "rpm -qa | grep MySQL". Use only DA provided ones.
this screwed up my system, how can I deinstall
Hi,
Today I followed the instructions to the letter like in the first post. Installing version 1.1
I am on a freebsd 6.0 machine with the latest DA installed.
My sites are down, no email I can not get in through putty anymore, I did a manual reboot through guys at the DC, no luck, drove there myself, 125 km's
Got the machine up, checked putty and sites while there, all seemed to work.
Then drove back home, only to find out it is all down again, have done the manual reboot through someone at the DC, managed to get in through putty, tried to get back to earlier version of php and shut dovecot out, cause I thought these caused the troubles.
No luck, now I am out again.
ONE Question, Is it possible to deinstall and get the machine back to work again?
thanks
Oliver
Hi,
Today I followed the instructions to the letter like in the first post. Installing version 1.1
I am on a freebsd 6.0 machine with the latest DA installed.
My sites are down, no email I can not get in through putty anymore, I did a manual reboot through guys at the DC, no luck, drove there myself, 125 km's
Got the machine up, checked putty and sites while there, all seemed to work.
Then drove back home, only to find out it is all down again, have done the manual reboot through someone at the DC, managed to get in through putty, tried to get back to earlier version of php and shut dovecot out, cause I thought these caused the troubles.
No luck, now I am out again.
ONE Question, Is it possible to deinstall and get the machine back to work again?
thanks
Oliver
httpd doesn't start after clean directadmin setup!!!
[root@server1-57 ~]# service httpd start
Starting httpd: fopen: No such file or directory
httpd: could not open document config file /etc/httpd/conf/extra/httpd-phpaddmodules.conf
[FAILED]
[root@server1-57 ~]# service httpd start
Starting httpd: fopen: No such file or directory
httpd: could not open document config file /etc/httpd/conf/extra/httpd-phpaddmodules.conf
[FAILED]
on the DA server I've had to protect two files by chattr command, they are:
/etc/httpd/conf/extra/httpd-suphp.conf
/usr/local/directadmin/custombuild/configure/suphp/configure.php5
the reason for the first file is we need to comment the line:
so as to setup a per-user php.ini according to http://help.directadmin.com/item.php?id=183
the reason for the second file is I have the line "--with-imap=/usr/local/imap-2000e" added to the file.
with every php recompile CustomBuild erases the above files and replaces them so these changes are lost unless we manually protect them. I have the idea that if CustomBuild tends to erase a file then it should be able to put these common setting and features back in place through it's own config file.
I don't know if it is making sense or not but I mean if CustomBuild removes these files then "Setup a per-user php.ini" and support for "imap with php" should already exist in CustomBuild so the admin would not have to go inside and immunize some files and perform hacks.
It might sound like this is a request for unlimited features but in fact common ones on productive servers are enough. on a server with 500 accounts that runs suphp there are at least 20 or 30 users that need custom php.ini and on a similar server with the same amount of accounts nowadays between 5 to 10 people require imap often for their helpdesks, this is what I am considering "common"
However if CustomBuild is not gonna support these, at least modification should be made to the code so it won't erase config files but instead it parses the file and makes needed changes to it and tries to compile, if then the config file looks bad and the compile is not successful it can erase the config file as a last resort.
I wish instead of just providing suggestions we could put some time and help with the developement of the tool!
/etc/httpd/conf/extra/httpd-suphp.conf
/usr/local/directadmin/custombuild/configure/suphp/configure.php5
the reason for the first file is we need to comment the line:
Code:
suPHP_ConfigPath /usr/local/etc/php5/cgi/the reason for the second file is I have the line "--with-imap=/usr/local/imap-2000e" added to the file.
with every php recompile CustomBuild erases the above files and replaces them so these changes are lost unless we manually protect them. I have the idea that if CustomBuild tends to erase a file then it should be able to put these common setting and features back in place through it's own config file.
I don't know if it is making sense or not but I mean if CustomBuild removes these files then "Setup a per-user php.ini" and support for "imap with php" should already exist in CustomBuild so the admin would not have to go inside and immunize some files and perform hacks.
It might sound like this is a request for unlimited features but in fact common ones on productive servers are enough. on a server with 500 accounts that runs suphp there are at least 20 or 30 users that need custom php.ini and on a similar server with the same amount of accounts nowadays between 5 to 10 people require imap often for their helpdesks, this is what I am considering "common"
However if CustomBuild is not gonna support these, at least modification should be made to the code so it won't erase config files but instead it parses the file and makes needed changes to it and tries to compile, if then the config file looks bad and the compile is not successful it can erase the config file as a last resort.
I wish instead of just providing suggestions we could put some time and help with the developement of the tool!
Last edited:
/usr/local/directadmin/custombuild/custom. There is a lot of info on DA forums and DA knowledgebase.