Page 2 of 2

Re: v1.5.16 Bug Reports and Comments

Posted: Wed May 29, 2024 2:09 am
by bipbaep
Yes, it has only tagged VLANs, and no untagged. About 20 VLANs in total.

Re: v1.5.16 Bug Reports and Comments

Posted: Wed Jun 19, 2024 11:12 am
by mnitech
A little gun-shy after 1.5.15 but did one of my test units this morning to 1.5.16.

Re: v1.5.16 Bug Reports and Comments

Posted: Sun Jul 07, 2024 8:53 pm
by oeyre
We upgraded 3 units overnight and will see how it goes for a few weeks before doing the rest of the network.

Re: v1.5.16 Bug Reports and Comments

Posted: Sun Jul 21, 2024 10:35 pm
by picasso
Watchdog timer fails to bounce the port, it reports the below....BUT what is latitude : X? It should read "watchdog triggered on port 2, action is Bounce Power" that is what the other switches report why does this one note latitude and fail to bounce port?

Jul 20 05:35:56 switch[1760]: Watchdog '5XHD-MTR2TDC' failure checking 10.11.0.232, watchdog triggered on port 2 (5XHD-MTR2TDC), action is Bounce Power switch latitude: x


EDIT: I think having - in the port name might be trigging bad things to happen with the watchdog. Removed it for testing.

Re: v1.5.16 Bug Reports and Comments

Posted: Mon Aug 05, 2024 10:34 am
by oeyre
oeyre wrote:We upgraded 3 units overnight and will see how it goes for a few weeks before doing the rest of the network.

It's been a few weeks now of our limited trial upgrading from 1.5.8 to 1.5.16, what has everyone's experience been like?

While we can't fault the software for day to day operations we are seeing that the memory used keeps going up. Is this normal/expected? Do we have a memory leak or is this just linux doing what it does and keeping everything in memory until it has to let go?

Screenshot: https://ibb.co/YPyZy2B