How about a truss -f?

On Thu, Mar 02, 2000 at 04:50:46PM -0500, Curtis Generous wrote:
> According to [EMAIL PROTECTED]:
> > 
> > How about a truss -f?
> > 
> > That might tell you why the spawned process is dying.
> > 
> > Also, you might want to quote the log files exactly next time. As a long-time user
> > of qmail you may be aware of how confusing a paraphrased error can be to people
> > trying to help you.
> > 
> > 
> > Regards.
> 
> You're abosultely right - my apologies.  Here is the output of truss:
> 
> 
>     # truss /var/qmail/bin/qmail-start ./Mailbox
> 
>     ...
>     0write(0, " 0", 1)                              = 1
>     /write(0, " /", 1)                              = 1
>     10write(0, " 1 0", 2)                           = 2
>      remote write(0, "   r e m o t e  ", 8)                 = 8
>     0write(0, " 0", 1)                              = 1
>     /write(0, " /", 1)                              = 1
>     20write(0, " 2 0", 2)                           = 2
> 
>     write(0, "\n", 1)                               = 1
>     time()                                          = 952033073
>     open("lock/trigger", O_RDONLY|O_NDELAY)         = 8
>     time()                                          = 952033073
>     time()                                          = 952033073
>     poll(0xFFFFFFFF7FFFB630, 3, 0)                  = 2
>     time()                                          = 952033073
>     read(2, 0x100118448, 2048)                      = 0
>     alert: oh no! lost spawn connection! dying...
>     write(0, " a l e r t :   o h   n o".., 46)      = 46
>     read(4, 0x100118448, 2048)                      = 0
>     alert: oh no! lost spawn connection! dying...
>     write(0, " a l e r t :   o h   n o".., 46)      = 46
>     open("mess/0", O_RDONLY|O_NDELAY)               = 9
>     fcntl(9, F_SETFD, 0x00000001)                   = 0
>     fstat(9, 0xFFFFFFFF7FFFB430)                    = 0
>     utime("remote/14/6791", 0xFFFFFFFF7FFFB770)     = 0
>     status: exiting
>     write(0, " s t a t u s :   e x i t".., 16)      = 16
>     _exit(0)
> 
> Here is exact syslog entries:
> 
> Mar  2 16:35:45 m67 qmail: 952032945.637216 alert: oh no! lost spawn connection! 
>dying...
> Mar  2 16:35:45 m67 qmail: 952032945.637536 alert: oh no! lost spawn connection! 
>dying...
> 
> --curtis
> 
> 
>     > 
>     > 
>     > On Thu, Mar 02, 2000 at 02:05:41PM -0500, Curtis Generous wrote:
>     > > Has anyone been successful in getting QMAIL-1.03 to run on a SPARC running
>     > > Solaris 7, and compiled using the Sun C compiler?  Here is my environment:
>     > > 
>     > > This is SUN Netra T1 running Solaris 7:
>     > > 
>     > >     m67[admin]% uname -a
>     > >     SunOS m67 5.7 Generic_106541-08 sun4u sparc SUNW,UltraSPARC-IIi-cEngine
>     > > 
>     > > 
>     > > Here are my compile time flags in conf-cc:
>     > > 
>     > >     cc -fast -xO4 -xdepend -xarch=v9
>     > > 
>     > > 
>     > > This is the C compiler being used:
> > > 
> > >     m67[admin]% which cc
> > >     /opt/SUNWspro/bin/cc
> > > 
> > >     m67[admin]% cc -V
> > >     cc: WorkShop Compilers 5.0 98/12/15 C 5.0
> > > 
> > > 
> > > I can't get qmail started.  When I invoke the standard /var/qmail/rc script, it
> > > exits immediately, with the following error logged in SYSLOG:
> > > 
> > >     qmail-send lost spawn connection, died.
> > > 
> > > Any ideas or suggestions?  I have built qmail many times under Solaris
> > > 2.6 so am very familiar with the build process.  The 'make setup check'
> > > went without a hitch. I haven't seen this error before and nothing in
> > > the archives game any insights. 
> > > 
> > > TIA,
> > > 

Reply via email to