Re: acidlab/php problem

2005-01-05 Thread Kenneth Jacker
  jbouse> I don't recall having yet seen a BTS entry from you so don't
  jbouse> have any further info to help from.

Thanks to Jeremy's comment above, I have succeeded in getting
'acidlab' to work correctly on sarge/testing!

First I checked out:

  http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=acidlab

and then:

  http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=acidlab-mysql

The second entry (#232091) on the above page contains a response from
Steve Langasek which states:

   Please confirm that you have the mysql.so extension *enabled* in
   the php.ini config for whichever PHP SAPI you're using
   (/etc/php4/apache/php.ini or /etc/php4/cgi/php.ini).


This resulted in my changing a portion of the "Dynamic Extensions"
section in /etc/php4/apache/php.ini to contain:

  extension=mysql.so
  extension=gd.so

That did it!

So, thanks to Jeremy for heading me in the right direction and Steve
for sharing the solution ...

As I've said before (in similar words):  Debian Rocks!

  -Kenneth


  


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: acidlab/php problem

2005-01-04 Thread Jeremy T. Bouse
You know another fine point to look first when having a problem
might be the developer maintaining the package itself. That would be
myself. From what I gleen from this email it's not enough and I don't
recall having yet seen a BTS entry from you so don't have any further
info to help from.

Regards,
Jeremy

On Tue, Jan 04, 2005 at 05:59:54PM -0500, Kenneth Jacker wrote:
> [sarge/testing; 2.6.8-1-686-smp 
>  snort-mysql-2.2.0-9 acidlab-0.9.6b20-10 php4-mysql-4:4.3.10-2
>  apache-ssl-1.3.33-2 mysql-server/mysql-common- 4.0.22-6 ... ]
> 
> I've tried about everything (including multiple installs of 'mysql',
> 'php4', and 'snort') I can think of, but no luck. So am turning to d-u ... !
> 
> Has anyone gotten snort-mysql and acidlab to work on 'sarge'?
> 
> The DB side is fine ... queries show that 'snort' is adding info.  The
> problem is with the initial web page (needed to initialize 'acidlab')
> of "https://acme.cs.appstate.edu/acidlab/acid_main.php";.  No matter
> what I do, I always get the following URL response:
> 
>   PHP ERROR: PHP build incomplete: the prerequisite MySQL support
>   required to read the alert database was not built into PHP. Please
>   recompile PHP with the necessary library (--with-mysql)
> 
> Note that 'phpmyadmin' works fine which suggests it isn't a 'php' problem.
> 
> Anyone know what a solution might be?
> 
> Thanks,
> 
> -- 
> Prof Kenneth H Jacker   [EMAIL PROTECTED]
> Computer Science Dept   www.cs.appstate.edu/~khj
> Appalachian State Univ
> Boone, NC  28608  USA
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 


signature.asc
Description: Digital signature


acidlab/php problem

2005-01-04 Thread Kenneth Jacker
[sarge/testing; 2.6.8-1-686-smp 
 snort-mysql-2.2.0-9 acidlab-0.9.6b20-10 php4-mysql-4:4.3.10-2
 apache-ssl-1.3.33-2 mysql-server/mysql-common- 4.0.22-6 ... ]

I've tried about everything (including multiple installs of 'mysql',
'php4', and 'snort') I can think of, but no luck. So am turning to d-u ... !

Has anyone gotten snort-mysql and acidlab to work on 'sarge'?

The DB side is fine ... queries show that 'snort' is adding info.  The
problem is with the initial web page (needed to initialize 'acidlab')
of "https://acme.cs.appstate.edu/acidlab/acid_main.php";.  No matter
what I do, I always get the following URL response:

  PHP ERROR: PHP build incomplete: the prerequisite MySQL support
  required to read the alert database was not built into PHP. Please
  recompile PHP with the necessary library (--with-mysql)

Note that 'phpmyadmin' works fine which suggests it isn't a 'php' problem.

Anyone know what a solution might be?

Thanks,

-- 
Prof Kenneth H Jacker   [EMAIL PROTECTED]
Computer Science Dept   www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]