Koozali.org: home of the SME Server

statistiche di sme server via web..

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« on: October 27, 2006, 10:26:12 PM »
salve gente,
cosa volevo fare?

ovviamente installare phpsysinfo! penso sia tra i migliori per vedere le statistiche, cosa molto importante, quando lasci il server acceso h24..

tra l'altro installando anche le utility per monitorare le temperature (cpu, hdd ecc) ti ritrovi un controllo completo del server in una sola pagina (usavo tutto ciò con 6.5).

qua sembra esserci qualcosa di diverso..non è stato prodotto direttamente un rpm o qualcosa di simile? ho provato a fare tutto a mano, ma nell'ibays non so xkè, ho provato a mettere la pass, ma mi dice sempre che non va bene, ed ho provato le piu assurde..

mentre le uniche guide che parlano dell'installazione di phpsysinfo sulla 7.0 non sono troppo adatte..

sapete se c'è qualcosa di ufficiale?

Offline pepz

  • ****
  • 415
  • +0/-0
statistiche di sme server via web..
« Reply #1 on: October 27, 2006, 11:45:01 PM »
ciao,
credo che il tuo contrib giusto sia sme7admin...
di seguito ti metto gli rpm da installare...  bye.

Step 1 : download and install rrdtool and perl-rrdtool from Tobi Oetiker (homepage, last version of rpms for RHEL/Fedora)
rpm -ivh http://sme.firewall-services.com/rpms/rrdtool-1.0.50-1.2.el4.rf.i386.rpm
rpm -ivh http://sme.firewall-services.com/rpms/perl-rrdtool-1.0.50-1.2.el4.rf.i386.rpm

Step 2 : download and install hddtemp from Emmanuel Varagnat (homepage)
rpm -ivh http://sme.firewall-services.com/rpms/hddtemp-0.3-0.beta12.2.2.el4.rf.i386.rpm

Step 3 : download and install sysstat from Sebastien Godard (homepage)
rpm -ivh http://sme.firewall-services.com/rpms/sysstat-5.0.5-1.i386.rpm
 
Step 4 : download and install smeserver-sme7admin from myself :)
rpm -ivh http://sme.firewall-services.com/rpms/smeserver-sme7admin-1.1.0-1.noarch.rpm
 
Step 5 : CONFIGURE LM_SENSORS if you want sensors support. Try sensors-detect script to autodetect your hardware.

Step 6 : open the server-manager and configure Sme7admin (in the new panel administration->sme7admin, there is a link to "Configuration of Sme7admin"). By default, the daemon sends the alerts (every 5 minutes if an alert is triggered) and status e-mails (every 15 minutes) to the server admin mail account.
You just have now to wait for the graphs and database to fill ;-). At its first start, sme7admind parses all the current logs, it may take a little time, although the rest of time it only parses the difference between the current log and the log cached 5 minutes before, which is very fast.
 
Step 7 (Optional :)) : Send complaint, bug reports, remarks, thanks to landry at firewall - services dot com
A big thanks goes to rv, who supported me during the development of sme7admin.

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« Reply #2 on: October 28, 2006, 12:25:17 PM »
pepz sei stato gentilissimo!

è proprio un guida bella precisa ;)

l'unica cosa è che ho problemi con lm_sensors.non mi vede i sensori...(se trovo una guida dovrei risolvere, xkè su sme 6.5 fungeva..è questione di moduli)

è una soluzione perfetta xkè riesci a monitorare tutto bello preciso..

pero se non rendi accessibile il server-manager all'esterno non ti può aiutare molto..

cmq lo tengo x quando sto a casa posso veramente controllare ogni minima cosa, mentre x quando sto fuori non saprei come fare..prima avevo sempre phpsysinfo, pero accessibile all'asterno e mi controllavo la temp, la ram ecc...

consigli?

Offline pepz

  • ****
  • 415
  • +0/-0
statistiche di sme server via web..
« Reply #3 on: October 28, 2006, 06:32:22 PM »
credo che importare tutto in una bays , e quindi poi raggiungerla dall' esterno, per qualcuno pratico col php non dovrebbe essere una cosa impossibile...

io non credo di essere all' altezza...

bye

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« Reply #4 on: October 29, 2006, 03:14:56 PM »
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe vt1211
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

la prima parte l'ho caricata in /etc/modprobe.conf ma la seconda dove va messa? questo mica l'ho capito!

AGGIORNAMENTO: ah ho notato che stanno in /etc/sysconfig/lm_sensors..
quindi in teoria vengono caricato all'avvio, ma se io provo a caricarlo in manuale, guardate qua:

[root@cube ~]# modprobe i2c-viapro
[root@cube ~]# modprobe i2c-isa
[root@cube ~]# modprobe eeprom
[root@cube ~]# modprobe vt1211
FATAL: Module vt1211 not found.
[root@cube ~]#

quel modulo non lo trova..è quello che determina il malfunzionamento! c'è soluzione?

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« Reply #5 on: October 29, 2006, 04:16:30 PM »
il dmesg alle utlime 2 righe restituisce:

i2c /dev entries driver
vt1211: disagrees about version of symbol struct_module

