Hi Andrea:
Since rebuilding perl-Tk on RHEL4 w/ Perl 5.8.5 (as opposed to the one
built with Perl 5.8.0), I no longer get the segfault. I have checked
the updated perl-Tk RPM into OSCAR trunk.
Thanks,
Bernard
On 4/27/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
> Bernard Li wrote:
> >> Moreover
Bernard Li wrote:
>> 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
Hi Andrea:
I've just had si_monitortk segfault on me again, so I'm replying to
this (old) thread:
On 2/23/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
> 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 proble
Bernard Li wrote:
> Was testing SystemImager trunk (3.9.0) on Fedora Core 6 i386 and got
> the following error during the middle of imaging:
>
> XS_Tk__Callback_Call error:
> no element found at line 1, column 0, byte 0 at
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/XML/Parser.pm
>
Was testing SystemImager trunk (3.9.0) on Fedora Core 6 i386 and got
the following error during the middle of imaging:
XS_Tk__Callback_Call error:
no element found at line 1, column 0, byte 0 at
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/XML/Parser.pm
line 187
Traceback:
no element
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
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/systemima
L PROTECTED]
> Cc: Bernard Li; sisuite-devel@lists.sourceforge.net
> Subject: Re: [Sisuite-devel] si_monitortk progressbar disabled
>
> Bernard, if you can test, does with si_monitortk of r3612
> work? I don't
> see any strangeness in the code...
>
> -Andrea
&
Bernard, if you can test, does with si_monitortk of r3612 work? I don't
see any strangeness in the code...
-Andrea
Andrea Righi wrote:
> ouch... I'm poking...
>
> Bernard Li wrote:
>> Hi Andrea:
>>
>> For me on Fedora Core 5, it was showing the numerical percentage through
>> the whole thing eve
ouch... I'm poking...
Bernard Li wrote:
> Hi Andrea:
>
> For me on Fedora Core 5, it was showing the numerical percentage through
> the whole thing even when 0 < $status < 100.
>
> Perhaps I can poke around the code to see what's wrong...
>
> Cheers,
>
> Bernard
>
_
ROTECTED]
> Sent: Thursday, June 08, 2006 10:26
> To: Bernard Li
> Cc: sisuite-devel@lists.sourceforge.net
> Subject: Re: [Sisuite-devel] si_monitortk progressbar disabled
>
> Bernard,
>
> in the last si_monitortk the progress bar is shown only when
> 0 < $status
>
Bernard,
in the last si_monitortk the progress bar is shown only when 0 < $status
< 100, I mean not for "special" states. I think in these cases it's
better to show an explicit label instead of the bar. Otherwise the
status of the node could be misleading, for example when the
installation is near
Hi Andrea:
I think the recent changes to
si_monitortk may have inadvertantly disabled the progressbar. It shows the
numerical progress even though --progress was passed (this is the default
setting for OSCAR).
Appreciate it if you can take a look
at this.
Thanks,
Bernard___
Right! I can recycle that from my web interface... and I think it can be
implemented without big efforts, since HList already supports image
elements...
-Andrea
Bernard Li wrote:
> Hey Andrea:
>
> Instead of using percentages to visualize image status, how about using
> a color progress bar? I
Hey Andrea:
Instead of using percentages to
visualize image status, how about using a color progress bar? I think it
was like that in your initial web prototype - think you can implement
this?
Cheers,
Bernard
And dmesg ;-)
Cheers,
Bernard
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Andrea Righi
> Sent: Wednesday, January 25, 2006 9:24
> To: Jeremy Enos
> Cc: sisuite-devel@lists.sourceforge.net
> Subject: Re: [Sis
Jeremy,
at the moment si_monitortk is able to show only some messages sent by an
explicit command (logmsg). So the purpose, for now, is only to give a
simple log-like feedback.
In the next releases we'd like to have a complete feedback (I mean
stdout+stderr over IP) and we're working to modi
Does si_monitortk only show stdout (not stderr)? That's what it appears
like to me, which would kind of defeat the purpose of it.
Jeremy
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop
It seems to be an error when sorting the clients table.. can you post
your /var/lib/systemimager/clients.xml?
Cheers,
-Andrea
Bernard Li wrote:
Hey Andrea:
I just got the following error message (on the terminal):
Argument "\x{67}\x{30}..." isn't numeric in numeric comparison (<=>) at
/usr/s
Hey Andrea:
I just got the following error message (on the terminal):
Argument "\x{67}\x{30}..." isn't numeric in numeric comparison (<=>) at
/usr/sbin/si_monitortk line 590.
Argument "\x{67}\x{30}..." isn't numeric in numeric comparison (<=>) at
/usr/sbin/si_monitortk line 590.
Any ideas what's
20 matches
Mail list logo
