Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX] Commit issue: “error: could not open /var/etc/pam.conf+: Operation not permitted" and "foreign file propagation failed during preprocessing”

1

0

Article ID: KB32493 KB Last Updated: 23 Apr 2020Version: 2.0
Summary:

This article provides information on how to clear the commit errors:

error: could not open /var/etc/pam.conf+: Operation not permitted
error: commit failed: foreign file propagation failed during preprocessing
Symptoms:
  1. Commit fails with the following error message:
    root# commit
    error: could not open /var/etc/pam.conf+: Operation not permitted
    error: commit failed: foreign file propagation failed during preprocessing
  2. The following log messages may be reported on the EX4300 during the commit issue:
    Oct 20 12:53:00   pfex: sflow socket connect failed (socket closed)
    
    Oct 20 12:53:00   fpc0 sflow socket connect failed (socket closed)
    Oct 20 12:53:00   authd[925]: LICENSE_SOCKET_FAILURE: 'evConnect' failed for socket 22:
Cause:
  1. Permission is missing in the authentication file.
  2. File corruption with pam.conf or pam.conf+ file.
Solution:

To fix this issue, full permission needs to be given to the password authentication management file:

  1. Start the shell as user root
    root> start shell
    root%
  2. Issue the following command to check the permissions:
    root% ls -lo /var/etc/pam
    -rw-------  1 root  wheel  - 203 Feb 14  2017 /var/etc/pam.conf
  3. Issue the following command to change the permissions:
    root% chflags 0 /var/etc/pam.conf+
    root% chmod 777 /var/etc/pam.conf
  4. Check the commit result. The log messages will not be reported with the commit.
    {master:0}[edit]
    root@co# commit full
    configuration check succeeds
    commit complete

    Note: If the above command does not work, then format install the switch to fix this issue.

Modification History:
2020-04-23: Updated formatting to correct overlapping text.

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search