Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-I option doesn't work anymore #2782

Closed
gquintard opened this issue Sep 24, 2018 · 1 comment

Comments

Projects
None yet
4 participants
@gquintard
Copy link
Contributor

commented Sep 24, 2018

In master, using a cli file with -I doesn't work anymore, even for something as simple as:

varnishd -I /tmp/start.cli -F -a :80 -f ''

with this cli file:

vcl.load def /tmp/def.vcl
vcl.use def

and this vcl:

vcl 4.0; backend b { .host = "0"; }

the process will hang for a variable amount of time, then exit

BEGIN of -I file processing
200 320     
-----------------------------
Varnish Cache CLI 1.0
-----------------------------
Linux,4.18.8-arch1-1-ARCH,x86_64,-jnone,-sdefault,-sdefault,-hcritbit
varnish-trunk revision 48a59957c1029f16b970bbfc19dafbedb0b5a5fd

Type 'help' for command list.
Type 'quit' to close CLI session.
Type 'start' to launch worker process.

> vcl.load def /tmp/def.vcl
200 14      
VCL compiled.

> vcl.use def
200 0       

END of -I file processing
CLI result = 400

this was apparently introduced by 48a5995

@bsdphk

This comment has been minimized.

Copy link
Contributor

commented Sep 26, 2018

This looks like trouble with the "close-on-fork" bitmap.

The worker process closes the cli connection to the manager, which reacts properly to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.