PDA

View Full Version : Make not working in CB 1.2



tdldp
03-20-2008, 05:48 AM
For information, making exim 4-69 in debian, fails under Custombuild...

Yours
tdldp

Log :
File already exists: exim-4.69.tar.gz
File already exists: exim
File already exists: exim_freebsd
File already exists: exim_debian
Found /usr/local/directadmin/custombuild/exim-4.69.tar.gz
Extracting ...
Done.
--13:37:58-- http://files.directadmin.com/services/custombuild/Makefile
=> `Local/Makefile'
Resolving files.directadmin.com... 72.35.85.222
Connecting to files.directadmin.com|72.35.85.222|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 48,388 (47K) [text/plain]

100%[====================================>] 48,388 134.12K/s

13:37:59 (133.87 KB/s) - `Local/Makefile' saved [48388/48388]

Trying to make exim...

>>> Creating links to source files...
>>> New Makefile installed
>>> Use "make makefile" if you need to force rebuilding of the makefile

make[1]: Entering directory `/usr/local/directadmin/custombuild/exim-4.69/build-
Linux-i386'
/bin/sh ../scripts/Configure-os.h
/bin/sh ../scripts/Configure-os.c
gcc buildconfig.c
/bin/sh ../scripts/Configure-config.h "make"
make[2]: Entering directory `/usr/local/directadmin/custombuild/exim-4.69/build-
Linux-i386'
make[2]: `buildconfig' is up to date.
make[2]: Leaving directory `/usr/local/directadmin/custombuild/exim-4.69/build-L
inux-i386'
Building configuration file config.h
>>> config.h built

make[2]: Entering directory `/usr/local/directadmin/custombuild/exim-4.69/build-
Linux-i386/pcre'
gcc pcre_maketables.c
gcc pcre_chartables.c
gcc pcre_fullinfo.c
gcc pcre_get.c
gcc pcre_globals.c
gcc pcre_compile.c
gcc pcre_config.c
gcc pcre_exec.c
gcc pcre_newline.c
gcc pcre_study.c
gcc pcre_tables.c
gcc pcre_try_flipped.c
gcc pcre_version.c
rm -f libpcre.a
ar cq libpcre.a
ranlib libpcre.a
gcc pcretest.c
gcc -o ../pcretest pcretest.o libpcre.a
make[2]: Leaving directory `/usr/local/directadmin/custombuild/exim-4.69/build-L
inux-i386/pcre'

>>> exicyclog script built
>>> exinext script built
>>> exiwhat script built
>>> exigrep script built
>>> eximstats script built
>>> exipick script built
>>> exiqgrep script built
>>> exiqsumm script built
>>> transport-filter.pl script built
>>> convert4r3 script built
>>> convert4r4 script built
>>> exim_checkaccess script built

