Installation Issue

[powderpa]

I am attempting to install the beta, and ran into a snag right out of the gate.

When running install.php I receive this very pretty error:

Warning: dl() [function.dl]: Temporary module name should contain only filename in /homepages/11/d218037147/htdocs/greenvillepc/billing/install.php on line 8
PHP script /homepages/11/d218037147/htdocs/greenvillepc/billing/install.php is protected by SourceGuardian and requires the SourceGuardian loader ixed.5.2.lin. The SourceGuardian loader has not been installed, or is not installed correctly. Please visit the SourceGuardian php encoder site to download required loader.

This is what I have done thus far:

I uploaded public_html into domain/billing

I uploaded the directories ixed and cron to ~/

I edited the cronjob.php to change the path as the instructions indicated, I changed it to: $path_to_cron = "../../cron/";

I ran the install.php, when, very politely it upchucked all over the place.

The server, is configured by default to run php 4.x, however, per the hosting providers instructions, I created an .htaccess file with the following code: AddType x-mapp-php5 .php

This enables me to map .php files located within the /billing subdirectory to use php5 instead of 4, a phpinfo() now returns: PHP Version 5.2.6 as the php version.

Is there a php.ini modification that is required for this to work? I poked around the forum and saw some references to php.ini, but before I break everything else, I thought I would ask here first, as my error did not really match any other i found on the forum exactly.

Also, in typical newbie fashion, attempting to cheat the system, I did relocate the idex directory to ../ to sync up with the instructions, and this made no difference.

Thank you.

- Keith

[Paul]

Hi Keith,

Thanks for the detailed breakdown. PHP 5.2+ requires a modification to php.ini for I'm pretty sure every type of encoder, including Source Guardian. It's due to a change in PHP. If you download this file, unzip and run it.. http://www.sourceguardian.com/ixeds/...to-install.zip

... it will tell you exactly which ixed loader needs to go in exactly what directory as well as the very minor 1 line change required in php.ini.

