-----Message d'origine----- De : Sigurður Guðbrandsson [mailto:sigurdur at raforninn.is] Envoyé : mercredi 19 septembre 2007 14:52 À : hobbit at hswn.dk Objet : RE: [hobbit] N00b starting to use Hobbit
Hi.
Did you configure the clients properly? That is, did you configure the correct IP address in the config files? Also, is there a firewall blocking this anywhere?
As for the port, you can change that in hobbitserver.cfg file. Just remember to restart the hobbit server. And do tell the clients to send to that port.
With regards,
In my previous message, I said something wrong. All informations are send to the Server only when I decided to force the client with the Client side configuration BUT ALL BDD are in red. The server can't reach them. Strange. Where I could investigate ?
"Les informations contenues dans ce message électronique peuvent être de nature confidentielles et soumises à une obligation de secret. Elles sont destinées à l'usage exclusif du réel destinataire. Si vous n'êtes pas le réel destinataire, ou si vous recevez ce message par erreur, merci de le détruire immédiatement et de le notifier à son émetteur."
"The information contained in this e-mail may be privileged and confidential. It is intended for the exclusive use of the designated recipients named above. If you are not the intended recipient or if you receive this e-mail in error, please delete it and immediately notify the sender."
Good day!
Guys, I need your help again. Is there someone here who have guidelines for setting up the alarm level for disk usage? It's just that I can't defend it if I'm just going to set something without reference.
Please kindly share it to me. I just need it so badly.
Thank you very much!
Ryan
I probably depends on how fast the disk fills up and how quickly you can respond to clean it.
Our "default" levels are 500Mg warning, and 100Mg red. On some other systems that have web servers that we want to be alarmed sooner, we have the warning at 1g, while the alarm is 500Mg.
We've been looking at changing some of the Oracle servers we have to higher than 500/100 since when someone is processing a giant load the archive logs can fill the disk up way to fast.
On a system that uses disk based backups, the level are even much higher, around 100g warning, and 70g alarm.
It'll all depend on the individual system and how fast you can respond when a warning/alarm notification goes out.
---Eric
-----Original Message----- From: Ryan Jay B. Lapuz [mailto:rlapuz at fcpp.fujitsu.com] Sent: Thursday, September 20, 2007 07:40 To: hobbit at hswn.dk Subject: [hobbit] Setting up Disk usage Alarm level
Good day!
Guys, I need your help again. Is there someone here who have guidelines for setting up the alarm level for disk usage? It's just that I can't defend it if I'm just going to set something without reference.
Please kindly share it to me. I just need it so badly.
Thank you very much!
Ryan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Thanks Eric,
Base on what you said, I added some points to consider and here it is:
Guidelines in setting up disk monitoring alarm levels:
- How fast the disk fills up? a. Temporary disk usage b. Regular disk usage increase (Monthly, Weekly)
- How fast you can respond whena warning/alarm nitification goes out? a. During the alarm, make sure that the remaining disk space can maintain system availability while addressing the problem. b. Identify what files to move/delete - this is to speed up the recovery
Can you please further eloborate if I miss other factors cause I think I still do. Maybe other menbers can also add their ideas so we can make a more effective guidlines for disk monitoring. I think this is very helpful specially to those that do not have a lot of experience like me.
Thanks and regards, Ryan
----- Original Message ----- From: "Eric Meddaugh" <etmsys at rit.edu> To: <hobbit at hswn.dk> Sent: Thursday, September 20, 2007 7:50 PM Subject: RE: [hobbit] Setting up Disk usage Alarm level
I probably depends on how fast the disk fills up and how quickly you can respond to clean it.
Our "default" levels are 500Mg warning, and 100Mg red. On some other systems that have web servers that we want to be alarmed sooner, we have the warning at 1g, while the alarm is 500Mg.
We've been looking at changing some of the Oracle servers we have to higher than 500/100 since when someone is processing a giant load the archive logs can fill the disk up way to fast.
On a system that uses disk based backups, the level are even much higher, around 100g warning, and 70g alarm.
It'll all depend on the individual system and how fast you can respond when a warning/alarm notification goes out.
---Eric
-----Original Message----- From: Ryan Jay B. Lapuz [mailto:rlapuz at fcpp.fujitsu.com] Sent: Thursday, September 20, 2007 07:40 To: hobbit at hswn.dk Subject: [hobbit] Setting up Disk usage Alarm level
Good day!
Guys, I need your help again. Is there someone here who have guidelines for setting up the alarm level for disk usage? It's just that I can't defend it if I'm just going to set something without reference.
Please kindly share it to me. I just need it so badly.
Thank you very much!
Ryan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Hi all,
It is already mentioned in the discussion one of the most interesting things in disk monitoring is How fast the disk fills up.
It would be nice to be able to monitor a sudden grow of used disk space.
Regards,
Bert Klomp
-----Original Message----- From: Ryan Jay B. Lapuz [mailto:rlapuz at fcpp.fujitsu.com] Sent: vrijdag 21 september 2007 2:48 To: hobbit at hswn.dk Subject: Re: [hobbit] Setting up Disk usage Alarm level
Thanks Eric,
Base on what you said, I added some points to consider and here it is:
Guidelines in setting up disk monitoring alarm levels:
- How fast the disk fills up? a. Temporary disk usage b. Regular disk usage increase (Monthly, Weekly)
- How fast you can respond whena warning/alarm nitification goes out? a. During the alarm, make sure that the remaining disk space can maintain system availability while addressing the problem. b. Identify what files to move/delete - this is to speed up the recovery
Can you please further eloborate if I miss other factors cause I think I still do. Maybe other menbers can also add their ideas so we can make a more effective guidlines for disk monitoring. I think this is very helpful specially to those that do not have a lot of experience like me.
Thanks and regards, Ryan
----- Original Message ----- From: "Eric Meddaugh" <etmsys at rit.edu> To: <hobbit at hswn.dk> Sent: Thursday, September 20, 2007 7:50 PM Subject: RE: [hobbit] Setting up Disk usage Alarm level
I probably depends on how fast the disk fills up and how quickly you can respond to clean it.
Our "default" levels are 500Mg warning, and 100Mg red. On some other systems that have web servers that we want to be alarmed sooner, we have the warning at 1g, while the alarm is 500Mg.
We've been looking at changing some of the Oracle servers we have to higher than 500/100 since when someone is processing a giant load the archive logs can fill the disk up way to fast.
On a system that uses disk based backups, the level are even much higher, around 100g warning, and 70g alarm.
It'll all depend on the individual system and how fast you can respond when a warning/alarm notification goes out.
---Eric
-----Original Message----- From: Ryan Jay B. Lapuz [mailto:rlapuz at fcpp.fujitsu.com] Sent: Thursday, September 20, 2007 07:40 To: hobbit at hswn.dk Subject: [hobbit] Setting up Disk usage Alarm level
Good day!
Guys, I need your help again. Is there someone here who have guidelines for setting up the alarm level for disk usage? It's just that I can't defend it if I'm just going to set something without reference.
Please kindly share it to me. I just need it so badly.
Thank you very much!
Ryan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
One other item I did touch on would be the purpose of the disk. For example disk based backups you might want at higher levels just to catch something before the night when all backups normally occur. This does go along the same lines as 1 & 2, but adds a little different thought into planning the levels.
---Eric
-----Original Message----- From: Ryan Jay B. Lapuz [mailto:rlapuz at fcpp.fujitsu.com] Sent: Thursday, September 20, 2007 20:48 To: hobbit at hswn.dk Subject: Re: [hobbit] Setting up Disk usage Alarm level
Thanks Eric,
Base on what you said, I added some points to consider and here it is:
Guidelines in setting up disk monitoring alarm levels:
- How fast the disk fills up? a. Temporary disk usage b. Regular disk usage increase (Monthly, Weekly)
- How fast you can respond whena warning/alarm nitification goes out? a. During the alarm, make sure that the remaining disk space can
maintain system availability while addressing the problem. b. Identify what files to move/delete - this is to speed up the recovery
Can you please further eloborate if I miss other factors cause I think I
still do. Maybe other menbers can also add their ideas so we can make a more effective guidlines for disk monitoring. I think this is very helpful specially to those that do not have a lot of experience like me.
Thanks and regards, Ryan
----- Original Message ----- From: "Eric Meddaugh" <etmsys at rit.edu> To: <hobbit at hswn.dk> Sent: Thursday, September 20, 2007 7:50 PM Subject: RE: [hobbit] Setting up Disk usage Alarm level
I probably depends on how fast the disk fills up and how quickly you can respond to clean it.
Our "default" levels are 500Mg warning, and 100Mg red. On some other systems that have web servers that we want to be alarmed sooner, we have the warning at 1g, while the alarm is 500Mg.
We've been looking at changing some of the Oracle servers we have to higher than 500/100 since when someone is processing a giant load the archive logs can fill the disk up way to fast.
On a system that uses disk based backups, the level are even much higher, around 100g warning, and 70g alarm.
It'll all depend on the individual system and how fast you can respond when a warning/alarm notification goes out.
---Eric
-----Original Message----- From: Ryan Jay B. Lapuz [mailto:rlapuz at fcpp.fujitsu.com] Sent: Thursday, September 20, 2007 07:40 To: hobbit at hswn.dk Subject: [hobbit] Setting up Disk usage Alarm level
Good day!
Guys, I need your help again. Is there someone here who have guidelines for setting up the alarm level for disk usage? It's just that I can't defend it if I'm just going to set something without reference.
Please kindly share it to me. I just need it so badly.
Thank you very much!
Ryan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (4)
-
etmsys＠rit.edu
-
johan.boye＠latecoere.fr
-
klomph＠nlr.nl
-
rlapuz＠fcpp.fujitsu.com