Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
31
Installation and Upgrades / Re: ldap bind problem - authentication and egroupware contacts
« on: December 15, 2009, 02:29:13 pm »
Hi Isaac
any more thoughts on this?
any more thoughts on this?
32
Installation and Upgrades / Re: Samba shares - permissions for subdirectories.
« on: December 15, 2009, 01:53:28 pm »
is it essential that the admin and support folders are under employee?
If not you can create groups in ebox eg manager employee admin support etc and assign users to each group and then give a directory name for the group.
so if all your users are in the employee group and you assign a directory employee to the group anyone can access it.
A folder support, assigned to the support group would only allow access to support group members.
This works, I have tried it (ebox 1.3)
What may work, I have not tried, is to create shares under the file sharing tab and specify a path under ebox of employee/support for example then give explicit access rights to that share. If this won't work you should be able to do the same by using a real path under the file system instead of under ebox. This seems more work than using the groups and folders assigned to groups but may do what you want
If not you can create groups in ebox eg manager employee admin support etc and assign users to each group and then give a directory name for the group.
so if all your users are in the employee group and you assign a directory employee to the group anyone can access it.
A folder support, assigned to the support group would only allow access to support group members.
This works, I have tried it (ebox 1.3)
What may work, I have not tried, is to create shares under the file sharing tab and specify a path under ebox of employee/support for example then give explicit access rights to that share. If this won't work you should be able to do the same by using a real path under the file system instead of under ebox. This seems more work than using the groups and folders assigned to groups but may do what you want
33
Installation and Upgrades / Re: ldap bind problem - authentication and egroupware contacts
« on: December 04, 2009, 07:41:13 am »
the sync all was just a comment from an ignorant point of view - always looks simpler when you don't know what you are talking about! 
Thanks for looking into it though
Thanks for looking into it though
34
Installation and Upgrades / Re: ldap bind problem - authentication and egroupware contacts
« on: December 03, 2009, 03:01:07 pm »
I have just discovered an interesting thing, could this be the problem?
If I search my web server which is acting as the master ldap server this happens:-
Without the administrator, ebox or ldap, can I authenticate a linux box?
Without the samba details and things like login shell on the master ldap can I authenticate a linux box?
If I add PDC status to my master then the slaves can not sync to it, as only usersandgroups are allowed on the master, so I seem to have a bit of a problem.
If the master and slaves are syncing data why do they not sync it all? It seems that if all the services were on one machine then the jabber or asterisk server would not care that the ldap database contains samba or groupware details so why should modules care if they are on separate machines.
Would it not be simpler to just sync everything (good backup in case of a failed server anyway) then all the details would be there, on any server, that a linux box could authenticate to. Then perhaps they could still authenticate if the office server went down even if they lost office services. (Getting ahead of myself here as I can't even authenticate from one server yet)
If I search my web server which is acting as the master ldap server this happens:-
Code: [Select]
ldapsearch -h web -xLLL -b dc=dcmc cn=admin
dn: cn=admin,dc=dcmc
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
ldapsearch -h web -xLLL -b dc=dcmc cn=ebox
dn: cn=ebox,dc=dcmc
objectClass: organizationalRole
objectClass: simpleSecurityObject
description: eBox admin account
cn: eboxHowever if I search the office server, that is providing egroupware, file share and PDC services, then this happens:-Code: [Select]
ldapsearch -h eboxoffice -xLLL -b dc=dcmc cn=admin
ldapsearch -h eboxoffice -xLLL -b dc=dcmc cn=eboxI get the same, non event, on the server with jabber and Asterisk runningCode: [Select]
ldapsearch -h eboxcomms -xLLL -b dc=dcmc cn=admin
ldapsearch -h eboxcomms -xLLL -b dc=dcmc cn=eboxBoth these servers are running as slaves to the master and both seem to have no ebox administrator and no ldap administrator.Without the administrator, ebox or ldap, can I authenticate a linux box?
Without the samba details and things like login shell on the master ldap can I authenticate a linux box?
If I add PDC status to my master then the slaves can not sync to it, as only usersandgroups are allowed on the master, so I seem to have a bit of a problem.
If the master and slaves are syncing data why do they not sync it all? It seems that if all the services were on one machine then the jabber or asterisk server would not care that the ldap database contains samba or groupware details so why should modules care if they are on separate machines.
Would it not be simpler to just sync everything (good backup in case of a failed server anyway) then all the details would be there, on any server, that a linux box could authenticate to. Then perhaps they could still authenticate if the office server went down even if they lost office services. (Getting ahead of myself here as I can't even authenticate from one server yet)
35
Installation and Upgrades / Re: ubuntu -> ldap -> ebox connection
« on: December 03, 2009, 11:20:04 am »
were you using ebox 1.3 or 1.2?
I can't get it to work on 1.3 so wondered what you were using
I can't get it to work on 1.3 so wondered what you were using
36
Installation and Upgrades / ldap bind problem - authentication and egroupware contacts
« on: December 03, 2009, 10:02:46 am »
Hi
I have been trying for a long time to authenticate a linux box against a ebox server using ldap (a long ongoing discussion on the emai list). so far no success (ebox1.3.10)
The problem seems to be one of binding to the ldap server - my ubuntu or kubuntu machines seem to link to the server ok then try to bind with the uid of the user trying to authenticate. Back comes a failure as can't bind to ldap server: uid=my user,ou=Users,dc=mydomain.
As a distraction I went back to looking at the egroupware part of the system - up to now I have been playing with groupdav to read the address book but thought that ldap would be a better alternative. Why? Because the ebox/egroupware accounts are stored in ldap and the contacts are in sql - ok (sort of) if you access egroupware by the web interface but you can't see both account holders and contacts at the same time. In a client like Kontact you need access via groupdav and ldap to see all your addresses.
Today i installed egroupware-ldap and switched my egroupware over to store contacts in ldap
When I tried to look at the address book in egroupware, what should happen but can't bind to ldap server: uid=my user,ou=Users,dc=mydomain
So it seems there is a fundamental problem of a user binding to the ldap server in order to interogate it, either because that user wants to authenticate against the server or just to look up information in it.
Ebox itself seems to always use its own special user/password to bind, which is fine but how do I change things so that an ordinary user can bind with their password?
Without this it seems impossible to authenticate against ebox and solving this would probably mean egroupware could use ldap for contacts as well
If anyone has any idea how to change access rights on ebox, without leaving it wide open to someone mucking up the database by mistake I would love to hear from you
I have been trying for a long time to authenticate a linux box against a ebox server using ldap (a long ongoing discussion on the emai list). so far no success (ebox1.3.10)
The problem seems to be one of binding to the ldap server - my ubuntu or kubuntu machines seem to link to the server ok then try to bind with the uid of the user trying to authenticate. Back comes a failure as can't bind to ldap server: uid=my user,ou=Users,dc=mydomain.
As a distraction I went back to looking at the egroupware part of the system - up to now I have been playing with groupdav to read the address book but thought that ldap would be a better alternative. Why? Because the ebox/egroupware accounts are stored in ldap and the contacts are in sql - ok (sort of) if you access egroupware by the web interface but you can't see both account holders and contacts at the same time. In a client like Kontact you need access via groupdav and ldap to see all your addresses.
Today i installed egroupware-ldap and switched my egroupware over to store contacts in ldap
When I tried to look at the address book in egroupware, what should happen but can't bind to ldap server: uid=my user,ou=Users,dc=mydomain
So it seems there is a fundamental problem of a user binding to the ldap server in order to interogate it, either because that user wants to authenticate against the server or just to look up information in it.
Ebox itself seems to always use its own special user/password to bind, which is fine but how do I change things so that an ordinary user can bind with their password?
Without this it seems impossible to authenticate against ebox and solving this would probably mean egroupware could use ldap for contacts as well
If anyone has any idea how to change access rights on ebox, without leaving it wide open to someone mucking up the database by mistake I would love to hear from you
37
Installation and Upgrades / Re: Force sync of pending operations
« on: November 16, 2009, 10:41:04 am »
Found out what I did wrong, oops!
I thought the change from using only usersandgroups, on the server, to being able to use other services as well had long since happened.
http://forum.ebox-platform.com/index.php?topic=2027.msg8554#msg8554
BUT I just found out it has not happened yet.
ha, serves me right for making rash assumptions
38
Installation and Upgrades / Re: Force sync of pending operations
« on: November 13, 2009, 02:00:14 pm »
they are both running 1.3.9
I can not tell you what version they were running when I first linked them together and the auto sync quite rapidly synced my first user
I can not tell you what version they were running when I first linked them together and the auto sync quite rapidly synced my first user
39
Installation and Upgrades / Re: Force sync of pending operations
« on: November 13, 2009, 01:45:37 pm »
I had this working a little while ago (well the servers did sync on their own, I never tried forced sync). Now however no sync is happening, forced or otherwise.
I can not offer any help other than to show what my logs show in the hope someone else may have an answer or suggestion (assuming your problem is the same as mine)
On the master the ebox log shows a lot of lines like this
2009/11/13 15:30:05 WARN> Events.pm:526 EBox::Events::__ANON__ - model EBox::Events::Model::Watcher::LogFiltering cannot be instantiated
2009/11/13 15:30:40 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param naomi.maloda on slave eboxcomms failed
2009/11/13 15:31:14 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param todd.sprinkel on slave eboxcomms failed
2009/11/13 15:31:33 INFO> Manager.pm:97 EBox::Monitor::Measure::Manager::register - EBox::Monitor::Measure::Thermal is not enabled to collect data
2009/11/13 15:31:34 DEBUG> LogFiltering.pm:70 EBox::Events::Model::Watcher::LogFiltering::new - Missing argument: tableInfo
2009/11/13 15:31:34 WARN> Events.pm:526 EBox::Events::__ANON__ - model EBox::Events::Model::Watcher::LogFiltering cannot be instantiated
2009/11/13 15:31:47 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param mwanga.chibago on slave eboxcomms failed
2009/11/13 15:32:21 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param naomi.maloda on slave eboxcomms failed
2009/11/13 15:32:55 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param stanley.machichimi on slave eboxcomms failed
While on the slave I am seeing this in the ebox log
2009/11/13 15:31:57 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:31:57 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2563 EBox::UsersAndGroups::waitSync - Master users: 5
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2564 EBox::UsersAndGroups::waitSync - Replica users: 1
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
2009/11/13 15:32:00 ERROR> UsersAndGroups.pm:2573 EBox::UsersAndGroups::waitSync - Replication failed
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2563 EBox::UsersAndGroups::waitSync - Master users: 5
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2564 EBox::UsersAndGroups::waitSync - Replica users: 1
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2563 EBox::UsersAndGroups::waitSync - Master users: 5
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2564 EBox::UsersAndGroups::waitSync - Replica users: 1
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
I can not offer any help other than to show what my logs show in the hope someone else may have an answer or suggestion (assuming your problem is the same as mine)
On the master the ebox log shows a lot of lines like this
2009/11/13 15:30:05 WARN> Events.pm:526 EBox::Events::__ANON__ - model EBox::Events::Model::Watcher::LogFiltering cannot be instantiated
2009/11/13 15:30:40 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param naomi.maloda on slave eboxcomms failed
2009/11/13 15:31:14 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param todd.sprinkel on slave eboxcomms failed
2009/11/13 15:31:33 INFO> Manager.pm:97 EBox::Monitor::Measure::Manager::register - EBox::Monitor::Measure::Thermal is not enabled to collect data
2009/11/13 15:31:34 DEBUG> LogFiltering.pm:70 EBox::Events::Model::Watcher::LogFiltering::new - Missing argument: tableInfo
2009/11/13 15:31:34 WARN> Events.pm:526 EBox::Events::__ANON__ - model EBox::Events::Model::Watcher::LogFiltering cannot be instantiated
2009/11/13 15:31:47 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param mwanga.chibago on slave eboxcomms failed
2009/11/13 15:32:21 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param naomi.maloda on slave eboxcomms failed
2009/11/13 15:32:55 DEBUG> slave-sync:74 main::__ANON__ - Trying to run method addUser with param stanley.machichimi on slave eboxcomms failed
While on the slave I am seeing this in the ebox log
2009/11/13 15:31:57 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:31:57 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2563 EBox::UsersAndGroups::waitSync - Master users: 5
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2564 EBox::UsersAndGroups::waitSync - Replica users: 1
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:32:00 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
2009/11/13 15:32:00 ERROR> UsersAndGroups.pm:2573 EBox::UsersAndGroups::waitSync - Replication failed
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2563 EBox::UsersAndGroups::waitSync - Master users: 5
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2564 EBox::UsersAndGroups::waitSync - Replica users: 1
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:32:04 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2563 EBox::UsersAndGroups::waitSync - Master users: 5
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2564 EBox::UsersAndGroups::waitSync - Replica users: 1
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2565 EBox::UsersAndGroups::waitSync - Master groups: 13
2009/11/13 15:32:08 DEBUG> UsersAndGroups.pm:2566 EBox::UsersAndGroups::waitSync - Replica groups: 13
40
Installation and Upgrades / Re: ldap passwords and master/slave
« on: November 03, 2009, 09:55:26 am »
I have tried reinstalling my master server. This time I just installed ebox then afterwards installed usersandgroups and I was not asked about details of an ldap login.
I now have a running master but two unemployed slaves that won't accept their new master.
This time round I ended up with a file ebox-ldap.passwd containing the new master password (more than I did on the last install)
I found a file on the slave called /etc/ldap/slapd-replica.d/cn=config/olcDatabase={1}hdb.ldif that seems to contain the old master password - I really don't know what I am doing here but I edited this to contain the new password. (I restarted the server at this point - the slave)
I am obviously missing something else vital as still no sync and the master does not think it has any slaves yet
Just tried to deactivate the slave usersandgroups - save - reactivate it again - save
Still the master thinks it has not slaves.
I now have a running master but two unemployed slaves that won't accept their new master.
This time round I ended up with a file ebox-ldap.passwd containing the new master password (more than I did on the last install)
I found a file on the slave called /etc/ldap/slapd-replica.d/cn=config/olcDatabase={1}hdb.ldif that seems to contain the old master password - I really don't know what I am doing here but I edited this to contain the new password. (I restarted the server at this point - the slave)
I am obviously missing something else vital as still no sync and the master does not think it has any slaves yet
Just tried to deactivate the slave usersandgroups - save - reactivate it again - save
Still the master thinks it has not slaves.
41
Installation and Upgrades / ldap passwords and master/slave
« on: November 02, 2009, 01:09:56 pm »
Can someone help me understand what is going as I am confused over how the passwords work with ldap?
I have successfully wrecked several servers already so I have had lots of experience now at installing ebox1.3!!
Until recently I had 3 ebox servers running with one master and 2 slaves - the slaves were linked using the password stored in /var/lib/ebox/conf/ebox-ldap.passwd not the ldap admin password entered during installation.
What are these two passwords, why are they different and when is one used rather than the other? This bit really puzzles me - I am quite happy to use this one here and that one there but would like to know why (I know, curiosity killed the cat).
I was just trying to get a linux client to authenticate against the ldap master (worked ok with a windows client) but it did not work - big mistake, I ran dpkg-reconfigure slapd to find out if I was using the right dn. I was but this killed the ldap! I reinstalled ubuntu and ebox (never managed to clear out usersandgroups without a full reinstall of the server) and this time round my server asked about linking to a ldap server for authentication (never done that before). I ignored this and carried on and ended up with a working usersandgroups on my new master but now the slaves don't sync to it. I looked in /var/lib/ebox/conf to see if the password was different to last time but I have no ebox-ldap.passwd this time.
I decided to try dpkg-reconfigure slapd again and see what happened - Yup it broke usersandgroups again! oops!
So, any idea how to replace a busted ldap master and get it to sync with 2 existing slaves?
ps (I am still smiling, I know this is only beta software)
pps (I guess I am going to know a lot about ebox installation by the time I finish)
I have successfully wrecked several servers already so I have had lots of experience now at installing ebox1.3!!
Until recently I had 3 ebox servers running with one master and 2 slaves - the slaves were linked using the password stored in /var/lib/ebox/conf/ebox-ldap.passwd not the ldap admin password entered during installation.
What are these two passwords, why are they different and when is one used rather than the other? This bit really puzzles me - I am quite happy to use this one here and that one there but would like to know why (I know, curiosity killed the cat).
I was just trying to get a linux client to authenticate against the ldap master (worked ok with a windows client) but it did not work - big mistake, I ran dpkg-reconfigure slapd to find out if I was using the right dn. I was but this killed the ldap! I reinstalled ubuntu and ebox (never managed to clear out usersandgroups without a full reinstall of the server) and this time round my server asked about linking to a ldap server for authentication (never done that before). I ignored this and carried on and ended up with a working usersandgroups on my new master but now the slaves don't sync to it. I looked in /var/lib/ebox/conf to see if the password was different to last time but I have no ebox-ldap.passwd this time.
I decided to try dpkg-reconfigure slapd again and see what happened - Yup it broke usersandgroups again! oops!
So, any idea how to replace a busted ldap master and get it to sync with 2 existing slaves?
ps (I am still smiling, I know this is only beta software)
pps (I guess I am going to know a lot about ebox installation by the time I finish)
42
Installation and Upgrades / Re: 1.3 usersandgroups failure
« on: October 29, 2009, 10:51:43 am »
OK when I started typing this I was still out of luck but I have been trying things and entering the result as I have gone along (without posting) - as you will see from the very end of this post it is now working 
I have reinstalled ubuntu8.04 server on two boxes - they are totally up to date
I installed ebox - that worked on both with no errors
I then installed ebox-usersandgroups on both boxes with absolutely nothing else
It worked but with errors
Setting up ebox-network (1.3.9-0ubuntu1~ppa1~hardy1) ...
Use of uninitialized value in string eq at /usr/share/ebox-network/ebox-netcfg-import line 58, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in string eq at /usr/share/ebox-network/ebox-netcfg-import line 58, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in numeric ne (!=) at /usr/share/perl5/EBox/Network.pm line 978, <DATA> line 228.
* Restarting eBox module: network
I was prompted for and entered a password for ldap administrator (set to the same on both boxes)
apparmor is not installed on either box and /etc/init.d/apparmor has been deleted from both boxes
I set one box up as an ldap master but entered no users at this stage
I have tried to set up the other box as slave but no luck - it won't recognise the ldap password.
I have tried with the ldap admin password I entered on install, I have tried with the one in /var/lib/eboxconf/ebox-ldap.passwd (typed in and copied and pasted from this file) - each time i try to activate it fails with a password error
I have tried with the firewall enabled on both boxes (both set to accept for ldap rule) and with the firewall disabled on both boxes
FINALLY I entered a user into the master then activated the slave (ebox-ldap.passwd) with both firewalls active and ldap accepted on both.
IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(and I can now see the user I entered on the master in the edit user bit of the slave)
I hope this excursion down a lot of mysterious blind alleys helps anyone else who finds themselves stuck (or provides some entertainment to the smug)
I have no idea what broke (or what I broke) in the begining or at various stages along the way
but thanks to all those who gave assistance.
I have reinstalled ubuntu8.04 server on two boxes - they are totally up to date
I installed ebox - that worked on both with no errors
I then installed ebox-usersandgroups on both boxes with absolutely nothing else
It worked but with errors
Setting up ebox-network (1.3.9-0ubuntu1~ppa1~hardy1) ...
Use of uninitialized value in string eq at /usr/share/ebox-network/ebox-netcfg-import line 58, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in string eq at /usr/share/ebox-network/ebox-netcfg-import line 58, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in concatenation (.) or string at /usr/share/ebox-network/ebox-netcfg-import line 66, <FD> line 10.
Use of uninitialized value in numeric ne (!=) at /usr/share/perl5/EBox/Network.pm line 978, <DATA> line 228.
* Restarting eBox module: network
I was prompted for and entered a password for ldap administrator (set to the same on both boxes)
apparmor is not installed on either box and /etc/init.d/apparmor has been deleted from both boxes
I set one box up as an ldap master but entered no users at this stage
I have tried to set up the other box as slave but no luck - it won't recognise the ldap password.
I have tried with the ldap admin password I entered on install, I have tried with the one in /var/lib/eboxconf/ebox-ldap.passwd (typed in and copied and pasted from this file) - each time i try to activate it fails with a password error
I have tried with the firewall enabled on both boxes (both set to accept for ldap rule) and with the firewall disabled on both boxes
FINALLY I entered a user into the master then activated the slave (ebox-ldap.passwd) with both firewalls active and ldap accepted on both.
IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(and I can now see the user I entered on the master in the edit user bit of the slave)
I hope this excursion down a lot of mysterious blind alleys helps anyone else who finds themselves stuck (or provides some entertainment to the smug)
I have no idea what broke (or what I broke) in the begining or at various stages along the way
but thanks to all those who gave assistance.
43
Installation and Upgrades / Re: 1.3 usersandgroups failure
« on: October 29, 2009, 07:06:49 am »
Decided to start over so I tried this (from JACalvo)
sudo apt-get -y --force-yes remove --purge libldap-2.4-2 slapd ebox-.*
sudo rm -rf /var/lib/ldap* && sudo rm -rf /etc/ldap/*
sudo apt-get -y --force-yes remove --purge libebox ebox
I then deleted the folders not removed as not empty i.e.
/usr/share/ebox and /usr/share/perl5/EBox
sudo updatedb and locate ebox found these which I also removed
/var/lib/ebox
/var/lib/ebox-usersandgroups
/var/log/ebox-usersandgroups
/etc/ebox
I guess this is pretty close to a clean install
sudo apt-get install ebox-webserver ebox-software ebox-monitor ebox-usersandgroups
was chugging along fine until it did this
Setting up ebox (1.3.9-0ubunt1~ppa1~hardy1) ...
Can't locate EBox/Config.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .).
BEGIN failed--compilation aborted.
dpkg: error processing ebox (--configure):
subprocess post-installation script returned error exit status 2
after which everything fell over due to ebox not being configured (apache was left up and running and so was postgreql)
Any ideas where to go next?
sudo apt-get -y --force-yes remove --purge libldap-2.4-2 slapd ebox-.*
sudo rm -rf /var/lib/ldap* && sudo rm -rf /etc/ldap/*
sudo apt-get -y --force-yes remove --purge libebox ebox
I then deleted the folders not removed as not empty i.e.
/usr/share/ebox and /usr/share/perl5/EBox
sudo updatedb and locate ebox found these which I also removed
/var/lib/ebox
/var/lib/ebox-usersandgroups
/var/log/ebox-usersandgroups
/etc/ebox
I guess this is pretty close to a clean install
sudo apt-get install ebox-webserver ebox-software ebox-monitor ebox-usersandgroups
was chugging along fine until it did this
Setting up ebox (1.3.9-0ubunt1~ppa1~hardy1) ...
Can't locate EBox/Config.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .).
BEGIN failed--compilation aborted.
dpkg: error processing ebox (--configure):
subprocess post-installation script returned error exit status 2
after which everything fell over due to ebox not being configured (apache was left up and running and so was postgreql)
Any ideas where to go next?
44
Installation and Upgrades / Re: 1.3 usersandgroups failure
« on: October 27, 2009, 02:54:16 pm »
thanks for the hint about the init.d file - it has gone and so has that error
The password bit has me confused though
I entered a password for admin user for ldap during installation and this is what I used in the users config before trying to activate the module.
I can access the ldap server with phpldapadmin using this password but the slave does not seem to.
I have just looked in /var/lib/ebox/conf/ebox-ldap.passwd (master server) and what is there is not what I entered. I have just tried to activate the slave using this password instead but it is unable to connect using that one either.
I am not in work tomorrow so I will have another try on thursday - I may well try and remove usersandgroups from both machines and start again and see what happens. (unless you suggest something different I could try)
Peter
The password bit has me confused though
I entered a password for admin user for ldap during installation and this is what I used in the users config before trying to activate the module.
I can access the ldap server with phpldapadmin using this password but the slave does not seem to.
I have just looked in /var/lib/ebox/conf/ebox-ldap.passwd (master server) and what is there is not what I entered. I have just tried to activate the slave using this password instead but it is unable to connect using that one either.
I am not in work tomorrow so I will have another try on thursday - I may well try and remove usersandgroups from both machines and start again and see what happens. (unless you suggest something different I could try)
Peter
45
Installation and Upgrades / Re: 1.3 usersandgroups failure
« on: October 27, 2009, 11:19:21 am »
yes that is what happened