We are considering releasing a zend version because zend optimizer (which is required, like SG's ixed loaders) may be more widespread.. in addition to Source Guardian, but no official decision has been made of yet.

I hope this helps, let us know if there is anything else we can do to help you get up and running.

Paul

[powderpa]

Two questions:

What directory should I run that php file from? It makes two suggestions, and these change depending from where I run it.

How to install SourceGuardian loaders
Server-wide setup

   1. Download ixed4.lin.x86-32.tar.gz (for Intel x86 32-bit processor) or ixed4.lin.x86-64.tar.gz (for Intel x86 64-bit processor)
   2. Extract it to folder /usr/lib/php/extensions/no-debug-non-zts-20060613
   3. Edit PHP.INI file (located at /usr/lib/php5/php.ini) and add following line:
      extension=ixed.5.2.6.lin

Run-time loading

   1. Download ixed4.lin.x86-32.tar.gz (for Intel x86 32-bit processor) or ixed4.lin.x86-64.tar.gz (for Intel x86 64-bit processor)
   2. Extract it to folder /homepages/11/d218037147/htdocs/greenvillepc/billing/ixed/

Of course, the only option I have here is the run-time loading, as the system wide php.ini is not available for editing, or is placing any files outside of the home directory (however, i can add directives to the php.ini on a per directory basis). Giving it the illusion that what ever additional configs i add are in fact system wide. But I don't think I have any fancy tricks to make it think its located in the /usr partition.

Second question:

How do I tell if the machine is 32/64?

a uname -a results in:
Linux infong594 2.6.16.33-20070131a-areca-filemon-3ware-e1000 #1 SMP Wed Jan 31 02:48:22 CET 2007 i686 GNU/Linux

a cat /proc/cpuinfo results in:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz
stepping	: 6
cpu MHz		: 1600.355
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 cx16 xtpr lahf_lm
bogomips	: 3206.88

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz
stepping	: 6
cpu MHz		: 1600.355
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 cx16 xtpr lahf_lm
bogomips	: 3200.39

processor	: 2
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz
stepping	: 6
cpu MHz		: 1600.355
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 cx16 xtpr lahf_lm
bogomips	: 3200.48

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5110  @ 1.60GHz
stepping	: 6
cpu MHz		: 1600.355
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 cx16 xtpr lahf_lm
bogomips	: 3200.45

Is there another command that I could use to find out if the host processor is 32/64? My gut feeling is 32.

Thank ya much,

- Keith

[Paul]

The i686 in the uname command indicates that it is indeed 32 bit, though your hardware architecture would support 64 bit.

Here's the fun part -
2. Extract it to folder /usr/lib/php/extensions/no-debug-non-zts-20060613
3. Edit PHP.INI file (located at /usr/lib/php5/php.ini) and add following line:
extension=ixed.5.2.6.lin
Step 1 mentions the PHP 4 ixed loader, but I think it got confused because you have both PHP 4 and PHP 5 installed. Are you on a VPS or you just have shell access to an account on a shared server?

Adding php directives from step 3 above may or may not work if you don't do it in /usr/lib/php5/php.ini - you can try your directory option and see if it works or not. If not, your hosting company should be able to do this for you. It's a simple change and I've yet to see a hosting company refuse to do it.

[powderpa]

When i added the php.ini line, it said: extension_dir does not exists /usr/local/lib/php/extensions/no-debug-non-zts-20060613

and it would be correct, as I have no write permission to place it there. There may be a directive to change the extension_dir I can add to my local php.ini to reconfigure the above path. I'm not 100%, will do some research.

Ignoring the php.ini mod, and just simply unzipping the file to the idex directory under billing, as outlined in the run time instructions it resulted in the same error message as before. No change.

Its shared hosting, with ssh access. 1and1.com is the host. I've never contacted support, so Im not sure exactly how they will react to such a request. They are a german company, I hope I don't get stuck talking to an angry german on the other end of the line.

If they fail to do this, I'll simply go sign up some place else to install this. I'll just point a subdomain at another hosting company. Any hosting recommendations? Cheaper the better.

When I do talk to support, I'm not sure I know how to word my question to properly convey what I need. How would i convey my need to them? I need xxx installed? I need you to download this file and stick it here? Honestly, I'm not 100% sure I fully understand what i'm doing myself. I'm just good at following directions.

I'm going to hit their online faq's as they do have alot of stuff preinstalled, but making it work sometimes takes slight modifications from the normal methods. As a last resort before I contact support.

If i find a solution, I will post it here, if not, I'm up for suggestions for a hosting provider for the script. I'm 99.9% sure if I can make it work, I want it after using the online demo.

Thanks,

- Keith

[powderpa]

Welcome to the Blesta Installation script. This will guide you through setting up Blesta on your server.

Before you proceed, please create your database (if you haven't already).

Note: You do not need to create any tables. This installation script will do that automatically. You must, however, create a database for Blesta to use. All of the information requested below is REQUIRED. You may not leave any field empty. THIS IS NOT AN UPGRADE SCRIPT. If you wish to upgrade from a previous version of Blesta to 1.3.0 click here.


This is what I needed to do. I don't know if you can use this method if this comes up for anybody else.

In the billing directory I have: a php.ini that contains:

extension=ixed.5.2.6.lin
extension_dir="/kunden/homepages/11/d218037147/htdocs/extention/no-debug-non-zts-20060613"

This only effects any running php scripts within the billing directory. (You also need to copy the php.ini to any subdirectories that contain executable php scripts)

I created an ~/extention/suggested_dir_name directory outside of the web access directory as suggested in the manual. Unzipped, refreshed, and was presented with the installation page, with all green OK's. I'm assuming green is a good color.

Thanks for your help, hope this might help someone in the future that has this problem.

- Keith

Ps. I see sucess is spelled incorrectly, I'm an idiot.

[Paul]

Awesome thanks for the feedback! So I take it you're fully up and running?

If there's anything you need help with let us know, and thanks for trying Blesta!

Paul

[powderpa]

Its fully up and running and I'm messing around with it. However, I did have some issues with the config with paths being wrong, took me a while to figure that out, but i got it.

To be very honest, I'm a nerd, not a billing clerk, so it seems very overwhelming to me. I think once I struggle through learning it, it will be exactly what I'm looking for.

Is it possible to send late notices before the due date? I know that sounds retarded, but lets say I have a DSL customer, payments are due on the 25'th of each month. If we do not deactivate their service, we get charged for the next months of service if it goes over the first of the next month. (It takes a few days to deactivate dsl, so we need some buffer).

So, let me, baa god, i'm so bad at billing stuff. Let me try to word it in another way.

John doe signs up on the first. His first bill is a pro-rated amount from the first to the 25'th. If we don't see a payment by the 26'th for the next months service, his service will be terminated.

Pro rating I'm assuming is a basic feature that should be easy to figure out? Even if prorated was done by hand, in a manually edited invoice, thats fine.

We offer DSL, it takes a few days to deactivate a customer, and if it runs over into the next month, we get charged from our provider for that customer. We want to avoid that.

So, in this configuration, the customer should receive a reminder notice a few days prior to the actual due date, vs after the due date. Since the day AFTER the due date, his service would be marked for suspension.

Now I may make no sense what so ever, but at least now I understand MYSELF. And i hope thats enough for you to understand it as well. I'm better at fixing things that are broke, then using things that work.

Thanks much man,

You've been a big help.

[powderpa]

I also noticed, the cronjob returns: Key validation failed.

I used the "License" key, located in tools/settings. Do you do it with or without the {}'s as in the example? I did it using, and not using, both returned failed.

my cron looks like:

0,15,30,45 * * * * GET -t 15m http://www.greenvillepc.net/billing/cronjob.php?key={I PUT MY KEY HERE with and WITHOUT {}'s}&cron=all > /dev/null 2>&1 &

- Keith

[Paul]

Originally Posted by powderpa

I also noticed, the cronjob returns: Key validation failed.

I used the "License" key, located in tools/settings. Do you do it with or without the {}'s as in the example? I did it using, and not using, both returned failed.

my cron looks like:

0,15,30,45 * * * * GET -t 15m http://www.greenvillepc.net/billing/cronjob.php?key={I PUT MY KEY HERE with and WITHOUT {}'s}&cron=all > /dev/null 2>&1 &

- Keith

A lot of people make this mistake.. which means we need to improve how we communicate what to do. Your key is not your license key, but your remote access key as found under Tools->Settings, under "Standard Settings". The remote access key is used for cron validation as well as API calls. Also just use key=YOURKEY no quotes or anything