cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
356
Views
0
Helpful
1
Replies
gstefanidis
Beginner

IXM out of memory

After a year of operation the IXM started to act weird, currently i have no access and on console i get

 

i cannot ether login on prompt

82.611841] EXT4-fs error (device sda2): ext4_find_entry:1450: inode #2: comm rcS: reading directory lblock 0
[ 82.625340] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 16, inode_bitmap = 524289
[ 82.638671] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 17, inode_bitmap = 557057
[ 82.651956] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 18, inode_bitmap = 589825
[ 82.665237] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 19, inode_bitmap = 622593
[ 82.678515] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 20, inode_bitmap = 655361
[ 82.691794] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 21, inode_bitmap = 688129
[ 82.705072] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 0, inode_bitmap = 171
[ 82.718002] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 1, inode_bitmap = 32939
[ 82.731107] EXT4-fs error (device sda2): ext4_read_inode_bitmap:223: comm mkdir: Cannot read inode bitmap - block_group = 2, inode_bitmap = 65537

 

 

mkdir: can't create directory '/etc/ipsec.d/': No space left on device
/etc/init.d/S95wtmp: line 30: echo: write error: No space left on device
/etc/init.d/S95wtmp: line 31: echo: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
/etc/init.d/S96radio: line 19: echo: write error: No space left on device
/etc/init.d/S96radio: line 22: echo: write error: No space left on device
ls: /mnt/container/rootfs/tmp/mdm/pktfwd/firmware/: No such file or directory

1 REPLY 1
alexstev
Cisco Employee

A search of the Cisco Bug Search Tool (https://bst.cloudapps.cisco.com/bugsearch/) did not provide any relevant bugs. I was just looking at the latest Release Notes (https://www.cisco.com/c/en/us/td/docs/routers/interface-module-lorawan/software/release/notes/b_lorawan_rn_2_1_0_1.html#concept_cvn_sx5_kdb) and was wondering which Cisco LoRaWAN Gateway OS Image Version you're running. There don't appear to be any known issues similar to yours listed in this doc either.

Content for Community-Ad

This widget could not be displayed.