JuniperForum.com
September 09, 2010, 02:15:45 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: If you have an interesting idea for an article or knowledgebase entry, please submit it!
 
  Home Help Login Register  
* *
Pages: [1]
  Print  
Author Topic: Enable Application Profiling  (Read 839 times)
fcar
Newbie
*
Posts: 24


View Profile
« on: October 21, 2008, 04:17:49 AM »

Hi,

What does this actually do and how does it work.

I am little bit confused with profiler and Enable Application Profiling

when i have a tick box on Enable Application Profiling and not on profiler does it Enable Application Profiling or does it relie on the profiler being enabled. ?

I hope someone can direct me or help me please.

Thanks
Frank.
Logged
screenie.
Hero Member
*****
Posts: 1236


View Profile
« Reply #1 on: October 21, 2008, 02:03:59 PM »

Application profiler depends on profiler services. So yes you have to enable profiler first. It should give you an idea on what system runs what.... The iea is to baseline first and watch for unexpected changes afterwards.
Logged

Regards, Screenie
------------------------
JNSS, JNCIA, JNCIS, JNCI
fcar
Newbie
*
Posts: 24


View Profile
« Reply #2 on: October 22, 2008, 02:34:09 AM »

Thanks Screenie!

I have done as you suggested and tried to turn profiler on but it is not having it, and said it in the results window

Error code:

Error Text:
Failed to start profiler. Failed: profiler cound not be started.

Error Details
No Details Available.

very usefull information,
I have had a look on the system and can't work out what is happening, I can restart it as I have been told not just in case we loose connectivity to the outside world.

NicBypass is enabled so it should not loose connectivity, we have alos set the switch it is connected to not to have port fast enabled so it does not negioate nic speeds it connects instantly with only 1second of data being lost but no one notices.

I am going to restart idp tomorrow morning, I found this on juniper kb site but does not help.
http://kb.juniper.net/KB4495

I will raise a call with them tomorrow if a reboot does not fix it.

could it be my rule base that is causing it not to start ?

thanks

Frank
Logged
fcar
Newbie
*
Posts: 24


View Profile
« Reply #3 on: October 22, 2008, 03:44:03 AM »

Hi all,

Found out that the db was over its limit.
I had to do the following to resolve it.

W/A: Manually purge profiler database using the following commands:
# profiler.sh status
(should say stopped.)
# cd /usr/idp/device/var/profile
# ls -l
(print list of *.db files)
# rm -f *
# profiler.sh start
Profiler starts again.

Logged
Pages: [1]
  Print  
 
Jump to:  

Navigation

Donate

Please consider donating if we've saved you time or money. It helps pay for the bandwidth, equipment, and hosting charges to keep this site running

Tools

Submit Article/KB - Do not submit questions here.

Recent

Stats

Members
Stats
  • Total Posts: 40719
  • Total Topics: 11389
  • Online Today: 82
  • Online Ever: 393
  • (August 06, 2008, 07:40:57 AM)
Users Online
Users: 0
Guests: 50
Total: 50
TinyPortal v1.0 beta 4 © Bloc
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!

Sponsored in part by CollarWise

Page created in 0.208 seconds with 37 queries.