[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: SPECweb and RH 7.1



Most probably the problem is related to the fact that now TUX
does a chroot to the docroot. Somewhere in the CAD_u.c the locations of
upfgen99 and cadgen99 are set:

	strcpy(tmpstr1, TUXAPI_docroot); strcat(tmpstr1, "/upfgen99");
	strcpy(tmpstr2, TUXAPI_docroot); strcat(tmpstr2, "/cadgen99");

You have to either change these (keeping in mind that now your root (/) is 
essentially your docroot) or move these files to the correct location. 
You have to fix the path for the "postlog" too or expect to see it created 
somewhere other than /tmp (i.e. docroot/tmp).

(If your docroot is "/http" and you have not modified CAD_u, TUX will 
be looking for upfgen99 and cadgen99 in /http/http and won't find them there.)

-Mohammad


Scottie M Brown wrote:
> 
> Has anyone seen a problem with the CAD_u code executing upfgen99 and
> cadgen99?  Everything else is working fine.  The output from strace is
> provided below.  Why is the execve failing?.
> 
> [root@server /root]# strace -f -p 1553
> fork()                                  = 1638
> [pid  1553] wait4(1638,  <unfinished ...>
> [pid  1638] execve("/http/cadgen99", ["/http/cadgen99", "-C", "/http/", "
> -e", "1
> 00", "-t", "100", "1", "100"], [/* 3 vars */]) = -1 ENOENT (No such file or
> directory)
> [pid  1638] write(1, "opening shared library /http/CAD"..., 259) = 259
> [pid  1638] send(3, "HTTP/1.1 200 OK\r\nContent-Type: t"..., 89, 0x8000) =
> 89
> [pid  1638] send(3, "<html>\n<head><title>SPECweb99 Dy"..., 275, 0x8000) =
> 275
> [pid  1638] send(3, "CAD: could not execute CADGEN!\n", 31, 0) = 31
> [pid  1638] send(3, "\n</pre>\n</body></html>\n", 23, 0) = 23
> [pid  1638] SYS_222(0x9, 0xbfffdc20, 0x40189ff0, 0xbfffdc20, 0x63) = -1
> EINVAL (Invalid argument)
> [pid  1638] write(1, "last event: -1.\n", 16) = 16
> [pid  1638] munmap(0x40019000, 4096)    = 0
> [pid  1638] _exit(0)                    = ?
> <... wait4 resumed> NULL, 0, NULL)      = 1638
> --- SIGCHLD (Child exited) ---
> 
> 
> 
> 
> Ingo Molnar <mingo@elte.hu>@redhat.com on 04/05/2001 02:15:20 AM
> 
> Please respond to tux-list@redhat.com
> 
> Sent by:  tux-list-admin@redhat.com
> 
> 
> To:   TUX Development Mailing List <tux-list@redhat.com>
> cc:
> Subject:  Re: SPECweb
> 
> 
> 
> 
> On Wed, 4 Apr 2001, Mohammad Banikazemi wrote:
> 
> > Unfortunately that is not the case. I had a lib directory in my
> > docroot. I also statically linked upfgen and cadgen but that didn't
> > help either. On the client side I see the same set of messages
> > (couldn't execute UPFGEN ...)
> 
> please strace the TUX process, this should show what fails. Plus, as
> mentioned in a previous mail:
> 
> ---->
> Replace this line in /etc/rc.d/init.d/tux:
> 
>     daemon /usr/sbin/tux -d -t $TUXTHREADS -r $DOCROOT $EXTRAOPTS
> $TUXMODULES
> 
> with this line:
> 
>     /usr/sbin/tux -t $TUXTHREADS -r $DOCROOT $EXTRAOPTS $TUXMODULES
> 
> additionally you might want to attach to the first TUX worker thread via
> gdb, to catch SIGSEGVs on the spot.
> 
>      Ingo
> 
> 
> 
> _______________________________________________
> tux-list mailing list
> tux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/tux-list
> 
> 
> 
> 
> _______________________________________________
> tux-list mailing list
> tux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/tux-list
> 


-- 

-Mohammad





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []