Support Center > Search Results > SecureKnowledge Details
FWM process cannot start due to the size of $FWDIR/tmp/fwmtrace.log file reaching 2GB limit
Symptoms
  • FWM daemon crashes with core dump files, although they are empty.

  • Size of $FWDIR/tmp/fwmtrace.log file is 2GB.

  • STRACE output when attached to the FWM daemon while its starting:

    open("/opt/CPsuite-R77/fw1/tmp/fwmtrace.log", O_WRONLY|O_APPEND|O_CREAT, 0666) = 74
    fstat64(74, {st_mode=S_IFREG|0664, st_size=2147483647, ...}) = 0
    mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x73bbc000
    fstat64(74, {st_mode=S_IFREG|0664, st_size=2147483647, ...}) = 0
    _llseek(74, 2147483647, [2147483647], SEEK_SET) = 0
    write(74, "mgmtha: 089 18:03:04 - CSlavePro"..., 46) = -1 EFBIG (File too large)
    --- SIGXFSZ (File size limit exceeded) ---
    +++ killed by SIGXFSZ +++
    
Cause

Every IPS update attempt is writing new data into the $FWDIR/tmp/fwmtrace.log file, and every action that occurs during the update itself gets written into the $FWDIR/tmp/fwmtrace.log file / $MDS_TEMPLATE/tmp/fwmtrace.log file until it reaches its limit (2GB).

If the size of the fwmtrace.log file has already reached its limit (2GB):

  • the FWM daemon would be able to start (Issue ID 01626339)
  • the FWM daemon would crash when it tries to write to this file (Issue ID 01960960)

Solution
Note: To view this solution you need to Sign In .