search for: asender

...as expected. The user can login to windows workstation connected to the domain. However; if I create an account through the BDC which writes to the master ldap database this is different and user cannot login to domain ****different User SID**** Created on the PDC [root@node1 ~]# pdbedit -Lv asender WARNING: The "printer admin" option is deprecated Unix username: asender NT username: asender Account Flags: [U ] User SID: S-1-5-21-3959433150-537517574-2380176113-3000 „²-------------------------------------- Primary Group SID: S-1-5-21-39...

...as expected. The user can login to windows workstation connected to the domain. However; if I create an account through the BDC which writes to the master ldap database this is different and user cannot login to domain ****different User SID**** Created on the PDC [root@node1 ~]# pdbedit -Lv asender WARNING: The "printer admin" option is deprecated Unix username: asender NT username: asender Account Flags: [U ] User SID: S-1-5-21-3959433150-537517574-2380176113-3000 „²-------------------------------------- Primary Group SID: S-1-5-21-39...

The LDAP server is working fine as I said it works fine in the command line. Anymore suggestions? email me: asender@ampwest.com.au Thanks Adrian >> >>Hello members >> >>I really have ran out of options here, and I don't know how to resolve this issue. I have a Samba LDAP primary domain controller. I have been using LAM - LDAP Account Manager to manage the accounts. The command...

...reason from ocfs2. The log like this: Jul 3 10:58:37 web1 kernel: d-con r0: PingAck did not arrive in time. Jul 3 10:58:37 web1 kernel: d-con r0: peer( Primary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown ) Jul 3 10:58:37 web1 kernel: d-con r0: asender terminated Jul 3 10:58:37 web1 kernel: d-con r0: Terminating asender thread Jul 3 10:58:37 web1 kernel: d-con r0: error receiving Data, e: -5 l: 4096! Jul 3 10:58:37 web1 kernel: block drbd0: new current UUID A69EE0FA8CB9B85D:C9BABEF0844508EB:2F0151CEDDA9713A:2F0051CEDDA9713B Jul 3 10:58:37...

...gin I get an error "LDAP error, server says: (-1) Can't contact LDAP server" LAM is configured correctly, and it used to work. I am almost positive this is not a "LAM" issue. Any help or suggestions would be greatly appreciated. Please email me suggestions or solutions: asender@ampwest.com.au Many Thanks Adrian.

Hi all, Muppet from the UK asking for help We are just about to have a T1 line installed in our office in Dallas and "Advantex" the supplier has sent a questionnaire asking a number of questions. I have put the question area at the bottom of the email, we will be using Digium's hardware. could anybody help :-) In the UK when I asked for a E1, number of trunks required and the

...( Connected -> BrokenPipe ) pdsk( UpToDate -> DUnknown ) .... and on and on and on with the DRBD disconnecting block drbd29: md_sync_timer expired! Worker calls drbd_md_sync(). block drbd21: md_sync_timer expired! Worker calls drbd_md_sync(). .... lots of that block drbd24: Terminating drbd24_asender block drbd21: asender terminated block drbd21: Terminating drbd21_asender .... eth0: port 3(nlb2.e0) entering forwarding state .... block drbd1: Handshake successful: Agreed network protocol version 91 block drbd1: conn( WFConnection -> WFReportParams ) block drbd38: Handshake successful: Agreed...

