CLI result = 300, how to troubleshoot?

[Poul-Henning Kamp]

--------
Dridi Boukelmoune writes:

> > 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.
>
> There may be something in your syslog, otherwise it is hard to tell
> without knowing what the init script is up to.

CLI commands are logged to the shared memory log, so

	varnishlog -d -g raw

may be able to tell you something

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.