Page MenuHomePhabricator

Unable to access mobilefrontend on betalabs
Closed, ResolvedPublic


Author: mgrover

my automation tests running on betalabs are failing because it says the "page is not connected to the server" url:

Version: unspecified
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:30 AM
bzimport set Reference to bz55662.

The hostname should be by the way - however it's also inaccessible.

DNS entry * points to which is bound to deployment-cache-mobile01. From

The varnish frontend (which listen on port 80) is not responding:

hashar@deployment-cache-mobile01:~$ sudo /etc/init.d/varnish-frontend status

  • varnishd-frontend is not running

hashar@deployment-cache-mobile01:~$ sudo /etc/init.d/varnish status

  • varnishd is running


It is not loading anymore:

hashar@deployment-cache-mobile01:~$ sudo /etc/init.d/varnish-frontend start

  • Starting HTTP accelerator [fail]

Message from VCC-compiler:
Could not load module netmapper
/usr/lib/x86_64-linux-gnu/varnish/vmods/ cannot open shared object file: No such file or directory
('' Line 3 Pos 8)
import netmapper;

Running VCC-compiler failed, exit 1

VCL compilation failed

varnish has to be manually upgraded on the beta cluster instances. I have ran apt-get dist-upgrade on all four instances (deployment-cache-text1 deployment-cache-upload04 deployment-cache-bits03 deployment-cache-mobile01 ) and rebooted them. is back up :-]

Some varnish packages were not up-to-date and I had to purge some configuration files to have puppet regenerate them properly. All four instances now have puppet running without any error and varnish / varnishhtcpd are running on all of them.