v1.5.26 Bug Reports and Comments

[jfrawley]

I found that NTP does not work when unit is loaded with a backup config file, do not recall if this happens from scratch build, after the unit is booted I have to disable NTP and then re-enable it. I also had an issue yesterday with SNMP, the boxes were populated by our tech, I found some typos in them, corrected the typos but our collector was not able to poll data from the unit- after disabling and enabling the SNMP service then it was working properly.

The NTP issue so far has been on multiple switches (primarily the WS-12-250-DC), I have yet to have one successfully work after a bootup- it always requires disable and enable. The backup configs were also used from the same FW version that was on the new switch and it also behaved this way with pre- 1.5.26 FW to a new switch with 1.5.26.

Not a major problem, but if I want to have accurate log files, I find myself needing to check status of NTP each time I am in a switch. This was never an issue PRE- 1.5.26 but I am not certain on which FW release this started.

[jfrawley]

NTP: We started seeing it as of 1.5.25 - however we have primarily gone from 1.5.14 to 1.5.25
I don't see it listed as a bug or fix on 1.5.26 either:
A lot of our upgraded WS series no longer get NTP updates. Initially this was when Mikrotiks were the NTP server, however we have also noticed several on 1.5.25 also not getting NTP updates from x.*countrycode*.pool.ntp.org.
Has anyone else struck this?

I have same issue, disable and enable NTP in the switch and it will work- at least for me. I also just reported this bug

[RTGLW]

Hi team. Just noting another oddity we've run into. We upgraded 2x WS-8-150-DC switches from 1.5.25 to 1.5.26 for testing and both ran into some sort of webserver problem afterwards as we couldn't reach the webGUI at all.

They were still accessible over SSH and after running the "web_conf_check" tool, we regained access to the webGUI. So maybe the lighttpd.conf file was unhappy after the upgrade. Both switches had logged a segmentation fault directly after a socket assignment error during boot:

Code: Select all

Jan 30 12:10:58 root: upgrading certificate
Jan 1 00:00:00 sysinit: Generating a RSA private key
Jan 1 00:00:01 sysinit: .+++++
Jan 1 00:00:12 sysinit: .......................................+++++
Jan 1 00:00:12 sysinit: writing new private key to '/etc/config/lighttpd.pem'
Jan 1 00:00:12 sysinit: -----
Jan 1 00:00:14 sysinit: 2019-01-01 00:00:14: (network.c.310) can't bind to socket: 0.0.0.0:80 Address already in use
Jan 1 00:00:14 sysinit: Segmentation fault
Jan 1 00:00:16 switch[1513]: Detected warm boot
Jan 1 00:00:19 switch[1510]: temp sensor version 1
Jan 1 00:00:20 root: stopped ntp daemon
Jan 1 00:00:20 root: started ntp daemon
Jan 1 00:00:21 root: sync time via ntp


Neither switch was rebooted before the upgrade, one had about a year of uptime and the other had roughly 8 weeks. Both had plenty of available memory as well we otherwise had no issues.