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.


Messages - Andy

Pages: [1] 2
1
Got a solution:

I altered the file
Code: [Select]
/usr/share/ebox/stubs/dns/named.conf.local.mas
and inserted the static information for the local domain:

Code: [Select]
zone "domain.local" {
        type slave;
        masters { 192.xxx.xxx.xxx; };
        file "/etc/bind/slave.domain.local";
};

Then I restarted DNS in the eBox webinterface. The file /etc/bind/named.conf.local was updated and the file /etc/bind/slave.domain.local appeared.

The owner of the slave-file must be "bind:bind"! Therefore it was root:root (and the file was named db.... - that didn't work).

I also entered the eBox IP in the local nameservers DNS settings (Windows 2000 Server) as nameserver, so that zone transfer is possible.
That's it!


2
Hello everybody,

I set up eBox (Core Version 1.48) as a caching DNS server. That works.

But I also want to use it as a slave for an existing domain in the local network.
I tried to setup the domain under "Infrastructure" - "DNS", inserting the existing domain name and the master nameserver for that domain. I also set the master's hostname as the nameserver for this domain. That didn't work so I deleted that domain.

In /usr/share/ebox/stubs/dns/named.conf.options.mas I set the forwarders to external nameserver and the LAN's existing master nameserver.
But when I try to resolve hostnames from the local network eBox asks the external DNS and I'm getting the wrong ip.

So how can I use eBox to resolve local hostnames (as a slave) asking the master in the local network AND to execute recursive queries asking external DNS?

And where does eBox save the dns cache file?

Kind regards,
Andy

3
Hello!

Any news on this topic? I have the same error, too.

/var/log/ebox-usercorner/error.log
says: Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/EBox/UserCorner/Auth.pm line 198.

The line 198 in Auth.pm:
Code: [Select]
$log->warn("Failed login from: $ip");from Method authen_cred

/var/log/ebox-usercorner/ebox.log
says:  Auth.pm:198 EBox::UserCorner::Auth::authen_cred - Failed login from:

Now I inserted the following line to Auth.pm:
Code: [Select]
$log->warn("self: $self , r: $r , user: $user , passwd: $passwd");
And after restarting it returned in the logs:
Code: [Select]
Auth.pm:198 EBox::UserCorner::Auth::authen_cred - self: EBox::UserCorner::Auth , r: Apache2::RequestRec=SCALAR(0x92e2188) , user: username , passwd: secret
Username and password are correct. But I don't what the other values stand for.
Does this help?

Greetz,
Andreas

4
Installation and Upgrades / Re: 1.4 slave usersandgroups nasty bug
« on: March 19, 2010, 09:13:40 am »
Hello Saturn,

can you explain me the workaround?

Do I have to watch for the sequence (activating users&groups, adding slave, creating users, activating filesharing and so on)?

5
Installation and Upgrades / Re: 1.4 slave usersandgroups nasty bug
« on: March 18, 2010, 07:06:11 pm »
Yes, same problem.
But look in Reply # 46 by "eboxbuggy":

He wrote that it's possible to add users with Samba enabled. It seems that only the sync queue had to be cleared.
I did that also and the pending operations disappeared. But the error still appears when I try to edit an "after-filesharing"-user...

I looked after the homedirs of the problem-users, they doesn't exist! But I didn't found something about that in the logs...

I like ebox, it's really a great software. But if it works I'll love it   ;D

6
Installation and Upgrades / Re: 1.4 slave usersandgroups nasty bug
« on: March 18, 2010, 04:59:06 pm »
Sorry, I don't understand this.

Why should you now be able to create users (and groups) on the master and sync it without any problems?

The users I created before activating shares on the slave are editable on the slave.
But after activating I create an user on the master, the master tries to load (or sync) without end.
On the slave I can see the new users but on the slave running Samba I get that nasty bug message.

I installed all servers with ebox 1.4 from CD an updated all to 1.43 before creating users or activating slaves...

Can you help me?


7
Hi everybody,

I tried to set up two master/slave servers with ebox 1.3.

After a few problems someone told me that it's not possible to run another "usersandgroups-depending" module on the master.
Does this restriction still exists in version 1.4?
Or it is possible to run e.g. samba-shares on the master, too (and e.g. email on the slave...)?

Regards,
Andreas

8
Got it!!

It was necessary to insert the slave's ip-address and hostname in  /etc/hosts  on the master


The synchronisation now worked, but a few operations are still in pending state.
How can I delete them?

I clicked "sync now" and some of the operations disappeared but a few are still there...
Where should I look after that?

Kind regards,
Andreas

9
Hello!

I'm still trying to get this master/slave thing running on eBox 1.3.15.

I followed step-by-step the HowTo you can find here:
http://trac.ebox-platform.com/wiki/Document/HowTo/EBoxMasterSlaveSetup

OK, and here's the problem:
I set up the master and at the point "If everything has gone well, you are now ready to add new users and groups to the master LDAP. " in the HowTo I created 2 users and 2 groups.

As I finished the Howto everything seems to work fine. The created users and groups had been synchronised to the slave where I can see AND edit them. Fine!

But when I create a user after that I'm not able to edit him on the slave. By clicking "edit" this message appears:
Code: [Select]
A really nasty bug has occurred
Exception
Unknown error at EBox::SambaLdapUser::_getAccountFlags Referral received
Trace
Unknown error at EBox::SambaLdapUser::_getAccountFlags Referral received at /usr/share/perl5/EBox/Ldap.pm line 684
EBox::Ldap::_errorOnLdap('Net::LDAP::Search=HASH(0xa89dfec)', 'HASH(0xa7bb7fc)') called at /usr/share/perl5/EBox/Ldap.pm line 323
EBox::Ldap::search('EBox::Ldap=HASH(0xa6ddf94)', 'HASH(0xa7bb7fc)') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 848
EBox::SambaLdapUser::_getAccountFlags('EBox::SambaLdapUser=HASH(0xa81ca54)', 'jdoe') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 858
EBox::SambaLdapUser::_userSharing('EBox::SambaLdapUser=HASH(0xa81ca54)', 'jdoe') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 459
EBox::SambaLdapUser::_userAddOns('EBox::SambaLdapUser=HASH(0xa81ca54)', 'jdoe') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 2097
EBox::UsersAndGroups::allUserAddOns('EBox::UsersAndGroups=HASH(0x9fdc2cc)', 'jdoe') called at /usr/share/perl5/EBox/CGI/UsersAndGroups/User.pm line 50
EBox::CGI::UsersAndGroups::User::_process('EBox::CGI::UsersAndGroups::User=HASH(0xa80d23c)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::UsersAndGroups::User=HASH(0xa80d23c)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'UsersAndGroups/User', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xa7fc5b0)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xa82d57c)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa82d57c)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa7fc5b0)') called at -e line 0
eval {...} called at -e line 0

The first 2 created users are still editable on the slave.
On the master you can see at the point "Slave Status" that the operation of the "problem-user" is still pending.

I tried the following:
- disabled module FileSharing on the slave
- disabled module usersandgroups on the slave
- created a new user on the master
- enabled usersandgroups on the slave

Same problem. The created user is not editable on the slave. The last created user still appears in "pending" on the master's slave status.

I think this is a bug. There must be the possibility to create users when you set up the slave yet. Can someone please give me a hint?

10
EDIT:

Modules enabled:

Master:
- Network
- Firewall (Packetfilter was configured for LDAP)
- Logs
- Users and Groups

Slave:
- Network
- Firewall
- Logs
- Users and Groups
- File Sharing

I remember when installing ebox-samba on the slave I was asked if local root should become LDAPadmin (I acked with yes) and for a bindn and a password.
Was that wrong? I guess those settings are overwritten by ebox, right?

11
Hello!

Getting tired of former bad configurations I installed my two servers new with the 1.3.15-installer.
I followed the howto here: http://trac.ebox-platform.com/wiki/Document/HowTo/EBoxMasterSlaveSetup

After configuration I was able to create users and groups on the master and I could see them on the slave, but:
- in the master's slave status there are the addUser / addGroup-operations still pending
- when I try to edit user on the slave there are two error messages:
Code: [Select]
Gruppenname Administrators gibt es nicht (means: group name administrators doesn't exist).
An internal error related to a template has occurred. This is a bug, relevant information can be found in the logs.

I hate the second message, it appears to often.
So does anybody has a hint where I can look to solve the problem?

As I metioned, it has been a new clean install on both servers...


12
Before I read this I activated File- and Printersharing on the master, and Email on the slave.
Now it's not possible to access Users or Groups on the slave anymore.

The same stupid error message appears:
Code: [Select]
An internal error has occurred. This is most probably a bug, relevant information can be found in the logs.It would be nice to know in WHICH log I have to look.

In /varlog/ebox/ebox.log  on the slave I found some errors:
Code: [Select]

2010/01/21 10:13:26 ERROR> Ldap.pm:682 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=Groups,dc=ebox,dc=domain,dc=tst',
          'attrs' => [
                       'cn',
                       'gidNumber',
                       'description'
                     ],
          'filter' => '(objectclass=*)',
          'scope' => 'one'
        };
2010/01/21 10:13:26 ERROR> Ldap.pm:684 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::groups Referral received
2010/01/21 10:17:03 INFO> Service.pm:615 EBox::Module::Service::restartService - Skipping restart for events as it's disabled
2010/01/21 10:17:20 ERROR> Ldap.pm:682 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=Users,dc=ebox,dc=domain,dc=tst',
          'attrs' => [
                       'uid',
                       'uidNumber'
                     ],
          'filter' => 'objectclass=*',
          'scope' => 'one'
        };
