The Layer 2 Tunneling Protocol process (l2tpd) could not create a context for handling asynchronous events.
The L2TPD_EVLIB_CREATE_FAILED message is logged each time l2tpd cannot create a context for handling asynchronous events.
When during its initialization l2tpd is unable to create the context for handling asynchronous events, the system will log a syslog message beginning with L2TPD_EVLIB_CREATE_FAILED.
The cause may be due to an internal software error.
Examine the following output to help determine the cause of this message:
user@router> show log l2tpd
user@router> show log messages
Look for any related events that occurred at or just before the L2TPD_EVLIB_CREATE_FAILED message.
If the cause is not yet clear and network status allows it, enable the l2tp traceoptions via the configuration CLI with the following steps:
user@router # set services l2tp traceoptions file l2tp.log
user@router # set services l2tp traceoptions flag init
user@router # set services l2tp traceoptions flag event
user@router # set services l2tp traceoptions flag states
user@router # commit and-quit
Restart the l2tp service:
user@router> restart l2tp-service
Examine the output of the following command to help determine the cause of the message:
user@router> show log l2tp.log
When done the above, disable the l2tp traceoptions by deleting the added configuration.