gcc exim_dbmbuild.c
In file included from exim.h:433,
from exim_dbmbuild.c:33:
dbstuff.h:103:16: error: db.h: No such file or directory
In file included from exim.h:433,
from exim_dbmbuild.c:33:
dbstuff.h:529: error: expected specifier-qualifier-list before 'DB'
exim_dbmbuild.c: In function 'main':
exim_dbmbuild.c:150: error: 'DB' undeclared (first use in this function)
exim_dbmbuild.c:150: error: (Each undeclared identifier is reported only once
exim_dbmbuild.c:150: error: for each function it appears in.)
exim_dbmbuild.c:150: error: 'd' undeclared (first use in this function)
exim_dbmbuild.c:151: error: 'DBT' undeclared (first use in this function)
exim_dbmbuild.c:151: error: expected ';' before 'key'
exim_dbmbuild.c:213: error: 'DB_HASH' undeclared (first use in this function)
exim_dbmbuild.c:295: error: 'content' undeclared (first use in this function)
exim_dbmbuild.c:298: error: 'key' undeclared (first use in this function)
exim_dbmbuild.c:298: error: 'R_NOOVERWRITE' undeclared (first use in this functi
on)
make[1]: *** [exim_dbmbuild.o] Error 1
make[1]: Leaving directory `/usr/local/directadmin/custombuild/exim-4.69/build-L
inux-i386'
make: *** [go] Error 2

*** The make has failed, do you want to try to make again? (y,n):

smtalk
03-20-2008, 06:25 AM
tdldp, make sure you have db4-devel installed.

tdldp
03-20-2008, 06:37 AM
I don't know if i have db4 devel.

How to's, and infos welcomed to install and check
EDITED : It seems that db4-devel is unknown under debian sarge apt-get system...
Exim 4.64 is already working under my system, using spamblocker, and i wonder why i now need berkeley db for it ???
Any way to install easily under debian ???

Tdldp

Following is another error :

Can not install php.ini because it is not set in options.conf.
great !!! BUT !
in options.conf, i have recommanded set ... php_ini=yes...
Followed guide though...

I know this is beta, but strangely i wouldn't say it works under debian classic installation...

smtalk
03-20-2008, 08:09 AM
apt-get install db4-dev


About the other problem - it will be fixed soon, for now just do the following changes to /usr/local/directadmin/custombuild/build file:

Find:

if [ "${PHPINI_OPT}" = "yes" ]; then
do_exit 1 "Can not install php.ini because it is not set in options.conf."
fi

Replace with:

if [ "${PHPINI_OPT}" = "no" ]; then
do_exit 1 "Can not install php.ini because it is not set in options.conf."
fi

tdldp
03-20-2008, 09:27 AM
apt-get install db4-dev



AS stated : under debian db4-dev is unknown...
venus:/usr/local/directadmin/custombuild# apt-get install db4-dev
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package db4-dev

which package list do u use ???

edited : For solution to install db4-dev...

apt-get install libdb4.4-dev

tdldp
03-25-2008, 03:06 AM
i must be damned...
Custombuild has messed up completely normal domain functionning under directadmin...

From now on, i can't chmod any user files from user ftp access.
All public_html directories, are set to owner : user group : apache
files are not chmodable and this is giving me a headache trying to find where to set back automatic ftp chmod access to all users...

Thks for help...
And last time i test something supposably supported in directadmin forums...

smtalk
03-25-2008, 04:28 AM
You can't edit apache owned files, because it's not ftp user owned files. You can reset the ownership using DirectAdmin file manager.

tdldp
03-25-2008, 06:13 AM
You can't edit apache owned files, because it's not ftp user owned files. You can reset the ownership using DirectAdmin file manager.

Ok but problem : Owner of files is user, group is apache... thus, why doesn't ftp manage correctly rights on file... (owner has rwx rights)

furthermore, since custombuild, awstats plugin doesn't function neither :

Warning: opendir(): SAFE MODE Restriction in effect. The script whose uid is 108 is not allowed to access /home/[user]/domains/ owned by uid 1034 in /usr/local/directadmin/plugins/awstats/user/index.html on line 10 Warning: opendir(/home/[user]/domains/): failed to open dir: Inappropriate ioctl for device in /usr/local/directadmin/plugins/awstats/user/index.html on line 10 Warning: readdir(): supp

there again, i guess it's group rights problem... (since apache updated..)

tdldp
03-25-2008, 07:28 AM
and one more...
After correcting db4 devel problem... new one on exim 4.69 !

make[2]: *** [cyrus_sasl.o] Error 1
make[2]: Leaving directory `/usr/local/directadmin/custombuild/exim-4.69/build-Linux-i386/auths'