2010/01/21 10:17:20 ERROR> Ldap.pm:684 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::uidList Referral received
2010/01/21 10:18:19 INFO> Service.pm:619 EBox::Module::Service::restartService - Restarting service for module: usercorner
2010/01/21 10:18:48 ERROR> Ldap.pm:682 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=Users,dc=ebox,dc=domain,dc=tst',
          'attrs' => [
                       'uid',
                       'uidNumber'
                     ],
          'filter' => 'objectclass=*',
          'scope' => 'one'
        };
2010/01/21 10:18:48 ERROR> Ldap.pm:684 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::uidList Referral received

Now I'm a little bit confused:
ebox is a user but also the name of the master machine.
Does the BaseDN (cn=) contain the machine's name or the user's name?

Is it possible to get the slave working again?
And where can I find (in the filesystem) the LDAP-server's configuration?
And where's the LDAP-client's config?


13
Hello!

I set up the master and slave again and replication seems to work.
On the slave I can see the user & groups I created on the master.

But what do you mean with:
Quote
The master can only contain 'usersandgroups', and no other modules that use groups such as mail or samba.

You can use the master only for administrate the users & groups? No file- and/or printersharing?
My idea was to use the master as a PDC with Samba for file- and printer-sharing and a slave for communication (gateway, proxy, mail). The users can fetch their mail from the slave and in the background the authentication aould be checked via LDAP on the master.
Am I wrong?

