CUPS 1.2.2 - cups-polld exited on Solaris client
angelb
angelb at bugarin.us
Tue Aug 1 13:49:25 PDT 2006
Hello all;
Here, I have configured a Solaris 10 client with CUPS 1.2.2. Before
starting cupsd, I decided to run truss against it. Not long after
cupsd started, the cups-polld daemon received a SIGTERM.
See the following truss output:
...
17628: recv(6, " E\015 p r i n t e r - u".., 2048, 0) = 2045
17628: brk(0x00102300) = 0
17628: brk(0x00104300) = 0
17628: time() = 1154460138
17628: recv(6, " A\0\f p r i n t e r - i".., 132, 0) = 132
17628: time() = 1154460138
17623: pollsys(0xFFBF97C0, 5, 0x00000000, 0x00000000) = 1
17628: write(2, " D E B U G : ", 7) = 7
17623: time() = 1154460138
17628: write(2, " [ c u p s - p o l l d ".., 25) = 25
17623: time() = 1154460138
17628: write(2, " F o u n d ", 7) = 7
17623: read(5, " D E B U G : [ c u p s".., 1023) = 39
17628: write(2, " 1 1 6 8", 4) = 4
17623: time() = 1154460138
17628: write(2, " p r i n t e r s .\n", 11) = 11
17623: write(1, " E [ 0 1 / A u g / 2 0".., 86) = 86
17628: time() = 1154460138
17623: close(5) = 0
17628: write(2, " D E B U G 2 : ", 8) Err#32 EPIPE
17623: close(5) Err#9 EBADF
17628: Received signal #13, SIGPIPE [ignored]
17623: time() = 1154460138
17623: write(1, " d [ 0 1 / A u g / 2 0".., 78) = 78
17628: sendto(4, " 2 3 0 5 6 3 i p p :".., 161, 0, 0xFFBFF7A0, 16) = 161
17626: Received signal #15, SIGTERM, in recv() [default]
17626: siginfo: SIGTERM pid=17623 uid=0
17623: kill(17626, SIGTERM) = 0
17628: write(2, " D E B U G 2 : ", 8) Err#32 EPIPE
17626: recv(6, 0x00047410, 2048, 0) Err#4 EINTR
17623: kill(17628, SIGTERM) = 0
17628: Received signal #13, SIGPIPE [ignored]
17623: time() = 1154460138
17628: Received signal #15, SIGTERM [default]
17628: siginfo: SIGTERM pid=17623 uid=0
17623: pollsys(0xFFBF97C0, 4, 0xFFBFBA28, 0x00000000) = 1
17623: time() = 1154460138
17623: recvfrom(4, " 2 3 0 5 6 3 i p p :".., 1540, 0, 0xFFBFB324, 0xFFBFBA2C) = 161
17623: time() = 1154460138
17623: write(1, " d [ 0 1 / A u g / 2 0".., 242) = 242
17623: time() = 1154460138
17623: Received signal #18, SIGCLD [caught]
17623: siginfo: SIGCLD CLD_KILLED pid=17626 status=0x000F
17623: lwp_sigmask(SIG_SETMASK, 0x00020000, 0x00000000) = 0xFFBFFEFF [0x0000FFFF]
17623: setcontext(0xFFBF90C0)
17623: time() = 1154460138
17623: so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 5
17623: ioctl(5, SIOCGIFCONF, 0xFFBF9680) = 0
17623: ioctl(5, SIOCGIFFLAGS, 0xFFBE9660) = 0
17623: ioctl(5, SIOCGIFNETMASK, 0xFFBE9660) = 0
17623: ioctl(5, SIOCGIFFLAGS, 0xFFBE9660) = 0
17623: Received signal #18, SIGCLD [caught]
17623: siginfo: SIGCLD CLD_KILLED pid=17628 status=0x000F
17623: lwp_sigmask(SIG_SETMASK, 0x00020000, 0x00000000) = 0xFFBFFEFF [0x0000FFFF]
17623: setcontext(0xFFBE9088)
17623: ioctl(5, SIOCGIFNETMASK, 0xFFBE9660) = 0
17623: ioctl(5, SIOCGIFBRDADDR, 0xFFBE9660) = 0
...
Does the truss report provide any clue as to what's causing the child
processes to get terminated?
While my AIX client was started as a seperate process from cupsd,
it's been running fine since early this morning.
Thanks,
Angel
More information about the cups
mailing list