Switching

last person joined: 23 hours ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  Ex4200 init: write failed: No space left on device

    Posted 09-25-2011 21:00

    Two ex4200 switches connected in a virtual chassis, both running 10.1R1.8

     

    Every time I try to save my config it gives me this:

     

    There were error(s) delivering the configuration.
    Error(s): 1) init: write failed: No space left on device

    2) commit failed: daemon file propagation failed

    3) remote commit-configuration failed on fpc1

    4) commit failed

     

    I know of the bug in this OS release but that isn't the problem here, the pfed log is at 0K.  

     

    Here is the output for show system storage:

     

    root@ex4200Server01> show system storage no-forwarding
    
    Filesystem              Size       Used      Avail  Capacity   Mounted on
    /dev/da0s1a             184M       110M        59M       65%  /
    devfs                   1.0K       1.0K         0B      100%  /dev
    /dev/md0                 34M        34M         0B      100%  /packages/mnt/jbase
    /dev/md1                 17M        17M         0B      100%  /packages/mnt/jcrypto-ex-10.1R1.8
    /dev/md2                5.7M       5.7M         0B      100%  /packages/mnt/jdocs-ex-10.1R1.8
    /dev/md3                130M       130M         0B      100%  /packages/mnt/jkernel-ex-10.1R1.8
    /dev/md4                 19M        19M         0B      100%  /packages/mnt/jpfe-ex42x-10.1R1.8
    /dev/md5                 44M        44M         0B      100%  /packages/mnt/jroute-ex-10.1R1.8
    /dev/md6                 23M        23M         0B      100%  /packages/mnt/jswitch-ex-10.1R1.8
    /dev/md7                 21M        21M         0B      100%  /packages/mnt/jweb-ex-10.1R1.8
    /dev/md8                126M      10.0K       116M        0%  /tmp
    /dev/da0s1f             123M       2.0M       111M        2%  /var
    /dev/da0s3d             314M        66K       289M        0%  /var/tmp
    /dev/da0s3e              55M       108K        51M        0%  /config
    /dev/md9                118M        12M        97M       11%  /var/rundb
    procfs                  4.0K       4.0K         0B      100%  /proc
    /var/jail/etc           123M       2.0M       111M        2%  /packages/mnt/jweb-ex-10.1R1.8/jail/var/etc
    /var/jail/run           123M       2.0M       111M        2%  /packages/mnt/jweb-ex-10.1R1.8/jail/var/run
    /var/jail/tmp           123M       2.0M       111M        2%  /packages/mnt/jweb-ex-10.1R1.8/jail/var/tmp
    /var/tmp                314M        66K       289M        0%  /packages/mnt/jweb-ex-10.1R1.8/jail/var/tmp/uploads
    devfs                   1.0K       1.0K         0B      100%  /packages/mnt/jweb-ex-10.1R1.8/jail/dev

     

    I am at a loss since there seems to be space left.  The error mentions fpc1, is that referring to the second member of the virtual chassis?  If that is the case, is that the drive that's full?  How would I clear info off of that one?  The reason I ask is once I "married" the two switched in the VC I could no longer connect to the management port on the second switch.  Is there another way I could get into it?  Assuming, of course, that I am correct in my assumption.

     

    Any help here would be had.



  • 2.  RE: Ex4200 init: write failed: No space left on device

    Posted 09-25-2011 22:50

    Hi dmaher804, 

     

    Maybe this could be your issue.

    http://kb.juniper.net/InfoCenter/index?page=content&id=KB16810

    For recommended releases see http://kb.juniper.net/InfoCenter/index?page=content&id=KB21476

     

    Jozef



  • 3.  RE: Ex4200 init: write failed: No space left on device

    Posted 09-26-2011 13:33

    The only issue is when I check the size of the size of the logs is '0'

    root@ex4200Server01:RE:0% ls -al | grep pfe
    -rw-r--r--   1 root  wheel       0 Jul 20 05:52 pfed_event_trace.log
    -rw-r--r--   1 root  wheel       0 Feb 13  2010 pfed_trace.log
    root@ex4200Server01:RE:0%

     

    Is it possible the other member of the virtual chassis is the one out of space?  If so, how to I delete files off of that particular member?



  • 4.  RE: Ex4200 init: write failed: No space left on device



  • 5.  RE: Ex4200 init: write failed: No space left on device

    Posted 09-27-2011 10:43

    Thank you Smiley Happy