On Thu, Aug 10, 2006 at 11:21:40AM +0200, Martin Sebald wrote: > > Very strange, though. If you turn the log level in Apache down to debug, > > you should get a pretty comprehensive trace of what's being done; that > > info might help pinpoint the cause of the trouble. > > I'll do that and click through the Typo3 backend and hope that the error > accurs soon. As this is a live server with many paying customers on it I > cannot do this very long. ;-) I'll be back with the result soon.
You don't have a staging/test environment where you can try out things like this? > >> I found a similar bug from 2004 on Google, bug # 287160, there the > >> problem was with version 4.3.9-1, but I cannot see any clue. > > That was originally, but the problem still exists in 4.3.9-2. I've got > > to get around to fixing that, and I'd imagine that it'll solve the > > problem for you too, actually. Can you try the fix described in > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287160;msg=135 and see > > if it does the job for you, too? > > Ah thank you for the link. But as written above: This is a live server and > as our own policy we do not compile any packages. We only use "final" > packages. Well, not the best idea to use a hybrid system with stable and > unstable packages, but stable is sometimes really unusable for us. I'd go beyond "not the best idea", all the way to "downright foolhardy". Unstable is, on occasion, quite unstable, and only running pre-packaged versions severely cramps your style in deploying bugfixes and customising software to suit your needs -- the very *epitomy* of what Free Software gives you. I know something of what I speak of here, too -- one of things I do in my job is put together new and customised packages to suit business needs. It's *crucial* to being able to give the best possible result, especially if you're using a moving target / possibly dangerously buggy suite of packages. I'm not trying to be harsh, but seriously, kill that policy. And setup a Xen instance to test things out on. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
