You have performed the action of archiving as figured below:
However, you notice the following message:
Dec 31 11:17:51 NMM-LGP1 tp_lgp: LOADER has exited normally with error status 1.
Dec 31 11:17:51 NMM-LGP1 snmptrapd: 11:17:51 TRAP6.TEXTPASS-LGP-MIB::loaderFailed TEXTPASS-GEN-MIB::deviceType.0 = STRING: "LGP" from localhost
Dec 31 11:17:57 NMM-LGP1 tp_lgp_collector: Collection failed from Node1: Get failed: 0 at /usr/TextPass/bin/tp_lgp_collector line 323.
Dec 31 11:17:57 NMM-LGP1 tp_lgp_collector: Collector failed on all nodes
Dec 31 11:17:57 NMM-LGP1 tp_lgp_collector: failed at nodes: Node1 Node2 Node3
Dec 31 11:17:58 NMM-LGP1 tp_lgp: COLLECTOR has exited with fatal error
Dec 31 11:17:58 NMM-LGP1 snmptrapd: 11:17:58 TRAP6.TEXTPASS-LGP-MIB::collectorFailed TEXTPASS-GEN-MIB::deviceType.0 = STRING: "LGP" from localhost
Dec 31 11:18:51 NMM-LGP1 tp_lgp: LOADER has parent pid 65441
These messages are not related to the archiving, they are related to the fact that the disk is full and LGP can't find sufficient place to collect new logs.
You should be able to see that these messages were there on the system before they perform the archiving, since the LGP disk became full. This should be resolved once space is available again on the disks. To get more information about this can be found in the Low Disk Space on LGP Servers KB Article.
Sometimes, it is convenient to apply actions like decreasing the archiving start period and use 3 months instead of 6, for example.