allora in rete ho trovato:

http://www.vdr-portal.de/board/thread.php?postid=525734

che dite? devo far funzionare lmsensors!

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« Reply #6 on: October 31, 2006, 10:25:53 PM »
pepz sai aiutarmi?

Offline pepz

  • ****
  • 415
  • +0/-0
statistiche di sme server via web..
« Reply #7 on: November 01, 2006, 12:47:29 AM »
qui sembra esserci la soluzione, prova a leggere sotto... bye.

Compiling the vt1211.ko Kernel Module

I basically followed the directions from VIA, except I used the latest patch file for kernel 2.6.17 available at Lars Ekman's website: http://hem.bredband.net/ekmlar/vt1211.html instead of the one VIA provides in their VIA FC5 Hardware Monitor Application Notes (www.viaarena.com). The patch file is designed to patch the whole kernel tree (only a small part, but you need the whole thing). If you have 2.6.17-1.2174_FC5, the module I compiled is already available on Lars Ekman's website.



Below is a copy & paste of the instructions from VIA, available on VIA Arena, with annotations made where I remember their instructions didn't work. Fill in the mentioned kernel name with your kernel. If I ever have to do this again, I'll make my own instructions.



I got the corresponding kernel source package from YUM instead of downloading the RPM. The package is called kernel-devel. This puts files in /usr/src/redhat. Note that when you're done, you can use YUM to again remove this package. I had to do a few things to get rpmbuild installed and working (I remember it needed a few software packages from YUM), but then I could make it through the first few lines.




#rpm –ivh kernel-2.6.15-1.2054_FC5.src.rpm#cd /usr/src/redhat/SPECS#rpmbuild –bp –-target=i686 kernel-2.6.spec#cd /usr/src/redhat/BUILD


Then they want you to move the kernel source tree to /usr/src/{name of kernel} and then apply the patch.




You can find the kernel source directory in path/usr/src/redhat/BUILD/kernel-2.6.15/linux-2.6.15.i686. Move thekernel source directory to path /usr/src/kernels and patch the os default kernel.#cd /usr/src/redhat/BUILD/kernel-2.6.15#mv linux-2.6.15.i686 /usr/src/linux-2.6.15-1.2054_FC5#cp vt1211_FC5.patch /usr/src#cd /usr/src#patch –p0 < vt1211_fc5.patchIf patch was successful, the following message can be found.Patching file linux-2.6.15-1.2054_FC5/drivers/hwmon/KconfigPatching file linux-2.6.15-1.2054_FC5/drivers/hwmon/MakefilePatching file linux-2.6.15-1.2054_FC5/drivers/hwmon/vt1211.c


Now you have the new kernel tree, and you need to compile the kernel with the vt1211 source as a module to get the vt1211.ko.




Select needed item and rebuild the patched kernelEdit the Makefile in directory linux-2.6.15-1.2054_FC5.Find the string“EXTRAVERSION = -prep” and modify it to “EXTRAVERSION = -1.2054_FC5”.#cd linux-2.6.15-1.2054_FC5#cp /boot/config-2.6.15-1.2054_FC5 .config#make menuconfigDevice Drivers ---> Hardware Monitoring support --->[M] Hardware Monitoring support[M] VT1211After set the kernel item completely and save it, we can rebuild the kernelsource. When the compiling module procedure is completed, you can findthe “vt1211.ko” module to path/lib/modules/2.6.15-1.2054_FC5/kernel/drivers/hwmon#make#cp linux-2.6.15-1.2054_FC5/drivers/hwmon/vt1211.ko/lib/modules/2.6.15-1.2054_FC5/kernel/drivers/hwmon#depmod -a


The GUI menuconfig didn't work for me. If you run make config, you can do the same thing in text mode. If you just run make, I think it will ask you if you want Kernel/Module whenever not specified by the .config file you copied from your boot folder. Make sure you select Module (type the letter 'm') for the vt1211 objects. Then, about six hours later, it'll finally make it through all the source and you'll get your .ko file. Copy it out of there and into your /lib/modules tree and then run depmod as in the instructions above.



When you're done, you can go back to the /usr/src/{linux kernel name} and run make clean, or you can remove that whole directory if you no longer need it. You can also remove the kernel-devel package, rpmbuild, etc.

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« Reply #8 on: November 01, 2006, 03:36:48 PM »
ma non compromette la stabilità sto kernel?

Offline pepz

  • ****
  • 415
  • +0/-0
statistiche di sme server via web..
« Reply #9 on: November 01, 2006, 05:38:43 PM »
hei, ti raccomando.....
fai prima tutte le prove su una macchina test!!
soprattutto con modifiche cosi invasive....

io x provare i vari software di backup, formatto ogni 2 giorni....

bye

Offline z3n0

  • ***
  • 105
  • +0/-0
    • http://www.giuseppeferraiolo.it
statistiche di sme server via web..
« Reply #10 on: November 02, 2006, 03:11:59 PM »
eh il punto è che per oran on ho macchine test..

ma dico io, xkè su sme 6.5 non avevo sto problema? i sensori vennero riconosciuti subito..