By the way:
I tried to use the UserCorner on the slave, but whe I try to log on with a user that exists in LDAP the UserCorner says "Incorrect password".
But on the master it worked...

14
Installation and Upgrades / Re: Slave tries to connect to local LDAP
« on: January 20, 2010, 04:39:24 pm »
Well it seems to work.
I defined a new FQDN in the master, saved, and activated usersandgroups.
The slave was able to connect to the master, using the password I found under the masters "LDAP Info".

But tell me:
How can I change the slave's state when I ever should need it?
Say, I will give up the master-test-server and I'm setting up a new master, what should I then do with the slave?

EDIT:
Great!!  It works! Master is syncing immediately. Now I'm trying to get Samba and Email running...

15
Installation and Upgrades / Re: Slave tries to connect to local LDAP
« on: January 20, 2010, 04:14:57 pm »
Thank you for that. Is that pinned somewhere? I guess it will be interesting to more users...

I set up the servers again, ebox is running, but:
How can I reconfigure the LDAP / slapd service?

When I run
Code: [Select]
dpkg-reconfigure slapd I'll only be asked for
- set up a new database configuration
- if the LDAP database should be deleted if slapd will be removed
- if I allow LDAP_v2

But nothing about admin's password and FQDN and so on.
How can I run that configuration again?

Pages: [1] 2