Mailing List Archive: Latest trunk build will not start (rev1586)

Latest trunk build will not start (rev1586)

Jun 27, 2007, 2:16 PM

Post #1 of 5 (1369 views)

Hello everyone.

I know tracking trunk is typically a bad idea, but I just wanted to post
this up. It seems the latest revision is giving me errors on startup
("Cannot create working directory NONE/var/$hostname") but I haven't
changed the startup command line parameters, which are as such:

varnishd -a 10.10.10.5:80 -T 10.10.10.5:8080 -b 10.11.11.200:80 -s
file, /var/cache/varnish/,10G -p thread_pool_max=1500 -p thread_pools=5
-p listen_depth=512 -p client_http11=on -p backend_http11=on -p
default_ttl=36000 -P /var/run/varnishd.pid

The error is from varnishd.c, line 549 - 553

if (mkdir(dirname, 0755) < 0 && errno != EEXIST) {
fprintf(stderr, "Cannot create working directory '%s': %s\n",
dirname, strerror(errno));
exit(1);
}

I'm not 100% sure where dirname gets set though. Don't know if this is a
bug or I am missing some parameter, thanks for any and all info :-)

-- james

Latest trunk build will not start (rev1586) [ In reply to ]

des at linpro

Jun 27, 2007, 11:56 PM

Post #2 of 5 (1339 views)

Permalink

James Quacinella <james at nyi.net> writes:
> I know tracking trunk is typically a bad idea, but I just wanted to
> post this up. It seems the latest revision is giving me errors on
> startup ("Cannot create working directory NONE/var/$hostname") but I
> haven't changed the startup command line parameters, which are as
> such:

Did you re-run autogen.sh after updating? In the top-level source
directory, what does 'grep STATE config.h' say?

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Latest trunk build will not start (rev1586) [ In reply to ]

denis at directmedia

Jun 28, 2007, 3:23 AM

Post #3 of 5 (1346 views)

Permalink

On 27.06.2007, at 23:16, James Quacinella wrote:

> Hello everyone.
>
> I know tracking trunk is typically a bad idea, but I just wanted to
> post
> this up. It seems the latest revision is giving me errors on startup
> ("Cannot create working directory NONE/var/$hostname") but I haven't
> changed the startup command line parameters, which are as such:
>
> varnishd -a 10.10.10.5:80 -T 10.10.10.5:8080 -b 10.11.11.200:80 -s
> file, /var/cache/varnish/,10G -p thread_pool_max=1500 -p
> thread_pools=5
> -p listen_depth=512 -p client_http11=on -p backend_http11=on -p
> default_ttl=36000 -P /var/run/varnishd.pid
>
> The error is from varnishd.c, line 549 - 553
>
> if (mkdir(dirname, 0755) < 0 && errno != EEXIST) {
> fprintf(stderr, "Cannot create working directory '%s': %s\n",
> dirname, strerror(errno));
> exit(1);
> }
>
> I'm not 100% sure where dirname gets set though. Don't know if this
> is a
> bug or I am missing some parameter, thanks for any and all info :-)
>
> -- james

You need to start configure with option --prefix=/usr/local

Denis

Latest trunk build will not start (rev1586) [ In reply to ]

des at linpro

Jun 28, 2007, 3:34 AM

Post #4 of 5 (1342 views)

Permalink

Denis Ahrens <denis at directmedia.de> writes:
> James Quacinella <james at nyi.net> writes:
> > I know tracking trunk is typically a bad idea, but I just wanted to
> > post this up. It seems the latest revision is giving me errors on
> > startup ("Cannot create working directory NONE/var/$hostname") but I
> > haven't changed the startup command line parameters, which are as
> > such:
> You need to start configure with option --prefix=/usr/local

Not necessarily.

Regardless of the selected prefix, ${localstatedir}/varnish (normally
${prefix}/var/varnish) should be created during installation.

In any case, this particular failure is most likely a result of not
re-running autogen.sh and configure after updating the source tree.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Latest trunk build will not start (rev1586) [ In reply to ]

james at nyi

Jun 28, 2007, 8:48 AM

Post #5 of 5 (1338 views)

Permalink

Dag-Erling Sm?rgrav wrote:
> In any case, this particular failure is most likely a result of not
> re-running autogen.sh and configure after updating the source tree.
>

Doh!

You're right. I usually do, I'm not sure how I overlooked that. Oh well,
sorry for the mailing list noise.

Thanks!

-- james