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 - centaur5

Pages: 1 [2] 3 4
Installation and Upgrades / proxy fails to start
« on: September 07, 2010, 05:39:55 am »
I anxiously awaited this weekend to upgrade my server to Zentyal 2.0 but ran across an error with the proxy that will make me hold off a bit.  I'm guessing it has something to do with an import because I tested 1.5/2.0 on a couple different servers to see if previous problems with the proxy were eliminated and the proxy seemed to function on my test boxes.  I exported the configuration on my 1.4 server and imported it after installing Zentyal Gateway 2.0.1 on top of Ubuntu Server 64 bit.  I've installed all updates available today.  After importing the configuration (which for some reason gave a few errors while saving so I had to keep clicking save til it made it all the way through) everything seems to be functional thus far except for the proxy.  I checked syslog and noticed the following error:

Sep  6 18:27:42 hostname squid[25767]: Bungled squid.conf line 46: acl timeHours_obje4191 time HASH(0x806b998)-HASH(0x806ecf0)

So I decided to comment out line 46 but then received this error:

Sep  6 18:29:16 hostname squid[26513]: Bungled squid.conf line 113: http_access allow obje4191 timeHours_obje4191

After commenting out line 46, 113, and 114 I can now start squid and everything seems to be okay.  As stated before I'm assuming this has something to do with the import as I'm aware a fresh install doesn't have this problem.  If you need further data let me know.  Otherwise, I guess I'll have to decide whether to manually enter all my data into Zentyal 2.0.

News and Announcements / Re: Zentyal 2.0-rc2 released!
« on: August 27, 2010, 06:59:51 pm »
Thank you very much for making such a rapid decision and getting a beta out for a replacement groupware solution so quickly!  I'm very impressed and quite frankly didn't expect such quick development and was trying to plan on what I would integrate by myself.  I looked at Zarafa last week when it was mentioned for a replacement and it appears to be a wonderful solution that will probably finally help me finish what I've been wanting to do for some time.  I'm going to have a look at this new module and since your company is showing such a sincere effort for a complete small business solution I'll be investing in subscriptions to show my support!

I would hope that Citadel isn't the choice.  I used Citadel before I started using Ebox and it was a great product but doesn't have very many mature methods to sync with Evolution or Thunderbird as a complete groupware solution.  The web interface is also quite confusing for most people so using that instead of a client isn't fun.

Installation and Upgrades / Re: Zarafa - ebox
« on: August 24, 2010, 09:30:45 pm »
I completely agree with Oceanwatcher on that one.  I've been waiting for a decent groupware solution that will preferably work with Evolution's notes and tasks.  Almost anything will work with Thunderbird mail/calendar but notes and tasks would be a real win to have.  Also pushing to phones is something I intend to do.  If Zarafa has those features and is easier to integrate with Ebox then I vote for it.  However, if Zimbra is the only solution then it should be the one.

My concern is this; how long after we choose the replacement whether it be Zimbra or Zarafa are we expecting to have a usable module?  I used to manually configure all the services offered by Ebox a couple years ago.  Now that I use Ebox I don't want to manually configure services because if I manually modify a file that I don't know Ebox depends on then all my changes will be gone.  I've been using Egroupware for a year now and although I would rather have better client sync support on Linux I've been able to deal with it.  I don't want to use a web interface for groupware.  I've been using the Ebox platform for a couple years and have anticipated every release hoping for a complete solution for everything I need and for more stable functionality.  After 2.0 is released I was going to see if it was good enough for me to stick with instead of finding an alternative project.  If I did decide to keep Ebox I had every intention of purchasing support to help contribute.  I understand this move needed to be done but if a new solution takes too long to implement I'm not sure what I'll do. 

appears to be fixed by this duplicate post

Installation and Upgrades / Re: HTTP-Proxy
« on: August 05, 2010, 10:11:07 pm »
I decided to wait a couple days to see if the proxy would stop again since other people were complaining that it wouldn't start at boot and the problem I was having is with the proxy randomly stopping.  For the past 2 days I have not had the proxy stop so I think this is fixed!  Thanks for your work!

Installation and Upgrades / Re: HTTP-Proxy
« on: July 29, 2010, 05:23:48 pm »
I decided to install Ebox 1.5.8 on a 10.04 test machine to find out for myself if the proxy is still crashing and he first couple days it was fine but now it crashes at least once a day as usual.  Is there anything I can paste to help track the bug and get it fixed?

Installation and Upgrades / Re: HTTP-Proxy
« on: July 23, 2010, 08:16:56 pm »
I filed a duplicate bug about this a couple months ago.  I noticed that new squid packages were released in 1.5 3 days ago.  Could anybody verify if the problem is now fixed?  I would like to install 1.5 in production this weekend but that problem is preventing me from doing so.

Out of the 3 users I setup on my master using Ebox 1.4.7 only one of them on the slave has a nonexistent shell and home directory when typing 'getent passwd'.  I don't want to have to delete the users and add them again since I would lose the home directories and mail boxes.  What is the best way that I can change the login shell and home directory information on the slave machine?  Also if I change the login shell on the master will it take place on the slave?

I noticed a new squid package 1.5.3 updated yesterday.  Does that mean you were able to reproduce the issue and it's fixed?

I have to login to Ebox and start it manually.  There have been a couple times that when doing so it came up with an error that saving a module failed.  Most times it will start fine though without errors.

I'm running ebox-squid-1.5.2 on ebox core 1.5.1 and I have the transparent proxy enabled.  Squid will stop at least 2 times a day and sometimes more.  I can't find any log file that is specific to only squid errors or crashes so if you need more info let me know what you want uploaded.

Installation and Upgrades / Re: Master/Slave 1.5 on 10.04
« on: May 28, 2010, 06:20:22 pm »
I successfully got the above error messages fixed by doing the usersandgroups cleanup suggested in the documentation and then manually removing /var/lib/ebox/conf/userjournal/servername.  The other trick on the error when clicking on the PDC tab was I had to uncheck the Enable PDC option under file sharing before removing the module and doing the usersandgroups cleanup.  However, now that I have the master and slave successfully connected for some reason it only synchronized all but one of my groups and although the slave shows all the users and groups in Ebox I still can't see any of the users when typing 'getent passwd' so the users and still not usable on the slave.  Any suggestions on how this can be fixed now that I got rid of all the error messages?

Installation and Upgrades / Re: Master/Slave 1.5 on 10.04
« on: May 27, 2010, 09:43:10 am »
I did the userandgroups-reinstall instructions per the documentation and I now successfully have the slave syncing groups from the master but users are no longer created on the master even though they show in Ebox that they exist they don't show in /etc/passwd.  I now get the following error when I go to the PDC tab under File Sharing:

