Junos OS

Expand all | Collapse all

There were error(s) delivering the configuration.

  • 1.  There were error(s) delivering the configuration.

    Posted 04-12-2015 16:23

    We recently upgraded from JunOS 10.4 to JunOS 12.3. The upgrade completed without issue.

     

    When commiting the switch configuration in J-Web, we get the following error -

     

    There were error(s) delivering the configuration.

    Error(s):
    1) rename failed for /var/etc/pam.conf

     

    I'm not seeing much on this error when doing a Google search, so any assistance offered would be much appreciated.

     

    Thanks!

     

     



  • 2.  RE: There were error(s) delivering the configuration.

    Posted 04-23-2015 05:00

    Hi,

     

    Were you able to figure out the solution for this?

     

    Regards,

    Wojciech



  • 3.  RE: There were error(s) delivering the configuration.

     
    Posted 04-23-2015 05:20

    Hi ,

     

    This is a bug reported on EX Switch for version 12.3  . Please open a JTAC ticket  for furthur analysis .



  • 4.  RE: There were error(s) delivering the configuration.

    Posted 04-23-2015 06:08

    Hi Sam,

     

    If that's a known bug there is no point in involving JTAC. Can you share PR number for that?


    Regards,

    Wojciech



  • 5.  RE: There were error(s) delivering the configuration.

     
    Posted 04-23-2015 06:11

    Hi ,

     

    Its a Engineering PR which is confidential . So I hope you will not be able to see the PR externally .

     

    But as per the PR its resolved in  14.1X53-D15 14.2R1 15.1R1.



  • 6.  RE: There were error(s) delivering the configuration.

    Posted 04-23-2015 06:15

    Hi Sam,

     

    Is there any workaround that I can use in 12.3?

     

    Regards,

    Wojciech



  • 7.  RE: There were error(s) delivering the configuration.

    Posted 04-23-2015 06:18

    JTAC pointed me to the following, which resolved the issue in 12.3

     

    Start shell user root

    ls -lo /var/etc/pam.conf
    chflags 0 /var/etc/pam.conf
    ls -lo /var/etc/pam.conf



  • 8.  RE: There were error(s) delivering the configuration.

    Posted 04-23-2015 06:20

    Thanks!

     

    Wojciech



  • 9.  RE: There were error(s) delivering the configuration.

     
    Posted 04-23-2015 22:12

    as @StreamingGeek point out that is a workaround that is working!



  • 10.  RE: There were error(s) delivering the configuration.

    Posted 08-26-2015 12:28

    I did a "chmod 777 /var/etc/pam.conf" and "chflags 0 /var/etc/pam.conf" - that seemed to work

     



  • 11.  RE: There were error(s) delivering the configuration.

    Posted 10-06-2015 07:42

    This worked for me.  you need to do this on each member in the stack by using the "request session member 0"

     

    request session member 0
    start shell
    su root
    chflags 0 /var/etc/pam.conf
    exit
    exit

    request session member 1
    start shell
    su root
    chflags 0 /var/etc/pam.conf
    exit
    exit

    request session member 2
    start shell
    su root
    chflags 0 /var/etc/pam.conf
    exit
    exit
    commit



  • 12.  RE: There were error(s) delivering the configuration.

     
    Posted 10-19-2015 02:18

    Big thanks to @StreamingGeek for posting the workaround - just hit this during a cut-over - saved me much grief!



  • 13.  RE: There were error(s) delivering the configuration.

    Posted 01-31-2017 09:41

    Thank you twood@bma.org.uk, running "chflags 0" on each of the stack members resolved this for me! Running a 3-switch stack of EX4200s with recommended-until-recently 12.3R8.7



  • 14.  RE: There were error(s) delivering the configuration.

    Posted 05-07-2018 05:12

    this workaround works. Thanks



  • 15.  RE: There were error(s) delivering the configuration.

     
    Posted 04-23-2015 06:19

    Hi ,

     

    Unfortunately there is no work around .



  • 16.  RE: There were error(s) delivering the configuration.

    Posted 05-09-2016 09:29

    i am seeing the same issue qfx5100. is there a PR for this bug yet ? does settting the flag on the file to 0 fix the issue ? what is the impact for this ? cosmetic ?



  • 17.  RE: There were error(s) delivering the configuration.

    Posted 07-18-2016 09:27

    Something has caused special file flags to be set on the file. The reason beind that change cound be a few things and I won't go into it, but you can clear it manually.

     

    1) Login to the stack as root

    2) start the cli and session into the affected member (if not the current master)

    3) Check the flags:

    root@sw01-access-10g-1b-b13:LC:2% ls -oal *.conf
    -rw-r--r--  1 root  wheel  -            100 Jul 18 16:15 bootpd.conf
    -rw-r--r--  1 root  wheel  -             98 Jul 18 16:15 cosd.conf
    -rw-r--r--  1 root  wheel  -           3943 Jul 18 16:15 ifinfo.conf
    -rw-r--r--  1 root  wheel  -              0 Jul 18 16:15 ifmdata.conf
    -rw-r--r--  1 root  wheel  -            929 Jul 18 16:15 inetd.conf
    -rw-------  1 root  wheel  -              0 Jul 18 16:15 keyadmin.conf
    -rw-r--r--  1 root  wheel  -           3637 Jul 18 16:15 login.conf
    -rw-r--r--  1 root  wheel  -              0 Jul 18 16:15 named.conf
    -rw-r-----  1 root  wheel  -            170 Jul 18 16:15 newsyslog.conf
    -rw-r--r--  1 root  wheel  -             65 Jul 18 16:15 ntp.conf
    -rw-r-----  1 root  wheel  schg,sunlnk  548 Apr 14  2015 pam.conf
    -rw-------  1 root  wheel  -              0 Jul 18 16:15 pam_radius.conf
    -rw-------  1 root  wheel  -            152 Jul 18 16:15 pam_tacplus.conf
    -rw-r--r--  1 root  wheel  -             18 Jul 18 16:15 resolv.conf
    -rw-r--r--  1 root  wheel  -            695 Jun 29 19:10 syslog.conf
    root@sw01-access-10g-1b-b13:LC:2%
    

    4) clear the flags on the affected file and verify they have been cleared:

    root@sw01-access-10g-1b-b13:LC:2% chflags 0 pam.conf
    root@sw01-access-10g-1b-b13:LC:2% ls -oal *.conf
    -rw-r--r--  1 root  wheel  -  100 Jul 18 16:15 bootpd.conf
    -rw-r--r--  1 root  wheel  -   98 Jul 18 16:15 cosd.conf
    -rw-r--r--  1 root  wheel  - 3943 Jul 18 16:15 ifinfo.conf
    -rw-r--r--  1 root  wheel  -    0 Jul 18 16:15 ifmdata.conf
    -rw-r--r--  1 root  wheel  -  929 Jul 18 16:15 inetd.conf
    -rw-------  1 root  wheel  -    0 Jul 18 16:15 keyadmin.conf
    -rw-r--r--  1 root  wheel  - 3637 Jul 18 16:15 login.conf
    -rw-r--r--  1 root  wheel  -    0 Jul 18 16:15 named.conf
    -rw-r-----  1 root  wheel  -  170 Jul 18 16:15 newsyslog.conf
    -rw-r--r--  1 root  wheel  -   65 Jul 18 16:15 ntp.conf
    -rw-r-----  1 root  wheel  -  548 Apr 14  2015 pam.conf
    -rw-------  1 root  wheel  -    0 Jul 18 16:15 pam_radius.conf
    -rw-------  1 root  wheel  -  152 Jul 18 16:15 pam_tacplus.conf
    -rw-r--r--  1 root  wheel  -   18 Jul 18 16:15 resolv.conf
    -rw-r--r--  1 root  wheel  -  695 Jun 29 19:10 syslog.conf
    root@sw01-access-10g-1b-b13:LC:2%

    5) Exit to the stack master and execut a commit full and quit.