Hello,

Sorry sorry sorry... this is a server running Midgard v1.4!
Was this bug corrected in v1.4.1?

Hope you didn't spend much time on this,
benjamin


"ISNARD,BENJAMIN (HP-France,ex1)" wrote:
> 
> Hello,
> 
> The versions I'm using are:
> RedHat6.2
> apache-1.3.12
> php-4.0.5
> the midgard versions are those from the web site
> midgard-lib-1.4.1-5
> midgard-php4-1.4.1-7
> mod_midgard-1.4.1-5
> 
> How can I apply this database switching patch?
> Tks!
> benjamin
> 
> alan_k wrote:
> >
> > We did see something similar before
> > adding the database switching patch.
> >
> > Which version of midgard are you using?
> >
> > Emiliano <[EMAIL PROTECTED]>
> > Forwarded From:
> >
> > > ISNARD,BENJAMIN (HP-France,ex1)
> > wrote:
> > >
> > > > I now have an apache configuration
> > with 2 virtualhosts which both use the
> > > > midgard engine but on 2 different
> > midgards databases, because one of the
> > DB
> > > > is a replication from another
> > host...
> > > > and it seems that when requesting a
> > (midgard) host on one virtualhost, the
> > > > midgard engine opens a connection
> > randomly to one or the other midgard
> > > > database, therefore giving a '404
> > page not found' quite frequently
> > because
> > > > there's no corresponding host in
> > the other db.
> > > > Is this setup not valid?
> > >
> > > Should be. If you set LogLevel to
> > debug, midgard will tell you in the
> > > error log which database it's trying
> > to open for which host. I'll try
> > > to recreate the problem.
> > >
> > > Emile
> > >

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to