Topic: System Monitor

[Derek]

I have installed the System Monitor package and it's 2 dependant packages. However, the graphs show up as broken links in my e-smith manager.

Has anyone encountered this problem or had experience getting this package working properly?

TIA

Derek

[Robert Heaton]

I had no problems using the system monitor, first I installed the two dependent packages;

rrdtool-1.0.28-1.i386.rpm
sysstat-3.3.3-3.i386.rpm

Then I installed the monitor;
e-smith-monitor_en-1.0-02.noarch.rpm

And I have had no problems, I'm using E-smith 4.1.2 I take it you're using the same???


Rob.

[Derek]

Hi Rob,

I'm using 4.1.1  I wonder if that could be a factor?

I installed the packages using rpm -ivh rrdtool...etc. Is that the same way you did it?

Derek

[Nate]

I have it installed on 4.1.1 it works great.

[Derek]

Hmmm....

I uninstalled it using rpm -e..and then reinstalled.

Works great now.

Gremlins I guess.

[vikram]

Hi

HOw do i install the system monitor and what all we can do with it.

reg

[Derek]

Go to this website. You can download the packages and it explains everything.

http://modesmith.dogbox.homeip.net/

[steve]

Fantastic addition

[DavidG]

Yes. I have the same issue from time to time. The fix is to simply force a re-install of the monitor rpm. It has only happened to my system when I've updated other components. The fix seems simple enough.

Nother question -

The HD usage graph is solid green - I can't see any "headroom". I'm using a MegaRAID adapter and RAID5 so I figured "monitor" can't see thru the HW BIOS on the adapter. Know of any workaround?

[Derek]

I don't know of a workaround but the developers are aware of the problem and I think that they are trying to include a fix in the next rpm release. You might want to search the developer mailing list archive to get more info.

[Jaime Nebrera]

Hi David,

  I'm one of the developers of e-smith monitor and can promise that besides Derek says we didn't know about this )))

  To calculate hd usage we run df -k every 15 minutes and take the info directly from it. If this command works under RAID you should not find any problem. The problem is we dont have any RAID (software nor hardware) and can't test it (the same thing happened with the network interfaces, our system is very simple).

  BTW, we have run into 2 problems while developing our new release:

    1) The Wpassword bug" or sometimes "graphs don't appear". This is a Perl related problem with the permissionjs of the monitor function. If we use the -T switch it seems some people get a "admin password bug". If we remove the -T but put the script with SUID the default behaviour is -T and graphs don't appear. At the end we have decided to let the SUID activated but use the -U inside the script. This mught be a security problem. This is caused because inside the script an external shell is used (rrdtool update command) with variables as arguments. We are studying RRDtool documentation to make use of some of its perl bindings, but wont make it for this 2.0-00 release.

    2) The data gathering script now runs as a daemon instead of in cron. Every thing works fine but we have been told that e-smith "remakes" the rc.d directory after an update, removing our link. We don't know yet how to solve this, any experience or ideas?

  Regards

[Patrick Basile]

Hello Jaime (and all),

I was wondering if the System Monitor software has been fixed to work with SME V5, or if there is a workaround to make it work until a 'fix' is found and implemented.  I loved this when it was runningon my 4.1.2 server, and sure would like it on my V5 machine.

Thoughts/ideas/tips?

Regards,
Patrick

[Robin Dunn]

Patrick Basile wrote:
>
> I was wondering if the System Monitor software has been fixed
> to work with SME V5, or if there is a workaround to make it
> work until a 'fix' is found and implemented.  

Just connect directly to http://yourdomain.com:980/ instead of what you normally do.  That way when it does the reload it will go to the right address.

--Robin