Change detector failed while scanning for changes to type User

I'm receiving lots of system log warnings in IdM.
These warnings are not bound to any particular action in IdM, they just do appear while IdM is on.
Almost one warning per one second.
Change detector failed while scanning for changes to type Server
Change detector failed while scanning for changes to type UserForm
Change detector failed while scanning for changes to type User
Change detector failed while scanning for changes to type Resource
SysLog detail:
Timestamp 123
Event
Server server11
Severity Warning
Component Repository
Error Code OCDT00
Message Change detector failed while scanning for changes to type User
Reported cause java.lang.NullPointerException
java.lang.NullPointerException
at com.waveset.repository.ObjectChange.equals(ObjectChange.java:112)
at java.util.HashMap.eq(HashMap.java:299)
at java.util.HashMap.containsKey(HashMap.java:381)
at java.util.HashSet.contains(HashSet.java:182)
at com.waveset.repository.ObjectChangeManager$RemoteChangeDetector.dispatchChanges(ObjectChangeManager.java:398)
at com.waveset.repository.ObjectChangeManager$RemoteChangeDetector.run(ObjectChangeManager.java:314)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

same here, just deployed 8.1 with oracle as db. It results in syslog table growing into 10+G and still growing.
wonder if there are others who are seeing this.
my "syslog -d 1" output looks like this...
2009-12-02 04:52:55.972 null W xxx RP OCDT00 Change
detector failed while scanning for changes to type Account
2009-12-02 04:53:06.400 null W xxx RP OCDT00 Change
detector failed while scanning for changes to type Server
2009-12-02 04:53:06.578 null W xxx RP OCDT00 Change
detector failed while scanning for changes to type User
2009-12-02 04:53:06.914 null W xxx RP OCDT00 Change
detector failed while scanning for changes to type Account
2009-12-02 04:53:17.479 null W xxx RP OCDT00 Change
detector failed while scanning for changes to type Server
C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0.18\webapps\ims\bin
lh syslog -d 1

