Quantcast

installation error 500

classic Classic list List threaded Threaded
34 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

installation error 500

Kévin Laîné
Hi Foswiki team and other

I've done all the install instruction on my shared hoster (with redhat), and on my own computer (with ubuntu).
and when I enter the "domain.com" and "localhost" I have the page "Welcome to Foswiki - Follow one of the below links to get started ..."

When clicking on Main.WebHome and bin/view :

On domain.com => Internal Server Error 500
On localhost => I have a text file "
#! /usr/bin/env perl
# See bottom of file for license and copyright information
use strict;
use warnings;

use File::Spec;

BEGIN {
    if ( defined $ENV{GATEWAY_INTERFACE} || defined $ENV{MOD_PERL} ) {
        $Foswiki::cfg{Engine} = 'Foswiki::Engine::CGI';
        use CGI::Carp qw(fatalsToBrowser);
        $SIG{__DIE__} = \&CGI::Carp::confess;
[...]

What is the problem ?

Thanks

Kévin
(french)

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Oliver Krüger-2
Hello Kevin,

thats hard to tell from the distance without further details. An error code 500 indicates a problem on the server side. That could be anything: insufficient access rights for the (perl) script, a crashing (perl) handler, whatever. The next step would be: look into the (error) log files of your webserver. Details on the reason for the 500 should be in there.

On your localhost you get the plain perl skript (instead the its output) because that perticular URL you entered was not interpreted as a perl script. You either have no perl installed or did not tell your webserver to treat files below foswiki/bin/* as perl scripts. We need to know which webserver you use (nginx, apache, lighttpd,… ) and how its configuration looks like in order to help you,

Kind regards,
Oliver



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Kévin Laîné
Thanks Olivier.

I put some information for people who can help me to find solution.


On shared hoster Web4all, I'm on Linux http1-apache, Server API: CGI/FastCGI
I'm using .htaccess as indicate on foswiki instruction
Here is vhost configuration :
# Generated by IWAL 20160204-14:02:25
<VirtualHost *:80>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
    ErrorLog /datas/log/apache2-vhosts/test.cir.re-error.log
    CustomLog /datas/log/apache2-vhosts/test.cir.re-combined.log combined
    Redirect /stats http://test.cir.re/awstats/awstats.pl
    # NO FW
    Alias /errors /datas/vol3/w4a178348/var/www/test.cir.re/errors
    ErrorDocument 401 /errors/401.php
    ErrorDocument 403 /errors/403.php
    ErrorDocument 404 /errors/404.php
    ErrorDocument 500 /errors/500.php
    ScriptAlias /awstats /opt/wrapper/awstats/
    ScriptAlias /cgi-bin /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin
        <Directory /opt/wrapper/awstats/>
            Options ExecCGI
            AddHandler cgi-script .pl
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
            AuthType Basic
            AuthName Statistiques
            AuthUserFile /datas/vol3/w4a178348/var/awstats/test.cir.re/test.cir.re.pwd
            Require valid-user
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin>
            Options ExecCGI
            AddHandler cgi-script .pl .fcgi .cgi
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/htdocs>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/errors>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
</VirtualHost>

<VirtualHost *:443>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
    ErrorLog /datas/log/apache2-vhosts/test.cir.re-error.log
    CustomLog /datas/log/apache2-vhosts/test.cir.re-combined.log combined
    Redirect /stats https://test.cir.re/awstats/awstats.pl
    SetEnv HTTPS on
    Alias /errors /datas/vol3/w4a178348/var/www/test.cir.re/errors
    ErrorDocument 401 /errors/401.php
    ErrorDocument 403 /errors/403.php
    ErrorDocument 404 /errors/404.php
    ErrorDocument 500 /errors/500.php
    ScriptAlias /awstats /opt/wrapper/awstats/
    ScriptAlias /cgi-bin /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin
        <Directory /opt/wrapper/awstats/>
            Options ExecCGI
            AddHandler cgi-script .pl
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
            AuthType Basic
            AuthName Statistiques
            AuthUserFile /datas/vol3/w4a178348/var/awstats/test.cir.re/test.cir.re.pwd
            Require valid-user
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin>
            Options ExecCGI
            AddHandler cgi-script .pl .fcgi .cgi
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/htdocs>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/errors>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
</VirtualHost>

when entering "perl tools/dependencies"

Content-type: text/plain

**** ERROR ****
The following critical dependencies are missing from your installation:
 ... CGI: Can't locate CGI.pm in @INC
 ... CGI::Session: Can't locate CGI/Session.pm in @INC
 ... Crypt::PasswdMD5: Can't locate Crypt/PasswdMD5.pm in @INC
 ... File::Copy::Recursive: Can't locate File/Copy/Recursive.pm in @INC
 ... JSON: Can't locate JSON.pm in @INC

Please install these modules and then ensure all dependencies are installed by either:
 -  viewing the System.PerlDependencyReport in your local Foswki,  or
 -  running the CLI shell script tools/dependencies from your server's command line.
You can get a complete list of Perl module dependencies by viewing System.SystemRequirements
on your local system or at http://foswiki.org/System/SystemRequirements.

Foswiki will not operate correctly unless the required dependencies are installed.

Your current library search path @INC contains:

   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/lib
   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/tools/../bin
   /usr/local/lib64/perl5
   /usr/local/share/perl5
   /usr/lib64/perl5/vendor_perl
   /usr/share/perl5/vendor_perl
   /usr/lib64/perl5
   /usr/share/perl5
   .
   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/lib/CPAN/lib

You can adjust the search path by editing bin/LocalLib.cfg


perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
2.02

perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'
1.1901

__________________________________________________
__________________________________________________
__________________________________________________

On my local host

Ubuntu 14.04 with Apache 2.0 Handler

Installed
apt-get install apache2 rcs libalgorithm-diff-perl libarchive-tar-perl libauthen-sasl-perl libcgi-pm-perl libcgi-session-perl libcrypt-passwdmd5-perl libdigest-sha-perl libemail-mime-perl libencode-perl liberror-perl libfile-copy-recursive-perl libhtml-parser-perl libhtml-tree-perl libio-socket-ip-perl libio-socket-ssl-perl libjson-perl liblocale-maketext-perl liblocale-maketext-lexicon-perl liblocale-msgfmt-perl libwww-perl liburi-perl libversion-perl

when entering "perl tools/dependencies"
[...]
Extensions and Perl modules used by installed Extensions:
     Apache::Request      Apache::Request is not installed.
        ModPerlEngineContrib: Optional Recommended if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib    
     FCGI::ProcManager      FCGI::ProcManager is not installed.
        FastCGIEngineContrib: Optional Required on nginx for dynamic FCGI handler management. Used by: FastCGIEngineContrib    
     mod_perl      mod_perl is not installed.
        ModPerlEngineContrib: Required  if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib

perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
2.02

perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'
1.2300


Thank you for helping if possible.

Kévin



Le Jeudi 4 février 2016 13h12, Oliver Krüger <[hidden email]> a écrit :


Hello Kevin,

thats hard to tell from the distance without further details. An error code 500 indicates a problem on the server side. That could be anything: insufficient access rights for the (perl) script, a crashing (perl) handler, whatever. The next step would be: look into the (error) log files of your webserver. Details on the reason for the 500 should be in there.

On your localhost you get the plain perl skript (instead the its output) because that perticular URL you entered was not interpreted as a perl script. You either have no perl installed or did not tell your webserver to treat files below foswiki/bin/* as perl scripts. We need to know which webserver you use (nginx, apache, lighttpd,… ) and how its configuration looks like in order to help you,

Kind regards,
Oliver





------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Chris Hoefler
Hi Kevin,
 
On shared hoster Web4all, I'm on Linux http1-apache, Server API: CGI/FastCGI
I'm using .htaccess as indicate on foswiki instruction
Here is vhost configuration :
# Generated by IWAL 20160204-14:02:25
<VirtualHost *:80>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
I notice that you are mixing in php scripts with this vhost. Are you you doing that on purpose? Foswiki is a Perl-based application, so it doesn't need php, and I generally wouldn't recommend mixing two applications (one php, one perl) together on one vhost. It makes your configuration harder to maintain, and it opens you up to some severe security vulnerabilities if you aren't careful.

**** ERROR ****
The following critical dependencies are missing from your installation:
 ... CGI: Can't locate CGI.pm in @INC
 ... CGI::Session: Can't locate CGI/Session.pm in @INC
 ... Crypt::PasswdMD5: Can't locate Crypt/PasswdMD5.pm in @INC
 ... File::Copy::Recursive: Can't locate File/Copy/Recursive.pm in @INC
 ... JSON: Can't locate JSON.pm in @INC

This is the reason your Foswiki installation isn't working on your vhost. You need to install these perl dependencies. Installing from the package manager is preferable, but if your hosting provider doesn't allow it, you can use cpan and install to a local::lib.

No idea what is wrong with your localhost, but I suspect you haven't enabled ExecCGI in the Foswiki /bin directory. Can you post the configuration file and the contents of /etc/apache2/mods-enabled?

On Thu, Feb 4, 2016 at 8:21 AM, Kévin Laîné <[hidden email]> wrote:
Thanks Olivier.

I put some information for people who can help me to find solution.


On shared hoster Web4all, I'm on Linux http1-apache, Server API: CGI/FastCGI
I'm using .htaccess as indicate on foswiki instruction
Here is vhost configuration :
# Generated by IWAL 20160204-14:02:25
<VirtualHost *:80>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
    ErrorLog /datas/log/apache2-vhosts/test.cir.re-error.log
    CustomLog /datas/log/apache2-vhosts/test.cir.re-combined.log combined
    Redirect /stats http://test.cir.re/awstats/awstats.pl
    # NO FW
    Alias /errors /datas/vol3/w4a178348/var/www/test.cir.re/errors
    ErrorDocument 401 /errors/401.php
    ErrorDocument 403 /errors/403.php
    ErrorDocument 404 /errors/404.php
    ErrorDocument 500 /errors/500.php
    ScriptAlias /awstats /opt/wrapper/awstats/
    ScriptAlias /cgi-bin /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin
        <Directory /opt/wrapper/awstats/>
            Options ExecCGI
            AddHandler cgi-script .pl
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
            AuthType Basic
            AuthName Statistiques
            AuthUserFile /datas/vol3/w4a178348/var/awstats/test.cir.re/test.cir.re.pwd
            Require valid-user
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin>
            Options ExecCGI
            AddHandler cgi-script .pl .fcgi .cgi
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/htdocs>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/errors>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
</VirtualHost>

<VirtualHost *:443>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
    ErrorLog /datas/log/apache2-vhosts/test.cir.re-error.log
    CustomLog /datas/log/apache2-vhosts/test.cir.re-combined.log combined
    Redirect /stats https://test.cir.re/awstats/awstats.pl
    SetEnv HTTPS on
    Alias /errors /datas/vol3/w4a178348/var/www/test.cir.re/errors
    ErrorDocument 401 /errors/401.php
    ErrorDocument 403 /errors/403.php
    ErrorDocument 404 /errors/404.php
    ErrorDocument 500 /errors/500.php
    ScriptAlias /awstats /opt/wrapper/awstats/
    ScriptAlias /cgi-bin /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin
        <Directory /opt/wrapper/awstats/>
            Options ExecCGI
            AddHandler cgi-script .pl
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
            AuthType Basic
            AuthName Statistiques
            AuthUserFile /datas/vol3/w4a178348/var/awstats/test.cir.re/test.cir.re.pwd
            Require valid-user
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin>
            Options ExecCGI
            AddHandler cgi-script .pl .fcgi .cgi
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/htdocs>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/errors>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
</VirtualHost>

when entering "perl tools/dependencies"

Content-type: text/plain

**** ERROR ****
The following critical dependencies are missing from your installation:
 ... CGI: Can't locate CGI.pm in @INC
 ... CGI::Session: Can't locate CGI/Session.pm in @INC
 ... Crypt::PasswdMD5: Can't locate Crypt/PasswdMD5.pm in @INC
 ... File::Copy::Recursive: Can't locate File/Copy/Recursive.pm in @INC
 ... JSON: Can't locate JSON.pm in @INC

Please install these modules and then ensure all dependencies are installed by either:
 -  viewing the System.PerlDependencyReport in your local Foswki,  or
 -  running the CLI shell script tools/dependencies from your server's command line.
You can get a complete list of Perl module dependencies by viewing System.SystemRequirements
on your local system or at http://foswiki.org/System/SystemRequirements.

Foswiki will not operate correctly unless the required dependencies are installed.

Your current library search path @INC contains:

   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/lib
   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/tools/../bin
   /usr/local/lib64/perl5
   /usr/local/share/perl5
   /usr/lib64/perl5/vendor_perl
   /usr/share/perl5/vendor_perl
   /usr/lib64/perl5
   /usr/share/perl5
   .
   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/lib/CPAN/lib

You can adjust the search path by editing bin/LocalLib.cfg


perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
2.02

perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'
1.1901

__________________________________________________
__________________________________________________
__________________________________________________

On my local host

Ubuntu 14.04 with Apache 2.0 Handler

Installed
apt-get install apache2 rcs libalgorithm-diff-perl libarchive-tar-perl libauthen-sasl-perl libcgi-pm-perl libcgi-session-perl libcrypt-passwdmd5-perl libdigest-sha-perl libemail-mime-perl libencode-perl liberror-perl libfile-copy-recursive-perl libhtml-parser-perl libhtml-tree-perl libio-socket-ip-perl libio-socket-ssl-perl libjson-perl liblocale-maketext-perl liblocale-maketext-lexicon-perl liblocale-msgfmt-perl libwww-perl liburi-perl libversion-perl

when entering "perl tools/dependencies"
[...]
Extensions and Perl modules used by installed Extensions:
     Apache::Request      Apache::Request is not installed.
        ModPerlEngineContrib: Optional Recommended if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib    
     FCGI::ProcManager      FCGI::ProcManager is not installed.
        FastCGIEngineContrib: Optional Required on nginx for dynamic FCGI handler management. Used by: FastCGIEngineContrib    
     mod_perl      mod_perl is not installed.
        ModPerlEngineContrib: Required  if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib

perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
2.02

perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'
1.2300


Thank you for helping if possible.

Kévin



Le Jeudi 4 février 2016 13h12, Oliver Krüger <[hidden email]> a écrit :


Hello Kevin,

thats hard to tell from the distance without further details. An error code 500 indicates a problem on the server side. That could be anything: insufficient access rights for the (perl) script, a crashing (perl) handler, whatever. The next step would be: look into the (error) log files of your webserver. Details on the reason for the 500 should be in there.

On your localhost you get the plain perl skript (instead the its output) because that perticular URL you entered was not interpreted as a perl script. You either have no perl installed or did not tell your webserver to treat files below foswiki/bin/* as perl scripts. We need to know which webserver you use (nginx, apache, lighttpd,… ) and how its configuration looks like in order to help you,

Kind regards,
Oliver





------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss




--
Chris Hoefler, PhD
Postdoctoral Research Associate
Straight Lab
Texas A&M University
2128 TAMU
College Station, TX 77843-2128

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Kévin Laîné
Thank you Chris

ok I understand now that php is not needed for foswiki ...
I can't install module on shared hoster and explanation for local install of module on => http://foswiki.org/Support/HowToInstallCpanModules
doesn't really work.

this command can't be execute
curl -L https://cpanmin.us | perl - App::cpanminus
but perl was announce to be support by my hoster, so I don't understand.

For my localhost, under the directory you asked and then my apache2.conf

lrwxrwxrwx 1 root root 36 févr.  1 23:34 access_compat.load -> ../mods-available/access_compat.load
lrwxrwxrwx 1 root root 28 févr.  1 23:34 alias.conf -> ../mods-available/alias.conf
lrwxrwxrwx 1 root root 28 févr.  1 23:34 alias.load -> ../mods-available/alias.load
lrwxrwxrwx 1 root root 29 févr.  2 00:15 apreq2.load -> ../mods-available/apreq2.load
lrwxrwxrwx 1 root root 33 févr.  1 23:34 auth_basic.load -> ../mods-available/auth_basic.load
lrwxrwxrwx 1 root root 33 févr.  1 23:34 authn_core.load -> ../mods-available/authn_core.load
lrwxrwxrwx 1 root root 33 févr.  1 23:34 authn_file.load -> ../mods-available/authn_file.load
lrwxrwxrwx 1 root root 33 févr.  1 23:34 authz_core.load -> ../mods-available/authz_core.load
lrwxrwxrwx 1 root root 33 févr.  1 23:34 authz_host.load -> ../mods-available/authz_host.load
lrwxrwxrwx 1 root root 33 févr.  1 23:34 authz_user.load -> ../mods-available/authz_user.load
lrwxrwxrwx 1 root root 32 févr.  1 23:34 autoindex.conf -> ../mods-available/autoindex.conf
lrwxrwxrwx 1 root root 32 févr.  1 23:34 autoindex.load -> ../mods-available/autoindex.load
lrwxrwxrwx 1 lint lint 37 févr.  4 20:00 cgid.conf -> /etc/apache2/mods-available/cgid.conf
lrwxrwxrwx 1 lint lint 37 févr.  4 20:00 cgid.load -> /etc/apache2/mods-available/cgid.load
lrwxrwxrwx 1 root root 26 févr.  2 00:17 cgi.load -> ../mods-available/cgi.load
lrwxrwxrwx 1 root root 30 févr.  1 23:34 deflate.conf -> ../mods-available/deflate.conf
lrwxrwxrwx 1 root root 30 févr.  1 23:34 deflate.load -> ../mods-available/deflate.load
lrwxrwxrwx 1 root root 26 févr.  1 23:34 dir.conf -> ../mods-available/dir.conf
lrwxrwxrwx 1 root root 26 févr.  1 23:34 dir.load -> ../mods-available/dir.load
lrwxrwxrwx 1 root root 26 févr.  1 23:34 env.load -> ../mods-available/env.load
lrwxrwxrwx 1 root root 29 févr.  1 23:34 filter.load -> ../mods-available/filter.load
lrwxrwxrwx 1 root root 27 févr.  1 23:34 mime.conf -> ../mods-available/mime.conf
lrwxrwxrwx 1 root root 27 févr.  1 23:34 mime.load -> ../mods-available/mime.load
lrwxrwxrwx 1 root root 34 févr.  1 23:35 mpm_prefork.conf -> ../mods-available/mpm_prefork.conf
lrwxrwxrwx 1 root root 34 févr.  1 23:35 mpm_prefork.load -> ../mods-available/mpm_prefork.load
lrwxrwxrwx 1 root root 34 févr.  1 23:34 negotiation.conf -> ../mods-available/negotiation.conf
lrwxrwxrwx 1 root root 34 févr.  1 23:34 negotiation.load -> ../mods-available/negotiation.load
lrwxrwxrwx 1 root root 27 févr.  2 00:15 perl.load -> ../mods-available/perl.load
lrwxrwxrwx 1 root root 27 févr.  1 23:35 php5.conf -> ../mods-available/php5.conf
lrwxrwxrwx 1 root root 27 févr.  1 23:35 php5.load -> ../mods-available/php5.load
lrwxrwxrwx 1 root root 30 févr.  2 00:16 rewrite.load -> ../mods-available/rewrite.load
lrwxrwxrwx 1 root root 31 févr.  1 23:34 setenvif.conf -> ../mods-available/setenvif.conf
lrwxrwxrwx 1 root root 31 févr.  1 23:34 setenvif.load -> ../mods-available/setenvif.load
lrwxrwxrwx 1 root root 29 févr.  1 23:34 status.conf -> ../mods-available/status.conf
lrwxrwxrwx 1 root root 29 févr.  1 23:34 status.load -> ../mods-available/status.load



# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#    /etc/apache2/
#    |-- apache2.conf
#    |    `--  ports.conf
#    |-- mods-enabled
#    |    |-- *.load
#    |    `-- *.conf
#    |-- conf-enabled
#    |    `-- *.conf
#     `-- sites-enabled
#         `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Require all denied
</Directory>

<Directory /usr/share>
    AllowOverride None
    Require all granted
</Directory>

<Directory /var/www/>
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
</Directory>

#<Directory /srv/>
#    Options Indexes FollowSymLinks
#    AllowOverride None
#    Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
    Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet


Le Jeudi 4 février 2016 19h30, Chris Hoefler <[hidden email]> a écrit :


Hi Kevin,
 
On shared hoster Web4all, I'm on Linux http1-apache, Server API: CGI/FastCGI
I'm using .htaccess as indicate on foswiki instruction
Here is vhost configuration :
# Generated by IWAL 20160204-14:02:25
<VirtualHost *:80>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
I notice that you are mixing in php scripts with this vhost. Are you you doing that on purpose? Foswiki is a Perl-based application, so it doesn't need php, and I generally wouldn't recommend mixing two applications (one php, one perl) together on one vhost. It makes your configuration harder to maintain, and it opens you up to some severe security vulnerabilities if you aren't careful.

**** ERROR ****
The following critical dependencies are missing from your installation:
 ... CGI: Can't locate CGI.pm in @INC
 ... CGI::Session: Can't locate CGI/Session.pm in @INC
 ... Crypt::PasswdMD5: Can't locate Crypt/PasswdMD5.pm in @INC
 ... File::Copy::Recursive: Can't locate File/Copy/Recursive.pm in @INC
 ... JSON: Can't locate JSON.pm in @INC

This is the reason your Foswiki installation isn't working on your vhost. You need to install these perl dependencies. Installing from the package manager is preferable, but if your hosting provider doesn't allow it, you can use cpan and install to a local::lib.

No idea what is wrong with your localhost, but I suspect you haven't enabled ExecCGI in the Foswiki /bin directory. Can you post the configuration file and the contents of /etc/apache2/mods-enabled?

On Thu, Feb 4, 2016 at 8:21 AM, Kévin Laîné <[hidden email]> wrote:
Thanks Olivier.

I put some information for people who can help me to find solution.


On shared hoster Web4all, I'm on Linux http1-apache, Server API: CGI/FastCGI
I'm using .htaccess as indicate on foswiki instruction
Here is vhost configuration :
# Generated by IWAL 20160204-14:02:25
<VirtualHost *:80>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
    ErrorLog /datas/log/apache2-vhosts/test.cir.re-error.log
    CustomLog /datas/log/apache2-vhosts/test.cir.re-combined.log combined
    Redirect /stats http://test.cir.re/awstats/awstats.pl
    # NO FW
    Alias /errors /datas/vol3/w4a178348/var/www/test.cir.re/errors
    ErrorDocument 401 /errors/401.php
    ErrorDocument 403 /errors/403.php
    ErrorDocument 404 /errors/404.php
    ErrorDocument 500 /errors/500.php
    ScriptAlias /awstats /opt/wrapper/awstats/
    ScriptAlias /cgi-bin /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin
        <Directory /opt/wrapper/awstats/>
            Options ExecCGI
            AddHandler cgi-script .pl
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
            AuthType Basic
            AuthName Statistiques
            AuthUserFile /datas/vol3/w4a178348/var/awstats/test.cir.re/test.cir.re.pwd
            Require valid-user
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin>
            Options ExecCGI
            AddHandler cgi-script .pl .fcgi .cgi
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/htdocs>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/errors>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
</VirtualHost>

<VirtualHost *:443>
    ServerAdmin [hidden email]
    SuexecUserGroup w4a178348 w4a178348
    DocumentRoot /datas/vol3/w4a178348/var/www/test.cir.re/htdocs
    ServerName test.cir.re
    ServerAlias ftp.test.cir.re www.test.cir.re
    LogLevel error
    ErrorLog /datas/log/apache2-vhosts/test.cir.re-error.log
    CustomLog /datas/log/apache2-vhosts/test.cir.re-combined.log combined
    Redirect /stats https://test.cir.re/awstats/awstats.pl
    SetEnv HTTPS on
    Alias /errors /datas/vol3/w4a178348/var/www/test.cir.re/errors
    ErrorDocument 401 /errors/401.php
    ErrorDocument 403 /errors/403.php
    ErrorDocument 404 /errors/404.php
    ErrorDocument 500 /errors/500.php
    ScriptAlias /awstats /opt/wrapper/awstats/
    ScriptAlias /cgi-bin /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin
        <Directory /opt/wrapper/awstats/>
            Options ExecCGI
            AddHandler cgi-script .pl
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
            AuthType Basic
            AuthName Statistiques
            AuthUserFile /datas/vol3/w4a178348/var/awstats/test.cir.re/test.cir.re.pwd
            Require valid-user
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/cgi-bin>
            Options ExecCGI
            AddHandler cgi-script .pl .fcgi .cgi
            AllowOverride AuthConfig
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/htdocs>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
        <Directory /datas/vol3/w4a178348/var/www/test.cir.re/errors>
            AddHandler fcgid-script .php
            FCGIWrapper "/opt/wrapper/php w4a178348 php55 test.cir.re" .php
            Options ExecCGI -Indexes Includes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            Allow from all
        </Directory>
</VirtualHost>

when entering "perl tools/dependencies"

Content-type: text/plain

**** ERROR ****
The following critical dependencies are missing from your installation:
 ... CGI: Can't locate CGI.pm in @INC
 ... CGI::Session: Can't locate CGI/Session.pm in @INC
 ... Crypt::PasswdMD5: Can't locate Crypt/PasswdMD5.pm in @INC
 ... File::Copy::Recursive: Can't locate File/Copy/Recursive.pm in @INC
 ... JSON: Can't locate JSON.pm in @INC

Please install these modules and then ensure all dependencies are installed by either:
 -  viewing the System.PerlDependencyReport in your local Foswki,  or
 -  running the CLI shell script tools/dependencies from your server's command line.
You can get a complete list of Perl module dependencies by viewing System.SystemRequirements
on your local system or at http://foswiki.org/System/SystemRequirements.

Foswiki will not operate correctly unless the required dependencies are installed.

Your current library search path @INC contains:

   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/lib
   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/tools/../bin
   /usr/local/lib64/perl5
   /usr/local/share/perl5
   /usr/lib64/perl5/vendor_perl
   /usr/share/perl5/vendor_perl
   /usr/lib64/perl5
   /usr/share/perl5
   .
   /datas/vol3/w4a159036/var/www/test.cir.re/htdocs/lib/CPAN/lib

You can adjust the search path by editing bin/LocalLib.cfg


perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
2.02

perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'
1.1901

__________________________________________________
__________________________________________________
__________________________________________________

On my local host

Ubuntu 14.04 with Apache 2.0 Handler

Installed
apt-get install apache2 rcs libalgorithm-diff-perl libarchive-tar-perl libauthen-sasl-perl libcgi-pm-perl libcgi-session-perl libcrypt-passwdmd5-perl libdigest-sha-perl libemail-mime-perl libencode-perl liberror-perl libfile-copy-recursive-perl libhtml-parser-perl libhtml-tree-perl libio-socket-ip-perl libio-socket-ssl-perl libjson-perl liblocale-maketext-perl liblocale-maketext-lexicon-perl liblocale-msgfmt-perl libwww-perl liburi-perl libversion-perl

when entering "perl tools/dependencies"
[...]
Extensions and Perl modules used by installed Extensions:
     Apache::Request      Apache::Request is not installed.
        ModPerlEngineContrib: Optional Recommended if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib    
     FCGI::ProcManager      FCGI::ProcManager is not installed.
        FastCGIEngineContrib: Optional Required on nginx for dynamic FCGI handler management. Used by: FastCGIEngineContrib    
     mod_perl      mod_perl is not installed.
        ModPerlEngineContrib: Required  if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib

perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
2.02

perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'
1.2300


Thank you for helping if possible.

Kévin



Le Jeudi 4 février 2016 13h12, Oliver Krüger <[hidden email]> a écrit :


Hello Kevin,

thats hard to tell from the distance without further details. An error code 500 indicates a problem on the server side. That could be anything: insufficient access rights for the (perl) script, a crashing (perl) handler, whatever. The next step would be: look into the (error) log files of your webserver. Details on the reason for the 500 should be in there.

On your localhost you get the plain perl skript (instead the its output) because that perticular URL you entered was not interpreted as a perl script. You either have no perl installed or did not tell your webserver to treat files below foswiki/bin/* as perl scripts. We need to know which webserver you use (nginx, apache, lighttpd,… ) and how its configuration looks like in order to help you,

Kind regards,
Oliver





------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss




--
Chris Hoefler, PhD
Postdoctoral Research Associate
Straight Lab
Texas A&M University
2128 TAMU
College Station, TX 77843-2128



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Chris Hoefler
this command can't be execute
curl -L https://cpanmin.us | perl - App::cpanminus
but perl was announce to be support by my hoster, so I don't understand.

What is the error message? What  are your current environment settings for PATH, PERL5LIB, PERL_MM_OPT, and PERL_MB_OPT?

For my localhost, under the directory you asked and then my apache2.conf

Your mods look fine, but you may need to enable a few, like mod_ssl if you want https and mod_rewrite if you want to use rewrite rules. Did you create a foswiki.conf and drop it into /etc/apache2/sites-available and symlink it to /etc/apache2/sites-enabled? Or you can alternatively just edit the /etc/apache2/sites-available/000-default.conf and enable that. Whichever is easier, but you need a configuration file for your site or it isn't going to work.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

George Clark-2
Does your hoster use cpanel for installing perl modules?   If yes,  then in your bin directory, copy LocalLib.cfg.txt to LocalLib.cfg,  and un-comment (remove the #)  from the line 
  Konsole output
# use cPanelUserConfig;

If your hoster does not provide any way to install CPAN modules,  you could unzip / extract the CpanContrib into your Foswik install and it will provide local copies of most of the dependencies.  Not 100% though, because some need to be compiled.  It's better to find out how to install the modules.

And on your local server,  you say it's returning perl source?   What Linux distribution are you using.   On Debian, you need to "sudo a2enmod cgid"  if I recall correctly.  Not sure about other distros.

George Clark


On 02/04/2016 01:04 PM, Chris Hoefler wrote:
this command can't be execute
curl -L https://cpanmin.us | perl - App::cpanminus
but perl was announce to be support by my hoster, so I don't understand.

What is the error message? What  are your current environment settings for PATH, PERL5LIB, PERL_MM_OPT, and PERL_MB_OPT?

For my localhost, under the directory you asked and then my apache2.conf

Your mods look fine, but you may need to enable a few, like mod_ssl if you want https and mod_rewrite if you want to use rewrite rules. Did you create a foswiki.conf and drop it into /etc/apache2/sites-available and symlink it to /etc/apache2/sites-enabled? Or you can alternatively just edit the /etc/apache2/sites-available/000-default.conf and enable that. Whichever is easier, but you need a configuration file for your site or it isn't going to work.


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140


_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Raymond Lutz
I am having the same problem. I don't know if it is EXACTLY the same problem as the fellow who started this thread but the symptom is the same.

I have been using foswiki/TWiki for years (>10 now) and have several world-facing installs of prior versions (1.1.9).
I'm not an idiot, but the new version is yet another big change from the past. (Argh!)

--> (I have to say that upgrading foswiki is one of the most painful procedures I have to do. I have done it a number of times now and never has it been easy. If any work is done, please consider making installation easier! Suggestion: checklists (with appropriate commands for copy-paste to command shell) instead of narrative instructions.

If you can give me some hints to help, I would appreciate it.
This is running on a CentOS Linux VPS container with (pseudo) root access.

1. Prior to starting, I reviewed the cpan modules and made sure all were installed with the proper versions.  The only exception was IO::Socket::SSL but I doubt I use that at this point.
2. I am putting off all the conversion of data and the like for a later phase. First step is to just get the out of the box install working.
3. I extracted the new version 2.0.3 into a new directory so I can get it all running before I port over the data. So far I am using all the defaults,
This is here: http://www.cognisys.com/w203
4. configure ran and I went through the interactive process. (I normally place my data, working, templates in ~/private/fw203 so it is completely out of web access. But initially, I found that I had to start at ground zero to get anything to run (even configure fails and says the data is incompatible -- when it only can't find it at the default location).)
5. I set up .htaccess as I normally do but I commented out the requirement for user of RaymondLutz to use configure for now, and added my IP address. Honestly I don't know if this is the same sort of thing used in this new version.

500 error. No mention in apache logs that I can tell.

I checked the normal things such as chmod settings, .htaccess, etc. Eliminate .htaccess and it provides a source listing of bin/view.

Here is what configure -check does. I finally resorted to just editing the LocalSite.cfg file until I can get something to run.

Prior to this, I added by hand a line for TempfileDir. (BTW, in my history of trying to follow along, I found there were race conditions using /tmp with two foswiki installs on the same VPS.

=========================
bash-3.2$ ./configure -check
Use of uninitialized value in concatenation (.) or string at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store/Implementation.pm line 33.
Subroutine check_current_value redefined at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store//Implementation.pm line 12.
Use of uninitialized value in concatenation (.) or string at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store/Implementation.pm line 37.
Day too small - -25171 > -24856
Sec too small - -25171 < 74752

Checking:Mail -> Basic settings & Auto-configure:  {WebMasterEmail}
WARNING:    You must configure e-mail if you want Foswiki to provide topic change notifications and new user registration services.

Checking:Internationalisation -> Locale:  {DisplayTimeValues}
WARNING:    The installed version of perl may be unable to support early dates on this platform.
Perl 5.12 or newer is required for extended date handling.  See help text for more information.

=========================
I'm a bit concerned about the error messages, although they appear inconsequential, any release should have no such warnings.
I will look into upgrading perl to a more recent version but I find it hard to believe this is causing the 500 error. I seem to remember it is not trivial in the VPS situation but I will check anyway.

ANY HINTS?

--Raymond Lutz



On 02/04/2016 11:03 AM, George Clark wrote:
Does your hoster use cpanel for installing perl modules?   If yes,  then in your bin directory, copy LocalLib.cfg.txt to LocalLib.cfg,  and un-comment (remove the #)  from the line 
  Konsole output
# use cPanelUserConfig;

If your hoster does not provide any way to install CPAN modules,  you could unzip / extract the CpanContrib into your Foswik install and it will provide local copies of most of the dependencies.  Not 100% though, because some need to be compiled.  It's better to find out how to install the modules.

And on your local server,  you say it's returning perl source?   What Linux distribution are you using.   On Debian, you need to "sudo a2enmod cgid"  if I recall correctly.  Not sure about other distros.

George Clark


On 02/04/2016 01:04 PM, Chris Hoefler wrote:
this command can't be execute
curl -L https://cpanmin.us | perl - App::cpanminus
but perl was announce to be support by my hoster, so I don't understand.

What is the error message? What  are your current environment settings for PATH, PERL5LIB, PERL_MM_OPT, and PERL_MB_OPT?

For my localhost, under the directory you asked and then my apache2.conf

Your mods look fine, but you may need to enable a few, like mod_ssl if you want https and mod_rewrite if you want to use rewrite rules. Did you create a foswiki.conf and drop it into /etc/apache2/sites-available and symlink it to /etc/apache2/sites-enabled? Or you can alternatively just edit the /etc/apache2/sites-available/000-default.conf and enable that. Whichever is easier, but you need a configuration file for your site or it isn't going to work.


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140


_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140


_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Chris Hoefler
I would do the following:
  1) Check Perl version. Foswiki 2.0 does need a newer Perl. It will run on Perl 5.8.8, but Perl 5.12 or greater is recommended for a number of reasons.
  2) Run tools/dependencies to check your dependencies instead of bin/configure. Among the things that are critical are CGI, which is no longer shipped with Foswiki, and JSON. The tool will make it clear which ones are needed by Foswiki core and which ones are needed by optional Extensions. (For example, if you are using mod_perl you will need Apache::Request)
  3) Check your working/logs/error.log as that usually has more descriptive Perl errors than the Apache log. (However, you can configure Apache for more verbose logging)

Prior to this, I added by hand a line for TempfileDir. (BTW, in my history of trying to follow along, I found there were race conditions using /tmp with two foswiki installs on the same VPS.

Not sure what you mean by this. Two Foswiki installations cannot share a working/tmp directory, for obvious reasons, but this is completely separate from the system /tmp directory which should not be accessible to your webserver.

On Mon, Feb 8, 2016 at 10:27 AM, Ray Lutz <[hidden email]> wrote:
I am having the same problem. I don't know if it is EXACTLY the same problem as the fellow who started this thread but the symptom is the same.

I have been using foswiki/TWiki for years (>10 now) and have several world-facing installs of prior versions (1.1.9).
I'm not an idiot, but the new version is yet another big change from the past. (Argh!)

--> (I have to say that upgrading foswiki is one of the most painful procedures I have to do. I have done it a number of times now and never has it been easy. If any work is done, please consider making installation easier! Suggestion: checklists (with appropriate commands for copy-paste to command shell) instead of narrative instructions.

If you can give me some hints to help, I would appreciate it.
This is running on a CentOS Linux VPS container with (pseudo) root access.

1. Prior to starting, I reviewed the cpan modules and made sure all were installed with the proper versions.  The only exception was IO::Socket::SSL but I doubt I use that at this point.
2. I am putting off all the conversion of data and the like for a later phase. First step is to just get the out of the box install working.
3. I extracted the new version 2.0.3 into a new directory so I can get it all running before I port over the data. So far I am using all the defaults,
This is here: http://www.cognisys.com/w203
4. configure ran and I went through the interactive process. (I normally place my data, working, templates in ~/private/fw203 so it is completely out of web access. But initially, I found that I had to start at ground zero to get anything to run (even configure fails and says the data is incompatible -- when it only can't find it at the default location).)
5. I set up .htaccess as I normally do but I commented out the requirement for user of RaymondLutz to use configure for now, and added my IP address. Honestly I don't know if this is the same sort of thing used in this new version.

500 error. No mention in apache logs that I can tell.

I checked the normal things such as chmod settings, .htaccess, etc. Eliminate .htaccess and it provides a source listing of bin/view.

Here is what configure -check does. I finally resorted to just editing the LocalSite.cfg file until I can get something to run.

Prior to this, I added by hand a line for TempfileDir. (BTW, in my history of trying to follow along, I found there were race conditions using /tmp with two foswiki installs on the same VPS.

=========================
bash-3.2$ ./configure -check
Use of uninitialized value in concatenation (.) or string at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store/Implementation.pm line 33.
Subroutine check_current_value redefined at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store//Implementation.pm line 12.
Use of uninitialized value in concatenation (.) or string at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store/Implementation.pm line 37.
Day too small - -25171 > -24856
Sec too small - -25171 < 74752

Checking:Mail -> Basic settings & Auto-configure:  {WebMasterEmail}
WARNING:    You must configure e-mail if you want Foswiki to provide topic change notifications and new user registration services.

Checking:Internationalisation -> Locale:  {DisplayTimeValues}
WARNING:    The installed version of perl may be unable to support early dates on this platform.
Perl 5.12 or newer is required for extended date handling.  See help text for more information.

=========================
I'm a bit concerned about the error messages, although they appear inconsequential, any release should have no such warnings.
I will look into upgrading perl to a more recent version but I find it hard to believe this is causing the 500 error. I seem to remember it is not trivial in the VPS situation but I will check anyway.

ANY HINTS?

--Raymond Lutz



On 02/04/2016 11:03 AM, George Clark wrote:
Does your hoster use cpanel for installing perl modules?   If yes,  then in your bin directory, copy LocalLib.cfg.txt to LocalLib.cfg,  and un-comment (remove the #)  from the line 
 
# use cPanelUserConfig;

If your hoster does not provide any way to install CPAN modules,  you could unzip / extract the CpanContrib into your Foswik install and it will provide local copies of most of the dependencies.  Not 100% though, because some need to be compiled.  It's better to find out how to install the modules.

And on your local server,  you say it's returning perl source?   What Linux distribution are you using.   On Debian, you need to "sudo a2enmod cgid"  if I recall correctly.  Not sure about other distros.

George Clark


On 02/04/2016 01:04 PM, Chris Hoefler wrote:
this command can't be execute
curl -L https://cpanmin.us | perl - App::cpanminus
but perl was announce to be support by my hoster, so I don't understand.

What is the error message? What  are your current environment settings for PATH, PERL5LIB, PERL_MM_OPT, and PERL_MB_OPT?

For my localhost, under the directory you asked and then my apache2.conf

Your mods look fine, but you may need to enable a few, like mod_ssl if you want https and mod_rewrite if you want to use rewrite rules. Did you create a foswiki.conf and drop it into /etc/apache2/sites-available and symlink it to /etc/apache2/sites-enabled? Or you can alternatively just edit the /etc/apache2/sites-available/000-default.conf and enable that. Whichever is easier, but you need a configuration file for your site or it isn't going to work.


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140


_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140


_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss




--
Chris Hoefler, PhD
Postdoctoral Research Associate
Straight Lab
Texas A&M University
2128 TAMU
College Station, TX 77843-2128

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

George Clark-2
In reply to this post by Raymond Lutz
On 02/08/2016 11:27 AM, Ray Lutz wrote:

--> (I have to say that upgrading foswiki is one of the most painful procedures I have to do. I have done it a number of times now and never has it been easy. If any work is done, please consider making installation easier! Suggestion: checklists (with appropriate commands for copy-paste to command shell) instead of narrative instructions.

We've been trying to be a bit less disruptive.  2.1 is an unzip on top of a 2.0 system.   Though it's looking as though the eventual Foswiki 3.0 might be another disruptive change.  But indeed 2.0 is really a very significant change.  
If you can give me some hints to help, I would appreciate it.
This is running on a CentOS Linux VPS container with (pseudo) root access.
I've never run on a VPS so I may very well be missing something here.
1. Prior to starting, I reviewed the cpan modules and made sure all were installed with the proper versions.  The only exception was IO::Socket::SSL but I doubt I use that at this point.
Unless you are sending Email directly from <a class="moz-txt-link-freetext" href="Net::SMTP">Net::SMTP. you shouldn't need this.  If your server supports it, best to use the "mailprogram" implementation vs. the pure perl mail.
2. I am putting off all the conversion of data and the like for a later phase. First step is to just get the out of the box install working.
Good plan.  The migration to Unicode *can* be a significant effort.  It really depends on the underlying data.
3. I extracted the new version 2.0.3 into a new directory so I can get it all running before I port over the data. So far I am using all the defaults,
This is here: http://www.cognisys.com/w203
So far this all looks correct.
4. configure ran and I went through the interactive process. (I normally place my data, working, templates in ~/private/fw203 so it is completely out of web access. But initially, I found that I had to start at ground zero to get anything to run (even configure fails and says the data is incompatible -- when it only can't find it at the default location).)
I don't think we've done much testing with radically different file paths.  I doubt that the bootstrap code will work correctly with unusual paths.  This will probably need manual configuration.  When you say configure ran, I assume it's cli configure you are referencing?
5. I set up .htaccess as I normally do but I commented out the requirement for user of RaymondLutz to use configure for now, and added my IP address. Honestly I don't know if this is the same sort of thing used in this new version.

500 error. No mention in apache logs that I can tell.
Have you tried running tools/dependencies? That should double check all the dependencies.  And then try cd  bin && ./view.  does that fail when run from the CLI?   Though my bet is that it's the store configuration - see below...

If it's all working from CLI and failing from the web server,  I'd be suspicious that the server is using different perl lib paths.

bash-3.2$ ./configure -check
Use of uninitialized value in concatenation (.) or string at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Configure/Checkers/Store/Implementation.pm line 33.
It appears that the $Foswiki::cfg{Store}{Implementation} is not configured.  Something failed in the bootstrap.

Day too small - -25171 > -24856
Sec too small - -25171 < 74752
Not sure where these errors are coming from.  But they are probably related to using a very old version of perl.  What version of perl are you using?

Checking:Internationalisation -> Locale:  {DisplayTimeValues}
WARNING:    The installed version of perl may be unable to support early dates on this platform.
Perl 5.12 or newer is required for extended date handling.  See help text for more information.

As with the Day / Sec errors above.   Old perl cannot handle dates before 1970 iirc. 
=========================
I'm a bit concerned about the error messages, although they appear inconsequential, any release should have no such warnings.
The Store Implementation error will be completely fatal.  That really should not be able to happen.  Something didn't get set when running Bootstrap.   I'd suggest removing LocalSite.cfg and rerunning "tools/configure -save"    Bootstrap will report something like: AUTOCONFIG: Store configured for PlainFile.     Continue and answer the "20 questions"  and when it promps for the Store,  enter it as Foswiki::Store::RcsWrap   or Foswiki::Store::RcsLite

Or you could take the default of PlainFile,  and then select an RCS store when you first visit bin/configure.
Konsole output
I will look into upgrading perl to a more recent version but I find it hard to believe this is causing the 500 error. I seem to remember it is not trivial in the VPS situation but I will check anyway.
Regarding perl version.  If you do have an opportunity to upgrade, I'd suggest getting to 5.20 or 5.22   Regular Expression performance against Unicode character strings is MUCH better on current perl.  


George

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Raymond Lutz
In reply to this post by Chris Hoefler
I am merging both responses of my plea for help. Thank you for your helpful comments so far.
I am making some progress but still can't get "out-of-the-box" version working. I am using PlainFile for now. I THINK this is the most plain configuration.

On 02/08/2016 9:47 AM, Chris Hoefler wrote:
I would do the following:
  1) Check Perl version. Foswiki 2.0 does need a newer Perl. It will run on Perl 5.8.8, but Perl 5.12 or greater is recommended for a number of reasons.
This is not possible. Perl 5.8.8 is all I can get at this point. Is there a way we can identify what the limitations are, because this seems like a show stopper.
I use Plesk panel and it does not support anything past 5.8.8. To 'require' a better perl than this VERY STANDARD level is a mistake I think.
My VPS hosting service confirmed that perl greater than 5.8.8 is not feasible.

  2) Run tools/dependencies to check your dependencies instead of bin/configure. Among the things that are critical are CGI, which is no longer shipped with Foswiki, and JSON. The tool will make it clear which ones are needed by Foswiki core and which ones are needed by optional Extensions. (For example, if you are using mod_perl you will need Apache::Request)
I believe these are all optional or do not apply to me. Here is the output of ./dependencies

----------------------------------
bash-3.2$ ./dependencies
   * *Perl version:* 5.008008
Perl modules used by Foswiki:
         DBD::Pg         DBD::Pg is not installed.
                Optional used for Foswiki Page Cache using PostgreSQL
         IO::Socket::SSL         IO::Socket::SSL 1.77 installed *Version 1.80 optional for
                Optional for outbound SSL/TLS connections, eg. e-mail.* IO::Socket::SSL version >= 1.80 required-- installed version is 1.77
         Win32::Console          Win32::Console is not installed.
                Optional required on Windows platforms if {UserInterfaceInternationalisation} is enabled in configuration.


Extensions and Perl modules used by installed Extensions:
         Apache::Request         Apache::Request is not installed.
                ModPerlEngineContrib: Optional Recommended if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib
         Apache2::Request        Apache2::Request is not installed.
                ModPerlEngineContrib: Optional Recommended if you're using Apache 2.x and plan to enable mod_perl Used by: ModPerlEngineContrib
         FCGI::ProcManager       FCGI::ProcManager is not installed.
                FastCGIEngineContrib: Optional Required on nginx for dynamic FCGI handler management. Used by: FastCGIEngineContrib
         mod_perl        mod_perl is not installed.
                ModPerlEngineContrib: Required  if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib
----------------------------------

The "mod_perl" error is not correct. mod_perl is installed and enabled.

Versions of these:
httpd    2.2.3-85.el5.centos
mod_perl    2.0.4-6.el5    


  3) Check your working/logs/error.log as that usually has more descriptive Perl errors than the Apache log. (However, you can configure Apache for more verbose logging)

Prior to this, I added by hand a line for TempfileDir. (BTW, in my history of trying to follow along, I found there were race conditions using /tmp with two foswiki installs on the same VPS.

Not sure what you mean by this. Two Foswiki installations cannot share a working/tmp directory, for obvious reasons, but this is completely separate from the system /tmp directory which should not be accessible to your webserver.
What I mean is that foswiki used to use the /tmp directory for temporary files and with more than one install on a VPS, the same /tmp was used, and the filenames were not sufficiently unique, resulting a hard-to-find race condition failure. I cant tell you how many hours I spent on this. So this is a hot button for me. I don't understand why I had to manually add the TempfileDir configuration parameter to LocalSite.cfg. It should exist and have a value, and should probably be in the working directory.

----------
George Clark proposes that I run view from cli.
--> My comments is that this should be a standard step OR there should be a test mode that can be run from cli as a standard step and provide equivalent results.

I get:
-------------------------------
bash-3.2$ ./view
Can't locate PlainFile.pm in @INC (@INC contains: /var/www/vhosts/cognisys.com/httpdocs/w203/lib /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /var/www/vhosts/cognisys.com/httpdocs/w203/lib/CPAN/lib) at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.
 at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.
        Foswiki::load_package("PlainFile") called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 2121
        Foswiki::new("Foswiki", "AdminUser", Foswiki::Request=HASH(0x91732b0), HASH(0x9185790)) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/UI.pm line 363
        Foswiki::UI::__ANON__() called at /usr/lib/perl5/site_perl/5.8.8/Error.pm line 421
        eval {...} called at /usr/lib/perl5/site_perl/5.8.8/Error.pm line 413
        Error::subs::try(CODE(0x90a1c74), HASH(0x9219d70)) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/UI.pm line 500
        Foswiki::UI::_execute(Foswiki::Request=HASH(0x91732b0), CODE(0x9196c68), "command_line", 1, "view", 1) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/UI.pm line 326
        Foswiki::UI::handleRequest(Foswiki::Request=HASH(0x91732b0)) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Engine/CLI.pm line 60
        Foswiki::Engine::CLI::run(Foswiki::Engine::CLI=HASH(0x8d73470)) called at ./view line 29.
Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.

Can't locate PlainFile.pm in @INC (@INC contains: path path-linux-thread-multi path path path-linux-thread-multi path path path-linux-thread-multi path . path)b

-------------------------------
But PlainFile.pm seems to exist in two locations:

/var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Store/PlainFile.pm
/var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Logger/PlainFile.pm

====================
Deleted LocalSite.cfg and reran ./configure -save
--> I don't really understand this question: sudo password for 'admin'

HERE IS THE TRANSCRIPT
-------------------------------------------------
LocalSite.cfg load failed
AUTOCONFIG: Bootstrap Phase 1: $VAR1 = {
          'HOME' => '/var/www/vhosts/cognisys.com',
          'SSH_CLIENT' => '72.220.142.178 22704 22',
          'SSH_CONNECTION' => '72.220.142.178 22704 69.73.148.108 22',
          'MANPATH' => '//man:',
          'LESSOPEN' => '|/usr/bin/lesspipe.sh %s',
          'MAIL' => '/var/spool/mail/root',
          'PWD' => '/var/www/vhosts/cognisys.com/httpdocs/w203/tools',
          'LANG' => 'en_US.UTF-8',
          'USER' => 'cognisys',
          'G_BROKEN_FILENAMES' => '1',
          'LOGNAME' => 'cognisys',
          'SHLVL' => '2',
          'HOSTNAME' => 'newvps.cognisys.com',
          'OLDPWD' => '/var/www/vhosts/cognisys.com/httpdocs/w203/lib',
          'INPUTRC' => '/etc/inputrc',
          '_' => './configure',
          'PATH' => '//sbin://bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin',
          'LS_COLORS' => 'no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:',
          'SHELL' => '/bin/bash',
          'HISTSIZE' => '1000',
          'TERM' => 'xterm',
          'SSH_TTY' => '/dev/pts/0'
        };
AUTOCONFIG: Found Bin dir: /var/www/vhosts/cognisys.com/httpdocs/w203/tools, Script name: configure using FindBin
AUTOCONFIG: TemplateDir = /var/www/vhosts/cognisys.com/httpdocs/w203/templates
AUTOCONFIG: ToolsDir = /var/www/vhosts/cognisys.com/httpdocs/w203/tools
AUTOCONFIG: WorkingDir = /var/www/vhosts/cognisys.com/httpdocs/w203/working
AUTOCONFIG: PubDir = /var/www/vhosts/cognisys.com/httpdocs/w203/pub
AUTOCONFIG: ScriptDir = /var/www/vhosts/cognisys.com/httpdocs/w203/bin
AUTOCONFIG: DataDir = /var/www/vhosts/cognisys.com/httpdocs/w203/data
AUTOCONFIG: LocalesDir = /var/www/vhosts/cognisys.com/httpdocs/w203/locale
AUTOCONFIG: Set initial {Site}{Locale} to  en_US.UTF-8
AUTOCONFIG: Store configured for PlainFile
AUTOCONFIG: Unable to find a valid 'grep' on the path. Forcing PurePerl search
AUTOCONFIG: Detected OS UNIX:  DetailedOS: linux
** Enter values for critical configuration items.
** type a new value or hit return to accept the value in brackets.

This is the root of all Foswiki URLs.
For example, =http://myhost.com:123=
(do not include the trailing slash.)

{DefaultUrlHost} (http://localhost): http://www.cognisys.com

This is the 'cgi-bin' part of URLs used to access the Foswiki bin
directory. For example =/foswiki/bin=.
See [[http://foswiki.org/Support/ShorterUrlCookbook][ShorterUrlCookbook]]
for more information on setting up Foswiki to use shorter script URLs.

{ScriptUrlPath} (/foswiki/bin): /w203/bin

Enter optional short URL for view script, Press enter for shortest URLs,  Enter "none" to use full URLs.
{ScriptUrlPaths}{view}: none

This is the URL path used to link to attachments. For stores where
attachments are stored as files (such as PlainFile and RCSLite) then this
will normally be the URL path to the =pub= directory.
For example =/foswiki/pub=

*Security Note:* files in the pub directory are *not*
protected by Foswiki access controls. If you require access controls, you
will have to use webserver controls (for example =.htaccess= on Apache).
See the
[[http://foswiki.org/Support/ApacheConfigGenerator][Apache Config Generator]]
for more information.

{PubUrlPath} (/foswiki/pub): /w203/pub

Enter a password for the 'admin' sudo account.

{Password}: XXXXXX (I entered a password but I really don't understand this question)
 The following directory settings have been guessed.  Press enter to confirm each setting:

This is the file system path used to access the Foswiki bin directory.

{ScriptDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/bin):

Suffix of Foswiki CGI scripts. For example, .cgi or .pl.
You may need to set this if your webserver requires an extension.

{ScriptSuffix} ():

Topic files store (file path, not URL). For example =/usr/local/foswiki/data=.
This directory must not be web accessible.

{DataDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/data):

Attachments store (file path, not URL), must match the attachments URL
path =/foswiki/pub= - for example =/usr/local/foswiki/pub=  This directory is
normally accessible from the web.

{PubDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/pub):

File path to templates directory. For example =/usr/local/foswiki/templates=.
This directory must not be web accessible.

{TemplateDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/templates):

File path to locale directory.
For example =/usr/local/foswiki/locale=.
This directory must not be web accessible.

{LocalesDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/locale):

Directory where Foswiki stores files that are required for the management
of Foswiki, but are not required to be accessed from the web.
A number of subdirectories will be created automatically under this
directory:
   * ={WorkingDir}/tmp= - used for security-related temporary files
    (these files can be deleted at any time without permanent damage).
     _Passthrough files_ are used by Foswiki to work around the limitations
     of HTTP when redirecting URLs.
     _Session files_ are used to record information about active
     users - for example, whether they are logged in or not.
     For obvious reasons, these files must *not* be browseable from the web!
     You are recommended to restrict filesystem permissions on this
     directory so only the web server user can acess it.
   * ={WorkingDir}/requestTmp= - used as an alternate location for the
     system =/tmp= directory.  This is only used if {TempfileDir}
     is configured.
   * ={WorkingDir}/work_areas= - these are work areas used by
     extensions that need to store persistent data across sessions.
   * ={WorkingDir}/registration_approvals= - this is used by the
     default Foswiki registration process to store registrations that
     are pending verification.

{WorkingDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/working):

File path to tools directory. For example =/usr/local/foswiki/tools=.
This directory must not be web accessible.

{ToolsDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/tools):

Store implementation.
<dl><dt>PlainFile</dt><dd>
(installed by the PlainFileStoreContrib) is just about the simplest store
that you can use with Foswiki. it uses simple text files to store
the history of topics and attachments, and does not require any external
programs. The use of text files makes it easy to implement 'out of band'
processing, as well as taking maximum advantage of filestore caching. This
is the reference implementation of a store.</dd></dl>
<dl><dt>RcsWrap</dt><dd>
(installed by the RCSStoreContrib) uses the 'rcs' revision control
system to store the history of topics and attachments. It calls the rcs
executables directly, and requires rcs to be installed on the server.
It's a good choice for sites that have a pre-existing Foswiki (or TWiki)
where compatibility with existing data and scripts is paramount.
Performance is generally good on most platforms except Windows.</dd></dl>
<dl><dt>RcsLite</dt><dd>
uses a pure-perl simplified implementation of the 'rcs' revision
control system.
It's a good choice for sites that have a pre-existing Foswiki (or TWiki)
where compatibility with existing data and scripts is paramount, but
RcsWrap cannot be used; for example, on  hosted platform where 'rcs'
cannot be installed, or on Windows where RcsWrap performance is poor.
</dd></dl>

{Store}{Implementation} (Foswiki::Store::PlainFile):

Set this when you are using a store that was initiated under an old
version of Foswiki, where the {Site}{CharSet} was set to something other
than 'utf-8', and you cannot convert the store to UTF8 for some reason.
This option takes the name of the encoding e.g. 'iso-8859-1'.
Note: you are *STRONGLY* recommended to convert the entire store to
UTF-8 in-place, as setting this option will incur a performance penatly.
See =tools/bulk_copy.pl= for details on converting your store.
Leave this undefined to use the default of utf-8 encoding.

{Store}{Encoding}:

This is the algorithm used to perform plain text (not query) searches.
Foswiki has two built-in search algorithms, both of which are designed to
work with the default flat-file databases (RcsWrap, RcsLite, and PlainFile).
   * The default 'Forking' algorithm, which forks a subprocess that
     runs a 'grep' command, is recommended for Linux/Unix.
     Forking may also work OK on Windows if you keep the directory path
     to Foswiki very short.
   * The 'PurePerl' algorithm, which is written in Perl and
     usually used on native Windows installations where forking
     is not stable, due to limitations in the length of command lines.
On Linux/Unix you will be just fine with the 'Forking' implementation.
However if you find searches run very slowly, you may want to try a
different algorithm, which may work better on your configuration.

Other store implementations and indexing search engines (for example,
[[http://foswiki.org/Extensions/KinoSearchContrib][KinoSearchContrib]])
may come with their own search algorithms.

{Store}{SearchAlgorithm} (Foswiki::Store::SearchAlgorithms::PurePerl): Forking
New configuration saved in /var/www/vhosts/cognisys.com/httpdocs/w203/lib/LocalSite.cfg

-----------------------------------------------------------
./view does run from cli but complains that .htpasswd not found in data

copied old .htpasswd to newly created /w203/data.

./view runs without error.

Still get 500 error from browser. Cleared history buffers in browser. Same error.
confirmed Configuration Server Firewall (csf) disabled.
Tried from new browser with no history. Still fails.
Checking .htaccess

my bin/.htaccess (only active lines):
-----------------------------------
# bin/.htaccess.txt
BrowserMatchNoCase ^$ anonymous_spider

Order Allow,Deny
Allow from all
Deny from env=anonymous_spider

SetHandler cgi-script

AuthUserFile /var/www/vhosts/cognisys.com/httpdocs/w203/data/.htpasswd
AuthName 'Enter your WikiName: (First name and last name, no space, no dots, capitalized, e.g. JohnSmith). Cancel to register if you do not have one.'
AuthType Basic

ErrorDocument 401 w203/bin/view/System/UserRegistration

Options ExecCGI FollowSymLinks

<FilesMatch "configure.*">
        SetHandler cgi-script
        Order Deny,Allow
        Deny from all
        Allow from 127.0.0.1, 192.168.1.10, 70.179.35.128, 72.220.142.178
        <!-- Require user RaymondLutz -->
        Satisfy All
</FilesMatch>
-----------------------------------

Since some of these settings go back a long way, they may be obsolete...

stuck again. 500 error.

Checked w203/working/logs/error.log
-->  empty

Hints?

--Ray



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Required Perl version

George Clark-2
Hi Ray,

Regarding Perl versions, Foswiki has been tested with Perl 5.8.8,  and it is still somewhat supported by the Foswiki project.  Note however that Perl 5.8.8 was released on Feb 2nd, 2006,  more than 10 years ago.  There is not much in the data processing space that is still useful and supported 10 years past it's original release.  It is almost certain that the next major version of Foswiki will require a modern Perl.  We are uncertain yet,  but at least 5.18.  But note that 5.18 is *already end of life*  See http://www.cpan.org/src/README.html

Some of the known issues with old perl:

   * Foswiki 2.1.0 fails in Foswiki/Configure/FileUtil.pm due to a perl bug.   Patch noted in the download page.
   * On any version of perl before 5.20, Regular expression processing on Unicode will be *significantly* slower.
   * Foswiki is going to crash if the "version" module is original with 5.8.8 / 5.10.0.   But that was also an issue in Foswiki 1.1.9
   * Date handling is very poor on older perl.

We do run the Unit Tests using a Perl 5.8.8 installation, so Foswiki should be reasonably functional. But again,  this is probably end of the road.  As far as I can find,  there is no major OS distribution that still ships with perl 5.8.8.

George Clark

On 02/08/2016 04:17 PM, Ray Lutz wrote:
On 02/08/2016 9:47 AM, Chris Hoefler wrote:
I would do the following:
  1) Check Perl version. Foswiki 2.0 does need a newer Perl. It will run on Perl 5.8.8, but Perl 5.12 or greater is recommended for a number of reasons.
This is not possible. Perl 5.8.8 is all I can get at this point. Is there a way we can identify what the limitations are, because this seems like a show stopper.
I use Plesk panel and it does not support anything past 5.8.8. To 'require' a better perl than this VERY STANDARD level is a mistake I think.
My VPS hosting service confirmed that perl greater than 5.8.8 is not feasible.



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500 - Store setting

George Clark-2
In reply to this post by Raymond Lutz
Okay,  this was your first issue.   I can recreate this issue by setting
the store to "PlainFile".    The proper setting is
"Foswiki::Store::PlainFile".    Your latest re-install seems to have
gotten by this.

I've opened task http://foswiki.org/Tasks/Item13947   to improve the
checker to detect an invalid store configuration.

So your original problem is explained.   Note that this can only happen
when using the CLI configure.  The Web interface provides a drop-down
select that would ensure the proper value is chosen.

Regarding "standard step" comment.   We are now in debugging.   And
running the view script from the CLI really is a somewhat standard step
when doing development.  But for basic installation it is very unusual
to have to do this.

On 02/08/2016 04:17 PM, Ray Lutz wrote:

---snip---

> ----------
> George Clark proposes that I run view from cli.
> --> My comments is that this should be a standard step OR there should
> be a test mode that can be run from cli as a standard step and provide
> equivalent results.
>
> I get:
> -------------------------------
> bash-3.2$ ./view
> Can't locate PlainFile.pm in @INC (@INC contains:
> /var/www/vhosts/cognisys.com/httpdocs/w203/lib
> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
> /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .
> /var/www/vhosts/cognisys.com/httpdocs/w203/lib/CPAN/lib) at
> /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Chris Hoefler
In reply to this post by Raymond Lutz
--> I don't really understand this question: sudo password for 'admin'

It is your (super) admin password for the /bin/configure script. You should probably leave it unset for the reasons described here,
http://foswiki.org/System/InstallationGuide#About_Administrators

 Since some of these settings go back a long way, they may be obsolete...

stuck again. 500 error.

Checked w203/working/logs/error.log
-->  empty

Hints?

Try deleting /bin/.htaccess since you don't need it anymore? Since your installation is already bootstrapped, it's hard to say why this would interfere, but it's the only thing I can think of. Your installation seems fairly standard to me otherwise.

I noticed this message from your pasted output,
AUTOCONFIG: Unable to find a valid 'grep' on the path. Forcing PurePerl search

Since you are using a linux distribution, there should probably be a grep available, so I would check your PATH settings and make sure everything is right. This is not a fatal error, it just seems a bit fishy to me and may be pointing to problems elsewhere. Or you could just have grep disabled, but I'm not sure why you would want that.

This is not possible. Perl 5.8.8 is all I can get at this point. Is there a way we can identify what the limitations are, because this seems like a show stopper.
I use Plesk panel and it does not support anything past 5.8.8. To 'require' a better perl than this VERY STANDARD level is a mistake I think.
My VPS hosting service confirmed that perl greater than 5.8.8 is not feasible.

Ok, but realize that Perl 5.8.8 is now more than 10 years old. I would be seriously investigating an upgrade path at this point. Foswiki will run on 5.8.8, but things like good Unicode support depend on newer Perl.

On Mon, Feb 8, 2016 at 3:17 PM, Ray Lutz <[hidden email]> wrote:
I am merging both responses of my plea for help. Thank you for your helpful comments so far.
I am making some progress but still can't get "out-of-the-box" version working. I am using PlainFile for now. I THINK this is the most plain configuration.

On 02/08/2016 9:47 AM, Chris Hoefler wrote:
I would do the following:
  1) Check Perl version. Foswiki 2.0 does need a newer Perl. It will run on Perl 5.8.8, but Perl 5.12 or greater is recommended for a number of reasons.
This is not possible. Perl 5.8.8 is all I can get at this point. Is there a way we can identify what the limitations are, because this seems like a show stopper.
I use Plesk panel and it does not support anything past 5.8.8. To 'require' a better perl than this VERY STANDARD level is a mistake I think.
My VPS hosting service confirmed that perl greater than 5.8.8 is not feasible.

  2) Run tools/dependencies to check your dependencies instead of bin/configure. Among the things that are critical are CGI, which is no longer shipped with Foswiki, and JSON. The tool will make it clear which ones are needed by Foswiki core and which ones are needed by optional Extensions. (For example, if you are using mod_perl you will need Apache::Request)
I believe these are all optional or do not apply to me. Here is the output of ./dependencies

----------------------------------
bash-3.2$ ./dependencies
   * *Perl version:* 5.008008
Perl modules used by Foswiki:
         DBD::Pg         DBD::Pg is not installed.
                Optional used for Foswiki Page Cache using PostgreSQL
         IO::Socket::SSL         IO::Socket::SSL 1.77 installed *Version 1.80 optional for
                Optional for outbound SSL/TLS connections, eg. e-mail.* IO::Socket::SSL version >= 1.80 required-- installed version is 1.77
         Win32::Console          Win32::Console is not installed.
                Optional required on Windows platforms if {UserInterfaceInternationalisation} is enabled in configuration.


Extensions and Perl modules used by installed Extensions:
         Apache::Request         Apache::Request is not installed.
                ModPerlEngineContrib: Optional Recommended if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib
         Apache2::Request        Apache2::Request is not installed.
                ModPerlEngineContrib: Optional Recommended if you're using Apache 2.x and plan to enable mod_perl Used by: ModPerlEngineContrib
         FCGI::ProcManager       FCGI::ProcManager is not installed.
                FastCGIEngineContrib: Optional Required on nginx for dynamic FCGI handler management. Used by: FastCGIEngineContrib
         mod_perl        mod_perl is not installed.
                ModPerlEngineContrib: Required  if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib
----------------------------------

The "mod_perl" error is not correct. mod_perl is installed and enabled.

Versions of these:
httpd    2.2.3-85.el5.centos
mod_perl    2.0.4-6.el5    


  3) Check your working/logs/error.log as that usually has more descriptive Perl errors than the Apache log. (However, you can configure Apache for more verbose logging)

Prior to this, I added by hand a line for TempfileDir. (BTW, in my history of trying to follow along, I found there were race conditions using /tmp with two foswiki installs on the same VPS.

Not sure what you mean by this. Two Foswiki installations cannot share a working/tmp directory, for obvious reasons, but this is completely separate from the system /tmp directory which should not be accessible to your webserver.
What I mean is that foswiki used to use the /tmp directory for temporary files and with more than one install on a VPS, the same /tmp was used, and the filenames were not sufficiently unique, resulting a hard-to-find race condition failure. I cant tell you how many hours I spent on this. So this is a hot button for me. I don't understand why I had to manually add the TempfileDir configuration parameter to LocalSite.cfg. It should exist and have a value, and should probably be in the working directory.

----------
George Clark proposes that I run view from cli.
--> My comments is that this should be a standard step OR there should be a test mode that can be run from cli as a standard step and provide equivalent results.

I get:
-------------------------------
bash-3.2$ ./view
Can't locate PlainFile.pm in @INC (@INC contains: /var/www/vhosts/cognisys.com/httpdocs/w203/lib /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /var/www/vhosts/cognisys.com/httpdocs/w203/lib/CPAN/lib) at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.
 at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.
        Foswiki::load_package("PlainFile") called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 2121
        Foswiki::new("Foswiki", "AdminUser", Foswiki::Request=HASH(0x91732b0), HASH(0x9185790)) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/UI.pm line 363
        Foswiki::UI::__ANON__() called at /usr/lib/perl5/site_perl/5.8.8/Error.pm line 421
        eval {...} called at /usr/lib/perl5/site_perl/5.8.8/Error.pm line 413
        Error::subs::try(CODE(0x90a1c74), HASH(0x9219d70)) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/UI.pm line 500
        Foswiki::UI::_execute(Foswiki::Request=HASH(0x91732b0), CODE(0x9196c68), "command_line", 1, "view", 1) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/UI.pm line 326
        Foswiki::UI::handleRequest(Foswiki::Request=HASH(0x91732b0)) called at /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Engine/CLI.pm line 60
        Foswiki::Engine::CLI::run(Foswiki::Engine::CLI=HASH(0x8d73470)) called at ./view line 29.
Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.

Can't locate PlainFile.pm in @INC (@INC contains: path path-linux-thread-multi path path path-linux-thread-multi path path path-linux-thread-multi path . path)b

-------------------------------
But PlainFile.pm seems to exist in two locations:

/var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Store/PlainFile.pm
/var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki/Logger/PlainFile.pm

====================
Deleted LocalSite.cfg and reran ./configure -save
--> I don't really understand this question: sudo password for 'admin'

HERE IS THE TRANSCRIPT
-------------------------------------------------
LocalSite.cfg load failed
AUTOCONFIG: Bootstrap Phase 1: $VAR1 = {
          'HOME' => '/var/www/vhosts/cognisys.com',
          'SSH_CLIENT' => '72.220.142.178 22704 22',
          'SSH_CONNECTION' => '72.220.142.178 22704 69.73.148.108 22',
          'MANPATH' => '//man:',
          'LESSOPEN' => '|/usr/bin/lesspipe.sh %s',
          'MAIL' => '/var/spool/mail/root',
          'PWD' => '/var/www/vhosts/cognisys.com/httpdocs/w203/tools',
          'LANG' => 'en_US.UTF-8',
          'USER' => 'cognisys',
          'G_BROKEN_FILENAMES' => '1',
          'LOGNAME' => 'cognisys',
          'SHLVL' => '2',
          'HOSTNAME' => 'newvps.cognisys.com',
          'OLDPWD' => '/var/www/vhosts/cognisys.com/httpdocs/w203/lib',
          'INPUTRC' => '/etc/inputrc',
          '_' => './configure',
          'PATH' => '//sbin://bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin',
          'LS_COLORS' => 'no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:',
          'SHELL' => '/bin/bash',
          'HISTSIZE' => '1000',
          'TERM' => 'xterm',
          'SSH_TTY' => '/dev/pts/0'
        };
AUTOCONFIG: Found Bin dir: /var/www/vhosts/cognisys.com/httpdocs/w203/tools, Script name: configure using FindBin
AUTOCONFIG: TemplateDir = /var/www/vhosts/cognisys.com/httpdocs/w203/templates
AUTOCONFIG: ToolsDir = /var/www/vhosts/cognisys.com/httpdocs/w203/tools
AUTOCONFIG: WorkingDir = /var/www/vhosts/cognisys.com/httpdocs/w203/working
AUTOCONFIG: PubDir = /var/www/vhosts/cognisys.com/httpdocs/w203/pub
AUTOCONFIG: ScriptDir = /var/www/vhosts/cognisys.com/httpdocs/w203/bin
AUTOCONFIG: DataDir = /var/www/vhosts/cognisys.com/httpdocs/w203/data
AUTOCONFIG: LocalesDir = /var/www/vhosts/cognisys.com/httpdocs/w203/locale
AUTOCONFIG: Set initial {Site}{Locale} to  en_US.UTF-8
AUTOCONFIG: Store configured for PlainFile
AUTOCONFIG: Unable to find a valid 'grep' on the path. Forcing PurePerl search
AUTOCONFIG: Detected OS UNIX:  DetailedOS: linux
** Enter values for critical configuration items.
** type a new value or hit return to accept the value in brackets.

This is the root of all Foswiki URLs.
For example, =http://myhost.com:123=
(do not include the trailing slash.)

{DefaultUrlHost} (http://localhost): http://www.cognisys.com

This is the 'cgi-bin' part of URLs used to access the Foswiki bin
directory. For example =/foswiki/bin=.
See [[http://foswiki.org/Support/ShorterUrlCookbook][ShorterUrlCookbook]]
for more information on setting up Foswiki to use shorter script URLs.

{ScriptUrlPath} (/foswiki/bin): /w203/bin

Enter optional short URL for view script, Press enter for shortest URLs,  Enter "none" to use full URLs.
{ScriptUrlPaths}{view}: none

This is the URL path used to link to attachments. For stores where
attachments are stored as files (such as PlainFile and RCSLite) then this
will normally be the URL path to the =pub= directory.
For example =/foswiki/pub=

*Security Note:* files in the pub directory are *not*
protected by Foswiki access controls. If you require access controls, you
will have to use webserver controls (for example =.htaccess= on Apache).
See the
[[http://foswiki.org/Support/ApacheConfigGenerator][Apache Config Generator]]
for more information.

{PubUrlPath} (/foswiki/pub): /w203/pub

Enter a password for the 'admin' sudo account.

{Password}: XXXXXX (I entered a password but I really don't understand this question)
 The following directory settings have been guessed.  Press enter to confirm each setting:

This is the file system path used to access the Foswiki bin directory.

{ScriptDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/bin):

Suffix of Foswiki CGI scripts. For example, .cgi or .pl.
You may need to set this if your webserver requires an extension.

{ScriptSuffix} ():

Topic files store (file path, not URL). For example =/usr/local/foswiki/data=.
This directory must not be web accessible.

{DataDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/data):

Attachments store (file path, not URL), must match the attachments URL
path =/foswiki/pub= - for example =/usr/local/foswiki/pub=  This directory is
normally accessible from the web.

{PubDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/pub):

File path to templates directory. For example =/usr/local/foswiki/templates=.
This directory must not be web accessible.

{TemplateDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/templates):

File path to locale directory.
For example =/usr/local/foswiki/locale=.
This directory must not be web accessible.

{LocalesDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/locale):

Directory where Foswiki stores files that are required for the management
of Foswiki, but are not required to be accessed from the web.
A number of subdirectories will be created automatically under this
directory:
   * ={WorkingDir}/tmp= - used for security-related temporary files
    (these files can be deleted at any time without permanent damage).
     _Passthrough files_ are used by Foswiki to work around the limitations
     of HTTP when redirecting URLs.
     _Session files_ are used to record information about active
     users - for example, whether they are logged in or not.
     For obvious reasons, these files must *not* be browseable from the web!
     You are recommended to restrict filesystem permissions on this
     directory so only the web server user can acess it.
   * ={WorkingDir}/requestTmp= - used as an alternate location for the
     system =/tmp= directory.  This is only used if {TempfileDir}
     is configured.
   * ={WorkingDir}/work_areas= - these are work areas used by
     extensions that need to store persistent data across sessions.
   * ={WorkingDir}/registration_approvals= - this is used by the
     default Foswiki registration process to store registrations that
     are pending verification.

{WorkingDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/working):

File path to tools directory. For example =/usr/local/foswiki/tools=.
This directory must not be web accessible.

{ToolsDir} (/var/www/vhosts/cognisys.com/httpdocs/w203/tools):

Store implementation.
<dl><dt>PlainFile</dt><dd>
(installed by the PlainFileStoreContrib) is just about the simplest store
that you can use with Foswiki. it uses simple text files to store
the history of topics and attachments, and does not require any external
programs. The use of text files makes it easy to implement 'out of band'
processing, as well as taking maximum advantage of filestore caching. This
is the reference implementation of a store.</dd></dl>
<dl><dt>RcsWrap</dt><dd>
(installed by the RCSStoreContrib) uses the 'rcs' revision control
system to store the history of topics and attachments. It calls the rcs
executables directly, and requires rcs to be installed on the server.
It's a good choice for sites that have a pre-existing Foswiki (or TWiki)
where compatibility with existing data and scripts is paramount.
Performance is generally good on most platforms except Windows.</dd></dl>
<dl><dt>RcsLite</dt><dd>
uses a pure-perl simplified implementation of the 'rcs' revision
control system.
It's a good choice for sites that have a pre-existing Foswiki (or TWiki)
where compatibility with existing data and scripts is paramount, but
RcsWrap cannot be used; for example, on  hosted platform where 'rcs'
cannot be installed, or on Windows where RcsWrap performance is poor.
</dd></dl>

{Store}{Implementation} (Foswiki::Store::PlainFile):

Set this when you are using a store that was initiated under an old
version of Foswiki, where the {Site}{CharSet} was set to something other
than 'utf-8', and you cannot convert the store to UTF8 for some reason.
This option takes the name of the encoding e.g. 'iso-8859-1'.
Note: you are *STRONGLY* recommended to convert the entire store to
UTF-8 in-place, as setting this option will incur a performance penatly.
See =tools/bulk_copy.pl= for details on converting your store.
Leave this undefined to use the default of utf-8 encoding.

{Store}{Encoding}:

This is the algorithm used to perform plain text (not query) searches.
Foswiki has two built-in search algorithms, both of which are designed to
work with the default flat-file databases (RcsWrap, RcsLite, and PlainFile).
   * The default 'Forking' algorithm, which forks a subprocess that
     runs a 'grep' command, is recommended for Linux/Unix.
     Forking may also work OK on Windows if you keep the directory path
     to Foswiki very short.
   * The 'PurePerl' algorithm, which is written in Perl and
     usually used on native Windows installations where forking
     is not stable, due to limitations in the length of command lines.
On Linux/Unix you will be just fine with the 'Forking' implementation.
However if you find searches run very slowly, you may want to try a
different algorithm, which may work better on your configuration.

Other store implementations and indexing search engines (for example,
[[http://foswiki.org/Extensions/KinoSearchContrib][KinoSearchContrib]])
may come with their own search algorithms.

{Store}{SearchAlgorithm} (Foswiki::Store::SearchAlgorithms::PurePerl): Forking
New configuration saved in /var/www/vhosts/cognisys.com/httpdocs/w203/lib/LocalSite.cfg

-----------------------------------------------------------
./view does run from cli but complains that .htpasswd not found in data

copied old .htpasswd to newly created /w203/data.

./view runs without error.

Still get 500 error from browser. Cleared history buffers in browser. Same error.
confirmed Configuration Server Firewall (csf) disabled.
Tried from new browser with no history. Still fails.
Checking .htaccess

my bin/.htaccess (only active lines):
-----------------------------------
# bin/.htaccess.txt
BrowserMatchNoCase ^$ anonymous_spider

Order Allow,Deny
Allow from all
Deny from env=anonymous_spider

SetHandler cgi-script

AuthUserFile /var/www/vhosts/cognisys.com/httpdocs/w203/data/.htpasswd
AuthName 'Enter your WikiName: (First name and last name, no space, no dots, capitalized, e.g. JohnSmith). Cancel to register if you do not have one.'
AuthType Basic

ErrorDocument 401 w203/bin/view/System/UserRegistration

Options ExecCGI FollowSymLinks

<FilesMatch "configure.*">
        SetHandler cgi-script
        Order Deny,Allow
        Deny from all
        Allow from 127.0.0.1, 192.168.1.10, 70.179.35.128, 72.220.142.178
        <!-- Require user RaymondLutz -->
        Satisfy All
</FilesMatch>
-----------------------------------

Since some of these settings go back a long way, they may be obsolete...

stuck again. 500 error.

Checked w203/working/logs/error.log
-->  empty

Hints?

--Ray



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss




--
Chris Hoefler, PhD
Postdoctoral Research Associate
Straight Lab
Texas A&M University
2128 TAMU
College Station, TX 77843-2128

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Other questions from the install

George Clark-2
In reply to this post by Raymond Lutz
On 02/08/2016 04:17 PM, Ray Lutz wrote:

         mod_perl        mod_perl is not installed.
                ModPerlEngineContrib: Required  if you're using Apache 1.3 and plan to enable mod_perl Used by: ModPerlEngineContrib
----------------------------------

The "mod_perl" error is not correct. mod_perl is installed and enabled.

Note that mod_perl is for Apache 1.3.  you are on Apache 2.x,   so you would have mod_perl2 installed.  So this is just noise.  we probably ought to remove the Dependencies included for ancient Apache 1.x

--> I don't really understand this question: sudo password for 'admin'
This replaces the old "configure password"  that had to be set when saving the configuration.  Foswiki 2.0 doesn't "require" that you set a password from configure.  If you omit it,  then you will lose access to configure unless you take other steps before logging out.  (Registering a user,  Adding them to AdminGroup,  etc...)

Since the CLI configuration is done without a web session,  we have to prompt for the password or you'd never have any way to create the first administrator.

---

What I mean is that foswiki used to use the /tmp directory for temporary files and with more than one install on a VPS, the same /tmp was used, and the filenames were not sufficiently unique, resulting a hard-to-find race condition failure. I cant tell you how many hours I spent on this. So this is a hot button for me. I don't understand why I had to manually add the TempfileDir configuration parameter to LocalSite.cfg. It should exist and have a value, and should probably be in the working directory.
On most systems,  using the system /tmp directory is sufficient.   working/tmp is a very badly named location.  It is used solely for session storage.  Foswiki 2.0 does allow the TempfileDir to be configured from bin/configure or tools/configure.  It is used to "influence" the storage of temporary files,  but some perl packages are quite insistent on using /tmp,  so it's not a guarantee even when configured.

You can query it, and set it using the CLI configure:
Konsole output
tools/configure -set {TempfileDir}='/tmp' -save
Konsole output
tools/configure -getcfg {TempfileDir}

---


./view runs without error.

Great!   So this says that at least for a simple view, perl libs, cpan dependencies, etc. are in good shape.

Still get 500 error from browser. Cleared history buffers in browser. Same error.

Is there any chance you hosting site could check the Apache error log, or the vps host apache error log? 

Looking through your .htaccess,   nothing really jumps out as "fatal".   The FilesMatch for configure is no longer needed.  But it won't cause this error. 

Could you also check ownership of the files, permissions and directories.   Make sure that Apache is able to read/write the necessary files.   That would cause a 500 error if it could not read .htpasswd,  etc.

Note that tools/configure also has a checker for validating file permissions.  It won't find ownership issues, but should detect permission errors:

Konsole output
tools/configure -check {PubDir} -method validate_permissions  
tools/configure -check {ScriptDir} -method validate_permissions   Konsole output
tools/configure -check {DataDir} -method validate_permissions      

George



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

Chris Hoefler
In reply to this post by Raymond Lutz
--> I don't really understand this question: sudo password for 'admin'

It is your (super) admin password for the /bin/configure script. You should probably leave it unset for the reasons described here,
http://foswiki.org/System/InstallationGuide#About_Administrators

 Since some of these settings go back a long way, they may be obsolete...

stuck again. 500 error.

Checked w203/working/logs/error.log
-->  empty

Hints?

Try deleting /bin/.htaccess since you don't need it anymore? Since your installation is already bootstrapped, it's hard to say why this would interfere, but it's the only thing I can think of. Your installation seems fairly standard to me otherwise.

I noticed this message from your pasted output,
AUTOCONFIG: Unable to find a valid 'grep' on the path. Forcing PurePerl search

Since you are using a linux distribution, there should probably be a grep available, so I would check your PATH settings and make sure everything is right. This is not a fatal error, it just seems a bit fishy to me and may be pointing to problems elsewhere. Or you could just have grep disabled, but I'm not sure why you would want that.

This is not possible. Perl 5.8.8 is all I can get at this point. Is there a way we can identify what the limitations are, because this seems like a show stopper.
I use Plesk panel and it does not support anything past 5.8.8. To 'require' a better perl than this VERY STANDARD level is a mistake I think.
My VPS hosting service confirmed that perl greater than 5.8.8 is not feasible.

Ok, but realize that Perl 5.8.8 is now more than 10 years old. I would be seriously investigating an upgrade path at this point. Foswiki will run on 5.8.8, but things like good Unicode support depend on newer Perl.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500

George Clark-2
On 02/08/2016 05:56 PM, Chris Hoefler wrote:
--> I don't really understand this question: sudo password for 'admin'

It is your (super) admin password for the /bin/configure script. You should probably leave it unset for the reasons described here,
http://foswiki.org/System/InstallationGuide#About_Administrators

Yikes.  no  He is configuring from the CLI,  using tools/configure.   So he has to set the Admin password, or he will have no way to create is first Administrator.

 Since some of these settings go back a long way, they may be obsolete...

stuck again. 500 error.

Checked w203/working/logs/error.log
-->  empty

Hints?

Try deleting /bin/.htaccess since you don't need it anymore? Since your installation is already bootstrapped, it's hard to say why this would interfere, but it's the only thing I can think of. Your installation seems fairly standard to me otherwise.

Ah... good point.   I'm confused now.   Ray,   did you use the ApacheConfigGenerator  for a real apache configuration,  or are you using .htaccess files.    Obviously if you don't have access to the apache configuration, you need the .htaccess.  But if you generated an apache configuration, then it is probably ignoring the .htaccess files,  but they could be deleted.

George

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500 - Store setting

Raymond Lutz
In reply to this post by George Clark-2
I am getting very close. I just wanted to let you know it is running but
I still can't see it from the world....
At this point I am trying to get any script to run in the directory....
stand by. Here is my result from your helpful comments.



Yes, I wondered if I needed to say "PlainFile" or magically come up with
the entire module description.
In CLI, just alter the help text to state exactly what needs to be
entered like
Enter one of the following:

Foswiki::Store::PlainFile
Foswiki::Store::RcsWrap
etc.

OR allow the shorthand (just PlainFile or RcsWrap) to be used in the CLI interface. I suggest the latter is better for useability.

Also, I suggest that the first message should not just "LocalSite.cfg load failed"
but "Did not find existing version of LocalSite.cfg. This is normal in a new installation."

Yes, it looks like my brain dead setting of PlainFile was corrected by the new install.
But "Forking" is probably wrong. It is the only thing I altered. And of course, I did not do it right.

In thinking back, the reason I had PlainFile wrong was because I originally set it to RcsWrap but in pursuit of getting to a baseline version that runs, backed that out.

===FROM LocalSite.cfg
$Foswiki::cfg{Store}{Implementation} = 'Foswiki::Store::PlainFile';
$Foswiki::cfg{Store}{ImplementationClasses} = [];
$Foswiki::cfg{Store}{PrefsBackend} = 'Foswiki::Prefs::TopicRAM';
$Foswiki::cfg{Store}{QueryAlgorithm} = 'Foswiki::Store::QueryAlgorithms::BruteForce';
$Foswiki::cfg{Store}{RememberChangesFor} = 2678400;
$Foswiki::cfg{Store}{SearchAlgorithm} = 'Forking';
===

I changed this to
$Foswiki::cfg{Store}{SearchAlgorithm} = 'Foswiki::Store::SearchAlgorithms::Forking';

Again, I suggest you change the prompt in the CLI interface to state EXACTLY what is expected OR allow the shorthand.

Made this change to LocalSite.cfg with no change. Still getting 500 error.

Although I hear you on the perl version issue, it will mean migrating my VPS to another node I am afraid, and that is nontrivial work that I would rather avoid at this stage.

I did this ./view >viewoutput.htm
I ftped this and viewed it locally and it looks great. I think perl is not the problem or it would have failed running the script from the CLI.

This is really close.

-Ray

On 02/08/2016 2:26 PM, George Clark wrote:

> Okay,  this was your first issue.   I can recreate this issue by setting
> the store to "PlainFile".    The proper setting is
> "Foswiki::Store::PlainFile".    Your latest re-install seems to have
> gotten by this.
>
> I've opened task http://foswiki.org/Tasks/Item13947   to improve the
> checker to detect an invalid store configuration.
>
> So your original problem is explained.   Note that this can only happen
> when using the CLI configure.  The Web interface provides a drop-down
> select that would ensure the proper value is chosen.
>
> Regarding "standard step" comment.   We are now in debugging.   And
> running the view script from the CLI really is a somewhat standard step
> when doing development.  But for basic installation it is very unusual
> to have to do this.
>
> On 02/08/2016 04:17 PM, Ray Lutz wrote:
>
> ---snip---
>> ----------
>> George Clark proposes that I run view from cli.
>> --> My comments is that this should be a standard step OR there should
>> be a test mode that can be run from cli as a standard step and provide
>> equivalent results.
>>
>> I get:
>> -------------------------------
>> bash-3.2$ ./view
>> Can't locate PlainFile.pm in @INC (@INC contains:
>> /var/www/vhosts/cognisys.com/httpdocs/w203/lib
>> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
>> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
>> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
>> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
>> /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .
>> /var/www/vhosts/cognisys.com/httpdocs/w203/lib/CPAN/lib) at
>> /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Foswiki-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
>


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500 - Store setting

Raymond Lutz
Whew, getting very close but no cigar.

Status:
I disabled .htaccess for now, copied to dothtaccess

$ ./view >viewoutput.htm   <-- this runs and the output is beautiful
when I open it in a browser

So this means perl and packages are all running (and shebang works)

but http://www.cognisys.com/w203/bin/view
produces 500 error.

I uploaded this script:
    simple.pl   <-- this runs and produces status of the server.
Try it.
http://www.cognisys.com/w203/bin/simple.pl

Copied to simple (no extension) and it produces the source of the
script. Thus I need the setting in .htaccess to allow no extension.
http://www.cognisys.com/w203/bin/simple


Created view.pl This fails too.
http://www.cognisys.com/w203/bin/view.pl

I tested shebang and it is not it.

Any ideas?

--Ray



On 02/08/2016 3:27 PM, Ray Lutz wrote:

> I am getting very close. I just wanted to let you know it is running but
> I still can't see it from the world....
> At this point I am trying to get any script to run in the directory....
> stand by. Here is my result from your helpful comments.
>
>
>
> Yes, I wondered if I needed to say "PlainFile" or magically come up with
> the entire module description.
> In CLI, just alter the help text to state exactly what needs to be
> entered like
> Enter one of the following:
>
> Foswiki::Store::PlainFile
> Foswiki::Store::RcsWrap
> etc.
>
> OR allow the shorthand (just PlainFile or RcsWrap) to be used in the CLI interface. I suggest the latter is better for useability.
>
> Also, I suggest that the first message should not just "LocalSite.cfg load failed"
> but "Did not find existing version of LocalSite.cfg. This is normal in a new installation."
>
> Yes, it looks like my brain dead setting of PlainFile was corrected by the new install.
> But "Forking" is probably wrong. It is the only thing I altered. And of course, I did not do it right.
>
> In thinking back, the reason I had PlainFile wrong was because I originally set it to RcsWrap but in pursuit of getting to a baseline version that runs, backed that out.
>
> ===FROM LocalSite.cfg
> $Foswiki::cfg{Store}{Implementation} = 'Foswiki::Store::PlainFile';
> $Foswiki::cfg{Store}{ImplementationClasses} = [];
> $Foswiki::cfg{Store}{PrefsBackend} = 'Foswiki::Prefs::TopicRAM';
> $Foswiki::cfg{Store}{QueryAlgorithm} = 'Foswiki::Store::QueryAlgorithms::BruteForce';
> $Foswiki::cfg{Store}{RememberChangesFor} = 2678400;
> $Foswiki::cfg{Store}{SearchAlgorithm} = 'Forking';
> ===
>
> I changed this to
> $Foswiki::cfg{Store}{SearchAlgorithm} = 'Foswiki::Store::SearchAlgorithms::Forking';
>
> Again, I suggest you change the prompt in the CLI interface to state EXACTLY what is expected OR allow the shorthand.
>
> Made this change to LocalSite.cfg with no change. Still getting 500 error.
>
> Although I hear you on the perl version issue, it will mean migrating my VPS to another node I am afraid, and that is nontrivial work that I would rather avoid at this stage.
>
> I did this ./view >viewoutput.htm
> I ftped this and viewed it locally and it looks great. I think perl is not the problem or it would have failed running the script from the CLI.
>
> This is really close.
>
> -Ray
>
> On 02/08/2016 2:26 PM, George Clark wrote:
>> Okay,  this was your first issue.   I can recreate this issue by setting
>> the store to "PlainFile".    The proper setting is
>> "Foswiki::Store::PlainFile".    Your latest re-install seems to have
>> gotten by this.
>>
>> I've opened task http://foswiki.org/Tasks/Item13947   to improve the
>> checker to detect an invalid store configuration.
>>
>> So your original problem is explained.   Note that this can only happen
>> when using the CLI configure.  The Web interface provides a drop-down
>> select that would ensure the proper value is chosen.
>>
>> Regarding "standard step" comment.   We are now in debugging.   And
>> running the view script from the CLI really is a somewhat standard step
>> when doing development.  But for basic installation it is very unusual
>> to have to do this.
>>
>> On 02/08/2016 04:17 PM, Ray Lutz wrote:
>>
>> ---snip---
>>> ----------
>>> George Clark proposes that I run view from cli.
>>> --> My comments is that this should be a standard step OR there should
>>> be a test mode that can be run from cli as a standard step and provide
>>> equivalent results.
>>>
>>> I get:
>>> -------------------------------
>>> bash-3.2$ ./view
>>> Can't locate PlainFile.pm in @INC (@INC contains:
>>> /var/www/vhosts/cognisys.com/httpdocs/w203/lib
>>> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
>>> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
>>> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
>>> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
>>> /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .
>>> /var/www/vhosts/cognisys.com/httpdocs/w203/lib/CPAN/lib) at
>>> /var/www/vhosts/cognisys.com/httpdocs/w203/lib/Foswiki.pm line 1762.
>>
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> _______________________________________________
>> Foswiki-discuss mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
>>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Foswiki-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
>


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: installation error 500 - Store setting

George Clark-2
On 02/08/2016 07:49 PM, Ray Lutz wrote:
> So this means perl and packages are all running (and shebang works)
>
> but http://www.cognisys.com/w203/bin/view
> produces 500 error.
Can you post your apache configuration?

Other than maybe spotting an issue in the config. gainig access to the
Apache log is about the only other thing I can suggest.

George


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Foswiki-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/foswiki-discuss
12
Loading...