freebsd 8.0, jail, installation errors [SOLVED]

redshirt

Interested in using epesibim. Have PC-BSD 8.0 (FreeBSD 8) running w/ jails via ezjail utility. Jailed environment working. Installed via ports: Apache22, php5 (5.3.2) w/ extensions, pear-1.9.0, nolapro php accounting w/ ioncube extensions, MySQL5 (5.0.90), and phpMyAdmin. Have epesi database created and ready to connect (user, password set).

I noticed some of pear is deprecated in php-5.3.2, or so it seems? Pear binary is at /usr/local/bin/pear, so it did install despite deprecated features.

Please note, I have no idea where the much lauded config.php file is that folks mention in the forums.

The first error I get is that the .htaccess the epesi php is trying to create from htaccess.txt is nto compatible with the hosting environment. I notice in the /usr/local/etc/php.ini file that the memory_limit = 128M.

Proceeding yields these errors:

Strict Standards: Declaration of HTML_QuickForm_header::accept() should be compatible with that of HTML_QuickForm_element::accept() in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm/header.php  on line 39

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Declaration of HTML_QuickForm_html::accept() should be compatible with that of HTML_QuickForm_element::accept() in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm/html.php on line 76

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Where do I start to fix this combination of errors?

shacky

Hi,
I think you have E_STRICT enabled in php.ini.
Please look for line like this



error_reporting = E_ALL | E_STRICT

If it's there please try without E_STRICT and report if it works.

Thanks
Paul

shacky

One more thing, sometimes there are more then one php.ini. There can be one for CLI, one for CGI, one for apache php module.... So get accurate one.

Paul

redshirt

Thank you! That solved the second error set. It proceeds to the database setup screen. But before I go there...

The installer also posted this error:

"Your hosting is not compatible with default epesi root .htaccess file. You should tweak it yourself. Default .htaccess file is:"

Now, regardless of what I make the htaccess.txt file, it complains. I'm not exactly sure what epesi installer is looking for. Memory is set in excess of 64M already. Is there a specific access rule for the directory?

The default htaccess.txt was:

Options -Indexes
php_value memory_limit "64M"
php_flag magic_quotes_gpc off
#SecFilterEngine Off

The directory settings in http.conf are:

<Directory "/usr/web/epesibim">
Options Indexes FollowSymLinks
AllowOverride AuthConfig
Order allow,deny
Allow from all
</Directory>

shacky

Hi,
this is just warning, that epesi is using your default settings, because your http server returned error with default epesi htaccess. You can try what line fails by renaming htaccess.txt to .htaccess and commenting out line by line and trying if epesi starts.

Some hints:
Turn off Indexes for best security.
Memory limit set at 128MB is OK, because it's bigger than default epesi value 🙂
Magic Quotes doesn't metter - epesi will autodetect it, but if you want get slighter less processing time of big requests turn this off in php.ini or with htaccess.

Paul

redshirt

Not understanding the process. Epesi does not create a .htaccess file. I can manually create it, but it still reports the errors based on htaccess.txt. It also completely ignores any changes I make in that file. It reports the same error even if the file is blank.

There are no obvious apache errors related to epesi unless I remove the htaccess.txt file, then it yields php errors related to the absent file.

I do see this: [Wed May 26 22:37:29 2010] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]

Is epesi looking for ssl?

Shoot. I see a new release. OK, I will download that and see what happens.

-r

redshirt

Well it makes no sense. With 1.09, and the php.ini settings that stopped the Strict error messages, I still get the error messages.

Strict Standards: Declaration of HTML_QuickForm_header::accept() should be compatible with that of HTML_QuickForm_element::accept() in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm/header.php  on line 39

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

Strict Standards: Declaration of HTML_QuickForm_html::accept() should be compatible with that of HTML_QuickForm_element::accept() in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm/html.php on line 76

Strict Standards: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/web/epesibim/modules/Libs/QuickForm/3.2.10/HTML/QuickForm.php on line 636

htaccess errors still present.

Any ideas? Can I proceed or is it going to crash? Guess I might just give it a go.

redshirt

OK. I got it installed!

Epesi wouldn't allow the process to proceed with the posted errors. I looked for more ways to suppress the STRICT coding errors. Found the following setting worked:

display_errors = Off

This is in addition to commenting out (; comment out):

;error_reporting = E_ALL | E_STRICT

The FreeBSD install default was for it to be enabled. But the DEFAULT php setting once commented out is as noted in the php.ini file:

; error_reporting
; Default Value: E_ALL & ~E_NOTICE
; Development Value: E_ALL | E_STRICT
; Production Value: E_ALL & ~E_DEPRECATED

shacky

Great! And thanks for fix suggestions - version on sf svn should not throw errors on configuration like yours any more.

Paul

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge