458386 – app-admin/collectd-5.2.0 - Assert error in VSM_n_Arg(), [...]/work/varnish-3.0.3/lib/libvarnishapi/vsm.c line 97: Condition((vd->n_opt) != 0) not true.

Bug 458386 - app-admin/collectd-5.2.0 - Assert error in VSM_n_Arg(), [...]/work/varnish-3.0.3/lib/libvarnishapi/vsm.c line 97: Condition((vd->n_opt) != 0) not true.

Summary: app-admin/collectd-5.2.0 - Assert error in VSM_n_Arg(), [...]/work/varnish-3....

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal normal (vote)
Assignee:	Johan Bergström

URL:
Whiteboard:
Keywords:

Depends on:	454594
Blocks:
	Show dependency tree

Reported:	2013-02-20 00:56 UTC by jon
Modified:	2013-03-07 00:25 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description jon 2013-02-20 00:56:32 UTC

Collectd's varnish plugin seems to have broken with the upgrade to 5.2.0. Collectd silently fails with the plugin enabled. When run from the command line I received the following message:

Assert error in VSM_n_Arg(), /var/tmp/portage/www-servers/varnish-3.0.3/work/varnish-3.0.3/lib/libvarnishapi/vsm.c line 97:
  Condition((vd->n_opt) != 0) not true.

I rolled back to 5.1.0-r2 and it works again. If I disable the plugin it works too... but I don't have any Varnish stats. :-) I need this for my Varnish servers.

I looked on collectd's website and see that there is a fix for the varnish plugin in v5.2.1. Seems like that might fix the problem.

Comment 1 Johan Bergström 2013-03-03 22:32:21 UTC

Sorry for the delay. I'm preparing a bump to 5.2.1 (need to re-do the perl fix and it insists on struggling against me). See bug 454594 for bump. Haven't confirmed that 5.2.1 indeed does fix varnish (and I personally don't use it), so I would appreciate if you could confirm that the verbump indeed fixes it as soon as I've posted the new ebuild.

Thanks!

Comment 2 jon 2013-03-05 17:03:09 UTC

(In reply to comment #1)
> Sorry for the delay. I'm preparing a bump to 5.2.1 (need to re-do the perl
> fix and it insists on struggling against me). See bug 454594 for bump.
> Haven't confirmed that 5.2.1 indeed does fix varnish (and I personally don't
> use it), so I would appreciate if you could confirm that the verbump indeed
> fixes it as soon as I've posted the new ebuild.
> 
> Thanks!

I'd be happy to give it a trial on one of our servers. Excuse me for a novice question: how will I know when the new build is available?

THX!

Comment 3 Johan Bergström 2013-03-05 21:06:31 UTC

(In reply to comment #2)
> I'd be happy to give it a trial on one of our servers. Excuse me for a
> novice question: how will I know when the new build is available?
> 
> THX!

Hey,
the new ebuild was uploaded to bug 454594 the other day. Give it a try and let me know if the varnish stuff is working as intended. If you by any chance also use the perl plugins, let me know if something fishy is going on. Pretty sure it shouldn't be, though.

Comment 4 jon 2013-03-07 00:24:56 UTC

I just gave 5.2.1 a whirl on one of our Varnish servers and it works fine. That would be a fix!

Comment 5 Johan Bergström 2013-03-07 00:25:43 UTC

Perfect, thanks for reporting back. Closing since 5.2.1 nowadays is in tree.