From: Matt Harrison <iwasinnamuknow@genestate.com>
To: gentoo-user@lists.gentoo.org
Subject: [SOLVED] Re: [gentoo-user] segfaults with php and cacti
Date: Sat, 05 Jul 2008 14:17:49 +0100 [thread overview]
Message-ID: <486F747D.9080008@genestate.com> (raw)
In-Reply-To: <1F802ACB-C2A0-46DE-951C-9F84BD37A48D@stellar.eclipse.co.uk>
Stroller wrote:
>
> On 4 Jul 2008, at 20:38, Matt Harrison wrote:
>> ... I want to add the cacti application to the same server but on a
>> separate
>> vhost.
>>
>> The problem is, trying to access the cacti interface through a browser
>> causes a segfault with php. I've also tried running the index.php from
>> the CLI and it still segfaults.
>
> I don't know anything about cacti but IIRC PHP4 & PHP5 are a bit
> different (in terms of Apache modules & stuff). Is it possible you're
> running the wrong one? Maybe this release of cacti is only stable on the
> one version?
>
> When posting try to give us as much information as possible. You need to
> give versions of stuff, confirm that you've run revdep-rebuild on your
> system and also tell us that you've checked the system logs. Since you
> don't mention debug or logging options for cacti I'll assume it doesn't
> have any, but you really need to state that, to prove to us that you've
> checked and to save us suggesting looking at them.
>
> Stroller.
Ack, I had forgotten to import the db schema before accessing the web
interface. I just wish the cacti people had found a way to make this
more obvious. I will send them a message and maybe they can make this a
little clearer in the future.
Thanks for the replies everyone.
Matt
--
gentoo-user@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-07-05 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 19:38 [gentoo-user] segfaults with php and cacti Matt Harrison
2008-07-05 8:54 ` [gentoo-user] " James
2008-07-05 12:55 ` [gentoo-user] " Stroller
2008-07-05 13:17 ` Matt Harrison [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=486F747D.9080008@genestate.com \
--to=iwasinnamuknow@genestate.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox