[389-users] Problems upgrading from PassSync 1.4 to PassSync 1.5
Hi list,I was expecting these new changes in PassSync (moreover those related to the 8th bit handling) , so congrats for the advances. I've found the following when I've tried the upgrade the product on one of my 2003 32bits windows controllers:1.- I cannot simply update. The installed version was 1.4. A message tells me to uninstall the previous version and reinstall.2.- If I uninstall the previous version, restart and install 1.5 from scratch, the installer stops when it tries to start the PassSync service , the rolls back the setup and does nothing. Error 1603 appears in the event viewer. I've troubleshooted this error according to Microsofts kb but none of the symptoms match my scenario.I've tried the upgrade of my other two windows2003 x32 controllers , but I'm asked to upgrade windows installer first. All in all , could those problems relate to an old windows installer version? I havent updated it yet, just needed to make sure first. Could also be related to the way the 1.5 .msi was generated?Regards!-- Juan Carlos Camargo Carrillo.@jcarloscamargo957-211157 ,650932877-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] 389-console LDIF export question
On 06/27/2013 04:57 AM, Michael Lang wrote: Dear all, I would like to clarify how the procedure to export - LDIF through the 389-console GUI is done (or how if reproduce should be done). As far as I've understood the exports on the server itself is done through creating a appropriate entry in cn=export,cn=task,cn=config For remote machines using the GUI this isn't valid as the nsFilename attribute requires a local write able location. What I've seen through looking at the LDAP protocol queries done during an export-to-ldif on console machine task is a query to the schema listing all attributeTypes which are then sent as attribute-retrieve-list in the ldap search. At least that's how I was able to reproduce the same LDIF from GUI-Console export and manually. Is this correct and should this be done in that way ? (I've noticed also the Warning: If you don't have permissions statement when using the LDIF export in the Console which more-or-less ack's my approach) Right. There is no way to do a database export to LDIF to a remote file on a remote machine. Are you trying to figure out a way to generate an LDIF file using ldapsearch that looks exactly like a database export LDIF file? Why? thanks for any hint. regards Mike -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Problems upgrading from PassSync 1.4 to PassSync 1.5
On 06/27/2013 03:28 AM, Juan Carlos Camargo wrote: Hi list, I was expecting these new changes in PassSync (moreover those related to the 8th bit handling) , so congrats for the advances. I've found the following when I've tried the upgrade the product on one of my 2003 32bits windows controllers: 1.- I cannot simply update. The installed version was 1.4. A message tells me to uninstall the previous version and reinstall. 2.- If I uninstall the previous version, restart and install 1.5 from scratch, the installer stops when it tries to start the PassSync service , the rolls back the setup and does nothing. Error 1603 appears in the event viewer. I've troubleshooted this error according to Microsofts kb but none of the symptoms match my scenario. I've tried the upgrade of my other two windows2003 x32 controllers , but I'm asked to upgrade windows installer first. All in all , could those problems relate to an old windows installer version? I havent updated it yet, just needed to make sure first. Could also be related to the way the 1.5 .msi was generated? We are having problems with 1.5 on 2003. I don't suppose you can upgrade to 2008 R2? If not, then in the meantime continue to use PassSync 1.4 Regards! -- Juan Carlos Camargo Carrillo. @jcarloscamargo 957-211157 , 650932877 -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] 389-console LDIF export question
On 06/27/2013 12:32 PM, Michael Lang wrote: On 06/27/2013 06:13 PM, Rich Megginson wrote: On 06/27/2013 04:57 AM, Michael Lang wrote: Dear all, I would like to clarify how the procedure to export - LDIF through the 389-console GUI is done (or how if reproduce should be done). As far as I've understood the exports on the server itself is done through creating a appropriate entry in cn=export,cn=task,cn=config For remote machines using the GUI this isn't valid as the nsFilename attribute requires a local write able location. What I've seen through looking at the LDAP protocol queries done during an export-to-ldif on console machine task is a query to the schema listing all attributeTypes which are then sent as attribute-retrieve-list in the ldap search. At least that's how I was able to reproduce the same LDIF from GUI-Console export and manually. Is this correct and should this be done in that way ? (I've noticed also the Warning: If you don't have permissions statement when using the LDIF export in the Console which more-or-less ack's my approach) Right. There is no way to do a database export to LDIF to a remote file on a remote machine. Are you trying to figure out a way to generate an LDIF file using ldapsearch that looks exactly like a database export LDIF file? Why? reason for that, I might not have file based access on the server itself but need to do backup's of the database which are not setup specific (with setup specific I mean without the right database configurations I might not be able to import the content). in this special case why I started to look into the ldif create, I had database backups but ran into a situation where my directory console was showing content but ldapsearch (and other tools/applications) where not getting any content at all. It was a strange situation and restoring the database trough restore didn't help where droping the databases and importing and LDIF was working (I still had another server running with the content). As mentioned above for the machines I have under complete access this shouldn't be the issue, but I also have other machines where I might be forced to do this through the LDAP protocol. That particular case sounds like you were missing the aci attribute which is an operational attribute. In general, if you want everything(1), you can do a search like this: ldapsearch -b dc=your,dc=suffix '(|(objectclass=*)(objectclass=ldapsubentry))' \* $OPERATIONAL_ATTRS where $OPERATIONAL_ATTRS is a list of operational attributes you can get from the schema. You'll definitely want aci in that list. If you know python, python-ldap has a nice schema parser. (1) This still won't get you everything - specifically, you won't get deleted entries and other replication metadata - If you think you need that information, add (objectclass=nsTombstone) to the search filter above. thanks for your response regards mIke thanks for any hint. regards Mike -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Problems upgrading from PassSync 1.4 to PassSync 1.5
Hi,thanks for the reply.We cannot make the upgrade to 2008 at the moment. I'll wait (*sobs*).De: "Rich Megginson" rmegg...@redhat.comPara: "General discussion list for the 389 Directory server project." 389-users@lists.fedoraproject.orgCC: "Juan Carlos Camargo" juancar...@eprinsa.esEnviados: Jueves, 27 de Junio 2013 18:09:13Asunto: Re: [389-users] Problems upgrading from PassSync 1.4 to PassSync 1.5On 06/27/2013 03:28 AM, Juan Carlos Camargo wrote:Hi list,I was expecting these new changes in PassSync (moreover those related to the 8th bit handling) , so congrats for the advances. I've found the following when I've tried the upgrade the product on one of my 2003 32bits windows controllers:1.- I cannot simply update. The installed version was 1.4. A message tells me to uninstall the previous version and reinstall.2.- If I uninstall the previous version, restart and install 1.5 from scratch, the installer stops when it tries to start the PassSync service , the rolls back the setup and does nothing. Error 1603 appears in the event viewer. I've troubleshooted this error according to Microsofts kb but none of the symptoms match my scenario.I've tried the upgrade of my other two windows2003 x32 controllers , but I'm asked to upgrade windows installer first. All in all , could those problems relate to an old windows installer version? I havent updated it yet, just needed to make sure first. Could also be related to the way the 1.5 .msi was generated? We are having problems with 1.5 on 2003. I don't suppose you can upgrade to 2008 R2? If not, then in the meantime continue to use PassSync 1.4 Regards!-- Juan Carlos Camargo Carrillo.@jcarloscamargo957-211157 ,650932877-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users-- Juan Carlos Camargo Carrillo.@jcarloscamargo957-211157 ,650932877-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