Unknown error at EBox::Ldap::getAttribute invalid DN at /usr/share/perl5/EBox/ line 719 EBox::Ldap::_errorOnLdap('Net::LDAP::Search=HASH(0x7f7a4a8c0990)', 'HASH(0x7f7a47eca048)') called at /usr/share/perl5/EBox/ line 358 EBox::Ldap::search('EBox::Ldap=HASH(0x7f7a49ab2bf8)', 'HASH(0x7f7a47eca048)') called at /usr/share/perl5/EBox/ line 599 EBox::Ldap::getAttribute('EBox::Ldap=HASH(0x7f7a49ab2bf8)', 'sambaDomainName=,dc=shemail,dc=nac,dc=bogus', 'sambaMinPwdLength') called at /usr/share/perl5/EBox/Samba/Model/ line 211 EBox::Samba::Model::PDC::row('EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)') called at (eval 1852) line 34 HTML::Mason::Commands::__ANON__('model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'action', ...) called at /usr/share/perl5/HTML/Mason/ line 135 HTML::Mason::Component::run('HTML::Mason::Component::Subcomponent=HASH(0x7f7a4a7b5f18)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', ...) called at /usr/share/perl5/HTML/Mason/ line 1284 eval {...} called at /usr/share/perl5/HTML/Mason/ line 1274 HTML::Mason::Request::comp(undef, undef, 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', ...) called at /usr/share/ebox/templates/ajax/modelViewer.mas line 149 HTML::Mason::Commands::__ANON__('model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)') called at /usr/share/perl5/HTML/Mason/ line 135 HTML::Mason::Component::run('HTML::Mason::Component::Subcomponent=HASH(0x7f7a4a831f88)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)') called at /usr/share/perl5/HTML/Mason/ line 1284 eval {...} called at /usr/share/perl5/HTML/Mason/ line 1274 HTML::Mason::Request::comp(undef, undef, 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)') called at /usr/share/ebox/templates/ajax/modelViewer.mas line 69 HTML::Mason::Commands::__ANON__('model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'hasChanged', undef) called at /usr/share/perl5/HTML/Mason/ line 135 HTML::Mason::Component::run('HTML::Mason::Component::Subcomponent=HASH(0x7f7a4a832180)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'hasChanged', undef) called at /usr/share/perl5/HTML/Mason/ line 1284 eval {...} called at /usr/share/perl5/HTML/Mason/ line 1274 HTML::Mason::Request::comp(undef, undef, 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'hasChanged', undef) called at /usr/share/ebox/templates/ajax/modelViewer.mas line 28 HTML::Mason::Commands::__ANON__('data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'action', 'view', 'editid', ...) called at /usr/share/perl5/HTML/Mason/ line 135 HTML::Mason::Component::run('HTML::Mason::Component::FileBased=HASH(0x7f7a4a832300)', 'data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'action', 'view', ...) called at /usr/share/perl5/HTML/Mason/ line 1284 eval {...} called at /usr/share/perl5/HTML/Mason/ line 1274 HTML::Mason::Request::comp(undef, undef, undef, 'data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', ...) called at /usr/share/perl5/HTML/Mason/ line 475 eval {...} called at /usr/share/perl5/HTML/Mason/ line 475 eval {...} called at /usr/share/perl5/HTML/Mason/ line 425 HTML::Mason::Request::exec('HTML::Mason::Request=HASH(0x7f7a4a8a7690)') called at /usr/share/perl5/HTML/Mason/ line 342 HTML::Mason::Interp::exec(undef, undef, 'data', undef, 'dataTable', 'HASH(0x7f7a4942f728)', 'model', 'EBox::Samba::Model::PDC=HASH(0x7f7a494178c8)', 'action', ...) called at /usr/share/perl5/EBox/CGI/ line 141 EBox::CGI::Base::_body('EBox::CGI::Controller::DataTable=HASH(0x7f7a4a888e90)') called at /usr/share/perl5/EBox/CGI/ line 89 EBox::CGI::ClientRawBase::_print('EBox::CGI::Controller::DataTable=HASH(0x7f7a4a888e90)') called at /usr/share/perl5/EBox/CGI/Controller/ line 292 EBox::CGI::Controller::DataTable::_print('EBox::CGI::Controller::DataTable=HASH(0x7f7a4a888e90)') called at /usr/share/perl5/EBox/CGI/ line 201 EBox::CGI::ClientRawBase::run('EBox::CGI::Controller::DataTable=HASH(0x7f7a4a888e90)') called at /usr/share/perl5/EBox/CGI/ line 120 EBox::CGI::Run::run('EBox::CGI::Run', 'Samba/Controller/PDC', '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(0x7f7a4a883a78)') called at /usr/lib/perl5/ModPerl/ line 204 eval {...} called at /usr/lib/perl5/ModPerl/ line 204 ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7f7a4a8a6e20)') called at /usr/lib/perl5/ModPerl/ line 170 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7f7a4a8a6e20)') called at /usr/lib/perl5/ModPerl/ line 31 ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7f7a4a883a78)') called at -e line 0 eval {...} called at -e line 0

I also get the following errors when trying to add a new user:

group name Domain Admins does not exist.

An internal error related to a template has occurred. This is a bug, relevant information can be found in the logs.

Pages: 1 [2] 3 4