Mailing List Archive: #1679: After upgrade, custom vmods are not moved so vcl does not compile

#1679: After upgrade, custom vmods are not moved so vcl does not compile

varnish-bugs at varnish-cache

Feb 20, 2015, 5:46 AM

Post #1 of 6 (1664 views)

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+--------------------
Reporter: razvanphp | Type: defect
Status: new | Priority: normal
Milestone: | Component: vmod
Version: 4.0.3 | Severity: normal
Keywords: |
-----------------------+--------------------
Today we upgraded to varnish 4.0.3 from the official debian wheezy repo.

For some reason (I can't find the changelog or motivation for this) the
vmod directory changed from `/usr/lib/varnish/vmods/` to `/usr/lib/x86_64
-linux-gnu/varnish/vmods/`. The std and directory vmods were moved to the
new folder, but custom ones not, resulting in errors and failed startup:

{{{
Unpacking replacement varnish ...
dpkg: warning: unable to delete old directory '/usr/lib/varnish/vmods':
Directory not empty
dpkg: warning: unable to delete old directory '/usr/lib/varnish':
Directory not empty
...
[FAIL] Starting HTTP accelerator: varnishd failed!
Message from VCC-compiler:
Could not load VMOD geoip
File name: /usr/lib/x86_64-linux-
gnu/varnish/vmods/libvmod_geoip.so
dlerror:: /usr/lib/x86_64-linux-
gnu/varnish/vmods/libvmod_geoip.so: cannot open shared object file: No
such file or directory
('input' Line 21 Pos 8)
import geoip;
-------#####-
}}}

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs

Re: #1679: After upgrade, custom vmods are not moved so vcl does not compile [ In reply to ]

varnish-bugs at varnish-cache

Feb 23, 2015, 4:05 AM

Post #2 of 6 (1630 views)

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+-----------------------
Reporter: razvanphp | Owner: lkarsten
Type: defect | Status: new
Priority: normal | Milestone:
Component: vmod | Version: 4.0.3
Severity: normal | Resolution:
Keywords: |
-----------------------+-----------------------
Changes (by lkarsten):

* owner: => lkarsten

Comment:

Reproduced on wheezy:
{{{
root@wheezy-amd64:~# dpkg -l varnish
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-
pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-========================-=================-=================-=====================================================
ii varnish 4.0.3-1~wheezy amd64 state of
the art, high-performance web accelerator
root@wheezy-amd64:~# dpkg -L varnish
[..]
ï¿¼/usr/lib/x86_64-linux-gnu/varnish/libvgz.so
/usr/lib/x86_64-linux-gnu/varnish/vmods
/usr/lib/x86_64-linux-gnu/varnish/vmods/libvmod_directors.so
/usr/lib/x86_64-linux-gnu/varnish/vmods/libvmod_std.so
/usr/lib/x86_64-linux-gnu/varnish/libvcc.so
}}}

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679#comment:1>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs

Re: #1679: After upgrade, custom vmods are not moved so vcl does not compile [ In reply to ]

varnish-bugs at varnish-cache

Feb 23, 2015, 11:52 AM

Post #3 of 6 (1627 views)

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+-----------------------
Reporter: razvanphp | Owner: lkarsten
Type: defect | Status: new
Priority: normal | Milestone:
Component: vmod | Version: 4.0.3
Severity: normal | Resolution:
Keywords: |
-----------------------+-----------------------

Comment (by lkarsten):

Hi.

Updated Debian packages (4.0.3-2) are available in Jenkins now, and will
be put onto repo.varnish-cache.org shortly.

Keeping the bug report open until we've confirmed it is in place.

Thanks for reporting this.

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs

Re: #1679: After upgrade, custom vmods are not moved so vcl does not compile [ In reply to ]

varnish-bugs at varnish-cache

Feb 24, 2015, 2:43 AM

Post #4 of 6 (1620 views)

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+-----------------------
Reporter: razvanphp | Owner: lkarsten
Type: defect | Status: closed
Priority: normal | Milestone:
Component: vmod | Version: 4.0.3
Severity: normal | Resolution: fixed
Keywords: |
-----------------------+-----------------------
Changes (by lkarsten):

* status: new => closed
* resolution: => fixed

Comment:

Confirmed now (on wheezy) that apt-get upgrades to 4.0.3-2 where this
issue is fixed.

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679#comment:3>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs

Re: #1679: After upgrade, custom vmods are not moved so vcl does not compile [ In reply to ]

varnish-bugs at varnish-cache

Feb 24, 2015, 6:20 AM

Post #5 of 6 (1621 views)

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+-----------------------
Reporter: razvanphp | Owner: lkarsten
Type: defect | Status: closed
Priority: normal | Milestone:
Component: vmod | Version: 4.0.3
Severity: normal | Resolution: fixed
Keywords: |
-----------------------+-----------------------

Comment (by razvanphp):

Ok, so I just updated an older 4.0.2 to 4.0.3-2~wheezy, everything is ok,
but the vmods dir is back to `/usr/lib/varnish/vmods`. Is this how it
should be?

I'm asking to know how to write my ansible scripts. Or.. is it a better
way to programmatically get the vmods dir?

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679#comment:4>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs

Re: #1679: After upgrade, custom vmods are not moved so vcl does not compile [ In reply to ]

varnish-bugs at varnish-cache

Jun 9, 2015, 4:36 AM

Post #6 of 6 (1472 views)

#1679: After upgrade, custom vmods are not moved so vcl does not compile
-----------------------+-----------------------
Reporter: razvanphp | Owner: lkarsten
Type: defect | Status: closed
Priority: normal | Milestone:
Component: vmod | Version: 4.0.3
Severity: normal | Resolution: fixed
Keywords: |
-----------------------+-----------------------

Comment (by lkarsten):

Yes, /usr/lib/varnish/vmods/ is how we intend to keep it.

The generic way would be to get it from pkg-config:

{{{
lkarsten@IMMER ~> pkg-config --variable=vmoddir varnishapi
/usr/lib/varnish/vmods
}}}

--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1679#comment:5>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs