On Monday I upgraded one of my servers from 14.4-p6 to 14.4-p8, and
after the reboot, yaf (net-mgmt/yaf) immediately started crashing with SIGSEGV about once per CPU-minute. The package hasn't changed
(although I did force-reinstall it just to make sure there was no
corruption in the executable).
pid 4650 (yaf), jid 0, uid 65534: exited on signal 11 (no core dump - bad address)
It did just occur to me to check whether the package had been updated,
and it has; des@ upgraded it to 2.19.3 in late June, and because of
the way yaf gets started in my environment, while the binary was
silently replaced, the running daemon probably never got restarted
until I rebooted the server. So now I've manually backed out the port upgrade to see if that fixes matters.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 59:30:09 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,017 |