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.
Pages: [1]
1
Installation and Upgrades / Zentyal 4.0: Gateway configuration is not applied
« on: December 29, 2014, 02:57:20 pm »
Hi Guys,
I'm just trying to convince Zentyal 4.0 to use my settings for the default gateway. When Gateway-settings get applied while initial setup everything is working, when done via webinterface anytime later nothing happens. This happens for me in Zentyal 4.0.0 and 4.0.5, so updating does not help.
IP Adress and DNS Resolver Settings get applied. The gateway is listed in Admin Interface as it should be. If I login via Shell and lookup the routes it's not there. If I apply the route via "route add default gw w.x.y.z" I get connectivity, but changing any setting removes the route again, so startup workarounds are no real cure.
There is no error in zentyal.log:
Anyone experiencing the same problem ? Any Ideas ?
I'm just trying to convince Zentyal 4.0 to use my settings for the default gateway. When Gateway-settings get applied while initial setup everything is working, when done via webinterface anytime later nothing happens. This happens for me in Zentyal 4.0.0 and 4.0.5, so updating does not help.
IP Adress and DNS Resolver Settings get applied. The gateway is listed in Admin Interface as it should be. If I login via Shell and lookup the routes it's not there. If I apply the route via "route add default gw w.x.y.z" I get connectivity, but changing any setting removes the route again, so startup workarounds are no real cure.
There is no error in zentyal.log:
Quote
2014/12/29 14:38:15 INFO> GlobalImpl.pm:624 EBox::GlobalImpl::saveAllModules - Saving config and restarting services: network dns firewall
2014/12/29 14:38:15 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: network
2014/12/29 14:38:21 INFO> GlobalImpl.pm:722 EBox::GlobalImpl::saveAllModules - Changes saved successfully
Anyone experiencing the same problem ? Any Ideas ?
2
Installation and Upgrades / Re: Zentyal 4.0 504 gateway timeout
« on: November 03, 2014, 12:44:59 am »
I have hit the same problem.
3
Installation and Upgrades / Can't add Openchange Mail Services
« on: July 10, 2014, 08:32:48 pm »
I'm still struggling to get Zentyal with Openchange/sogo up and running...
What I did before: Installed Zentyal 3.5 from scratch and joind it to our AD Domain as additional DC, which works (after i worked around some samba/bind9 DNS bug...). I never got to this point,so I was in good mood. I next added Openchange Webmail Module and installed all the dependencies. I then added our maildomain foobar.de and pressed the apply button. While zentyal tried to apply my changes, the process borked out again
I get the following log entry in zentyal.log:
So Zentyal complains about an already assigned e-mail username. u.user is a quite "normal" user in our Active Directory structure. We are storing E-Mail Adresses of our users in the AD User Properties Mail Field since quite some time, since we have a lot of services querying AD via LDAP using this attribute. Does Zentyal try to auto assign a new address by some pattern to every existing user ?
What should I do to get past this step ?
What I did before: Installed Zentyal 3.5 from scratch and joind it to our AD Domain as additional DC, which works (after i worked around some samba/bind9 DNS bug...). I never got to this point,so I was in good mood. I next added Openchange Webmail Module and installed all the dependencies. I then added our maildomain foobar.de and pressed the apply button. While zentyal tried to apply my changes, the process borked out again
I get the following log entry in zentyal.log:
Code: [Select]
2014/07/10 20:10:13 DEBUG> Samba.pm:3063 EBox::Samba::checkMailNotInUse - Address user@foobar.de is already in use by the Benutzer u.user at Address user@foobar.de is already in use by the Benutzer u.user at /usr/share/perl5/EBox/Samba.pm line 3063
EBox::Samba::checkMailNotInUse('EBox::Samba=HASH(0x5e5bbb0)', 'user@foobar.de', undef) called at /usr/share/perl5/EBox/Mail.pm line 1983
EBox::Mail::checkMailNotInUse('EBox::Mail=HASH(0x5d4f5d8)', 'user@foobar.de') called at /usr/share/perl5/EBox/MailUserLdap.pm line 106
EBox::MailUserLdap::setUserAccount('EBox::MailUserLdap=HASH(0x793a248)', 'EBox::Samba::User=HASH(0x9b2cd50)', 'user', 'foobar.de') called at /usr/share/perl5/EBox/MailUserLdap.pm line 76
EBox::MailUserLdap::setupUsers('EBox::MailUserLdap=HASH(0x793a248)') called at /usr/share/perl5/EBox/Mail.pm line 414
EBox::Mail::setupLDAP('EBox::Mail=HASH(0x5d4f5d8)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 268
EBox::Module::LDAP::_performSetup('EBox::Mail=HASH(0x5d4f5d8)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 253
EBox::Module::LDAP::_regenConfig('EBox::Mail=HASH(0x5d4f5d8)') called at /usr/share/perl5/EBox/Module/Kerberos.pm line 368
EBox::Module::Kerberos::_regenConfig('EBox::Mail=HASH(0x5d4f5d8)') called at /usr/share/perl5/EBox/Module/Base.pm line 234
eval {...} at /usr/share/perl5/EBox/Module/Base.pm line 233
EBox::Module::Base::save('EBox::Mail=HASH(0x5d4f5d8)') called at /usr/share/perl5/EBox/GlobalImpl.pm line 651
eval {...} at /usr/share/perl5/EBox/GlobalImpl.pm line 650
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x48d86c8)', 'progress', 'EBox::ProgressIndicator=HASH(0x48d4908)') called at /usr/share/perl5/EBox/Global.pm line 95
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x4903090)', 'progress', 'EBox::ProgressIndicator=HASH(0x48d4908)') called at /usr/share/zentyal/global-action line 32
So Zentyal complains about an already assigned e-mail username. u.user is a quite "normal" user in our Active Directory structure. We are storing E-Mail Adresses of our users in the AD User Properties Mail Field since quite some time, since we have a lot of services querying AD via LDAP using this attribute. Does Zentyal try to auto assign a new address by some pattern to every existing user ?
What should I do to get past this step ?
4
Installation and Upgrades / Re: Trying to join 3.5 as Additional DC doesn't suceed
« on: June 18, 2014, 01:06:15 pm »5
Installation and Upgrades / Re: Trying to join 3.5 as Additional DC doesn't suceed
« on: June 18, 2014, 10:34:37 am »
Of course. I'll just need an hour to finish other work first 
6
Installation and Upgrades / Re: Trying to join 3.5 as Additional DC doesn't suceed
« on: June 17, 2014, 06:48:13 pm »
Server and Domainlevel is 2008R2.
7
Installation and Upgrades / Trying to join 3.5 as Additional DC doesn't suceed
« on: June 17, 2014, 12:28:02 pm »
Hi guys,
Our "Simple" Scenario: We're seeking for a new groupware solution, since our old one is hopelessly outdated. We would like to have a solution integrated to our existing Microsoft AD to ease usermanagement. Sogo does look like a decent solution to our needs, so I try to give it a whirl. I started evaluating Zentyal 3.4, but 3.4 doesn't seem to really support integration into an existing AD Infrastructure, so I gave 3.5 a whirl, or at least i tried multiple times.
Trying out different Daily Builds yielded different results, but none was a state which could be defined as working
I learned: Trying to setup Zentyal while installing is a bad idea, which (currently) never works and fails in early stages. I got all different kinds of errors, so I gave up on that. Trying to setup Zentyal after Installation gives better results, but nonetheless fails.
I'm able to workaround some errors, but setting up bind gives me hard troubles all the time and automatic setup of bind failed miserably in every occurence. After joining samba to the AD zentyal tries to setup bind and afterwards restarts it, which fails. When I try to restart bind to get some meaningful error message after the automatic process fails, bind restarts flawlessly... Needless to say, that because of failed nsupdate commands inbetween the state of the DNS Zones are not as desired.
Has anyone successfully gotten a Zentyal 3.5 box joined to an AD Domain ? Any hints ?
Our "Simple" Scenario: We're seeking for a new groupware solution, since our old one is hopelessly outdated. We would like to have a solution integrated to our existing Microsoft AD to ease usermanagement. Sogo does look like a decent solution to our needs, so I try to give it a whirl. I started evaluating Zentyal 3.4, but 3.4 doesn't seem to really support integration into an existing AD Infrastructure, so I gave 3.5 a whirl, or at least i tried multiple times.
Trying out different Daily Builds yielded different results, but none was a state which could be defined as working
I learned: Trying to setup Zentyal while installing is a bad idea, which (currently) never works and fails in early stages. I got all different kinds of errors, so I gave up on that. Trying to setup Zentyal after Installation gives better results, but nonetheless fails.
I'm able to workaround some errors, but setting up bind gives me hard troubles all the time and automatic setup of bind failed miserably in every occurence. After joining samba to the AD zentyal tries to setup bind and afterwards restarts it, which fails. When I try to restart bind to get some meaningful error message after the automatic process fails, bind restarts flawlessly... Needless to say, that because of failed nsupdate commands inbetween the state of the DNS Zones are not as desired.
Has anyone successfully gotten a Zentyal 3.5 box joined to an AD Domain ? Any hints ?
8
German / Re: Kann Zentyal mein IPfire ablösen
« on: May 19, 2014, 04:39:23 pm »
Du fährst sicher geschickter damit eine gewissen funktionale Trennung beizubehalten, ich würde da IPFire durchaus beibehalten an deiner Stelle und neben einer Lösung auf dem Host z.B Ipfire mit kvm virtualisieren. Zuviele Lösungen für einzelne Probleme auf einer Kiste neigt zu kuriosen Seitenwirkungen. Dabei würde ich dann auf dem Host denke ich Zentyal nehmen, mit Ubuntu als Basis von Zentyal bist du relativ flexibel im Setup.
9
German / Re: Bekomme Netzwerkfreigabe nicht aktiviert (Second Domain Controller)
« on: May 19, 2014, 04:32:36 pm »
Dagegen hilft ein berherzter Anschub im Terminal als Superuser:
/usr/share/zentyal/unconfigure-module users
/usr/share/zentyal/purge-module users
Danach neu versuchen und es sollte gehen. Hatte dasselbe Problem, habs tief im Forum gefunden
/usr/share/zentyal/unconfigure-module users
/usr/share/zentyal/purge-module users
Danach neu versuchen und es sollte gehen. Hatte dasselbe Problem, habs tief im Forum gefunden
Pages: [1]