...mounting it on one node and starting bonnie++ causes only that node to crash. On DRBD level I get the following error when that node dissapears drbd0: PingAck did not arrive in time. drbd0: peer( Primary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk(UpToDate -> DUnknown ) drbd0: asender terminated drbd0: Terminating asender thread That however is an expected error because of the reboot. At first I assumed OCFS2 to be the root of this problem ..so I moved forward and setup an ISCSI target on a 3rd node, and used that device with the same OCFS2 setup. There no crashes occured and...

...mounting it on one node and starting bonnie++ causes only that node to crash. On DRBD level I get the following error when that node dissapears drbd0: PingAck did not arrive in time. drbd0: peer( Primary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk(UpToDate -> DUnknown ) drbd0: asender terminated drbd0: Terminating asender thread That however is an expected error because of the reboot. At first I assumed OCFS2 to be the root of this problem ..so I moved forward and setup an ISCSI target on a 3rd node, and used that device with the same OCFS2 setup. There no crashes occured and...

...e just upgraded to version 3.0.21rc1. I decided to re-populate the database and test if everything is working. ./smbldap-populate -a root -k 0 -m 0 -> ok ./smbldap-useradd -m -a username -> ok ./smbldap-passwd username -> ok smbpasswd username - > fail [root@node1 sbin]# smbpasswd asender New SMB password: Retype new SMB password: ldapsam_set_account_policy: Could not set account policy for sambaDomainName=DDESIGN,dc=ddesign,dc=com, error: Undefined attribute type (sambaPwdHistoryLength: attribute type undefined) ldapsam_set_account_policy: Could not set account policy for sambaD...

...I have the following issue. [root@node1 sbin]# su bbong su: user bbong does not exist [root@node1 sbin]# ./smbldap-useradd -m -a bbong ./smbldap-useradd: user bbong exists [root@node1 sbin]# su bbong [bbong@node1 sbin]$ Could you please reply to this on the list, as well as send me an email to: asender@ampwest.com.au Your help is greatly appreciated. Regards Adrian Sender

...d Jul 11 14:30:50 node1 kernel: audit(1121056250.376:0): avc: denied { connect } for pid=4637 exe=/usr/sbin/httpd scontext=root:system_r:httpd_t tcontext=root:system_r:httpd_t tclass=tcp_socket Any help or suggestions would be greatly appreciated. Please email me suggestions or solutions: asender@ampwest.com.au Many Thanks

...1 12:07:20 ubu10a kernel: [ 1354.433074] block drbd0: Peer authenticated > using 20 bytes of 'sha1' HMAC > Apr 1 12:07:20 ubu10a kernel: [ 1354.433083] block drbd0: conn( WFConnection > -> WFReportParams ) > Apr 1 12:07:20 ubu10a kernel: [ 1354.433097] block drbd0: Starting asender > thread (from drbd0_receiver [2145]) > Apr 1 12:07:20 ubu10a kernel: [ 1354.433562] block drbd0: data-integrity-alg: > <not-used> > Apr 1 12:07:20 ubu10a kernel: [ 1354.434090] block drbd0: > drbd_sync_handshake: > Apr 1 12:07:20 ubu10a kernel: [ 1354.434094] block drbd0...

Hi, I am trying to (live-)migrate a paravirtualized machine from hosta to hostb: -----8<---- hosta:~ # xm list pvm Name ID Mem VCPUs State Time(s) pvm 64 384 1 -b---- 0.5 hostb:~ # xm list pvm Error: Domain ''pvm'' does not exist. hosta:~ # xm migrate pvm 192.168.0.2 Error:

...f you could email me directly as well as the list that would be much appreciated, our mail server sometimes gives a funny error "The current command did not succeed. The mail server responded: Excessively complex FETCH attribute list. *****Please email me directly as well as the list***** asender@ampwest.com.au Many thanks for the help. Kind Regards. Adrian Sender

...omplaining about CUPS not configured). May 9 22:30:21 sg1 kernel: block drbd0: PingAck did not arrive in time. May 9 22:30:21 sg1 kernel: block drbd0: peer( Secondary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown ) May 9 22:30:21 sg1 kernel: block drbd0: asender terminated May 9 22:30:21 sg1 kernel: block drbd0: Terminating drbd0_asender May 9 22:30:22 sg1 kernel: block drbd0: new current UUID BC856D7A6F94F041:237F4033E81B62DF:1E248D699B6793A9:1E238D699B6793A9 May 9 22:30:22 sg1 kernel: block drbd0: Connection closed May 9 22:30:22 sg1 kernel: block d...

...1: link becomes ready [ 58.949609] block drbd0: Handshake successful: Agreed network protocol version 90 [ 58.950101] block drbd0: Peer authenticated using 20 bytes of 'sha1' HMAC [ 58.950108] block drbd0: conn( WFConnection -> WFReportParams ) [ 58.952094] block drbd0: Starting asender thread (from drbd0_receiver [4622]) [ 58.952094] block drbd0: data-integrity-alg: <not-used> [ 58.952094] block drbd0: drbd_sync_handshake: [ 58.952094] block drbd0: self 19E7AFE5788793A0:0000000000000000:8E425F0092DD9387:498BBCEDBE36C105 bits:0 flags:0 [ 58.952094] block drbd0: peer...

Hello Samba Users, Simo and I have put together a new document which includes the latest replication methods using Openldap. Instead of using the ageing slurpd for replication (which is no longer actively developed or supported); Openldap as of version 2.3 supports a new feature called delta-syncrepl. http://wiki.samba.org/index.php/Replicated_Failover_Domain_Controller_and_fi