Dear fellow users,
I am running varnish-cache 7.2.1 (compiled from source) in
preproduction.
After some seemingly minor settings changes, every time I
try to start varnishd, I get the following on the terminal:
# /etc/init.d/varnish start Starting Varnish HTTP(S) proxy:
varnishWarnings: Change will take effect when VCL script is reloaded
Child launched OK CLI result = 300 failed!
Now the questions are what does this mean?, and how do I get
a more detailed error message? Obviously, the failure to
start varnishd makes varnishlog useless, but maybe there is
another log file for such startup errors.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
I am running varnish-cache 7.2.1 (compiled from source) in
preproduction.
After some seemingly minor settings changes, every time I
try to start varnishd, I get the following on the terminal:
# /etc/init.d/varnish start Starting Varnish HTTP(S) proxy:
varnishWarnings: Change will take effect when VCL script is reloaded
Child launched OK CLI result = 300 failed!
Now the questions are what does this mean?, and how do I get
a more detailed error message? Obviously, the failure to
start varnishd makes varnishlog useless, but maybe there is
another log file for such startup errors.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded