Am 22.06.2011 um 22:25 schrieb Russell Van Tassell: > Just the typical "stupid" questions... did you compile icinga as 32 or 64 > bit? Were they compiled with the current kernel/libc versions, or with one > prior to it? Have you shut down all the icinga processes, and then restarted? > Are you using IDO?
That was, why I show uname: 64Bit Yes, with the current kernel/libc Shutting down the whole machine Yes, I use IDO, but that isn't used for status.cgi > When you say "all others are working," what are you seeing, specifically? > Have you tried other browsers? Other client machines? Much of the old UI is > handled by "status.cgi" ... are all those pages not working at all with all, I mean all other *.cgi > From what I've seen via google, these segfaults it sound generally more like > version compatibilities (at least with other tools/packages). I found them too, but I have this problem since yesterday and I didn't update anything, nor I changed anything. cu denny ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
