Now, my next problem, when installing, it only shows PARSER as a configureable module, and the install eventually fails.
Last lines of install_log are:
Fatal error: Call to undefined function: mysql_connect() in /usr/local/campsite/bin/create_instance.php on line 149
make: *** [default_instance] Error 255
The problem with WHICH is the same as the one on FreeBSD and I posted this
solution to bugzilla last week.
I tried to process instalation i a way
./configure --upgrade
make
make install
create instance .....
On FreeBSD process stops at make part.
Ondra
On Friday 15 April 2005 04:42, campsite-support@eserver2.mdlf.org wrote:
> This message was sent from: Campsite Support.
>
> ----------------------------------------------------------------
>
> SOLVED:
>
> This line in .install_conf/global_functions is the culprit (Line 229):
>
> [ "$WHICH" = "" ] && export WHICH=`which --skip-alias which 2> /dev/null`
>
> Debian's 'which' does not support the --skip-alias switch. replacing the
> line with:
>
> [ "$WHICH" = "" ] && export WHICH=`which which 2> /dev/null`
>
> Allows the install to continue.
>
> Now, my next problem, when installing, it only shows PARSER as a
> configureable module, and the install eventually fails.
>
> Last lines of install_log are:
>
> Fatal error: Call to undefined function: mysql_connect() in
> /usr/local/campsite/bin/create_instance.php on line 149
> make: *** [default_instance] Error 255
>
> Tod.
>
> ----------------------------------------------------------------
> Sent using Phorum software version 3.4.3a
------------------------------------------
Posted to Phorum via PhorumMail
> Debian's 'which' does not support the --skip-alias switch. replacing the
> line with:
> [ "$WHICH" = "" ] && export WHICH=`which which 2> /dev/null`
> Allows the install to continue.
Sorry, I should have fixed this for 2.2.0 but somehow I forgot to make the
changes to CVS.
> Now, my next problem, when installing, it only shows PARSER as a
> configureable module, and the install eventually fails.
Yes, the parser is the only configurable module at when installing the campsite
base. It's not an error. When creating instances the user has the option to
configure every module. Type: /usr/local/campsite/bin/create_instance --help
> Fatal error: Call to undefined function: mysql_connect() in
> /usr/local/campsite/bin/create_instance.php on line 149
> make: *** [default_instance] Error 255
Please install php-mysql extension; I'll modify the script to display a message
explaining what you have to install when this error poped up.
Mugur
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
------------------------------------------
Posted to Phorum via PhorumMail
> > Fatal error: Call to undefined function: mysql_connect() in
> > /usr/local/campsite/bin/create_instance.php on line 149
> > make: *** [default_instance] Error 255
> Please install php-mysql extension; I'll modify the script to
> display a message
> explaining what you have to install when this error poped up.
>
> Mugur
Phorum via PhorumMail
That confused me for a but until I realized I needed the CLI version of PHP4 to have MySQL access. Enabling mysql.so in the CLI version allowed the install to complete... however...
The install attempts to run create_instancew (as you know), but without ever asking for the database name, user, or password, and so botches the install.
Also, you shouldn't have "NameVirtualHost $SERVER_ADDRESS" in the vhost-template.conf file; Only one NameVirtualHost line should be present in most setups, and that should normally appear in the main apache .conf file. Having it appear more than once can cause unpredictable results (all my virtual hosts suddenly redirected to the default campsite host, for instance).
Also, the documentation says to fo to the URL http://campsite_install/admin/ but there is no admin directory. There's an admin-tools, and an admin.php, but no admin
> The install attempts to run create_instancew (as you know), but without
> ever asking for the database name, user, or password, and so botches the
> install.
The install script does not ask for detailed data about instance parameters;
for advanced users there is another method to install campsite:
./configure [--upgrade]
make
su
make install
/usr/local/campsite/bin/create_instance --db_name [instance_name]
[other_params]
> Also, you shouldn't have "NameVirtualHost $SERVER_ADDRESS" in the
> vhost-template.conf file; Only one NameVirtualHost line should be present
> in most setups, and that should normally appear in the main apache .conf
> file. Having it appear more than once can cause unpredictable results (all
> my virtual hosts suddenly redirected to the default campsite host, for
> instance).
Ok, thanks for advice
> Also, the documentation says to fo to the URL
> http://campsite_install/admin/ but there is no admin directory. There's an
> admin-tools, and an admin.php, but no admin
No need, apache will automatically call admin.php script when requesting:
http://[site_name]/admin/
Mugur
__________________________________
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail
------------------------------------------
Posted to Phorum via PhorumMail
> The install script does not ask for detailed data about
> instance parameters;
> for advanced users there is another method to install campsite:
>
> ./configure [--upgrade]
Which doesn't allow for setting of the web server user & group, that I saw. I just hunted around & edited the make.env file by hand, but that caused another problem when I went to create a new instance.
> make
> su
> make install
> /usr/local/campsite/bin/create_instance --db_name
> [instance_name]
> [other_params]
apparently install_conf.php gets set up at the same time as make.env, so changing make.env still left me with a broken install_conf.php after running through the install. No big deal, another quick edit & I was able to create instances. (Yes, I know I could have just supplied creat_instance with --apache_user and --apache_group every time I created a new instance, but that's not solving the problem, only working around it).
> Type:
> /usr/local/campsite/bin/create_instance --help
>
> to get a list of valid parameters.
Thank you
> > Also, the documentation says to fo to the URL
> > http://campsite_install/admin/ but there is no admin
> directory. There's an
> > admin-tools, and an admin.php, but no admin
> No need, apache will automatically call admin.php script when
> requesting:
> http://[site_name]/admin/
>
> Mugur
First, I apologise, I misinformed there... That should be 'admin-files', not 'admin-tools'
Umm... That isn't what's going on here. I get a 404 when I got to http://[site_name]/admin/
http://[site_name]/admin-files/ brings up a login screen, with a broken image (trying to load from http://[site_name]/admin/img/sign_big.gif which is impossible with no admin directory). Entering any user/pass (admin/admn00 or anything else) and clicking on LOGIN results in a blank page; the full HTML of which is [/body][/html] (I changed the brackets to not interfere with posting this).
Watching the MySQL log shows that no attempt is made to authenticate against the database.
(note: this almost seems like an exec-type of problem, I'm going to dig a little more & see if my server is allowing execution of CGIs & such in /usr/local/campsite. Hrmm).
Has anyone here been able to do a clean install of 2.2.0 yet and have it work? Maybe I'm just overlooking something, and I'll be the furst to admit I can be daft at times.
> Which doesn't allow for setting of the web server user & group, that I
> saw. I just hunted around & edited the make.env file by hand, but that
> caused another problem when I went to create a new instance.
Type:
make distclean
./install
Please set the web server user & group when asked if you wanted to modify the
install configuration. Go on with install. At the end of install you should get
something like:
--------------------------------------------------
STEP 2
Compiling sources (this may take a while, please wait)...done
The root password is needed in order to install campsite. Please supply
password.
Root password:
Preparing install environment...OK
Configuration done
> Umm... That isn't what's going on here. I get a 404 when I got to
> http://[site_name]/admin/
It means that you did not set the apache virtual host correctly. Please check
you apache configuration file. Look for NameVirtualHost. It must look like:
NameVirtualHost [my_ip_address]:80
Please make sure you edited the file:
/usr/local/campsite/etc/campsite/campsite-vhost.conf
and replaced $SERVER_ADDRESS with your server IP address, $SERVER_NAME with
apache virtual host name. This virtual host name must be registered in DNS,
otherwise it won't work. Now include the campsite-vhost.conf file from apache
main configuration file:
Include /usr/local/campsite/etc/campsite/campsite-vhost.conf
Restart apache.
> http://[site_name]/admin-files/ brings up a login screen, with a broken
> image (trying to load from http://[site_name]/admin/img/sign_big.gif which
> is impossible with no admin directory). Entering any user/pass
> (admin/admn00 or anything else) and clicking on LOGIN results in a blank
> page; the full HTML of which is [/body][/html]
I know it seems strange to you but http://[site_name]/admin/ and
http://[site_name]/admin/img/sign_big.gif should work even though there is no
admin directory. The admin.php script takes care of this. If it didn't work
it's an apache configuration problem.
> Watching the MySQL log shows that no attempt is made to authenticate
> against the database.
Do you have the PHP module installed and activated?
> Has anyone here been able to do a clean install of 2.2.0 yet and have it
> work? Maybe I'm just overlooking something, and I'll be the furst to admit
> I can be daft at times.
Actually yes, there are campsite 2.2.0 instances installed and working
Regards,
Mugur
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
------------------------------------------
Posted to Phorum via PhorumMail