Summary: | [bsnmpd] regression on 12-STABLE: crash on start | ||
---|---|---|---|
Product: | Base System | Reporter: | emz |
Component: | bin | Assignee: | Shteryana Shopova <syrinx> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | admin, ae, ed, emaste, eugene, markj |
Priority: | --- | Keywords: | regression |
Version: | 12.0-STABLE | ||
Hardware: | Any | ||
OS: | Any | ||
See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221487 | ||
Bug Depends on: | |||
Bug Blocks: | 228911 |
Description
emz
2018-11-23 09:19:41 UTC
Ed, can you take a look at this? It looks very like the problem appears after r332100. Also, Eugene or Vladislav, can you try revert r332100, rebuild/reinstall the world and try to reproduce the problem? A commit references this bug: Author: syrinx Date: Fri Jun 21 07:45:59 UTC 2019 New revision: 349265 URL: https://svnweb.freebsd.org/changeset/base/349265 Log: No need for each bsnmpd(1) module to open connection to syslog bsnmpd(1) main does that early on init and the connection is available to all loaded modules Event: Vienna Hackathon 2019 PR: 233431 , 221487 MFC after: 2 weeks Changes: head/usr.sbin/bsnmpd/modules/snmp_lm75/snmp_lm75.c A commit references this bug: Author: syrinx Date: Sat Jan 18 10:55:38 UTC 2020 New revision: 356865 URL: https://svnweb.freebsd.org/changeset/base/356865 Log: MFC r349265: No need for each bsnmpd(1) module to open connection to syslog bsnmpd(1) main does that early on init and the connection is available to all loaded modules PR: 233431 , 221487 Event: Vienna Hackathon 2019 Changes: _U stable/12/ stable/12/usr.sbin/bsnmpd/modules/snmp_lm75/snmp_lm75.c Is this resolved now? *** Bug 221487 has been marked as a duplicate of this bug. *** I can start bsnmpd without issue on -CURRENT, with no non-default config or with pf enabled as described in PR221487. Confirmation from the original reporter or ae@ would be useful, ideally against the 12.2 BETA/RC images. Yeah, seems to be working from some point for me too, thanks. (In reply to Eugene M. Zheganin from comment #7) Thanks for the update. |