Bernard Li wrote: > Hi all: > > I've had si_monitortk seg fault on me a couple of times already but it > seems to be getting worse and I would like to get to the bottom of it. > > What is the best way to figure out why exactly did it crash? > Currently I do not think si_monitor logs any messages in log files > (/var/log/systemimager/si_monitor.log is always empty), but perhaps we > should starting doing it to help troubleshoot problems? > > I am running strace with si_monitortk right now, but it doesn't look > like it is going to crash, it is somewhat intermittent and hard to > predict when it will crash :(
Bernard, the main problem is that perl-Tk is quite buggy... :-( have you tried to update it to a more recent releaes? I'm using v800.024 without problems, also when I try to install a lot of clients... Moreover, in si_monitor.log are reported only the log messages of the monitoring daemon (si_monitor) and I don't think it's the right place for the log messages of the si_monitortk interface. To debug the problem you could try to generate a core dump when the segfault occurs (just set core file size to unlimited `ulimit -c unlimited`), and try to analyze the core dump with gdb... but I'm quite sure that an update of perl-tk will strongly reduce your segfaults... Cheers, -Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