Similar Messages

  • Failed while scanning for CD/DVD drives, error 2355

    Failed while scanning for CD / DVD drives, error 2355.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    D: Unsupported CD or DVD drive.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    As far as I know I do NOT have a virtual drive on this pc.
    Any help???

    Failed while scanning for CD / DVD drives, error 2355.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    D: Unsupported CD or DVD drive.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    As far as I know I do NOT have a virtual drive on this pc.
    Any help???

  • Unable to burn cds. Have run diognostics. i tunes not running in safe mode. invalid lower filters registry value. Failed while scanning for CD/DVD drives, error 2500. Please help.

    Unable to burn CDs using i tunes. Have run diognostics.    Summary:-   i tunes not running in safe mode.
                                                                                                                                        Invalid lower filters registry value.
                                                                                                                                        Failed while scanning for CD/DVD drives, error 2500
    Please help.

    That's why you want to make a backup of the registry. If you didn't make a backup, use MS system restore to go back. The only values you should remove are UpperFilter or LowerFilter - one or both may be in there and can be removed. If neither value exists, then that is probably why you can't burn and Windows is not recognizing your drive as a writable drive.
    ... an HP employee expressing his own opinion.
    Please post rather than send me a Message. It's good for the community and I might not be able to get back quickly. - Thank you.

  • An error occurred while scanning for security updates. (0x80004003)

    Has anyone seen this error:   An error occurred while scanning for security updates. (0x80004003)?
    This error occurs when I run the MBSA tool either locally or remote against a workstation.  I also thought that the firewall may be the issue, it is not.  I ran the MBSA tool on the WSUS replica and WSUS upstream server and received the same results. I
    have been running the MBSA tool and have not run into this probem before.   I am running SolarWinds PatchManager on the upstream WSUS server and have recently configured the upstream and downstream servers to communicate, I imported
    the certifcate from the WSUS upstream to the replica and noticed that after this we started having issues with the MBSA scans.  Not sure if this is related but it is the only change between MBSA working and not working.  P.S.  The scan does
    work when we use the offline scenario instead of pointing to the WSUS server.
    Any help would be appreciated.
    Thanks
    bc

    Yes, the log file was too large I have pasted the 2nd half after running MBSA on the server (the setting is to scan using Windows Server Update Services (WSUS) only.)  This second half of the windowslog file shows errors after running MBSA
    MBSA scan time was 9:44 PM
    2014-07-31   
    19:38:35:487  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:44:14:497  216   2344  
    Report Uploading 4 events using cached cookie, reporting URL =
    http://eus1:8530/ReportingWebService/ReportingWebService.asmx
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING: ReportEventBatch failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING: SOAP Fault: 0x00012c
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    faultstring:Fault occurred
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    ErrorCode:ConfigChanged(2)
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    Message:(null)
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    ID:2b9836c5-3159-494b-ae27-72559d089586
    2014-07-31   
    19:44:14:555  216   2344  
    Report WARNING: Reporter failed to upload events with hr = 8024400d.
    2014-07-31   
    19:45:57:201  9128   12a8  
    Misc   =========== 
    Logging initialized (build: 7.6.7600.256, tz: -0400) 
    ===========
    2014-07-31   
    19:45:57:201  9128   12a8  
    Misc     = Process: C:\Program Files\Microsoft Baseline Security Analyzer 2\mbsa.exe
    2014-07-31   
    19:45:57:201  9128   12a8  
    Misc     = Module: C:\Windows\system32\wuapi.dll
    2014-07-31   
    19:45:57:200  9128   12a8  
    COMAPI -------------
    2014-07-31   
    19:45:57:201  9128   12a8  
    COMAPI -- START --  COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:45:57:202  9128   12a8  
    COMAPI ---------
    2014-07-31   
    19:45:57:218  216   2344  
    Agent  *************
    2014-07-31   
    19:45:57:218  9128   12a8  
    COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:45:57:218  216   2344  
    Agent  ** START **  Agent: Finding updates [CallerId = MBSA]
    2014-07-31   
    19:45:57:218  216   2344  
    Agent  *********
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Include potentially superseded updates
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Online = Yes; Ignore download priority = No
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Criteria = "IsInstalled=0 or
    IsInstalled=1"
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Search Scope = {Machine}
    2014-07-31   
    19:45:58:410  216   2344  
    PT     +++++++++++  PT: Synchronizing server updates 
    +++++++++++
    2014-07-31   
    19:45:58:410  216   2344  
    PT       + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://eus1:8530/ClientWebService/client.asmx
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING: SOAP Fault: 0x00012c
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    faultstring:Fault occurred
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    ErrorCode:ConfigChanged(2)
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    Message:(null)
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    ID:e9b0d06e-d0c8-443f-abc9-512bc0f2cfa1
    2014-07-31   
    19:46:00:481  216   2344  
    PT     Initializing simple targeting cookie,
    clientId = e651f142-bc0f-467d-b416-d344215f5c0a, target group = EMCC Servers, DNS name = elf1.monarch.com
    2014-07-31   
    19:46:00:481  216   2344  
    PT       Server URL =
    http://eus1:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-31   
    19:46:18:451  216   2344  
    PT     +++++++++++ 
    PT: Synchronizing extended update info  +++++++++++
    2014-07-31   
    19:46:18:451  216   2344  
    PT       + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://eus1:8530/ClientWebService/client.asmx
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {92AEAB02-F8FC-4527-B285-50FDC8EF3F85}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {2212D902-7C3B-408E-96A3-ECE4D00BFAE6}.101 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {490BE004-BC5C-4EEF-AC82-769542FC3A2D}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {568C1005-5178-4C13-8486-18E2C5AF4834}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Update {D9F49D05-AC6D-4A2A-8150-D2B4B730DEED}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {74844E07-2F55-40D4-9E16-E17A2815FEBE}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {3C72A908-F3CD-413D-B2BF-ECB68D24B6FE}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {50990D0B-4795-4830-9C3A-753485B2D433}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {9DB82D0B-5611-4BC1-A4B8-432FE1A3CC43}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {7BB7B30C-351D-4F8C-ABE4-5F7965635A03}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {AEF6280F-8C4D-4804-9913-407582227E75}.202 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {16BB6A11-B540-4486-AB13-F3B9789E90B5}.105 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {1B127611-D28E-4167-A1DC-243A51BC528F}.203 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {2F6F2013-2990-4FA6-8AB9-CA59DCA4E62D}.202 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {21732D13-3D34-4DD7-B663-32F2A1631EA9}.105 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Update {E879EE15-340D-442C-B8A4-CF91D18C1B6B}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Update {99FEC317-44CD-40B4-B67E-94C840510983}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {8096C018-252D-4C32-BC9E-F33AC67ECFF1}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {ECCC4D19-3032-4C82-91AB-A31560B13F80}.205 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {BB49CC19-8847-4986-AA93-5E905421E55A}.103 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {023BB023-490F-4DF3-BCAA-9521EE8B5847}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {9676C624-58CB-4A30-B7B3-1D013CF3DBBC}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {1BB3DE24-0D76-4D59-9B9E-556722BFE852}.101 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {F4695A25-0D22-4E3B-9BA9-9BBC62198C28}.103 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {11152F27-ACCA-4438-B21D-A0B61480D33B}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {308DE327-7354-4481-9981-DEA0FC61925E}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {16E9C62D-05B2-4E14-BFB0-CF55EDBD4F61}.106 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {C750962E-9D5E-45CE-9967-AE2D67115966}.202 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {9F7D6930-6816-423A-AF3C-C83ADFA7F612}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {497BCC31-ACF7-46E2-B664-C79FD2D39F8B}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Update {E00B2634-BEF9-4C32-B2BF-DEAF7D7221E4}.102 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {7738E837-B152-487B-8527-CD3A9C0E43E3}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {39757C3A-7ABE-4418-8B2A-C7EA7D88B36A}.202 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {A8968B3A-7FB5-4089-888F-4CDB14055DE9}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {E6ED643C-8611-4453-A723-9847B7BF60EB}.103 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {C499223D-2F22-4626-BBE5-F5A35E7A5854}.204 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {48BEEF41-9D2D-4E72-9A61-59F98B12C07A}.204 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {332AA342-7AC4-4FB4-9C27-C2C9F4EAE6C0}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {2661BD46-2980-4FCF-A062-B3A0C7820663}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {DC548E48-407C-48E1-ACA4-6B4C0DF14E69}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {ED981249-8D8F-42A1-87DB-0AB5C07430B2}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {18FEE64A-1E7F-4932-8158-E8AB241F3A1A}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {3732354D-3DAE-4E71-B82C-61A12C300F72}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {3061954E-EDAA-4625-837C-CE768D68927D}.204 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {78F92451-801A-40F5-9582-CB8D1CA993BE}.202 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {ADA7CF51-66B0-4A00-B37B-68D569D6FF8B}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {345B0353-DFC6-48CC-A6B6-A490CA26B503}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {1330DB53-75FF-4D87-9270-6A5449A67AD7}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {E35E5957-A5A9-4576-9D54-314A34C47C53}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Update {DC17765A-6814-47AD-9F54-5BFBCBF95FB0}.101 is not a valid bundle. Not
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {CEFF8CA0-08DB-41D0-B825-FCC2CEBAF8B4}.108 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {2FECFFA0-44C8-4719-8F72-EC7BD8EDB793}.1 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {2BDE2BA3-EF93-49C6-A3C6-A806835A680F}.200 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {FA04F2A3-4DB5-4903-A08C-ADDFCF93EE28}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {0B8586A5-EEB6-4DC0-BCDA-2635C7E12B55}.102 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:895  216   2344  
    Agent  Update {A6BD61A7-CC63-4068-8510-AA5268FB03E8}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {4C0BA6A7-A8F0-417E-B9DA-906207429CE6}.204 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {CE9876A9-83BF-4EDC-8793-4CBD6F3A6C5A}.202 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {63A011AC-FF81-44B9-811C-BECE5DC6C34B}.101 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {4A0A69AD-4237-43E7-8FB9-5A814361EC76}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {7E8ACCAD-2892-4F2D-9549-1FF8BE44AAD1}.203 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {E17C01AE-BACC-4147-97AD-51A0708126D2}.102 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {CB1F1FAE-F738-49E7-AE3E-7A0C2308838B}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {9696B7B0-FF6F-4AA6-B29C-E0200CB6EB79}.200 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {B58F24B1-58A0-4661-9882-0FF509712946}.102 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {E47BE4B1-5EF0-442F-995F-C000D5AFF062}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {D68E0CB2-9501-405E-AF9C-156F352D6735}.107 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {09593FB3-C94B-4A07-84C4-2E60703AD644}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {99C920B7-65AB-4ACD-A4AD-C4F522E4D7A9}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {EDE986B7-03CE-4B0C-8891-AF09113CB0DB}.200 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {B8315ACF-BF26-4C3A-979B-80A46D06697F}.200 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {013AF7D6-EC9F-4DEF-AE41-007D211F9FBC}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {6E3C01DB-6977-46D2-A537-00F53DA0B3B3}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {9842D9DB-8AE8-4F0B-B974-66787AEC8FBC}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:896  216   2344  
    Agent  Update {0C1447DC-904E-4DCE-B208-50741D1CC65C}.102 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {DD7619DD-D6A6-4765-8406-612FD79583BA}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {ABB0AFDD-4B0A-4C3E-8341-07EA3941C465}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {B66BA1DF-4BC1-4145-859F-239C9F9BB5A0}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {E2C928E1-BE92-4715-817D-FD6090F2FB07}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {C16FDFFD-A0D3-49EB-A8EB-B8F5E21D52C3}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {57260DFE-227C-45E3-9FFC-2FC77A67F95A}.104 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent   * Added update {5BCDA2FE-A3F5-42C9-91F0-823230942BD8}.204 to search result
    2014-07-31   
    19:46:18:897  216   2344  
    Agent    * Found 151 updates and 95 categories in search; evaluated appl. rules of 1327 out of 2207 deployed entities
    2014-07-31   
    19:46:18:918  216   2344  
    Agent  *********
    2014-07-31   
    19:46:18:918  216   2344  
    Agent  **  END 
    **  Agent: Finding updates [CallerId = MBSA]
    2014-07-31   
    19:46:18:918  216   2344  
    Agent  *************
    2014-07-31   
    19:46:18:932  216   2344  
    Report REPORT EVENT: {A427D5D8-F546-4FBB-9F5F-931DF1F46063}      
    2014-07-31 19:46:18:898-0400      1     
    147    101    {00000000-0000-0000-0000-000000000000}  
    0       0     
    MBSA   Success      
    Software Synchronization   Windows Update Client successfully detected 151 updates.
    2014-07-31   
    19:46:18:932  216   2344  
    Report REPORT EVENT: {C8151494-E563-4AEB-B37F-14FD7864BF5D}      
    2014-07-31 19:46:18:898-0400      1     
    156    101    {00000000-0000-0000-0000-000000000000}  
    0       0     
    MBSA   Success      
    Pre-Deployment Check Reporting client status.
    2014-07-31   
    19:46:18:933  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:934  9128   2550  
    COMAPI >>--  RESUMED 
    -- COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:46:18:934  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:934  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:936  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:936  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:936  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:19:032  9128   2550  
    COMAPI   - Updates found = 151
    2014-07-31   
    19:46:19:033  9128   2550  
    COMAPI ---------
    2014-07-31   
    19:46:19:033  9128   2550  
    COMAPI --  END 
    --  COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:46:19:033  9128   2550  
    COMAPI -------------
    2014-07-31   
    19:46:23:918  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    bc

  • Error while scanning for Serial-ATA devices.

    There was an error while scanning for Serial-ATA devices. I'm not sure how to trouble shoot this. I believe a secondary drive in bay 2 died.

    I also have just began to hit this issue.
    I have 4 2T enterprise class WD drives in a raid 1+0 (or was it 0+1) config.
    Device Model: WDC WD2002FYPS-01U1B1
    One disk (disk0 in bay 2) keeps disappearing. Completely. /dev/disk0 and /dev/rdisk0 vanish.
    If I look at "about this mac" / "More Info" / "Serial-ATA" I get the "error while scanning ...".
    If I reboot, the offending disc comes back and the raid volumes start rebuilding.
    The SMART status is (reported to be) fine.
    I use the 'smartmon' tools and look at the extended SMART status and the values of the counters all looks the same as the other drives. I can run an extended offline test, which takes forever to execute. disk 1 and 3 eventually finish with success (it writes this status into a SMART log area on the disc).
    Disk 2 and 0 take longer. I image this is because 2 is being read to resilver 0. Currently, I am running with disk0 absent again, and disk 2s test did not complete. It claims it was aborted by the host, so I imagine the one on disk0 will claim the same after I reboot.
    My system is under extended AppleCare until 16 Jan 2011, so if I can determine that this is a disc controller error, I can get it fixed. The drives have a 5 year warrantee, and are less than 1yr old, so they are covered. I just need to figure out what the issue is.
    I will now reboot and recover disk0 and see if perhaps there is anything recorded in the SMART log.
    There is nothing in kernel.log specific to disk0. I include the log extract here for posterity. The "speed" volume is not raid 0+1, just striped, which is why it gets aborted.
    Dec 21 23:30:26 8way kernel[0]: AppleRAID::restartSet - restarting set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
    Dec 21 23:30:26 8way kernel[0]: AppleRAIDMirrorSet::rebuild complete for set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
    Dec 22 04:17:22 8way kernel[0]: AppleRAID::restartSet - restarting set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
    Dec 22 04:17:22 8way kernel[0]: AppleRAIDMirrorSet::rebuild complete for set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
    Dec 22 05:23:16 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:23:30 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:23:44: --- last message repeated 1 time ---
    Dec 22 05:23:44 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:24:14: --- last message repeated 4 times ---
    Dec 22 05:24:19 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:24:56: --- last message repeated 2 times ---
    Dec 22 05:24:56 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:25:17: --- last message repeated 1 time ---
    Dec 22 05:25:17 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:25:31: --- last message repeated 1 time ---
    Dec 22 05:25:31 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on EB932B0E-8476-480C-BBD4-53A9A77D9FEF
    Dec 22 05:25:45: --- last message repeated 1 time ---
    Dec 22 05:25:45 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:26:15: --- last message repeated 2 times ---
    Dec 22 05:26:21 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:26:51: --- last message repeated 4 times ---
    Dec 22 05:27:12 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:27:33: --- last message repeated 1 time ---
    Dec 22 05:27:26 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:27:40: --- last message repeated 1 time ---
    Dec 22 05:27:40 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:28:24: --- last message repeated 1 time ---
    Dec 22 05:28:24 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:28:39: --- last message repeated 1 time ---
    Dec 22 05:28:39 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
    Dec 22 05:29:14 8way kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76), member 3C6E9EA4-831A-4
    57A-8CA5-6E7E9CBEED25, set byte offset = 222462894080.
    Dec 22 05:29:14 8way kernel[0]: AppleRAID::recover() member 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25 from set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76) has been marked
    offline.
    Dec 22 05:29:14 8way kernel[0]: AppleRAID::restartSet - restarting set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
    Dec 22 05:32:38 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:33:22: --- last message repeated 1 time ---
    Dec 22 05:33:22 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:34:06: --- last message repeated 1 time ---
    Dec 22 05:34:06 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
    Dec 22 05:34:53: --- last message repeated 1 time ---
    Dec 22 05:34:53 8way kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D), member 9722C38E-DFF9-4
    68F-8DE5-809432493168, set byte offset = 35194773504.
    Dec 22 05:34:53 8way kernel[0]: AppleRAID::recover() member 9722C38E-DFF9-468F-8DE5-809432493168 from set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D) has been marked
    offline.
    Dec 22 05:34:53 8way kernel[0]: AppleRAID::restartSet - restarting set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
    Dec 22 05:37:24 8way kernel[0]: AppleAHCIDiskQueueManager::setPowerState(0x13d64500, 2 -> 1) timed out after 100113 ms
    Dec 22 05:37:44 8way kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...
    Dec 22 05:37:44 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002be on EB932B0E-8476-480C-BBD4-53A9A77D9FEF
    Dec 22 05:37:44 8way kernel[0]: AppleRAID::recover() member EB932B0E-8476-480C-BBD4-53A9A77D9FEF from set "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BBE0) has been marked
    offline.
    Dec 22 05:37:44 8way kernel[0]: AppleRAID::restartSet - restarting set "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BBE0).
    Dec 22 05:37:44 8way kernel[0]: disk4: media is not present.
    Dec 22 05:37:59 8way kernel[0]: speed::terminate(kIOServiceSynchronous) timeout
    Dec 22 05:37:59 8way kernel[0]: AppleRAID::completeRAIDRequest - underrun detected, expected = 0xa000, actual = 0x9e00, set = "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BB
    E0)
    Dec 22 05:37:59 8way kernel[0]: disk4: data underrun.
    Dec 22 05:37:59 8way kernel[0]: jnl: disk4: dojnlio: strategy err 0x5
    Dec 22 05:37:59 8way kernel[0]: jnl: disk4: end_transaction: only wrote 0 of 40960 bytes to the journal!
    Dec 22 05:37:59 8way kernel[0]: disk4: media is not present.
    Dec 22 05:38:00 8way kernel[0]: jnl: disk4: close: journal 0x13f34e04, is invalid. aborting outstanding transactions

  • SEVERE: An error occured while scanning for the next trigger to fire

    Hi All,
    I followed below steps to configure Oracle BI publisher scheduler on oracle 10g database.
    1.Log in to BI Publisher as a user with Administrator privileges and select the Admin tab.
    2.Under System Maintenance, select Scheduler Configuration.
    3.Enter the database connection information for the target Oracle database and user.
    Database Type: 10g
    Connection String: jdbc:oracle:thin://<hostname>:<port#>:<oracle SID>
    Username/Password for the database user
    Database Driver Class: oracle.jdbc.driver.OracleDriver
    4.Click the Test Connection button to make sure the connection information is valid.
    5.Click the Install Schema button to install the scheduler tables.
    6.Restart the BI Publisher application.
    The Schema installed successfully.
    But when I am starting the weblogic server I am getting below error and BI publisher application is not getting up.
    INFO: Handling 6 triggers that missed their scheduled fire-time.
    23-Dec-2011 05:29:38 org.quartz.core.ErrorLogger schedulerError
    SEVERE: An error occured while scanning for the next trigger to fire.
    org.quartz.JobPersistenceException: Couldn't acquire next trigger: Couldn't retrieve trigger: Invalid column name [See nested exception: org.quartz.JobPersistenceException: Couldn't retrieve trigger: Invalid column name [See nested exception: java.sql.SQLException: Invalid column name]]
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1773)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
    * Nested Exception (Underlying Cause) ---------------
    org.quartz.JobPersistenceException: Couldn't retrieve trigger: Invalid column name [See nested exception: java.sql.SQLException: Invalid column name]
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1126)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1759)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
    * Nested Exception (Underlying Cause) ---------------
    java.sql.SQLException: Invalid column name
    at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
    at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
    at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java:3372)
    at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:2009)
    at oracle.jdbc.driver.OracleResultSet.getBinaryStream(OracleResultSet.java:668)
    at org.apache.commons.dbcp.DelegatingResultSet.getBinaryStream(DelegatingResultSet.java:233)
    at org.quartz.impl.jdbcjobstore.oracle.OracleDelegate.getObjectFromBlob(OracleDelegate.java:154)
    at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTrigger(StdJDBCDelegate.java:2382)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1115)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1759)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
    23-Dec-2011 05:30:55 org.quartz.core.ErrorLogger schedulerError
    The system details are as below :
    BI Publisher version : 10.1.3.4
    Oracle DB : 10 G
    Weblogic server :10.3.2
    Please suggest to resolve this issue.
    Thanks,
    Sachin

    Hi,
    This errors occurs if you have configured some schema for the scheduler and configured it on BIP, but the configured schema is no longer available.
    That is why I am suggesting you to replace the current quartz.properties file with the original file that exits during installation.
    Then try to start the server, and see if the server starts without error.
    After that you can try to configure the scheduler from BIP console.
    thanks,
    sandeep

  • ClamAV fails to scan for viruses in emails [CLAWS MAIL]

    I've recently switched from Thunderbird to Claws Mail and ran into one small, but annoying, problem.
    I want to use ClamAV + the clamav extension for claws mail to scan for viruses, however it does seem to have permission problems.
    clamd is running, user and group clamav all have the relevant permissions as far as I can tell, however upon scanning my mail, I always end up with the following error:
    Scanning error:
    /home/username/.claws-mail/mimetmp/0000000e.mimetmp: lstat() failed: Permission denied. ERROR
    Here's my clamd.conf:
    ## Please read the clamd.conf(5) manual before editing this file.
    # Comment or remove the line below.
    #Example
    # Uncomment this option to enable logging.
    # LogFile must be writable for the user running daemon.
    # A full path is required.
    # Default: disabled
    LogFile /var/log/clamav/clamd.log
    # By default the log file is locked for writing - the lock protects against
    # running clamd multiple times (if want to run another clamd, please
    # copy the configuration file, change the LogFile variable, and run
    # the daemon with --config-file option).
    # This option disables log file locking.
    # Default: no
    #LogFileUnlock yes
    # Maximum size of the log file.
    # Value of 0 disables the limit.
    # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes)
    # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes). To specify the size
    # in bytes just don't use modifiers.
    # Default: 1M
    #LogFileMaxSize 2M
    # Log time with each message.
    # Default: no
    LogTime yes
    # Also log clean files. Useful in debugging but drastically increases the
    # log size.
    # Default: no
    #LogClean yes
    # Use system logger (can work together with LogFile).
    # Default: no
    #LogSyslog yes
    # Specify the type of syslog messages - please refer to 'man syslog'
    # for facility names.
    # Default: LOG_LOCAL6
    #LogFacility LOG_MAIL
    # Enable verbose logging.
    # Default: no
    #LogVerbose yes
    # Log additional information about the infected file, such as its
    # size and hash, together with the virus name.
    #ExtendedDetectionInfo yes
    # This option allows you to save a process identifier of the listening
    # daemon (main thread).
    # Default: disabled
    PidFile /run/clamav/clamd.pid
    # Optional path to the global temporary directory.
    # Default: system specific (usually /tmp or /var/tmp).
    TemporaryDirectory /tmp
    # Path to the database directory.
    # Default: hardcoded (depends on installation options)
    DatabaseDirectory /var/lib/clamav
    # Only load the official signatures published by the ClamAV project.
    # Default: no
    OfficialDatabaseOnly yes
    # The daemon can work in local mode, network mode or both.
    # Due to security reasons we recommend the local mode.
    # Path to a local socket file the daemon will listen on.
    # Default: disabled (must be specified by a user)
    LocalSocket /var/lib/clamav/clamd.sock
    # Sets the group ownership on the unix socket.
    # Default: disabled (the primary group of the user running clamd)
    LocalSocketGroup clamav
    # Sets the permissions on the unix socket to the specified mode.
    # Default: disabled (socket is world accessible)
    #LocalSocketMode 660
    # Remove stale socket after unclean shutdown.
    # Default: yes
    #FixStaleSocket yes
    # TCP port address.
    # Default: no
    #TCPSocket 3310
    # TCP address.
    # By default we bind to INADDR_ANY, probably not wise.
    # Enable the following to provide some degree of protection
    # from the outside world.
    # Default: no
    #TCPAddr 127.0.0.1
    # Maximum length the queue of pending connections may grow to.
    # Default: 200
    #MaxConnectionQueueLength 30
    # Clamd uses FTP-like protocol to receive data from remote clients.
    # If you are using clamav-milter to balance load between remote clamd daemons
    # on firewall servers you may need to tune the options below.
    # Close the connection when the data size limit is exceeded.
    # The value should match your MTA's limit for a maximum attachment size.
    # Default: 25M
    #StreamMaxLength 10M
    # Limit port range.
    # Default: 1024
    #StreamMinPort 30000
    # Default: 2048
    #StreamMaxPort 32000
    # Maximum number of threads running at the same time.
    # Default: 10
    #MaxThreads 20
    # Waiting for data from a client socket will timeout after this time (seconds).
    # Default: 120
    #ReadTimeout 300
    # This option specifies the time (in seconds) after which clamd should
    # timeout if a client doesn't provide any initial command after connecting.
    # Default: 5
    #CommandReadTimeout 5
    # This option specifies how long to wait (in miliseconds) if the send buffer is full.
    # Keep this value low to prevent clamd hanging
    # Default: 500
    #SendBufTimeout 200
    # Maximum number of queued items (including those being processed by MaxThreads threads)
    # It is recommended to have this value at least twice MaxThreads if possible.
    # WARNING: you shouldn't increase this too much to avoid running out of file descriptors,
    # the following condition should hold:
    # MaxThreads*MaxRecursion + (MaxQueue - MaxThreads) + 6< RLIMIT_NOFILE (usual max is 1024)
    # Default: 100
    #MaxQueue 200
    # Waiting for a new job will timeout after this time (seconds).
    # Default: 30
    #IdleTimeout 60
    # Don't scan files and directories matching regex
    # This directive can be used multiple times
    # Default: scan all
    #ExcludePath ^/proc/
    #ExcludePath ^/sys/
    # Maximum depth directories are scanned at.
    # Default: 15
    #MaxDirectoryRecursion 20
    # Follow directory symlinks.
    # Default: no
    #FollowDirectorySymlinks yes
    # Follow regular file symlinks.
    # Default: no
    #FollowFileSymlinks yes
    # Scan files and directories on other filesystems.
    # Default: yes
    #CrossFilesystems yes
    # Perform a database check.
    # Default: 600 (10 min)
    #SelfCheck 600
    # Execute a command when virus is found. In the command string %v will
    # be replaced with the virus name.
    # Default: no
    #VirusEvent /usr/local/bin/send_sms 123456789 "VIRUS ALERT: %v"
    # Run as another user (clamd must be started by root for this option to work)
    # Default: don't drop privileges
    User clamav
    # Initialize supplementary group access (clamd must be started by root).
    # Default: no
    #AllowSupplementaryGroups no
    # Stop daemon when libclamav reports out of memory condition.
    #ExitOnOOM yes
    # Don't fork into background.
    # Default: no
    #Foreground yes
    # Enable debug messages in libclamav.
    # Default: no
    #Debug yes
    # Do not remove temporary files (for debug purposes).
    # Default: no
    #LeaveTemporaryFiles yes
    # Detect Possibly Unwanted Applications.
    # Default: no
    #DetectPUA yes
    # Exclude a specific PUA category. This directive can be used multiple times.
    # See http://www.clamav.net/support/pua for the complete list of PUA
    # categories.
    # Default: Load all categories (if DetectPUA is activated)
    #ExcludePUA NetTool
    #ExcludePUA PWTool
    # Only include a specific PUA category. This directive can be used multiple
    # times.
    # Default: Load all categories (if DetectPUA is activated)
    #IncludePUA Spy
    #IncludePUA Scanner
    #IncludePUA RAT
    # In some cases (eg. complex malware, exploits in graphic files, and others),
    # ClamAV uses special algorithms to provide accurate detection. This option
    # controls the algorithmic detection.
    # Default: yes
    #AlgorithmicDetection yes
    ## Executable files
    # PE stands for Portable Executable - it's an executable file format used
    # in all 32 and 64-bit versions of Windows operating systems. This option allows
    # ClamAV to perform a deeper analysis of executable files and it's also
    # required for decompression of popular executable packers such as UPX, FSG,
    # and Petite. If you turn off this option, the original files will still be
    # scanned, but without additional processing.
    # Default: yes
    #ScanPE yes
    # Executable and Linking Format is a standard format for UN*X executables.
    # This option allows you to control the scanning of ELF files.
    # If you turn off this option, the original files will still be scanned, but
    # without additional processing.
    # Default: yes
    #ScanELF yes
    # With this option clamav will try to detect broken executables (both PE and
    # ELF) and mark them as Broken.Executable.
    # Default: no
    #DetectBrokenExecutables yes
    ## Documents
    # This option enables scanning of OLE2 files, such as Microsoft Office
    # documents and .msi files.
    # If you turn off this option, the original files will still be scanned, but
    # without additional processing.
    # Default: yes
    #ScanOLE2 yes
    # With this option enabled OLE2 files with VBA macros, which were not
    # detected by signatures will be marked as "Heuristics.OLE2.ContainsMacros".
    # Default: no
    #OLE2BlockMacros no
    # This option enables scanning within PDF files.
    # If you turn off this option, the original files will still be scanned, but
    # without decoding and additional processing.
    # Default: yes
    #ScanPDF yes
    ## Mail files
    # Enable internal e-mail scanner.
    # If you turn off this option, the original files will still be scanned, but
    # without parsing individual messages/attachments.
    # Default: yes
    #ScanMail yes
    # Scan RFC1341 messages split over many emails.
    # You will need to periodically clean up $TemporaryDirectory/clamav-partial directory.
    # WARNING: This option may open your system to a DoS attack.
    # Never use it on loaded servers.
    # Default: no
    #ScanPartialMessages yes
    # With this option enabled ClamAV will try to detect phishing attempts by using
    # signatures.
    # Default: yes
    #PhishingSignatures yes
    # Scan URLs found in mails for phishing attempts using heuristics.
    # Default: yes
    #PhishingScanURLs yes
    # Always block SSL mismatches in URLs, even if the URL isn't in the database.
    # This can lead to false positives.
    # Default: no
    #PhishingAlwaysBlockSSLMismatch no
    # Always block cloaked URLs, even if URL isn't in database.
    # This can lead to false positives.
    # Default: no
    #PhishingAlwaysBlockCloak no
    # Allow heuristic match to take precedence.
    # When enabled, if a heuristic scan (such as phishingScan) detects
    # a possible virus/phish it will stop scan immediately. Recommended, saves CPU
    # scan-time.
    # When disabled, virus/phish detected by heuristic scans will be reported only at
    # the end of a scan. If an archive contains both a heuristically detected
    # virus/phish, and a real malware, the real malware will be reported
    # Keep this disabled if you intend to handle "*.Heuristics.*" viruses
    # differently from "real" malware.
    # If a non-heuristically-detected virus (signature-based) is found first,
    # the scan is interrupted immediately, regardless of this config option.
    # Default: no
    #HeuristicScanPrecedence yes
    ## Data Loss Prevention (DLP)
    # Enable the DLP module
    # Default: No
    #StructuredDataDetection yes
    # This option sets the lowest number of Credit Card numbers found in a file
    # to generate a detect.
    # Default: 3
    #StructuredMinCreditCardCount 5
    # This option sets the lowest number of Social Security Numbers found
    # in a file to generate a detect.
    # Default: 3
    #StructuredMinSSNCount 5
    # With this option enabled the DLP module will search for valid
    # SSNs formatted as xxx-yy-zzzz
    # Default: yes
    #StructuredSSNFormatNormal yes
    # With this option enabled the DLP module will search for valid
    # SSNs formatted as xxxyyzzzz
    # Default: no
    #StructuredSSNFormatStripped yes
    ## HTML
    # Perform HTML normalisation and decryption of MS Script Encoder code.
    # Default: yes
    # If you turn off this option, the original files will still be scanned, but
    # without additional processing.
    #ScanHTML yes
    ## Archives
    # ClamAV can scan within archives and compressed files.
    # If you turn off this option, the original files will still be scanned, but
    # without unpacking and additional processing.
    # Default: yes
    #ScanArchive yes
    # Mark encrypted archives as viruses (Encrypted.Zip, Encrypted.RAR).
    # Default: no
    #ArchiveBlockEncrypted no
    ## Limits
    # The options below protect your system against Denial of Service attacks
    # using archive bombs.
    # This option sets the maximum amount of data to be scanned for each input file.
    # Archives and other containers are recursively extracted and scanned up to this
    # value.
    # Value of 0 disables the limit
    # Note: disabling this limit or setting it too high may result in severe damage
    # to the system.
    # Default: 100M
    #MaxScanSize 150M
    # Files larger than this limit won't be scanned. Affects the input file itself
    # as well as files contained inside it (when the input file is an archive, a
    # document or some other kind of container).
    # Value of 0 disables the limit.
    # Note: disabling this limit or setting it too high may result in severe damage
    # to the system.
    # Default: 25M
    #MaxFileSize 30M
    # Nested archives are scanned recursively, e.g. if a Zip archive contains a RAR
    # file, all files within it will also be scanned. This options specifies how
    # deeply the process should be continued.
    # Note: setting this limit too high may result in severe damage to the system.
    # Default: 16
    #MaxRecursion 10
    # Number of files to be scanned within an archive, a document, or any other
    # container file.
    # Value of 0 disables the limit.
    # Note: disabling this limit or setting it too high may result in severe damage
    # to the system.
    # Default: 10000
    #MaxFiles 15000
    ## Clamuko settings
    # Enable Clamuko. Dazuko must be configured and running. Clamuko supports
    # both Dazuko (/dev/dazuko) and DazukoFS (/dev/dazukofs.ctrl). DazukoFS
    # is the preferred option. For more information please visit www.dazuko.org
    # Default: no
    #ClamukoScanOnAccess yes
    # The number of scanner threads that will be started (DazukoFS only).
    # Having multiple scanner threads allows Clamuko to serve multiple
    # processes simultaneously. This is particularly beneficial on SMP machines.
    # Default: 3
    #ClamukoScannerCount 3
    # Don't scan files larger than ClamukoMaxFileSize
    # Value of 0 disables the limit.
    # Default: 5M
    #ClamukoMaxFileSize 10M
    # Set access mask for Clamuko (Dazuko only).
    # Default: no
    #ClamukoScanOnOpen yes
    #ClamukoScanOnClose yes
    #ClamukoScanOnExec yes
    # Set the include paths (all files inside them will be scanned). You can have
    # multiple ClamukoIncludePath directives but each directory must be added
    # in a seperate line. (Dazuko only)
    # Default: disabled
    #ClamukoIncludePath /home
    #ClamukoIncludePath /students
    # Set the exclude paths. All subdirectories are also excluded. (Dazuko only)
    # Default: disabled
    #ClamukoExcludePath /home/bofh
    # With this option you can whitelist specific UIDs. Processes with these UIDs
    # will be able to access all files.
    # This option can be used multiple times (one per line).
    # Default: disabled
    #ClamukoExcludeUID 0
    # With this option enabled ClamAV will load bytecode from the database.
    # It is highly recommended you keep this option on, otherwise you'll miss detections for many new viruses.
    # Default: yes
    #Bytecode yes
    # Set bytecode security level.
    # Possible values:
    # None - no security at all, meant for debugging. DO NOT USE THIS ON PRODUCTION SYSTEMS
    # This value is only available if clamav was built with --enable-debug!
    # TrustSigned - trust bytecode loaded from signed .c[lv]d files,
    # insert runtime safety checks for bytecode loaded from other sources
    # Paranoid - don't trust any bytecode, insert runtime checks for all
    # Recommended: TrustSigned, because bytecode in .cvd files already has these checks
    # Note that by default only signed bytecode is loaded, currently you can only
    # load unsigned bytecode in --enable-debug mode.
    # Default: TrustSigned
    #BytecodeSecurity TrustSigned
    # Set bytecode timeout in miliseconds.
    # Default: 5000
    # BytecodeTimeout 1000
    My freshclam.conf:
    ## Please read the freshclam.conf(5) manual before editing this file.
    # Comment or remove the line below.
    #Example
    # Path to the database directory.
    # WARNING: It must match clamd.conf's directive!
    # Default: hardcoded (depends on installation options)
    #DatabaseDirectory /var/lib/clamav
    # Path to the log file (make sure it has proper permissions)
    # Default: disabled
    UpdateLogFile /var/log/clamav/freshclam.log
    # Maximum size of the log file.
    # Value of 0 disables the limit.
    # You may use 'M' or 'm' for megabytes (1M = 1m = 1048576 bytes)
    # and 'K' or 'k' for kilobytes (1K = 1k = 1024 bytes).
    # in bytes just don't use modifiers.
    # Default: 1M
    #LogFileMaxSize 2M
    # Log time with each message.
    # Default: no
    #LogTime yes
    # Enable verbose logging.
    # Default: no
    #LogVerbose yes
    # Use system logger (can work together with UpdateLogFile).
    # Default: no
    #LogSyslog yes
    # Specify the type of syslog messages - please refer to 'man syslog'
    # for facility names.
    # Default: LOG_LOCAL6
    #LogFacility LOG_MAIL
    # This option allows you to save the process identifier of the daemon
    # Default: disabled
    #PidFile /var/run/freshclam.pid
    # By default when started freshclam drops privileges and switches to the
    # "clamav" user. This directive allows you to change the database owner.
    # Default: clamav (may depend on installation options)
    #DatabaseOwner clamav
    # Initialize supplementary group access (freshclam must be started by root).
    # Default: no
    #AllowSupplementaryGroups yes
    # Use DNS to verify virus database version. Freshclam uses DNS TXT records
    # to verify database and software versions. With this directive you can change
    # the database verification domain.
    # WARNING: Do not touch it unless you're configuring freshclam to use your
    # own database verification domain.
    # Default: current.cvd.clamav.net
    #DNSDatabaseInfo current.cvd.clamav.net
    # Uncomment the following line and replace XY with your country
    # code. See http://www.iana.org/cctld/cctld-whois.htm for the full list.
    # You can use db.XY.ipv6.clamav.net for IPv6 connections.
    #DatabaseMirror db.XY.clamav.net
    # database.clamav.net is a round-robin record which points to our most
    # reliable mirrors. It's used as a fall back in case db.XY.clamav.net is
    # not working. DO NOT TOUCH the following line unless you know what you
    # are doing.
    DatabaseMirror database.clamav.net
    # How many attempts to make before giving up.
    # Default: 3 (per mirror)
    #MaxAttempts 5
    # With this option you can control scripted updates. It's highly recommended
    # to keep it enabled.
    # Default: yes
    #ScriptedUpdates yes
    # By default freshclam will keep the local databases (.cld) uncompressed to
    # make their handling faster. With this option you can enable the compression;
    # the change will take effect with the next database update.
    # Default: no
    #CompressLocalDatabase no
    # With this option you can provide custom sources (http:// or file://) for
    # database files. This option can be used multiple times.
    # Default: no custom URLs
    #DatabaseCustomURL http://myserver.com/mysigs.ndb
    #DatabaseCustomURL file:///mnt/nfs/local.hdb
    # Number of database checks per day.
    # Default: 12 (every two hours)
    #Checks 24
    # Proxy settings
    # Default: disabled
    #HTTPProxyServer myproxy.com
    #HTTPProxyPort 1234
    #HTTPProxyUsername myusername
    #HTTPProxyPassword mypass
    # If your servers are behind a firewall/proxy which applies User-Agent
    # filtering you can use this option to force the use of a different
    # User-Agent header.
    # Default: clamav/version_number
    #HTTPUserAgent SomeUserAgentIdString
    # Use aaa.bbb.ccc.ddd as client address for downloading databases. Useful for
    # multi-homed systems.
    # Default: Use OS'es default outgoing IP address.
    #LocalIPAddress aaa.bbb.ccc.ddd
    # Send the RELOAD command to clamd.
    # Default: no
    NotifyClamd /etc/clamav/clamd.conf
    # Run command after successful database update.
    # Default: disabled
    #OnUpdateExecute command
    # Run command when database update process fails.
    # Default: disabled
    #OnErrorExecute command
    # Run command when freshclam reports outdated version.
    # In the command string %v will be replaced by the new version number.
    # Default: disabled
    #OnOutdatedExecute command
    # Don't fork into background.
    # Default: no
    #Foreground yes
    # Enable debug messages in libclamav.
    # Default: no
    #Debug yes
    # Timeout in seconds when connecting to database server.
    # Default: 30
    #ConnectTimeout 60
    # Timeout in seconds when reading from database server.
    # Default: 30
    #ReceiveTimeout 60
    # With this option enabled, freshclam will attempt to load new
    # databases into memory to make sure they are properly handled
    # by libclamav before replacing the old ones.
    # Default: yes
    #TestDatabases yes
    # When enabled freshclam will submit statistics to the ClamAV Project about
    # the latest virus detections in your environment. The ClamAV maintainers
    # will then use this data to determine what types of malware are the most
    # detected in the field and in what geographic area they are.
    # Freshclam will connect to clamd in order to get recent statistics.
    # Default: no
    #SubmitDetectionStats /path/to/clamd.conf
    # Country of origin of malware/detection statistics (for statistical
    # purposes only). The statistics collector at ClamAV.net will look up
    # your IP address to determine the geographical origin of the malware
    # reported by your installation. If this installation is mainly used to
    # scan data which comes from a different location, please enable this
    # option and enter a two-letter code (see http://www.iana.org/domains/root/db/)
    # of the country of origin.
    # Default: disabled
    #DetectionStatsCountry country-code
    # This option enables support for our "Personal Statistics" service.
    # When this option is enabled, the information on malware detected by
    # your clamd installation is made available to you through our website.
    # To get your HostID, log on http://www.stats.clamav.net and add a new
    # host to your host list. Once you have the HostID, uncomment this option
    # and paste the HostID here. As soon as your freshclam starts submitting
    # information to our stats collecting service, you will be able to view
    # the statistics of this clamd installation by logging into
    # http://www.stats.clamav.net with the same credentials you used to
    # generate the HostID. For more information refer to:
    # http://www.clamav.net/support/faq/faq-cctts/
    # This feature requires SubmitDetectionStats to be enabled.
    # Default: disabled
    #DetectionStatsHostID unique-id
    # This option enables support for Google Safe Browsing. When activated for
    # the first time, freshclam will download a new database file (safebrowsing.cvd)
    # which will be automatically loaded by clamd and clamscan during the next
    # reload, provided that the heuristic phishing detection is turned on. This
    # database includes information about websites that may be phishing sites or
    # possible sources of malware. When using this option, it's mandatory to run
    # freshclam at least every 30 minutes.
    # Freshclam uses the ClamAV's mirror infrastructure to distribute the
    # database and its updates but all the contents are provided under Google's
    # terms of use. See http://code.google.com/support/bin/answer.py?answer=70015
    # and http://safebrowsing.clamav.net for more information.
    # Default: disabled
    #SafeBrowsing yes
    # This option enables downloading of bytecode.cvd, which includes additional
    # detection mechanisms and improvements to the ClamAV engine.
    # Default: enabled
    #Bytecode yes
    # Download an additional 3rd party signature database distributed through
    # the ClamAV mirrors. Here you can find a list of available databases:
    # http://www.clamav.net/download/cvd/3rdparty
    # This option can be used multiple times.
    #ExtraDatabase dbname1
    #ExtraDatabase dbname2
    Any help is much appreciated.

    MatejLach wrote:
    clamd is running, user and group clamav all have the relevant permissions as far as I can tell, however upon scanning my mail, I always end up with the following error:
    Scanning error:
    /home/username/.claws-mail/mimetmp/0000000e.mimetmp: lstat() failed: Permission denied. ERROR
    Seems like a permissions error to me... maybe check the actual file it is attempting to scan... I know it is in your home folder, but just to be sure, you might want to check that everything is sane.

  • Occasional hang at boot while scanning for PnP cards

    Sometimes my media center won't boot. It hangs at:
    isapnp: Scanning for PnP cards...
    This only happens once in a while (once every 10 or 20 boots). The system is an ION based system, it does not happen on my desktop system? Anyone seen this behaviour? Something ACPI related maybe? Thanks!

    i know, but i really dont know what else to include. I dont know what log files i should be reading. Im new to Arch
    EDIT: I just checked my /var/log/slim.log file and i notice every time the system fails it has the message::
    slim: unexpected signal 15
    EDIT: i also get the following message in slim.log:
    slim: pam_end: system error
    Last edited by yuggoth (2013-03-18 21:37:03)

  • P10 shutting down without bluescreen while scanning for viruses or cleaning

    My P10 shuts down when I scan for viruses or cleaning the system. Since I bought the notebook it works absolutely perfect. But 2 days ago I recognized this For normal work e.g. word, excel, surfing the net and so on, nothing happens, everything works but if I begin to scan, XP shuts down. It just turns off as if you unplug it from circuit!!! Can somebody help me, wrong drivers?, false hardware? I dont know how to solve the problem!!!! Which information do you need???

    Hi Kay,
    This sounds like a classic case of over-heating. Especially if you notice increased fan activity just prior to the notebook shutting down.
    Try cleaning the dust and debris from the CPU heat-sink. You will find lots of posts in this forum describing ways of doing this. My personla favorite is to use a vacuum cleaner hose against the air intake grilles.
    Also, it is worth making sure that the air intake grilles are not being blocked, and that sufficient air can get into the notebook to cool it properly. Don't stand your notebook on a soft surface or carpet since this will allow more dust to be sucked in.
    HTH

  • New 7.01 Problem: iTunes locking up while scanning for "playback gaps."

    Anybody have any ideas on how to fix this? When I open iTunes, it immediately begins scanning for "playback gaps" and locks up after maybe 20-30 songs...and it does not consistently lock up on any one song it is scanning.
    This is most frustrating: the 7.01 upgrade has rendered iTunes non-functional.
    Any help would be appreciated.

    I USED to be able to get a playlist or two, I had gotten 5 GB of music back on it by putting 1-2 playlists on, ejecting, plugging back in, rinse, repeat. Now iTunes locked up AGAIN, checked the iPod, NO MUSIC. Really glad I bought this ******* piece of **** two years ago! Totally worth my money!
    Now, on top of all this, I find this in the help section.
    Symptoms
    You may notice the following symptoms on your Windows PC after installing the iCloud Control Panel, iTunes 10.5 or later, or Safari 5.1 or later:
    Apple software on Windows: May see performance issues and blank iTunes Store
    iTunes is slow to respond.
    Windows is slow to respond.
    iTunes stops responding when backing up or syncing with an iPhone, iPad, or iPod touch.
    Oh, so you mean that since you guys released 10.5, (and its now up to 10.6.??) people have had this issue of their iTunes not responding? What the ****. So basically since 10.5 people have had their iTunes not working correctly? Fix this crap.
    I already did the LSP check thing, only one besides the apple one are two windows ones that are up to date and should be there. There is no other help to be had. What a joke.

  • Retrying a particular failed Process Task for all the OIM Users

    Hi,
    We are using OIM 11.1.1. On a particular day one of the systems was unavailable hence all the process tasks for that system failed for a number of users. Is there any way of viewing all the failed process task and retrying them together, there are over 3000 users and it is not possible to go through them one by one.
    Any method either through the console or doing it programatically would be very helpful.
    Thanks in advance.
    UZ

    The OTI table has all the rejected task information. You can use it to link to user and resource instances through the OIU table as well.
    You can then take the SCH_KEY and then use code like this to process them:
    public void completeTask(){
    long[] task = new long[] {123123,3242134,23432,43534,34656,456456};
    int counter = 0;
    for (long key:task){
    try {
    counter++;
    provIntf.retryTask(key);
    System.out.println(counter + "|" + task.length);
    } catch (Exception e) {
    -Kevin

  • Event CREATED is not triggered for objects of type USER

    Dear all,
    I'm currently configuring a workflow, which should be started when new user account is created. I took event CREATE for object type USER as a start event, but the workflow does not start, when I create new user account via transaction code SU01. If I test workflow in SWUS, everything works fine. I checked the event trace, but it shows no records for events triggered when I use SU01 and create a user.
    Could you please advise how I can activate triggering of this event without using ABAP-developed event trigger?
    Thank you in advance.

    but here the requirement is to trigger workflow after the user account is created in the system.
    One more way to trigger a workflow is by the messages output. I mean when a user account is created successfully then a message will displayed on the screen let say User ABC created Successfully right so, when ever this message is raised then you can start the workflow by using this message. this can be done by using the txn SWUY
    1. Open SWUY txn.
    2. Click on Continue  and in the next screen give the area as the message class name from which the message is getting triggered and its number in the field Message and click on continue.
    3. Then it will open the PFTC txn mention the description and click on the workflow builder button and design the workflow as per you requirement.
    and once this is done , so when ever the message from the above mentioned message class is raised at that time your workflow will also be started.
    In this way I hope you can reduce your development time , searching for the right BADI or User exit and implementing the code and testing..
    Here in the above txn all you have to make sure that from which message class the message is getting displayed once the user is created successfully, I suggest you a way is you create a dummy user and once the dummy user is created succeffully system will display the message right?, so just double click on the message at the bottom of the screen this will let you knwo what is the message class and number it is using. and once you know tyr to approach the above steps....

  • SPS 18 Installation fails while asking for Java Crypthography Extension

    Hi @ all,
    some weeks ago we deployed the file "tc_sec_java_crypto_signed_fs_lib.sda by the SDM. But we didn´t enabled strong encryption in the portal.
    Now, i want to update my portalstack from SPS 14 to SPS 18 and while i update J2EE Sapinstaller asks for Java Crypthography Extension-Source-Code. But i don´t want to install it, because automatically the database is set to strong encryption and i can´t use / administrate in anymore.
    I still undeployed the IAEK-FS-File but the problem persists.
    I´m very pleasent for every answer.
    Best Regards
    Lars

    Hey,
    that´s fine Sascha.
    It works greatly. SPS 18 not asking für JCE anymore.
    The Installation is now running.
    Thx a lot!
    Greetingz
    Lars

  • Xerox workcentre 7225 print driver fails while searching for networked printer

    HelloJoe,Thanks - So I took those steps and the printer is created as a local printer using a TCP/IP port with the proper IP address for that printer. It appears I can get to its property pages. But when I try to print, the job goes to the queue and it just hangs eventually timing out and it shows error for printing that document... I can ping the IP adddress from the PC and it returns pings. ? 

    This unit is working fine from several other PCs, WIN 7 and WIN XP, in the building. Installing on a WIN7 64 bit PC. During the installation it starts to look for the networked printer and stops, posting the message -  [ Xerox windows common installer has stopped ] , then installer just hangs. I have uninstalled and tried the following versions with the same error -  Date: 2 Jun, 2014Version: 5.351.8.0.0Size: 17.7 MBFormat: EXEand tried  Global Print driver  Date: 15 Dec, 2014Version: 5.404.8.0Format: WWW NOTE - I even tried a manual driver installation which appears to work but the printer fails to print - returning a print error and cancels the job. Help,Jim  

  • Client blocks after a crash while registering for change notification

    Hi, I just moved this message from the Jdbc forum as being of more general interest, not limited to any Java client.
    I got a client crash since the JVM was short of heap space (the involved application was inserting data).
    Then I run the application again.
    Connection was ok, but then the client was blocked forever while waiting for a server reply (in a socket read) during the execution of a select intended to register a change notification listener.
    It seems that the crashed session left around something dirty in the server, concerning the change notification machinery. Perhaps some locks on concerned tables.
    Restarting the server solved the problem, although far from optimal.
    Server is 11gR2.
    Any suggestion to cleanup after such a crash is welcome, since so far I guessed that a terminated session (whether crashed or not) should have cleaned up locks and alike.

    since so far I guessed that a terminated session (whether crashed or not) should have cleaned up locks and alike.it is possible/probable that Oracle RDBMS does not know or care that the client crashed.
    It is likely that Oracle is waiting for additional requests from this client session.
    I doubt that any "clean up" has been performed.

Maybe you are looking for