cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Level 7
Report Inappropriate Content
Message 1 of 3

McAfee crashing every ten seconds

This is repeating every ten seconds on at least a couple of new Macs (MBP and Mac Mini) with fresh installs of 10.10.3:

Jun  4 12:28:34 stone01 McAfee Reporter[15744]: Reporter : FMP exception in ReporterRegisterWithFMP: msg :: connect call failed

Jun  4 12:28:34 stone01 McAfee Reporter[15744]: Failed to register with FMP

Jun  4 12:28:34 stone01 Menulet[15746]: Menulet : Caught an Exception while Registering with FMP

Jun  4 12:28:34 stone01 Menulet[15746]: Failed to register with FMP

Jun  4 12:28:34 stone01 com.apple.xpc.launchd[1] (com.mcafee.menulet): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jun  4 12:28:35 stone01 com.apple.xpc.launchd[1] (com.mcafee.ssm.Eupdate): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jun  4 12:28:35 stone01 com.apple.xpc.launchd[1] (com.mcafee.reporter): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

Jun  4 12:28:35 stone01 com.apple.xpc.launchd[1] (com.mcafee.virusscan.fmpd[15748]): Service exited due to signal: Segmentation fault: 11

Jun  4 12:28:35 stone01 com.apple.xpc.launchd[1] (com.mcafee.virusscan.fmpd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jun  4 12:28:35 stone01 ReportCrash[15730]: Saved crash report for fmpd[15748] version ??? to /Library/Logs/DiagnosticReports/fmpd_2015-06-04-122835_stone01.crash

Jun  4 12:28:35 stone01 ReportCrash[15730]: Removing excessive log: file:///Library/Logs/DiagnosticReports/fmpd_2015-06-04-122512_stone01.crash

The crash log has:

Process:               fmpd [16142]

Path:                  /usr/local/McAfee/fmp/bin/fmpd

Identifier:            fmpd

Version:               ???

Code Type:             X86 (Native)

Parent Process:        launchd [1]

Responsible:           fmpd [16142]

User ID:               0

Date/Time:             2015-06-04 12:32:58.344 -0700

OS Version:            Mac OS X 10.10.3 (14D136)

Report Version:        11

Anonymous UUID:        F06741A3-44A0-8CF8-8CEA-951D735DAB8D

Time Awake Since Boot: 2400 seconds

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000064

VM Regions Near 0x64:

-->

    __TEXT                 00000000000b5000-0000000000166000 [  708K] r-x/rwx SM=COW  /usr/local/McAfee/fmp/bin/fmpd

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   libenterpriseagent.dylib       0x00422092 FMPEnterprise::FmpAgent::decryptBuffer(unsigned char const*, unsigned int, unsigned char**, unsigned int&, std::string) + 18

1   libfmpenterpriseplugin.dylib   0x003d5c2a FMPEnterprisePlugin::FMPEntAgentWrapper::decryptBuffer(unsigned char const*, unsigned int, unsigned char**, unsigned int&) + 90

2   libfmpenterpriseplugin.dylib   0x003db55f FMPEnterprisePlugin::FMPEntConfigController::loadConfigData() + 127

3   libfmpenterpriseplugin.dylib   0x003dadee FMPEnterprisePlugin::FMPEntConfigController::getInstance() + 158

4   fmpd                           0x0010c9a8 FMP::FMPController::FMPController() + 56

5   fmpd                           0x0010e7d5 FMP::FMPController::getInstance() + 197

6   fmpd                           0x001115be main + 206

7   fmpd                           0x000b9ef5 start + 53

Thread 0 crashed with X86 Thread State (32-bit):

  eax: 0x7a05a800  ebx: 0xbff47ad8  ecx: 0xbff47b7c  edx: 0x0000041c

  edi: 0x0042208e  esi: 0x00000000  ebp: 0xbff47aa8  esp: 0xbff47a80

   ss: 0x00000023  efl: 0x00010282  eip: 0x00422092   cs: 0x0000001b

   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f

  cr2: 0x00000064

 

Logical CPU:     0

Error Code:      0x00000004

Trap Number:     14

Binary Images:

   0xb5000 -   0x165ff3 +fmpd (???) <54123460-1F09-352E-BB26-6791F90599E6> /usr/local/McAfee/fmp/bin/fmpd

  0x1e0000 -   0x1e7ff3 +libfmputils.dylib (0) <3931DBC8-FD1E-343A-A313-A294D6F06247> /usr/local/McAfee/fmp/lib/libfmputils.dylib

  0x1f2000 -   0x216ffb +libfmphelpers.dylib (0) <13F09324-B824-3DE5-A03E-17F442832780> /usr/local/McAfee/fmp/lib/libfmphelpers.dylib

  0x22f000 -   0x233fff +libfmplicense.dylib (0) <140BD155-ACE5-309E-B4E1-EDCD9BE2F23C> /usr/local/McAfee/fmp/lib/libfmplicense.dylib

  0x23a000 -   0x264ff7 +libboost_serialization.dylib (0) <6FF80133-A28B-39D5-BF6A-4637847BAA2D> /usr/local/McAfee/fmp/lib/libboost_serialization.dylib

  0x2cd000 -   0x2eaffb +libboost_wserialization.dylib (0) <2079F8BC-750A-3430-B18E-E940A2BE2976> /usr/local/McAfee/fmp/lib/libboost_wserialization.dylib

  0x340000 -   0x344ffb +libboost_date_time.dylib (0) <BE2E474D-CC89-3E5C-A61A-934E916CCD38> /usr/local/McAfee/fmp/lib/libboost_date_time.dylib

  0x352000 -   0x364ff3 +libboost_filesystem.dylib (0) <7B91B435-1244-3EE8-B0B8-89F273846411> /usr/local/McAfee/fmp/lib/libboost_filesystem.dylib

  0x376000 -   0x379fff +libboost_system.dylib (0) <2C2B17DD-C71C-3F79-B9D9-641413E3A44E> /usr/local/McAfee/fmp/lib/libboost_system.dylib

  0x380000 -   0x382fff +libeventwriter.4.dylib (0) /Library/McAfee/*/libeventwriter.4.dylib

  0x389000 -   0x396ffb +libboost_thread.dylib (0) <45CFDE5F-22F7-300E-802F-7616409D0766> /usr/local/McAfee/fmp/lib/libboost_thread.dylib

  0x3c4000 -   0x3edfff +libfmpenterpriseplugin.dylib (0) <CD2F27BE-141E-3A45-A702-B1413F5C00BE> /usr/local/McAfee/fmp/lib/libfmpenterpriseplugin.dylib

  0x41c000 -   0x52fff7 +libenterpriseagent.dylib (0) <43A66C3E-DAAE-3CEE-B5E2-C7BF0F6E82E8> /usr/local/McAfee/fmp/lib/libenterpriseagent.dylib

0x8fe5d000 - 0x8fe90e03  dyld (353.2.1) <06B1254D-9BB9-327C-BA15-8F18FFF97586> /usr/lib/dyld

0x90261000 - 0x90263ffb  libsystem_secinit.dylib (18) <3CBA3BD3-8BA2-358D-BD1A-A1C3DF5D84E6> /usr/lib/system/libsystem_secinit.dylib

0x90264000 - 0x9045afff  libicucore.A.dylib (531.48) <A1002DA8-DAA9-30E8-95AE-1BF575AC5AB5> /usr/lib/libicucore.A.dylib

0x9045b000 - 0x9045cfff  libremovefile.dylib (35) <49DCAF7B-4466-3775-9E58-EA5D7CBA8AE0> /usr/lib/system/libremovefile.dylib

0x9045e000 - 0x904b4fff  libc++.1.dylib (120) <D8DE4962-66CD-3491-904E-9291EEE5E570> /usr/lib/libc++.1.dylib

0x91267000 - 0x9126cff7  libmacho.dylib (862) <48DE74F8-09E3-344F-A82F-665083A3BF8F> /usr/lib/system/libmacho.dylib

0x91e2c000 - 0x91e95ff7  libcorecrypto.dylib (233.1.2) <F188C1A7-E88F-3EC5-A6AA-22C02E3F0C93> /usr/lib/system/libcorecrypto.dylib

0x92176000 - 0x9219cff3  libxpc.dylib (559.20.9) <15931AC6-7282-332D-9A44-6CFF84AC63AF> /usr/lib/system/libxpc.dylib

0x92740000 - 0x92748fff  libsystem_dnssd.dylib (561.1.1) <45CDAF46-03DE-33DB-A627-14F245993EF2> /usr/lib/system/libsystem_dnssd.dylib

0x92749000 - 0x92750ff3  libunwind.dylib (35.3) <29D9343F-9A0A-3535-B0AE-E7CC761D95EE> /usr/lib/system/libunwind.dylib

0x92bc6000 - 0x92bc8fff  libsystem_coreservices.dylib (9) <20E66A47-8D67-344A-A393-73926F0E5FB2> /usr/lib/system/libsystem_coreservices.dylib

0x92f88000 - 0x92fc5fff  libsystem_network.dylib (412.20.3) <039F7709-8BFA-3299-8FD7-168145568642> /usr/lib/system/libsystem_network.dylib

0x92fd4000 - 0x92fd4fff  libunc.dylib (29) <CE960997-9D4A-3848-BAC7-B2255E6765FD> /usr/lib/system/libunc.dylib

0x93483000 - 0x93487ffb  libcache.dylib (69) <55501A00-AF64-3554-8F46-8D5AFEDEC332> /usr/lib/system/libcache.dylib

0x94320000 - 0x94322ff7  libquarantine.dylib (76.20.1) <8694AC5A-7359-3CC6-8E93-CABFCC919D4B> /usr/lib/system/libquarantine.dylib

0x94323000 - 0x94323fff  libkeymgr.dylib (28) <06DDCEF8-EB84-3F68-9E19-FD1A12B764FD> /usr/lib/system/libkeymgr.dylib

0x94324000 - 0x9434dfff  libsystem_info.dylib (459.20.1) <91DEA2CC-26A7-32CD-ABC5-0B2754874E38> /usr/lib/system/libsystem_info.dylib

0x9448f000 - 0x94495ff7  libsystem_trace.dylib (72.20.1) <5F23BE77-1C60-3859-B528-C6B3C184C95C> /usr/lib/system/libsystem_trace.dylib

0x9450a000 - 0x9450bfff  libsystem_blocks.dylib (65) <5D98F022-E863-31D4-8ADE-D53B2AE0D331> /usr/lib/system/libsystem_blocks.dylib

0x94691000 - 0x946aafff  libsystem_malloc.dylib (53.1.1) <58CD8BC7-55D1-3862-8E5D-728EE2EBE447> /usr/lib/system/libsystem_malloc.dylib

0x94781000 - 0x94786ff7  libcompiler_rt.dylib (35) <6630682F-AB76-3E55-BE51-0A3E61B6CFC2> /usr/lib/system/libcompiler_rt.dylib

0x950df000 - 0x9526eff3  libsqlite3.dylib (168) <C3F78985-C19B-3320-9F71-543969632128> /usr/lib/libsqlite3.dylib

0x95e2a000 - 0x95e2cfff  libsystem_configuration.dylib (699.1.5) <CC818B5B-D6A6-3313-A0FD-6F781B24DAD4> /usr/lib/system/libsystem_configuration.dylib

0x95e2d000 - 0x95e36fff  libcopyfile.dylib (118.1.2) <FAF3268F-C580-33D3-A5B4-74B8A8713216> /usr/lib/system/libcopyfile.dylib

0x95e37000 - 0x95e39fff  libsystem_sandbox.dylib (358.20.5) <FA3A0729-6839-38AC-B365-5E89A125F091> /usr/lib/system/libsystem_sandbox.dylib

0x95f61000 - 0x95f69fff  libsystem_pthread.dylib (105.10.1) <4A229519-29A1-3ABF-8CEF-43BCE4ACDA06> /usr/lib/system/libsystem_pthread.dylib

0x960f1000 - 0x96124fe3  libsystem_m.dylib (3086.1) <951F633F-57B7-398B-912F-F6ED4DB1C597> /usr/lib/system/libsystem_m.dylib

0x9680f000 - 0x96900ffb  libiconv.2.dylib (42) <4AF77F10-0BEC-3BE0-99DF-C5170EDB316B> /usr/lib/libiconv.2.dylib

0x96901000 - 0x96907ff7  libsystem_networkextension.dylib (167.1.10) <FC20E3AD-A53D-3346-AC71-829E82832AE8> /usr/lib/system/libsystem_networkextension.dylib

0x96dcc000 - 0x96debfff  libsystem_kernel.dylib (2782.20.48) <D1D17CE0-1D1D-3243-9E9D-78C70F19B0ED> /usr/lib/system/libsystem_kernel.dylib

0x96e6a000 - 0x96f60ff7  libxml2.2.dylib (26) <2F37833C-4D55-3A09-9A0C-5904E8B6892A> /usr/lib/libxml2.2.dylib

0x97b11000 - 0x97b1fff7  libz.1.dylib (55) <DF3B8F77-8931-3A6B-8BDF-DB67315050E6> /usr/lib/libz.1.dylib

0x97b20000 - 0x97b31fff  libsystem_coretls.dylib (35.20.2) <3688680D-90B5-373F-9E0D-46809E98B023> /usr/lib/system/libsystem_coretls.dylib

0x97e1a000 - 0x97e40ff3  libc++abi.dylib (125) <E9AF8CA1-D54D-37E3-8363-A3E8C0840F71> /usr/lib/libc++abi.dylib

0x98927000 - 0x9892dff3  libsystem_platform.dylib (63) <509993B7-3F26-3360-B899-0BBB15152516> /usr/lib/system/libsystem_platform.dylib

0x9892e000 - 0x989c3fff  libsystem_c.dylib (1044.10.1) <9804163C-4DEC-3B94-9854-00248E44554F> /usr/lib/system/libsystem_c.dylib

0x99e76000 - 0x99e77fff  libSystem.B.dylib (1213) <C45CC429-5DE4-3B01-8450-B3BD1AA03C3F> /usr/lib/libSystem.B.dylib

0x99ff2000 - 0x9a009fff  libsystem_asl.dylib (267) <85BD88AD-618E-3325-AC31-10DBAB8E9AF3> /usr/lib/system/libsystem_asl.dylib

0x9a02b000 - 0x9a037ff3  libcommonCrypto.dylib (60061) <024B3913-15C6-3005-9E5A-EB24918F6977> /usr/lib/system/libcommonCrypto.dylib

0x9a038000 - 0x9a038fff  liblaunch.dylib (559.20.9) <A0885899-CDE9-3688-8C3C-B583E24090E0> /usr/lib/system/liblaunch.dylib

0x9a493000 - 0x9a4bafff  libdispatch.dylib (442.1.4) <B26A176C-39F7-3362-B128-27B1211068B9> /usr/lib/system/libdispatch.dylib

0x9a5bd000 - 0x9a5c0fff  libdyld.dylib (353.2.1) <30CE0D0E-7E82-3CD5-92E7-9C1D6AD3327C> /usr/lib/system/libdyld.dylib

0x9a5c1000 - 0x9a5caff7  libsystem_notify.dylib (133.1.1) <B8503E99-214B-3AC3-A7CA-CC837ABD7B25> /usr/lib/system/libsystem_notify.dylib

0x9a6f1000 - 0x9a744fff  libstdc++.6.dylib (104.1) <D0EB2C99-5939-3ABA-9C18-D9AD75CE23A1> /usr/lib/libstdc++.6.dylib

External Modification Summary:

  Calls made by other processes targeting this process:

    task_for_pid: 0

    thread_create: 0

    thread_set_state: 0

  Calls made by this process:

    task_for_pid: 0

    thread_create: 0

    thread_set_state: 0

  Calls made by all processes on this machine:

    task_for_pid: 3233

    thread_create: 0

    thread_set_state: 0

VM Region Summary:

ReadOnly portion of Libraries: Total=55.6M resident=9.8M(18%) swapped_out_or_unallocated=45.8M(82%)

Writable regions: Total=17.4M written=88K(0%) resident=288K(2%) swapped_out=0K(0%) unallocated=17.1M(98%)

REGION TYPE                      VIRTUAL

===========                      =======

Kernel Alloc Once                     4K

MALLOC                             9316K

MALLOC (admin)                       16K

Stack                              64.0M

VM_ALLOCATE                           8K

__DATA                              692K

__IMPORT                              4K

__LINKEDIT                         43.7M

__OBJC                                4K

__TEXT                             11.9M

mapped file                       204.9M

shared memory                         4K

===========                      =======

TOTAL                             334.4M

2 Replies
Highlighted
Level 9
Report Inappropriate Content
Message 2 of 3

Re: McAfee crashing every ten seconds

What version are you running?

I have the same OS, running EPM 2.2.0 (1298), CMA 4.8.0.1938.

I noticed there is a MER tool located in: /usr/local/McAfee/fmp/bin/FMPMertool

Can you run it and see if anything else pops out that might lead to the cause?

Highlighted
Level 7
Report Inappropriate Content
Message 3 of 3

Re: McAfee crashing every ten seconds

1FMP

1.1FMP database

[sqlite3 /usr/local/McAfee/fmp/var/FMP.db select i_msgId,i_msgTime,i_msg from fmpDataLog;]

1|2015-Apr-22 10:23:32|FMPController Started

2|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

3|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

4|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

5|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

6|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

7|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

8|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

9|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

10|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

11|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

12|2015-Apr-22 10:24:19|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

13|2015-Apr-22 10:24:54|FMPController Started

14|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

15|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

16|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

17|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

18|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

19|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

20|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

21|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

22|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

23|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

24|2015-Apr-22 10:25:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

25|2015-Apr-22 10:46:47|FMPController Started

26|2015-Apr-22 10:46:56|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

27|2015-Apr-22 10:46:56|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

28|2015-Apr-22 10:46:56|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

29|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

30|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

31|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

32|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

33|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

34|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

35|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

36|2015-Apr-22 10:46:57|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

37|2015-Apr-22 11:01:42|FMPController Started

38|2015-Apr-22 11:01:44|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

39|2015-Apr-22 11:01:44|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

40|2015-Apr-22 11:01:44|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

41|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

42|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

43|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

44|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

45|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

46|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

47|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

48|2015-Apr-22 11:01:45|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

49|2015-Apr-22 12:54:05|FMPController Started

50|2015-Apr-22 15:38:15|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

51|2015-Apr-22 15:38:15|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

52|2015-Apr-22 15:38:15|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

53|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

54|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

55|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

56|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

57|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

58|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

59|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

60|2015-Apr-22 15:38:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

61|2015-Apr-22 15:39:27|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

62|2015-Apr-22 15:39:27|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

63|2015-Apr-22 15:39:27|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

64|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

65|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

66|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

67|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

68|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

69|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

70|2015-Apr-22 15:39:28|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

71|2015-Apr-22 15:39:29|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

72|2015-Apr-22 17:13:22|FMPController Started

73|2015-Apr-23 07:09:23|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

74|2015-Apr-23 07:09:23|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

75|2015-Apr-23 07:09:23|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

76|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

77|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

78|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

79|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

80|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

81|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

82|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

83|2015-Apr-23 07:09:25|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

84|2015-Apr-23 07:46:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

85|2015-Apr-23 07:46:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

86|2015-Apr-23 07:46:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

87|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

88|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

89|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

90|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

91|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

92|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

93|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

94|2015-Apr-23 07:46:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

95|2015-Apr-23 09:43:24|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

96|2015-Apr-23 09:43:24|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

97|2015-Apr-23 09:43:24|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

98|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

99|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

100|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

101|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

102|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

103|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

104|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

105|2015-Apr-23 09:43:26|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

106|2015-Apr-23 09:54:45|FMPController Started

107|2015-Apr-23 09:57:16|FMPController Started

108|2015-Apr-23 10:05:07|FMPController Started

109|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

110|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

111|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

112|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

113|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

114|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

115|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

116|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

117|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

118|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

119|2015-Apr-23 10:07:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

120|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

121|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

122|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

123|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

124|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

125|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

126|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

127|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

128|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

129|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

130|2015-Apr-23 10:08:34|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

131|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

132|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

133|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

134|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

135|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

136|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

137|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

138|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

139|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

140|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

141|2015-Apr-23 14:40:31|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

142|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

143|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

144|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

145|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

146|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

147|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

148|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

149|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

150|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

151|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

152|2015-Apr-23 14:45:03|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

153|2015-Apr-23 19:16:11|FMPController Started

154|2015-Apr-23 19:16:36|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

155|2015-Apr-23 19:16:36|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

156|2015-Apr-23 19:16:36|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

157|2015-Apr-23 19:16:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

158|2015-Apr-23 19:16:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

159|2015-Apr-23 19:16:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

160|2015-Apr-23 19:16:37|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

161|2015-Apr-23 19:16:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

162|2015-Apr-23 19:16:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

163|2015-Apr-23 19:16:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

164|2015-Apr-23 19:16:38|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

165|2015-May-04 07:35:40|FMPController Started

166|2015-May-04 07:44:15|FMPController Started

167|2015-May-04 10:31:24|FMPController Started

168|2015-May-04 10:38:25|FMPController Started

169|2015-May-04 10:39:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

170|2015-May-04 10:39:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

171|2015-May-04 10:39:16|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

172|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

173|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

174|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

175|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

176|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

177|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

178|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

179|2015-May-04 10:39:17|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

180|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

181|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

182|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

183|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

184|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

185|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

186|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

187|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

188|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

189|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

190|2015-May-05 07:37:41|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

191|2015-May-11 06:41:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

192|2015-May-11 06:41:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

193|2015-May-11 06:41:59|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

194|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

195|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

196|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

197|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

198|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

199|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

200|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 101

201|2015-May-11 06:42:00|EventManager::handleFMMessage - Got a EVENT_REGISTRATION message from 102

[sqlite3 /usr/local/McAfee/fmp/var/FMP.db select i_msgId,i_repTime,i_repFM,i_repBriefMsg,i_repDetailMsg from reports;]

1|2015-Apr-22 10:26:33|2|22 serialization::archive 9 0 0 4294967295 18 HE_ThreatLabUpdate 9 HE_Update 1429723593 2|22 serialization::archive 9 0 0 9 HE_Update 0 0 3 0 0 0 19 HE_UpdateDatVersion 9 7586.0000 22 HE_UpdateEngineVersion 9 5700.7163 15 HE_UpdateStatus 15 HE_UpdateFailed 0 0 2 0 8 Progress 34 Unable to find a valid repository. 8 Progress 22 Update process failed. 1429723593 2

2|2015-Apr-22 16:46:32|2|22 serialization::archive 9 0 0 4294967295 18 HE_ThreatLabUpdate 9 HE_Update 1429746392 2|22 serialization::archive 9 0 0 9 HE_Update 0 0 3 0 0 0 19 HE_UpdateDatVersion 9 7586.0000 22 HE_UpdateEngineVersion 9 5700.7163 15 HE_UpdateStatus 15 HE_UpdateFailed 0 0 2 0 8 Progress 34 Unable to find a valid repository. 8 Progress 22 Update process failed. 1429746392 2

3|2015-May-04 16:46:07|2|22 serialization::archive 9 0 0 4294967295 18 HE_ThreatLabUpdate 9 HE_Update 1430783167 2|22 serialization::archive 9 0 0 9 HE_Update 0 0 3 0 0 0 19 HE_UpdateDatVersion 9 7791.0000 22 HE_UpdateEngineVersion 9 5700.7163 15 HE_UpdateStatus 19 HE_UpdateSuccessful 0 0 0 0 1430783167 2

4|2015-May-05 16:45:37|2|22 serialization::archive 9 0 0 4294967295 18 HE_ThreatLabUpdate 9 HE_Update 1430869537 2|22 serialization::archive 9 0 0 9 HE_Update 0 0 3 0 0 0 19 HE_UpdateDatVersion 9 7792.0000 22 HE_UpdateEngineVersion 9 5700.7163 15 HE_UpdateStatus 19 HE_UpdateSuccessful 0 0 0 0 1430869537 2

5|2015-May-06 16:46:18|2|22 serialization::archive 9 0 0 4294967295 18 HE_ThreatLabUpdate 9 HE_Update 1430955937 2|22 serialization::archive 9 0 0 9 HE_Update 0 0 3 0 0 0 19 HE_UpdateDatVersion 9 7793.0000 22 HE_UpdateEngineVersion 9 5700.7163 15 HE_UpdateStatus 19 HE_UpdateSuccessful 0 0 0 0 1430955937 2

1.2FMP log

~ ~

usage: basename string [suffix]

       basename [-a] [-s suffix] string [...]

~

Completed generating FMP diagnostic report.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community