FS#72781 - [munin] 2.0.68-1 is broken "Can't use string ("local_address") as a HASH ref while "strict refs""

Attached to Project: Community Packages
Opened by Bob Arctor (oduesp) - Thursday, 18 November 2021, 06:36 GMT
Last edited by Jonas Witschel (diabonas) - Thursday, 02 December 2021, 13:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Santiago Torres (sangy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
After upgrading munin (2.0.67-2 -> 2.0.68-1) no metrics are saved no more and the /var/log/munin/munin-update.log file is filed with this error:
2021/11/18 07:30:01 [INFO] starting work in 1583676 for eastbound (127.0.0.1:4949).
2021/11/18 07:30:01 [ERROR] Munin::Master::UpdateWorker<eastbound;eastbound> died with 'Can't use string ("local_address") as a HASH ref while "strict refs" in use at /usr/share/perl5/vendor_perl/Munin/Master/Node.pm line 158.'

This is also the case with remote nodes, not juste localhost.

Additional info:
* package version(s)
munin-2.0.68-1-any.pkg.tar.zst
* config and/or log files etc.
2021/11/18 07:30:01 [ERROR] Munin::Master::UpdateWorker<eastbound;eastbound> died with 'Can't use string ("local_address") as a HASH ref while "strict refs" in use at /usr/share/perl5/vendor_perl/Munin/Master/Node.pm line 158.'

* link to upstream bug report, if any

Steps to reproduce:
Update munin to 2.0.68-1 and watch that nothing works anymore.

Temp Fix: Downgrade to 2.0.67-2
This task depends upon

Closed by  Jonas Witschel (diabonas)
Thursday, 02 December 2021, 13:01 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#72761 
Comment by Hexhu (hexhu) - Sunday, 21 November 2021, 07:54 GMT
I got the exact same error and all metric requests failed. Rolling munin back to 2.0.67-2 made the error disappear. munin-node's version does not matter.
Comment by Carsten (xabbu) - Sunday, 21 November 2021, 16:26 GMT
This commit seems to introduced the problem https://github.com/munin-monitoring/munin/commit/de74370848a7d18ce780dfcf8dbd8dbb026f6128

After reverting this commit, a new error appears, very similar to the first.

2021/11/21 17:10:00 [ERROR] Error in node communication with com (com:4949): Can't use string ("use_node_name") as a HASH ref while "strict refs" in use at /usr/share/perl5/vendor_perl/Munin/Master/Node.pm line 159, <GEN1> line 2.

I needed to revert also this commit to make the error go away. https://github.com/munin-monitoring/munin/commit/64794bed4cedf8d95d0d3f8845d08399fdddd4f0
Comment by Malte (malteger) - Monday, 22 November 2021, 20:37 GMT
This has been reported upstream, a fix is available: https://github.com/munin-monitoring/munin/issues/1440
Comment by ilf (ilf) - Tuesday, 23 November 2021, 16:25 GMT
Dupe: https://bugs.archlinux.org/task/72761
Comment by Hexhu (hexhu) - Wednesday, 24 November 2021, 07:36 GMT
Can confirm this issue is fixed in munin 2.0.69-1

Loading...