ss-mppt-15l

[Marvin]

Can some one tell me what this log is saying on ss-mppt-15l. I loose communication every 30 minutes or so and when it comes back I get this log. Any help would be appreciated.

Dec 31 17:00:05 sysinit: killall: udhcpc: no process killed
Dec 31 17:00:08 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 31 17:00:08 kernel: Error garbage collecting node at 0040000c!
Dec 31 17:00:08 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 31 17:00:08 kernel: Error garbage collecting node at 0040000c!
Dec 31 17:00:08 kernel: No space for garbage collection. Aborting GC thread
Dec 31 17:00:08 sysinit: /usr/bin/set_model: line 279: can't create /www/Product.js: No space left on device
Dec 31 17:00:09 kernel: vtss_core: module license '(c) Vitesse Semiconductor Inc.' taints kernel.
Dec 31 17:00:09 kernel: switch: 'Luton26' board detected
Dec 31 17:00:11 kernel: vtss_port: Loaded port module on board Luton26, type 5
Dec 31 17:00:11 kernel: nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
Dec 31 17:00:11 system: Setting MAC address from flash configuration: EC:13:B2:E1:12:D0
Dec 31 17:00:12 kernel: i2c /dev entries driver
Dec 31 17:00:12 kernel: i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19
Dec 31 17:00:12 kernel: Argh. No free space left for GC. nr_erasing_blocks is 0. nr_free_blocks is 0. (erasableempty: yes, erasingempty: yes, erasependingempty: yes)
Dec 31 17:00:12 kernel: Error garbage collecting node at 0040000c!
Dec 31 17:00:12 sysinit: /etc/rc.common: eval: line 324: can't create /etc/config/wireless: No space left on device
Dec 31 17:00:12 sysinit: Loading defaults
Dec 31 17:00:13 sysinit: Adding custom chains
Dec 31 17:00:13 system: starting ntpclient
Dec 31 17:00:14 dhcp6c: starting dhcp6c
Dec 31 17:00:14 sysinit: Loading zones
Dec 31 17:00:14 dhcp6c: Using MAC address DUID 00:03:00:06:EC:13:B2:E1:12:D0
Dec 31 17:00:14 sysinit: Loading forwarding
Dec 31 17:00:14 sysinit: Loading redirects
Dec 31 17:00:14 sysinit: Loading rules
Dec 31 17:00:14 sysinit: Loading includes
Dec 31 17:00:14 admin: adding lan (eth0) to firewall zone lan
Dec 31 17:00:15 dropbear[645]: Running in background
Dec 31 17:00:16 netonix: 1.5.5 on WS-8-150-DC
Dec 31 17:00:19 UI: web config OK
Dec 31 17:00:19 syslogd exiting
Dec 31 17:00:20 syslogd started: BusyBox v1.19.4
Dec 31 17:00:23 kernel: Error garbage collecting node at 0040000c!
Dec 31 17:00:23 sysinit: Warning: file_put_contents(../etc/lighttpd.conf): failed to open stream: No space left on device in /www/config.php on line 1953
Dec 31 17:00:23 kernel: eth0: no IPv6 routers present
Dec 31 17:00:24 sysinit: 1969-12-31 17:00:23: (network.c.272) warning: please use server.use-ipv6 only for hostnames, not without server.bind / empty address; your config will break if the kernel default for IPV6_V6ONLY changes
Dec 31 17:00:24 sysinit: 1969-12-31 17:00:23: (network.c.272) warning: please use server.use-ipv6 only for hostnames, not without server.bind / empty address; your config will break if the kernel default for IPV6_V6ONLY changes
Dec 31 17:00:24 sysinit: 1969-12-31 17:00:23: (log.c.216) server started
Dec 31 17:00:25 kernel: vcoreiii_fdma_inj:4360 Assert failed: props->switch_frm || props->port_mask != 0
Dec 31 17:00:25 kernel: *** Failure:/home/dev/vtss_linuxbsp_4_48a/build_dir/linux-vcoreiii_lu26/kmod-vtss_switch/linux_support/kernel/vtss_switch-eth.c:212: vtss_fdma_inj(NULL, l, DMACH_TX, raw_frm_sz_bytes, &netinj_opts)
Dec 31 17:00:26 switch[785]: temp sensor version 3
Dec 31 17:00:27 switch[786]: Detected cold boot
Dec 31 17:00:28 switch[786]: PoE enabled on port 2, PoE Smart is starting cable check
Dec 31 17:00:28 switch[786]: PoE enabled on port 3, PoE Smart is starting cable check
Dec 31 17:00:30 system: starting ntpclient
Dec 31 17:00:33 switch[786]: Port 3 cable check results: Open, Open, Short, Short
Dec 31 17:00:33 switch[786]: Port 3 passed PoE Smart cable check, turning on power
Dec 31 17:00:33 switch[786]: Port 2 cable check results: Ok, Ok, Short, Short
Dec 31 17:00:33 switch[786]: Port 2 passed PoE Smart cable check, turning on power
Dec 31 17:00:36 Port: link state changed to 'up' (10M-F) on port 2
Dec 31 17:00:36 STP: msti 0 set port 2 to discarding
Dec 31 17:00:38 STP: msti 0 set port 2 to learning
Dec 31 17:00:38 STP: msti 0 set port 2 to forwarding
Dec 31 17:00:41 Port: link state changed to 'up' (100M-F) on port 3
Dec 31 17:00:41 STP: msti 0 set port 3 to discarding
Dec 31 17:00:43 system: starting ntpclient
Dec 31 17:00:44 STP: msti 0 set port 3 to learning
Dec 31 17:00:44 STP: msti 0 set port 3 to forwarding
Dec 31 17:00:56 system: starting ntpclient
Dec 31 17:01:00 Port: link state changed to 'down' on port 3
Dec 31 17:01:00 STP: msti 0 set port 3 to discarding
Dec 31 17:01:00 Port: link state changed to 'down' on port 2
Dec 31 17:01:00 STP: msti 0 set port 2 to discarding
Dec 31 17:01:01 Port: link state changed to 'up' (100M-F) on port 3
Dec 31 17:01:01 STP: msti 0 set port 3 to discarding
Dec 31 17:01:02 Port: link state changed to 'up' (100M-F) on port 2
Dec 31 17:01:02 STP: msti 0 set port 2 to discarding
Dec 31 17:01:04 STP: msti 0 set port 2 to learning
Dec 31 17:01:04 STP: msti 0 set port 2 to forwarding
Dec 31 17:01:04 STP: msti 0 set port 3 to learning
Dec 31 17:01:04 STP: msti 0 set port 3 to forwarding
Dec 31 17:01:10 system: starting ntpclient
Dec 31 17:01:23 system: starting ntpclient
Dec 31 17:01:36 system: starting ntpclient
Dec 31 17:01:38 STP: msti 0 set port 3 to discarding
Dec 31 17:01:39 STP: MSTI0: New root on port 3, root path cost is 240004, root bridge id is 32768.00-56-2B-0E-EC-A7
Dec 31 17:01:39 STP: msti 0 set port 3 to learning
Dec 31 17:01:39 STP: msti 0 set port 3 to forwarding
Dec 31 17:01:49 system: starting ntpclient
Jul 29 08:17:05 system: time set by NTP server

[Stephen]

It appears to be telling you that it's running out of usable memory. A lot of things could cause this, first thing to check though is to make sure it's not getting hacked. Is this device on a publicly accessible network? If it is, try using the Access Control List to isolate access.

Another possibility from reports revealed that a malfunctioning SFP module can quickly cause problems like this. If possible, try replacing them with known good ones to see if this issue stops (assuming you're using SFP modules) and for that matter other devices on the network that are malfunctioning and sending malformed packets have been known to do this as well. Although that is more rare.

Also there are still reports that the Discovery Protocol could be causing a memory leak. Try disabling it to see if it helps. I've never heard of it happening that quickly though which is why I suspect it's not this but it's worth knowing about.

[Marvin]

Thanks appreciate the help!