make[1]: *** No rule to make target `auths/auths.a', needed by `exim'. Stop.
make[1]: Leaving directory `/usr/local/directadmin/custombuild/exim-4.69/build-Linux-i386'
make: *** [go] Error 2

smtalk
03-25-2008, 10:06 AM
Ok but problem : Owner of files is user, group is apache... thus, why doesn't ftp manage correctly rights on file... (owner has rwx rights)

furthermore, since custombuild, awstats plugin doesn't function neither :

Warning: opendir(): SAFE MODE Restriction in effect. The script whose uid is 108 is not allowed to access /home/[user]/domains/ owned by uid 1034 in /usr/local/directadmin/plugins/awstats/user/index.html on line 10 Warning: opendir(/home/[user]/domains/): failed to open dir: Inappropriate ioctl for device in /usr/local/directadmin/plugins/awstats/user/index.html on line 10 Warning: readdir(): supp

there again, i guess it's group rights problem... (since apache updated..)

http://directadmin.com/forum/showpost.php?p=127152&postcount=4

About the safe mode - it's a personal setting, CustomBuild doesn't edit your php.ini file. Edit /usr/local/lib/php.ini and turn safe_mode off.

tdldp
03-26-2008, 04:03 AM
http://directadmin.com/forum/showpost.php?p=127152&postcount=4

About the safe mode - it's a personal setting, CustomBuild doesn't edit your php.ini file. Edit /usr/local/lib/php.ini and turn safe_mode off.

yes i doubt it is personnal setting, and that custombuild is not there to tweak settings... (i manually maintain servers other than the 2 using directadmin as panel software, and know how to edit), but if this was set on by default under directadmin, is it good to turn it off ??? (will it generate new problems to DA for which i have difficulty to know the depth of its action in all services).

Yours..

tdldp
03-26-2008, 04:34 AM
Follow up :

I have managed to :

Build php 5 with following options :

#PHP settings. default_php possible values - 5 or 6
default_php=5
php5_cli=no
php5_cgi=yes
php6_cli=no
php6_cgi=no
php_ini=yes
#Possible values - recommended or dist
php_ini_type=recommended
zend=yes

#Possible values - 4.1, 5.0 or 5.1
mysql=5.0
mysql_inst=yes
mysql_backup=yes

#Possible values - 1.3, 2.0 or 2.2
apache_ver=2.2

su_php is set after a build suphp following method...

I now have following problem :

short tags not answering... ok go in php.ini and set it to on... restart httpd, and still same problem...
On on domain, (a particular thing that needed forking), i have an error 500 on the domain....

1° : Where is php.ini ???
a whereis php.ini gives me : /usr/local/lib and in it a symlink php.ini ... how do i follow symlink and how do i know if it works???

2° Is it becauses i've setup zend (which i wan't to give a try), and that is tells me it changes php.ini location, that i can't modify php.ini like i wish ??? If yes where do i make the changes to set back on short tags ???
EDITED Nothing to do : When install under CGI : php.ini is located apparently by default under : /usr/local/etc/php5/cgi
edited php.ini solved short tags problem and other php configuration problems...
My two pence idea is that php.ini should be parsed from previous locations and content reused in new php.ini version...

3° : How do i solve that error 500 ???
EDITED : After Log control, changed rights on public_html to 755 (maximum) instead of 777... Solved issues... (Suphp chmod 755 requirements)

EDITED :
4° Still having chmod problems on server...
tried fixes, but changes nothing... next post will be some logs...

Thanks for you help, i'm getting nuts with this...

Tdldp

tdldp
03-26-2008, 11:26 AM
There seems to be a stable state on server following installs...

Yet i have the following problems consecutive to installs :

Squirrelmail : (updated via custombuild)
ERROR
Error opening ../data/default_pref
Default preference file not found or not readable!
Please contact your system administrator and report this error.

webmail : (uebimiau)
ERROR (2): chmod() [function.chmod]: Operation not permitted (/webmail/smarty/Smarty.class.php:1456)

.htaccess :
Url rewriting, is not working anymore for our clients...

Directadmin Skins :
I use a mail only skin called Cliomail, which doesn't function anymore :

Warning: You have incorrect skin configuration. Please edit "ca/config.html" line that starts with |?CA_ROOT= and replace "admin" with your username or update to latest DirectAdmin.

To edit it you might need to set correct permissions first.

Then click here to edit config.html

If you don't want to edit config.html you can just reset skin. To reset skin click here (but better just simply edit one line in ca/config.html)


When i edit file : http://IP:2222/CMD_FILE_MANAGER/skins/cliomail/ca/config.html?action=edit
i get :



|?CA_SKIN=ClioMail|
|?CA_VERSION=1.05|
|?CA_DAVERSION=1.22.2|
|?CA_LANGVERSION=1.16|
|?CA_PHP=/usr/local/bin/php|
|?CA_ROOT=/usr/local/directadmin/data/skins/`SKIN`/|
|?MIN_USERNAME_LENGTH=3|


and i replace by :


|?CA_SKIN=ClioMail|
|?CA_VERSION=1.05|
|?CA_DAVERSION=1.22.2|
|?CA_LANGVERSION=1.16|
|?CA_PHP=/usr/local/php5/bin/php-cgi|
|?CA_ROOT=/usr/local/directadmin/data/skins/`SKIN`/|
|?MIN_USERNAME_LENGTH=3|


I get error : Status: 500 Internal Server Error X-Powered-By: PHP/5.2.5 Content-type: text/html

More to come

smtalk
03-26-2008, 02:21 PM
The cause of all problems is PHP5 as CGI, because you don't know how to use it. Use PHP5 as CLI or read more documentation (PHP files needs to be executed as user:user, so a fix for e.g. squirrelmail would be "chown -R webapps:webapps /var/www/html/squirrelmail").

tdldp
03-27-2008, 10:50 AM
These new messages on setting password in plugin awstats :

Warning: fopen(/etc/awstats/awstats.domain.fr.conf): failed to open stream: Permission denied in /usr/local/directadmin/plugins/awstats/user/options.php on line 45 Warning: fwrite(): supplied argument is not a valid stream resource in /usr/local/directadmin/plugins/awstats/user/options.php on line 53 Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/directadmin/plugins/awstats/user/options.php on line 54 Password protected!

Furthermore :

when entrying in http://domain.fr/awstats and after entering login / password,
i get this :

Error: AWStats database directory defined in config file by 'DirData' parameter (/home/girard/domains/domain.fr/stats/) does not exist or is not writable.

Setup ('/etc/awstats/awstats.domain.fr.conf' file, web server or permissions) may be wrong.
Check config file, permissions and AWStats documentation (in 'docs' directory).

And indeed in /home/girard/domains/domain.fr/ the directory awstats is not created anymore...


I still have no FTP user rights on file to chmod, and modify files that need to be uploaded on the server... I upload a user.sh file that is called by unzip.php (shell script running on server) and a photo directory for which i need to put on chmod 777 . Our users can also upload files and sh scripts that need to be chmoded and their are refused systematically.


Finally your answer on which all problems is due to PHP5 on cgi, is a bit ubiquous... I had first installed php5 on CLI. It messed up the box. For those right problems, you pointed a note to lookup knowledgebase. Which specifically says : No problem, change to php5 on cgi. It is even given with howto, and most of all no advertisement from directadmin that changing to cgi will break more things than it solves... Now you tell me pass back to CLI. but at no moment the right problems that were totally inexistant before custombuild, (and running therefore under the normal php4 install with directadmin), are solved....

Follow up will follow as i finish this evening pointing out everything that still disfunctions following custombuild use

Tdldp

smtalk
03-27-2008, 01:52 PM
It (PHP 5 as CLI) could mess your server if you didn't use "./build all d" for the first time.

tdldp
03-28-2008, 02:16 AM
It (PHP 5 as CLI) could mess your server if you didn't use "./build all d" for the first time.

and this is not in the FAQ ???? Am i an idiot or what ??? I know how to read, and before custombuild, i RTFM completely, and did not have this probably most precious information !!!!

U know what is missing in your FAQ in N°3 :

After installing, basic standard howto (i supposed most of us want : PHP5 (AS CLI)/ Mysql 5 / phpmyadmin / uebimiau / roundcube / squirrelmail / exim by default on the server...) with :

All prenecessary commands like a "./build all d" for the first run in PHP5 as CLI, and all necessary information that could make any reasonnable person take precautions before going in migration !!!! (And commands for other php modes, because i suppose each modes has it's prerequisites)

And in other Faq N° : Precautions to take, tweaking options and consequences (because u know them better than other users who will want to give custombuild a try)

I still think custombuild is a great thing, even if it messed up completely my box... but i think for moment, that the project is not user oriented, just a bit admin's oriented, and again not that much : I mean I can't afford to know every tips for my servers under Fedora , CentOs, Debian and Windows...)

Tdldp

smtalk
03-28-2008, 06:57 AM
Thank you, it's added to the CustomBuild FAQ now. It was mentioned here: http://files.directadmin.com/services/custombuild/1.1.

tdldp
04-06-2008, 10:17 AM
Thank you, it's added to the CustomBuild FAQ now. It was mentioned here: http://files.directadmin.com/services/custombuild/1.1.

great... but i did all from FAQ.... and with 1.2 not 1.1...

Nearly all problems are solved today...
My last worry, and not less is FTP chmoding...
It isn't worling anymore, since using first custombuild...

i get these errors :
SITE CHMOD 744 admin_promo.php
550 CHMOD 744 admin_promo.php: No such file or directory
This server doesn't support attribute modifications.
Failed [Server doesn't support attribute modifications]

Users can't modify their rights anymore, and this is a MAJOR dysfunction since custombuild...

EDITED : For those having this problem... Update of proftpd install a conf file (/etc/proftpd.conf) which contains :

<Limit SITE_CHMOD>
DenyAll
</Limit>

I just commented out this command, and solved this last but not least problem...

What a mess, but glad to have finished solving this out...

tdldp
04-07-2008, 12:49 AM
Had Talked too fast...

A theme problem still happens...

I have a mail only (cliomail) theme, running... This theme since custombuild (or apache 2 maybe) is dysfunctionning...

error is :
Status: 500 Internal Server Error X-Powered-By: PHP/5.2.5 Content-type: text/html


I suppose it's once more right problems, but checking files gives me a 755 right on all files... (correct for usage..)

What is this problem ???

Tdldp

smtalk
04-07-2008, 01:45 AM
Try chown -R webapps:webapps /full/path/to/cliomail

tdldp
04-18-2008, 08:11 AM
Try chown -R webapps:webapps /full/path/to/cliomail

Sorry to insist, but after various tests including : using skin under /home/admin/skins, using skin under /usr/local/directadmin/data/skins, and chmoding / Chrooting directory and files correctly, i still get that :
Status: 500 Internal Server Error X-Powered-By: PHP/5.2.5 Content-type: text/html

error...

I know custombuild is not in cause at this stage (it is purely a Apache 2 problem) but where could the problem be ???

Yours

tdldp
04-25-2008, 03:49 AM
SOLVED :

This Thread is now closed having found ALL solutions for my problems...

For cliomail users experimenting problems with skin responding error 500...

Check in /ca/config.html your :

|?CA_PHP=/path/to/php5/|

In my case, i had to switch :

|?CA_PHP=/usr/local/php5/bin/php-cgi|
to
|?CA_PHP=/usr/local/php5/bin/php|

to make Skin work...

So To conclude, with this product CustomBuild, i'd say it's a good idea, but absolutely not user nor newbie admin level oriented...
After using, lots of tweeking is necessary to solve problems...

will-lo
08-19-2010, 09:43 PM
may I get a copy of Cliomail please? the download link is not working anymore.