I extracted the following weird error from the sys-log regarding pdu and schannel (have the same PID): Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, effective(65534, 65533), real(65534, 0)] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, effective(65534, 65533), real(65534, 0)] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) Feb 24 10:40:37 s-svr01 smbd[31833]: process_request_pdu: failed to do schannel processing. I also sometimes get this error. Does someone know, what this means? Feb 24 10:41:57 s-svr01 smbd[31573]: [2004/02/24 10:41:57, 0, pid=31573, effective(1137, 505), real(1137, 0)] rpc_server/srv_util.c:get_domain_user_groups(372) Feb 24 10:41:57 s-svr01 smbd[31573]: get_domain_user_groups: primary gid of user [pichle.a] is not a Domain group ! Feb 24 10:41:57 s-svr01 smbd[31573]: get_domain_user_groups: You should fix it, NT doesn't like that Feb 24 10:42:24 s-svr01 smbd[31573]: [2004/02/24 10:42:24, 0, pid=31573, effective(1137, 505), real(1137, 0)] smbd/posix_acls.c:create_canon_ace_lists(1481) Feb 24 10:42:24 s-svr01 smbd[31573]: create_canon_ace_lists: malformed ACL in file ACL ! Deny entry after Allow entry. Failing to set on file jfdf/hp.bmp. Server: Samba 3.0.2a-SuSE Client: WinXP-SP1 w/ "SignOrSeal-patch" If you need more information (syslogs, config, ...), please mail me! Thanks in advance, Stumpfl Markus
On Tue, 2004-02-24 at 20:56, Stumpfl Markus wrote:> I extracted the following weird error from the sys-log regarding pdu and > schannel (have the same PID): > > Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, > effective(65534, 65533), real(65534, 0)] > rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) > Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU > Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, > effective(65534, 65533), real(65534, 0)] > rpc_server/srv_pipe_hnd.c:process_request_pdu(605) > Feb 24 10:40:37 s-svr01 smbd[31833]: process_request_pdu: failed to do > schannel processing.Is this actually causing you issues? This error may be harmless. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040224/26e054e2/attachment.bin
I also get this error in my logs. I'm not sure if it's related to a problem I'm having with roaming profiles at the moment. A Windows XP computer with all the most recent updates from Windows Update has intermittent problems with roaming profiles returning "DETAIL - The network name cannot be found." as the important part of the error. I'll respond again when I know which update it is (it's probably going to take me a couple more hours to discover exactly which patch it is). Clint -- Clint Sharp Systems Administrator, AT&T Wireless International IT Desk: 425-580-1900 Mobile: 206-369-7394> -----Original Message----- > From: samba-bounces+clint=typhoon.org@lists.samba.org > [mailto:samba-bounces+clint=typhoon.org@lists.samba.org] On > Behalf Of Stumpfl Markus > Sent: Tuesday, February 24, 2004 1:56 AM > To: MailingList_Samba > Subject: [Samba] PDU & schannel errors > > > I extracted the following weird error from the sys-log > regarding pdu and schannel (have the same PID): > > Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, > pid=31833, effective(65534, 65533), real(65534, 0)] > rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) > Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU > Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, > pid=31833, effective(65534, 65533), real(65534, 0)] > rpc_server/srv_pipe_hnd.c:process_request_pdu(605) > Feb 24 10:40:37 s-svr01 smbd[31833]: process_request_pdu: > failed to do > schannel processing. > > > I also sometimes get this error. Does someone know, what this means? > > Feb 24 10:41:57 s-svr01 smbd[31573]: [2004/02/24 10:41:57, 0, > pid=31573, effective(1137, 505), real(1137, 0)] > rpc_server/srv_util.c:get_domain_user_groups(372) > Feb 24 10:41:57 s-svr01 smbd[31573]: get_domain_user_groups: primary > gid of user [pichle.a] is not a Domain group ! > Feb 24 10:41:57 s-svr01 smbd[31573]: get_domain_user_groups: You > should fix it, NT doesn't like that > Feb 24 10:42:24 s-svr01 smbd[31573]: [2004/02/24 10:42:24, 0, > pid=31573, effective(1137, 505), real(1137, 0)] > smbd/posix_acls.c:create_canon_ace_lists(1481) > Feb 24 10:42:24 s-svr01 smbd[31573]: > create_canon_ace_lists: malformed > ACL in file ACL ! Deny entry after Allow entry. Failing to > set on file jfdf/hp.bmp. > > > Server: Samba 3.0.2a-SuSE > Client: WinXP-SP1 w/ "SignOrSeal-patch" > > If you need more information (syslogs, config, ...), please mail me! > > Thanks in advance, > > Stumpfl Markus > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >
"Stumpfl Markus" <htl.traun.kustos@eduhi.at> wrote in message news:003701c3fabc$760dfe10$0139680a@htltraun.eduhi.at...> I extracted the following weird error from the sys-log regarding pdu and > schannel (have the same PID): > > Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, > effective(65534, 65533), real(65534, 0)] > rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) > Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU > Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, > effective(65534, 65533), real(65534, 0)] > rpc_server/srv_pipe_hnd.c:process_request_pdu(605) > Feb 24 10:40:37 s-svr01 smbd[31833]: process_request_pdu: failed to do > schannel processing.I get the same errors on my samba 3.0.2 PDC whenever someone logs on. It appears to harmless, as everything works just fine.