Bad time zone in Syslog Collector Status screen

Hi, we have a LMS 4.0 and we are watching a wrong time zone in the Syslog Collector Status screen, it says GMT +2 but it should be GMT +1. In the Windows operating system, time settings are well configured; can anyone help me to fix this, please?
Regards.

Hi,
please find attached some screenshots: one with the LMS time, another one with the OS time and the last one with the syslog collector time. The only problem is that they have been taken at different times but it can be seen that OS time zone is UTC + 1 and Syslog Collector time zone is GMT + 2.
Kind regards.

Similar Messages

  • Syslog collector status...invalid messages

    hi,
    In RME->Administration->Syslog Analysis->Syslog Collector Analysis
    i see a lot of (almost 40-50%)message count under the "invalid messages" column.
    I wonder if this needs to be considered seriously, and if yes, please guide me as to what steps do i need to take in order to solve this..

    I imagine it'd be those that do not conform to syslog msg format specifications, such as those described
    here: http://www.ciscopress.com/articles/article.asp?p=426638

  • LMS 3.2 Syslog Collector error

    Hi,
    At RME: ToolsSyslogSyslog Collector Status screen at table Collector Status No records.
    I had changed hostname on this server and i have ran /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/hostnamechange.pl script with proprer parameters.
    Now I cannot add collector, because of  "SSL certificate status" error:
    SSL certificate issue occurred, check if:
    1. The Self-signed Certificates are valid. For example, Check the certificate expiry date on the servers.
    2. The Self-signed Certificates of this server are copied to the Syslog Collector server and vice-versa.
    To do this, go to Common Services > Server > Security > Multi-Server Trust Management > Peer Server Certificate Setup. and add the certificate. See the User Guide for CiscoWorks Common Services for more details..
    3.The SyslogCollector process on Syslog Collector server and the SyslogAnalyzer process in the current working server are restarted after Step 2.
    4.Both hosts are reachable by host name.
    Collector status : Could not connect to the collector _myhostname_._mydomainname_ due to SSL certificate issue
    I use an third party Certificate, and https access is working propery for user access.
    I want to run Syslog Collector locally, syslog file is a local server hence I use syslog-ng for other reason.
    This is my SyslogCollector log:
    SyslogCollector - [Thread: main] INFO , 24 Mar 2011 16:47:45,305, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 24 Mar 2011 16:47:45,308, System Initialized.
    SyslogCollector - [Thread: main] INFO , 24 Mar 2011 16:47:45,408, Queue Cap 100000
    SyslogCollector - [Thread: main] INFO , 24 Mar 2011 16:47:47,699, Service started...
    How can I correct this situation, how can I run Syslog Collector.
    Balazs

    Try unsubscribing and subscribing the collector so it can accept the updated info. If that does not work, post the SyslogAnalyzerUI.log and SyslogCollector.log from CSCOpx/log directory.

  • Time Zone issues in Global Instance

    Hi,
    Can someone give best practice in addressing issues in Global instance due to change in date & time.
    Say
    1) A user is in America and system time zone is GMT
    2) Order screen: sched ship date shown based on user preference as GMT-5hrs. Say it is 30-Jun-2008 7:30 pm
    3) However, in the back end the data is stored as 1-Jul-2008 12:30 AM
    4) This certainly seems to have an impact to standard date fields.
    5) This also seems to have impact on effectivity dates which don't have timestamp. Eg, pricelist effectivity end date = 30-Jun-2008. The pricelist becomes ineffective at 7 PM EST because of system time zone being GMT.
    Any pointers to address such issues, would be of great help.
    Thanks.
    -bs

    Hi,
    below is an answer from Oracle on similar issue regarding timezones:
    Oracle E-Business Suite version 11i10 or higher
    1 Oracle RDBMS 9i or higher
    2 The database must be configured to use the time zone file
    'timezlrg.dat' rather than the 'timezone.dat' file
    3 The database must be started in the standard corporate time zone
    4 Profile 'Server Timezone' (SERVER_TIMEZONE_ID) must be set at the Site
    level, and must be set to the same standard corporate time zone as the
    database
    5 Profile 'Client Timezone' (CLIENT_TIMEZONE_ID) must be set at the user
    level
    6 Profile 'Enable Timezone Conversions' (ENABLE_TIMEZONE_CONVERSIONS)
    must be set to 'Yes' ('Y') at the Site level.
    7 Profile 'Concurrent: Multiple Time Zones' (CONC_MULTI_TZ) should be
    set to 'No' (N) at the Site level
    8 Environment variable FORMS60_APPSLIBS must be set in the Forms tier
    (this has always been a requirement for 11i)
    9 Forms must be launched through the Personal Home Page or Navigate portlet
    Additionally check these notes:
    Note 330075.1
    Note:188059.1
    malin

  • Syslog Collector failure with third party SSL certificate

    Hello,
    We recently replaced our self-signed SSL certificates with certificates provided by our agency. After the change subscription attempts to the collector in [RME>Tools>Syslog>Syslog Collector Status] failed: SCLA0126: Could not subscribe to the Collector.
    I believe the problem originates with the way the CSRs are handeled. An identification number rather than the actual FQDN must be provided in the common name field and this number is expected by the CA. A chain was built with multiple government CAs, and warnings received that the chain does not end in a trusted CA. My hands are bound by this policy - is there a way to make this work or any suggested workaround? Tried a DNS CNAME with the id number. No joy. I haven't tried renaming the host to the id number but I might if you think it might work and then will just cname the current hostname. We are running Solaris 10 systems. Here is the error from AnalyzerDebug.log:
    javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
            at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
            at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:117)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1584)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:866)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:678)
            at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
            at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2213)
            at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
            at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)
            at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:761)
            at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
            at com.cisco.nm.rmeng.fcss.common.FcssSyslogCollector.<init>(FcssSyslogCollector.java:95)
            at com.cisco.nm.rmeng.sa.SyslogAnalyzerEngine.notifySubscribers(SyslogAnalyzerEngine.java:975)
            at com.cisco.nm.rmeng.sa.SyslogAnalyzerEngine.start(SyslogAnalyzerEngine.java:1031)
            at com.cisco.nm.rmeng.sa.SyslogAnalyzerService.main(SyslogAnalyzerService.java:55)
    Thanks....!!!
    = Uwe =

    The subscriber list is empty because we could not add the subscription after the swapping the certs. Sorry, was asked to obscure the host names - it shows host name only not FQDN.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 10:37:33,198, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 10:37:33,201, System Initialized.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 10:37:36,694, Service started...
    SyslogCollector - [Thread: Thread-9] WARN , 14 Feb 2010 10:42:04,383, Unable to add monitor for
    SyslogCollector - [Thread: SyslogObjectForwarder] ERROR, 14 Feb 2010 11:07:42,369, Could not send syslogs, removing the subscriber...Connection refused
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:02,499, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:02,501, System Initialized.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:02,850, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 11:23:06,047, Service started...
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:33,732, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:33,735, System Initialized.
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:34,148, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 14 Feb 2010 23:59:37,352, Service started...
    SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:34,112, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:34,115, System Initialized.
    SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:34,565, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 15 Feb 2010 23:59:38,168, Service started...
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:43,806, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:43,816, System Initialized.
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:44,220, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 11:57:47,493, Service started...
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:00,424, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:00,427, System Initialized.
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:00,781, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 14:12:04,007, Service started...
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:33,851, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:33,854, System Initialized.
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:34,303, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 16 Feb 2010 23:59:37,834, Service started...
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:51,156, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:51,166, System Initialized.
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:51,516, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 16:42:54,734, Service started...
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:33,673, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:33,676, System Initialized.
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:34,130, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 17 Feb 2010 23:59:37,759, Service started...
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:42,526, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:42,533, System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:42,886, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:55:46,111, Service started...
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:34,144, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:34,147, System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:34,604, Subscriber list is empty!
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:38,116, Service started...
    Our secondary host shows a subscriber, however no syslog packets are seen. Also, this subscriber can not be unsubscribed (deleted).
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:09:19,098, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:09:19,101, System Initialized.
    SyslogCollector - [Thread: main] WARN , 18 Feb 2010 16:09:22,723, Unable to resurrect connection to a subscriber.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:09:22,770, Service started...
    SyslogCollector - [Thread: Thread-11] WARN , 18 Feb 2010 16:14:07,828, Unable to add monitor for
    SyslogCollector - [Thread: Thread-13] WARN , 18 Feb 2010 16:14:08,008, Unable to add monitor for
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:32:29,557, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:32:29,560, System Initialized.
    SyslogCollector - [Thread: main] WARN , 18 Feb 2010 16:32:33,205, Unable to resurrect connection to a subscriber.
    SyslogCollector - [Thread: main] WARN , 18 Feb 2010 16:32:33,263, Unable to resurrect connection to a subscriber.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 16:32:33,277, Service started...
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:33,728, Logging System Initialized.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:33,733, System Initialized.
    SyslogCollector - [Thread: main] WARN , 18 Feb 2010 23:59:37,786, Unable to resurrect connection to a subscriber.
    SyslogCollector - [Thread: main] WARN , 18 Feb 2010 23:59:37,857, Unable to resurrect connection to a subscriber.
    SyslogCollector - [Thread: main] INFO , 18 Feb 2010 23:59:37,869, Service started...

  • Ciscoworks syslog collector issue

    Hi All,
    In a central location i have a ciscoworks syslog collector version 3.5. The issue is not all the logs generated in the device are collected by  ciscoworks including the devices connected in LAN. The major issue is on Cisco6500 series switches where i see multiple interface flaps in log but only few are found in syslog.
    Regards,
    Sathvik

    Hi,
    check  here Admin > Collection Settings > Syslog > Syslog Collector Status  , see if messages are falling under fitered or Invalid
    then check the filter:
    Admin > Network > Notification and Action Settings > Syslog Message Filters
    I would suggest you to create a filter with all  *  and see if that helps.
    you can look at this thread  as well:
    https://supportforums.cisco.com/thread/2244888?tstart=60
    Thanks-
    Afroz
    [Do rate the useful post]

  • Integrate Remote Syslog Collector with LMS 4.1

    We have LMS 4.1 in our network. We had recently installed Remote Syslog Collector on a new Server to collect logs from all the devices. How can we integrate the Remote Syslog Collector with the LMS Server?
    Thanks in Advance.

    You simply have to subscribe the IP address of the Remote Syslog Collector in Ciscowork LMS server under :
    Admin > Collection Settings > Syslog > Syslog Collector Status
    Once it is subscribed, it should start working, simialar to how it works when Syslog Collector is Local on LMS server.
    For more details see docuement :
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/install/guide/appendc.html#wp1049873
    -Thanks

  • Product Delivered Status Date should be there in Standard Search and Result screen of Service Order. Product Delivered Time should be Available in Result screen and In Result screen there should be facility to filter on basis of Time

    Hi team,
    Product Delivered Status Date should be there in Standard Search and Result screen of Service Order. Product Delivered Time should be Available in Result screen and In Result screen there should be facility to filter on basis of Time.
    How to add this in search result screen.configuration is it possible? or any changes in development.
    Compnent - BT116S_SRVO
    Thanks
    Kalpana

    Hi Kalpana
    Please reread my comment. I said to try and populate "Requested End" Date.
    Make sure the date profile assigned to the transaction includes this Date Type.
    If you can populate this either manually or programmatically the solution should be quite forward.
    If you cannot do this, only then should you look at making any significant sort of enhancement.
    Regards
    Arden

  • RUEI 12.1.0.3.0 - Collectors Status Okay but Last Update time not updated

    Hi all,
    Under System > Status > Collectors Status
    Status shows OK but Last Update Time is not updated. The last update time is frozen.
    Anyone has a similar experience? Would someone help, please?
    Regards,
    Nathan

    Hi Nathan,
    that seems odd indeed. would not know the cause or any sensibl explaination unless I have system details, Can you pls file an SR for this issue and upload the helpdesk file to the SR?
    a helpdesk file is created under system >>maintenance>>helpdesk report
    It will create a zip file that we can read in support, see the events the system is capturing, analyze your configuration. That will allow us for very quick follow up. if you want me to track it internally at Oracle pls send me the SR# in a direct mail: [email protected] -- I'm the responsible product manager for RUEI so happy to follow up on this.
    R, jurgen

  • Multiple time zones on iOS lock screen?

    I'm desperate to be able to display multiple time zones on my lock screen in iOS (7.03) is there anyway to do this currently?
    As with most ppl my iphone is also my watch, and as I travel frequently i like to keep my eye on time zone back home to know when is a good time to call/FaceTime etc...
    Seems like an obvious feature no one has thought about?

    Sorry, no.
    If you'd like to see this as a feature, tell Apple:
    http://www.apple.com/feedback/iphone.html

  • Can the iphone 5s display two clocks/time zones on my lock screen?

    Can the iphone 5s display two clocks/time zones on my lock screen?

    Sorry, no.
    If you'd like to see this as a feature, tell Apple:
    http://www.apple.com/feedback/iphone.html

  • DP background jobs in local time zone

    We are using APO DP in an international environment (SCM 4.1). We have setup up the system, that is using the local time zone (personal user settings), which is working fine in interactive planning (data views & macros). But when executing the macros
    in background (APO background jobs triggered immediately by a process chain), the macro is run based on the server time and not in the local time zone. The ALEREMOTE user is set up in the same way online users regarding time zone settings.
    Can someone explain, why the local time zone isn't used in the macros when executing in background, and tell me which setting we have missed.
    Many thanks in advance
    Marco

    HI,
    I understand the issue, the issue is the Australia gets days very first from the world.. it almost GMT+11 hrs. will almost a day difference to US.
    I am not sure whether my proposal will make sense, but let me try
    As the month completes we will copy the sales history  for the closed month. where technically the the month is current month as per the system time.
    Why can not change the macro to copy current period and run at system time? i am not sure aobut the otherconstriantes.
    But looking at your question, it could be possible where your client has the local time zone defined. you can check the same from any APO screen, from menu > systems->status. you can see both time zone ( local) system time.
    I suggest you check with basis if we can use the local time zone, we can use the localtimezone but agian everyone has to use our local time.. NO SENSE i guess..
    Yarala

  • Time zone problem in grid control

    hi
    my management server (10g) is on windows 2000 and windows is running on time zone GMT+5
    Iinstalled agent 10g on Red Hat Linux Advance Server 4 and during instalation it sucessfully detects the OMS running on windows. After installation, it doesnt start the agent.
    I tried manually starting agent butfailed and in log file i found the following error
    2006-03-22 07:05:21 Thread-16384 Starting Agent 10.2.0.1.0 from /opt/oracle/product/10.2.0/agent10g (00701)
    2006-03-22 07:05:27 Thread-16384 <Ping Manager> Invalid TIMEZONE for agent not compatible with OMS timezone, Agent will shutdown. Update agentTZRegion property in /opt/oracle/product/10.2.0/agent10g/sysman/config/emd.properties file (00900)
    2006-03-22 07:05:28 Thread-16384 [E-Mail IMAP Server] InstanceProperty (imap_host) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:29 Thread-16384 [Database Instance] InstanceProperty (DBVersion) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:31 Thread-16384 [E-Mail POP Server] InstanceProperty (pop_host) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:31 Thread-16384 [Cluster Database] InstanceProperty (DBVersion) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:32 Thread-16384 [Load Balancer Switch] InstanceProperty (snmpTimeout) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:32 Thread-16384 [E-Mail SMTP Inbound Server] InstanceProperty (smtp_host) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:32 Thread-16384 [E-Mail SMTP Outbound Server] InstanceProperty (smtp_host) is marked OPTIONAL but is being used (00506)
    2006-03-22 07:05:39 Thread-16384 No such metric sqlnetParams (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric ha_flashrecovery (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric ha_recovery (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric ha_rac_intrconn (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric db_options (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric linuxProvision (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric ProgramResourceUtilization (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric LogFileMonitoring (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric storage_reporting_data (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric storage_reporting_keys (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric storage_reporting_alias (00400)
    2006-03-22 07:05:39 Thread-16384 No such metric storage_reporting_issues (00400)
    2006-03-22 07:05:39 Thread-16384 EMAgent started successfully (00702)
    2006-03-22 07:05:39 Thread-16384 EMAgent abnormal terminating (00704)
    The time zone for agent and my linux system is Asia/Karachi with is GMT+5. can you give me a clue how to resolve this?
    Regards

    # perl executable directory
    perlBin=/opt/oracle/product/10.2.0/agent10g/perl/bin
    # script directory
    scriptsDir=/opt/oracle/product/10.2.0/agent10g/sysman/admin/scripts
    # emd Root directory(read-only location). Metrics should not create files
    # under this directory
    emdRoot=/opt/oracle/product/10.2.0/agent10g
    # agent Root directory(writeable).
    # Use this property to base any temporary file creation.
    agentStateDir=/opt/oracle/product/10.2.0/agent10g
    # Chronos root directory
    chronosRoot=/opt/oracle/product/10.2.0/agent10g/sysman/emd/chronos
    # OMS Upload URL
    # if there is no receiving OMS or if you wish to disable the UploadManager
    # please set this value to empty or comment out below line
    REPOSITORY_URL=http://lhrpc419:4889/em/upload/
    # Proxy settings used for fetchlets. not applicable for uploader.
    #proxyHost=www-proxy.us.oracle.com
    #proxyPort=80
    #dontProxyFor=.us.oracle.com
    # If it is necessary to go through an http proxy server to get to the
    # repository, uncomment the following two lines
    #REPOSITORY_PROXYHOST=
    #REPOSITORY_PROXYPORT=
    #REPOSITORY_PROXYREALM=%EM_REPOS_PROXYREALM%
    #REPOSITORY_PROXYUSER=%EM_REPOS_PROXYUSER%
    #REPOSITORY_PROXYPWD=%EM_REPOS_PROXYPWD%
    # This string is used by the agent to connect to remote targets
    # ***IMPORTANT*** Do not change the contents of this setting. Only the
    # install should modify this value.
    agentSeed=144455808
    # This string is used by the agent to determine which algorithm to use for encrypted data
    # The string value will be same as the release version
    agentVersion=10.2.0.0.0
    # How long, in minutes, collector will wait until next load.
    UploadInterval=15
    # If an upload fails, we want to backoff by UploadFailBackoff
    # percentage more each time for each successive upload failure
    # e.g. if we start the retry at 1 minute. If we fail in our next
    # upload attempt, we try again 1minute 12 seconds later etc.
    UploadFailBackoffPct= 20
    # Maximum amount of time, in seconds, upload will wait for response from
    # repository before timing out.
    # 0 means infinite.
    UploadTimeout=1800
    # Timeout for upload a file, HealthMonitor will abort the EMD process if
    # UploadManager does not finish uploading one file within this time
    # Unit is minite, the default value is 1 hour ( 15 Min)
    #UploadMaxTime=30
    # How big the file the collector will upload (in KB)
    # the actual file size could be slightly bigger.
    # This is only a guidance.
    UploadFileSize=2048
    # The maximum number of megabytes(MB) the upload manager will support in the
    # upload directory before temporarily disabling collections, logging and tracing
    UploadMaxBytesXML=50
    # The maximum number of files the upload manager will support in the
    # upload directory before temporarily disabling collections, logging and tracing
    UploadMaxNumberXML=5000
    # The maximum amount (%) of disk space that can be used on the EMD filesystem
    # before the following is disabled:
    # - Collection of data (upload manager)
    # - Logging and tracing
    UploadMaxDiskUsedPct=98
    # The amount (%) of disk space that can be used on the EMD filesystem
    # before the following is re-enabled after being disabled previously:
    # - Collection of data (upload manager)
    # - Logging and tracing
    UploadMaxDiskUsedPctFloor=95
    # Time out for the Agent to think that the access to the database could be
    # hung. The Agent would not allow more threads to go and hang with a database
    # if any one access to the database does not return within DbHangTimeout
    # seconds.
    # The more the timeout more the possibility of allowing more threads
    # to be hung in the EMD with a bad database.it is specified in seconds.
    #DbHangTimeout=200
    # The script to run if disk space usage exceeds parameters or if certain other
    # error conditions occur.
    #emdFailureScript=emdfail.command
    # The location of the file that contains the root certificate.
    emdRootCertLoc=/opt/oracle/product/10.2.0/agent10g/sysman/config/b64LocalCertificate.txt
    internetCertLoc=/opt/oracle/product/10.2.0/agent10g/sysman/config/b64InternetCertificate.txt
    # The download URL for the EMD Oracle Wallet and its local file location.
    # Note: Ensure that this URL references a valid port number at which the
    # console is available on http
    emdWalletSrcUrl=http://lhrpc419:4889/em/wallets/emd
    emdWalletDest=/opt/oracle/product/10.2.0/agent10g/sysman/config/server
    # The email address for out-of-band notifications
    emd_email_address=_NOT_AVAILABLE_
    emd_email_gateway=_NOT_AVAILABLE_
    # The return email address for out-of-band notifications
    emd_from_email_address=_NOT_AVAILABLE_
    # EMD main servlet URL
    EMD_URL=http://nisar.lhr.systemsltd.com:3872/emd/main/
    # Whether the EMD should listen on all NICs on the current host (the default)
    # or just the NIC associated with the hostname in EMD_URL
    AgentListenOnAllNICs=TRUE
    # This parameter indicates the thread model to use. uncomment one of the
    # following ThreadPoolModel line to indicate the model, agent need to use.
    # SMALL if number of targets is less than 11.
    # MEDIUM if number of targets is from 11 to 50.
    # LARGE if number of targets is greater than 50.
    # This parameter can be overriden by 'MaxThreads' which indicates the maximum
    # number of threads that CEMD can have running at any point of time. User can
    # mostly use the other parameter ThreadPoolModel to indicate what model for the
    # agent to use.
    # ThreadPoolModel = SMALL
    # ThreadPoolModel = MEDIUM
    # ThreadPoolModel = LARGE
    # This parameter indicates the stack size, threads have to be created with.
    # we can set it to 0 to use the OS default value.
    # In some version of solaris(such as 2.9 ) specify a stack size may cause Java Hotspot warning
    # when JVM is used.
    NormalThreadStackSize=0
    #Signals that users want to ignore.
    #It can be one or combination of SIGTERM, SIGINT
    # The signals can listed with ',' as delimiter.
    #IgnoreSignals=
    # This property is NO LONGER USED for host config collection (instead, hostConfigClasspath is used).
    # If noone else uses it, it can be removed.
    ouiLoc=/opt/oracle/product/10.2.0/agent10g/oui
    # Classpath for host config collection
    # VERY IMPORTANT NOTE: If you change the host config classpath entries in this section, you HAVE
    # to change the HOST_CONFIG_TEST_CLASSPATH entry in the utl/emdwqaenv file too.
    # NOTE: if the location of log4j-core.jar is changed
    # make sure that appropriate changes are also made
    # to the CLASSPATH variable in this file if necessary
    # PORTING NOTE: Check OUI-required jar files for OUI APIs to work. They could be different on your platform.
    # Also, our version of xmlparserv2.jar must be compatible with the one OUI expects (both OUI and ECM use XML parser).
    hostConfigClasspath=/opt/oracle/product/10.2.0/agent10g/oui/jlib/xmlparserv2.jar:/opt/oracle/product/10.2.0/agent10g/oui/jlib/OraInstaller.jar:/opt/oracle/product/10.2.0/agent10g/oui/jlib/srvm.jar:/opt/oracle/product/10.2.0/agent10g/oui/jlib/share.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/emcoreAgent.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/emagentRT.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/emagentSDK.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/log4j-core.jar
    # JAVA HOME required for JavaExt metric calls
    JAVA_HOME=/opt/oracle/product/10.2.0/agent10g/jdk/jre
    # CLASSPATH required for JavaExt metric calls
    CLASSPATH=/opt/oracle/product/10.2.0/agent10g/jdbc/lib/ojdbc14.jar:/opt/oracle/product/10.2.0/agent10g/lib/xmlparserv2.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/log4j-core.jar:/opt/oracle/product/10.2.0/agent10g/jlib/http_client.jar:/opt/oracle/product/10.2.0/agent10g/jlib/share.jar:/opt/oracle/product/10.2.0/agent10g/jlib/jssl-1_1.jar:/opt/oracle/product/10.2.0/agent10g/jlib/javax-ssl-1_1.jar:/opt/oracle/product/10.2.0/agent10g/jlib/ojmisc.jar:/opt/oracle/product/10.2.0/agent10g/jlib/repository.jar:/opt/oracle/product/10.2.0/agent10g/opmn/lib/optic.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/emagentRT.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/emagentSDK.jar:/opt/oracle/product/10.2.0/agent10g/lib/dmsEmd.jar:/opt/oracle/product/10.2.0/agent10g/sysman/jlib/emcoreAgent.jar
    # this is the java option
    #JAVA_OPTIONS=-Xmx128m
    #JAVA_OPTIONS=-Djava.awt.headless=true
    # These are the optional Java flags for the in-process Java
    # Native Interface (JNI)
    agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true -Dnetworkaddress.cache.ttl=1800 -Djava.awt.headless=true
    # When set to true, the emd.log and emd.trc file will be appended by a pid
    # For example:
    # emd_15789.log
    # emd_15789.trc
    # By default, it is not set for regression test purpose.
    # After installed, please uncomment this line because when EMD is restarted,
    # previous log information will be lost if not set to true.
    #LogFileWithPID=true
    # Default log file maximum size before rolling in Kilobytes
    LogFileMaxSize=4096
    # Maximum number of log file roll files to maintain before deletion
    LogFileMaxRolls=4
    # Default trace file maximum size before rolling in Kilobytes
    TrcFileMaxSize=4096
    # Maximum number of trace file roll files to maintain before deletion
    TrcFileMaxRolls=4
    # To enable the metric browser, uncomment the following line
    # This is a reloadable parameter
    #enableMetricBrowser=true
    # To disable Remote operations (non-reachable agent) uncomment the following
    # line:
    #disableRemoteOperations=true
    # How long (in secs) until a remote operation sumbitted via the dispatcher can
    # take before the agent in bounced by the watchdog. This timeout applied to only
    # those operation which ought to finish within a certain interval of time
    RemoteAPITimeout=300
    # add an additional admin path from which the agent will read additional
    # target metadata. The specified path should have the mandatory 4 directories
    # under it. 1. metadata 2. scripts 3. default_collection 4. discover
    #altAdminPath=<additional admin path>
    # The health monitor executes callbacks in a separate thread. if for some
    # reason the threads spawned from health monitor to execute callbacks are
    # hung, the agent could run out of resource and freeze.
    # so when the current thread count spawned from the Health monitor reaches
    # this limit, the agent is bounced. the default is set to 5.
    #MaxHealthMonitorThreads=5
    # SSL session cache flag
    #SSLSessionCache=TRUE
    # emagent perl tracing levels
    # supported levels: DEBUG, INFO, WARN, ERROR
    # default level is WARN
    EMAGENT_PERL_TRACE_LEVEL=WARN
    # other optional parameters for perl tracing
    # EMAGENT_PERL_TRACE_DIR default to $ORACLE_HOME/sysman/log
    #EMAGENT_PERL_TRACE_DIR=
    # EMAGENT_PERL_TRACE_FILESIZE default to 5M
    #EMAGENT_PERL_TRACE_FILESIZE=5
    # this section define the logging level for each component,
    # it is "reloadable", you can change the level at runtime to reset
    # the logging level, but if you remove the line, it will not be
    # changed.
    tracelevel.main=WARN
    tracelevel.emSDK.xml=WARN
    tracelevel.emSDK.utl=WARN
    tracelevel.Dispatcher=WARN
    tracelevel.ThreadPool=WARN
    tracelevel.pingManager=WARN
    tracelevel.collector=WARN
    tracelevel.http=WARN
    tracelevel.http.client=WARN
    tracelevel.browser=WARN
    tracelevel.ssl=WARN
    tracelevel.ssl.io=WARN
    tracelevel.blackouts=WARN
    tracelevel.upload=WARN
    tracelevel.command=WARN
    tracelevel.reload=WARN
    tracelevel.scheduler=WARN
    tracelevel.Authentication=WARN
    tracelevel.metadata=WARN
    tracelevel.targets=WARN
    tracelevel.TargetManager=DEBUG
    tracelevel.engine=WARN
    tracelevel.javaproc=WARN
    tracelevel.vpxoci=WARN
    tracelevel.javavm=WARN
    tracelevel.fetchlets=WARN
    tracelevel.fetchlets.os=WARN
    tracelevel.fetchlets.osline=WARN
    tracelevel.fetchlets.oslinetok=WARN
    tracelevel.fetchlets.snmp=WARN
    tracelevel.fetchlets.UDM=WARN
    tracelevel.fetchlets.PropsFromAssocTgt=WARN
    tracelevel.fetchlets.sql=WARN
    tracelevel.fetchlets.url=WARN
    tracelevel.fetchlets.urllines=WARN
    tracelevel.fetchlets.urllinetoken=WARN
    tracelevel.fetchlets.URLTiming=WARN
    tracelevel.fetchlets.OJMX=WARN
    tracelevel.fetchlets.propEcho=WARN
    tracelevel.fetchlets.readFromFile=WARN
    tracelevel.fetchlets.readMultFromFile=WARN
    tracelevel.fetchlets.throwable=WARN
    tracelevel.fetchlets.resourceGrab=WARN
    tracelevel.fetchlets.statusHang=WARN
    tracelevel.fetchlets.emSDK=WARN
    tracelevel.recvlets=WARN
    tracelevel.recvlets.snmp=WARN
    tracelevel.credproviders=WARN
    tracelevel.utl=WARN
    tracelevel.NLS=WARN
    tracelevel.util.dates=WARN
    tracelevel.util.emdprops=WARN
    tracelevel.util.files=WARN
    tracelevel.util.fileops=WARN
    tracelevel.resman.socket=WARN
    tracelevel.resman.process=WARN
    tracelevel.ResMonitor=WARN
    tracelevel.emtgtctl=WARN
    # The following three properties are for HTTP timeout
    # Timeout value for reading Http primary header, default is 30 seconds.
    httpTimeoutPrimaryHeader=30
    # Timeout value for reading http secondary headers, default is 30 seconds
    httpTimeoutSecondaryHeaders=30
    # Timeout value for reading http body, default is 60 seconds.
    httpTimeoutBody=60
    # Timeout used by ping manager
    #PingTimeout=30
    #Timeout for Dynamic property evaluation. This is provided in seconds.
    #The dynamicPropsComputeTimeout value applies to all target types unless if a
    #target type specific value is provided using the
    #dynamicPropsComputeTimeout_<targetType>= syntax
    #dynamicPropsComputeTimeout=30
    #Requested by RAC team in bug 4423072
    dynamicPropsComputeTimeout_rac_database=120
    #bug 4595094
    dynamicPropsComputeTimeout_oracle_database=120
    agentTZRegion=Asia/Karachi

  • LMS 4.2 – Missing messages in Remote Syslog Collector

    Remote syslog Collector are dropping syslog messages - randomly. During analyzing we found out that syslog messages are stored in RSAC in file: /var/log/syslog_info
    According to information from /etc/rsyslog.conf are the same syslog messages stored again in other files: /var/log/messages, /var/log/boot.log
    In every file are missing the same messages. Load of RSAC and physical server is very low. When we send messages to more syslog servers (for example to other debian server in the same or different vlan) in the same physical server in vmware, we always receive every message.
    We are using LMS 4.2.3 (Soft appliance) and for syslog messages RSAC 5.2 (linux in vmware). We receive approximately 200-300k syslog messages per day and RSAC drop approximately 100k.
    Please what we have to change to receive all messages?
    Why RSAC store the same messages more times?
    Thanks
    Milos

    I think this should change what you want - if not, revert it to the default:
    for security, make a backup of the following file and open it in a text editor:
    NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties
    change the following to a value that might fit your needs but be careful this can affect system performance:
        QUEUE_CAPACITY=100000
    save the file and restart the following syslog processes:
    in a DOS box check the status of the following processes (they should be started) and restart them:
        pdshow SyslogAnalyzer SyslogCollector
        pdterm SyslogAnalyzer SyslogCollector
        pdexec SyslogAnalyzer SyslogCollector
        pdshow SyslogAnalyzer SyslogCollector
    now, try to re-run your report.

  • Running, MS conn ok, Dia Queue time: 0.00 sec, J2EE status info unavailable

    hi all,
    I have installed solution manager and was running fine but now when i start it then getting below issue in sapmmc
    Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable
    while log of disp+work and dev_jcontrol having issue...
    DpMsgAdmin: Set patchno for this platform to 254
    Release check o.K.
    Fri Oct 29 12:46:57 2010
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 4372
      argv[0] = F:\usr\sap\SOL\SYS\exe\uc\NTAMD64\jcontrol.exe
      argv[1] = F:\usr\sap\SOL\SYS\exe\uc\NTAMD64\jcontrol.exe
      argv[2] = pf=F:\usr\sap\SOL\SYS\profile\SOL_DVEBMGS00_solman4
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64995
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=SOL
      argv[7] = -DSAPMYNAME=solman4_SOL_00
      argv[8] = -DSAPPROFILE=F:\usr\sap\SOL\SYS\profile\SOL_DVEBMGS00_solman4
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Fri Oct 29 12:47:00 2010
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
    *** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 568
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2480) [nixxi.cpp    4424]
    *** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    Fri Oct 29 12:47:17 2010
    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN
    Fri Oct 29 12:47:37 2010
    DpEnvCheckJ2ee: switch off j2ee start flag
    DpEnvCheckJ2ee: switch off j2ee start flag
    dev_jcontrol
    trc file: "F:\usr\sap\SOL\DVEBMGS00\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 4372
    system name : SOL
    system nr.  : 00
    started at  : Fri Oct 29 12:46:57 2010
    arguments       :
           arg[00] : F:\usr\sap\SOL\SYS\exe\uc\NTAMD64\jcontrol.exe
           arg[01] : pf=F:\usr\sap\SOL\SYS\profile\SOL_DVEBMGS00_solman4
           arg[02] : -DSAPSTART=1
           arg[03] : -DCONNECT_PORT=64995
           arg[04] : -DSAPSYSTEM=00
           arg[05] : -DSAPSYSTEMNAME=SOL
           arg[06] : -DSAPMYNAME=solman4_SOL_00
           arg[07] : -DSAPPROFILE=F:\usr\sap\SOL\SYS\profile\SOL_DVEBMGS00_solman4
           arg[08] : -DFRFC_FALLBACK=ON
           arg[09] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 2864] Fri Oct 29 12:46:57 2010
    [Thr 2864] *** WARNING => INFO: Unknown property [instance.box.number=SOLDVEBMGS00solman4] [jstartxx.c   841]
    [Thr 2864] *** WARNING => INFO: Unknown property [instance.en.host=solman4] [jstartxx.c   841]
    [Thr 2864] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2864] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    thanks in advance
    Diya Chopra

    Dear all,
    Even i am also facing same problem.
    We are setting up Diaster recover  (DR ) where we are doing the mirror copy of the Source System to Target System.
    After mounting all the files in Target DR System, i made the following changes in Target System.
    OS: AIX
    Dual stack System(ABAP +JAVA)
    Instance number used :
    00--ASCS00
    02-- DVEBMGS02
    01--SCS01
    03--D03 -------------------------------------------------------------------------->  It is maintained in another DR Server
    Database Used: Oracle
    a)renamed the Profiles (/usr/sap/KBP/SYS/profile).
    b)Changed the dbenv files (/home/kbpadm)  and (/home/orakbp)
    c)set right permissions in all files and folders in /usr/sap.
    d)Oracle is running and DB is also up
    e)Started the profiles using sapcpe
    e)After switching user (sidadm), Started the SAP Applications and SAP applications are up.
    When i checked the GetProcess list according to instance wise, i am getting below output.
    kbpadm>  sapcontrol -nr 02 -function GetProcessList
    31.07.2013 13:16:55
    GetProcessList
    OK
    name, description, dispstatus, textstatus, starttime, elapsedtime, pid
    disp+work, Dispatcher, YELLOW, Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable, 2013 07 31 11:26:41, 1:50:14, 14549078
    rslgcoll, Central Syslog Collector, GREEN, Running, 2013 07 31 11:26:41, 1:50:14, 11141296
    rslgsend, Central Syslog Sender, GREEN, Running, 2013 07 31 11:26:41, 1:50:14, 11862158
    igswd_mt, IGS Watchdog, GRAY, Stopped, , , 13631708.
    kbpadm> sapcontrol -nr 01 -function GetProcessList
    31.07.2013 14:41:22
    GetProcessList
    OK
    name, description, dispstatus, textstatus, starttime, elapsedtime, pid
    msg_server, MessageServer, GREEN, Running, 2013 07 31 11:25:53, 3:15:29, 14614568
    enserver, EnqueueServer, GRAY, Stopped, , , 14483586
    kbpadm> sapcontrol -nr 00  -function GetProcessList
    31.07.2013 14:41:55
    GetProcessList
    OK
    name, description, dispstatus, textstatus, starttime, elapsedtime, pid
    msg_server, MessageServer, GREEN, Running, 2013 07 31 11:26:17, 3:15:38, 10879188
    enserver, EnqueueServer, GRAY, Stopped, , , 13041698
    J2EE is not coming up. ALSO plz tel where to update 'system/type'  .
    There is a warning msg :
    J2ee Startup: profile parameter 'system/type' not correctly set to start J2EE; use 'J2EE' for Java only and 'DS' for double stack instance
    Server0 is not running.
    Kindly Assist.
    Regards.
    Gayathri.K

Maybe you are looking for