This article describes the syslog message GENCFG: op 2 (Gencfg Blob) failed
This message is informational only and does not indicate an error condition.
When a GENCFG: op 2 (Gencfg Blob) failed event occurs, a message similar to the following is reported:
(FPC Slot 7, PIC Slot 0) kernel: GENCFG: op 2 (Gencfg Blob) failed; err 5 (Invalid)
/kernel: GENCFG: op 2 (Gencfg Blob) failed; err 7 (Doesn't Exist)
The messages are informational only and do not impact device performance. The kernel generates this message because it does not have a handler for a certain gencfg blob message. This is because the actual event handler is done elsewhere in Junos.
Perform these steps to determine the cause and resolve the problem (if any):
1. Collect the show command output to help determine the cause of this message.
Capture the output to a file (in case you have to open a technical support case). To do this, configure each SSH client/terminal emulator to log your session.
show log messages
show log escript.log
2. Analyze the show command output. Look for any related events that occurred at or just before the GENCFG: op 2 (Gencfg Blob) failed message.
If the message occurs sporadically, or as part of a commit being done, this is normal and the message can safely be ignored. Otherwise, continue with the next step.
3. During a maintenance window, as it will impact transit traffic, try rebooting the router.