Messages

31

Installation and Upgrades / Re: Master/Slave 1.5 on 10.04

« on: May 26, 2010, 12:33:24 am »

My master now sees the slave.  I still can't enable the Users and Groups module on the slave cause it gives the error listed above.

32

Installation and Upgrades / Master/Slave 1.5 on 10.04

« on: May 24, 2010, 11:00:46 pm »

I have 2 fresh installs of 10.04 and I'm trying to enable master/slave between them.  For some reason I don't have the Mode option under Users and Groups which I'm not sure if that's typical for the master.  However, on the slave when I tried to enable the module after typing in the master information I get the following error:

A really nasty bug has occurred
Exception
Failed to enable: Replication failed
Trace
Failed to enable: Replication failed at /usr/share/perl5/EBox/CGI/ServiceModule/ConfigureModuleController.pm line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x7f...') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x7f...') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', '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(0x7f8a25dd8cf0)') 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(0x7f8a25ddc270)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7f8a25ddc270)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7f8a25dd8cf0)') called at -e line 0
eval {...} called at -e line 0


All packages are up to date as of this writing.  I might be doing something wrong but in case it's a bug I figured I would post it. 

33

News and Announcements / Re: New eBox 1.4-2 installer released!

« on: May 24, 2010, 03:29:34 am »

When you say that you've added refresh patterns for Ubuntu and windows updates does that mean you used squid to cache them so apt-cacher (or any other alternative) is no longer necessary?  If so, have the 1.5 development packages been built on top of 1.4-2 so they include the features already?

34

Installation and Upgrades / Re: Ebox-firewall 1.5 unable to start on 10.04

« on: May 24, 2010, 03:10:54 am »

Problem is now fixed with the new updated package I upgraded today.  Thanks very much for the fast response and getting it patched!

35

Installation and Upgrades / Re: Squid 1.5 on 10.04

« on: May 24, 2010, 03:03:03 am »

Problem is now fixed with the new updated package I upgraded today.  Thanks very much for the fast response and getting it patched!

36

Installation and Upgrades / Ebox-firewall 1.5 unable to start on 10.04

« on: May 23, 2010, 12:04:58 pm »

I just did a new server install of 10.04 and have been experiencing issues with the transparent proxy not working.  I also then noticed that other devices that were allowed rules to communicate with the outside world weren't either.  As I looked further into it I found that the ebox-firewall isn't successfully loading and explains why those firewall rules aren't working.  Here is the error I'm getting:

2010/05/23 03:57:22 DEBUG> ModelProvider.pm:246 EBox::Model::ModelProvider::AUTOLOAD - Trace begun at /usr/share/perl5/EBox/Model/ModelProvider.pm line 245
EBox::Model::ModelProvider::AUTOLOAD('EBox::OpenVPN=HASH(0xa2b9f48)') called at /usr/share/perl5/EBox/Iptables.pm line 892
EBox::Iptables::_vpnIfaces at /usr/share/perl5/EBox/Iptables.pm line 672
EBox::Iptables::_iexternalCheckInit('EBox::Iptables=HASH(0x9aa6a00)') called at /usr/share/perl5/EBox/Iptables.pm line 691
EBox::Iptables::_iexternal('EBox::Iptables=HASH(0x9aa6a00)') called at /usr/share/perl5/EBox/Iptables.pm line 528
EBox::Iptables::start('EBox::Iptables=HASH(0x9aa6a00)') called at /usr/share/perl5/EBox/Firewall.pm line 259
EBox::Firewall::_enforceServiceState('EBox::Firewall=HASH(0x9a73940)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 610
EBox::Module::Service::_regenConfig('EBox::Firewall=HASH(0x9a73940)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 635
EBox::Module::Service::__ANON__ at /usr/share/perl5/Error.pm line 416
eval {...} at /usr/share/perl5/Error.pm line 408
Error::subs::try('CODE(0x9aa6460)', 'HASH(0x9aa6600)') called at /usr/share/perl5/EBox/Module/Service.pm line 642
EBox::Module::Service::restartService('EBox::Firewall=HASH(0x9a73940)') called at /etc/init.d/ebox line 91
main::__ANON__ at /usr/share/perl5/Error.pm line 416
eval {...} at /usr/share/perl5/Error.pm line 408
Error::subs::try('CODE(0x8958580)', 'HASH(0x9a7a3d8)') called at /etc/init.d/ebox line 102
main::moduleAction('firewall', 'restartService', 'restart') called at /etc/init.d/ebox line 158
main::moduleRestart('firewall') called at /etc/init.d/ebox line 191
main::main at /etc/init.d/ebox line 208
2010/05/23 03:57:22 ERROR> ModelProvider.pm:248 EBox::Model::ModelProvider::AUTOLOAD - Undefined method initializeInterfaces
2010/05/23 03:57:22 ERROR> Service.pm:638 EBox::Module::Service::__ANON__ - Error restarting service: Undefined method initializeInterfaces

37

Installation and Upgrades / Squid 1.5 on 10.04

« on: May 23, 2010, 06:21:26 am »

I just installed a fresh 10.04 server and whenever I try to install ebox-squid I get the following error:

A really nasty bug has occurred
Exception
No such daemon: ebox.squid
Trace
No such daemon: ebox.squid at /usr/share/perl5/EBox/Service.pm line 74
EBox::Service::running('ebox.squid') called at /usr/share/perl5/EBox/Squid.pm line 181
EBox::Squid::isRunning('EBox::Squid=HASH(0x265cacc0)') called at /usr/share/perl5/EBox/Module/Service.pm line 359
EBox::Module::Service::addModuleStatus('EBox::Squid=HASH(0x265cacc0)', 'EBox::Dashboard::Section=HASH(0x265de060)') called at /usr/share/perl5/EBox/SysInfo.pm line 75
EBox::SysInfo::modulesWidget('EBox::SysInfo=HASH(0x264c9da8)', 'EBox::Dashboard::Widget=HASH(0x265d29f0)', undef) called at /usr/share/perl5/EBox/Module/Base.pm line 651
EBox::Module::Base::widget('EBox::SysInfo=HASH(0x264c9da8)', 'modules') called at /usr/share/perl5/EBox/CGI/Dashboard/Index.pm line 56
EBox::CGI::Dashboard::Index::masonParameters('EBox::CGI::Dashboard::Index=HASH(0x263b2e28)') called at /usr/share/perl5/EBox/CGI/Base.pm line 517
EBox::CGI::Base::_process('EBox::CGI::Dashboard::Index=HASH(0x263b2e28)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::Dashboard::Index=HASH(0x263b2e28)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Dashboard/Index', '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(0x2649e9d8)') 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(0x265cb3b0)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x265cb3b0)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x2649e9d8)') called at -e line 0
eval {...} called at -e line 0

38

News and Announcements / Re: Roadmap for eBox 2.0 available in our development trac

« on: April 07, 2010, 07:15:14 pm »

Thanks for the excellent product you've been working on and I anxiously await the new release.  I noticed that 2.0 is due in 3 months and one of the goals listed is 10.04.  Is that to say that it should probably be about 3 months til 10.04 can be used with Ebox in it's entirety (not 1.5)?

39

News and Announcements / Re: New eBox 1.5 packages for Ubuntu 10.04 Lucid

« on: February 17, 2010, 06:09:55 pm »

Do you suspect that upgrading from Jaunty then Karmic to get to Lucid will break Ebox since there are no Karmic packages?  Is the only reliable upgrade path going to be from Hardy to Lucid?

40

Installation and Upgrades / Upgrading to Lucid and Ebox 1.4

« on: January 28, 2010, 05:33:25 am »

To my surprise I made a bad choice by installing Ebox 1.3 on Jaunty assuming it would continue to receive updates.  Now I'm wondering that since I'll first have to upgrade to Karmic before Lucid will Ebox completely break by the time I get to Lucid and Ebox 1.4?  I noticed Lucid packages have not begun to be posted in the PPA so I'm wondering if the best way to get 1.4 is going to be formatting my machine and going back to Hardy.  I know, I shouldn't have done beta software but it has run quite well with only a couple items not working.  If somebody could please advise it would be greatly appreciated!

41

Installation and Upgrades / Ebox 1.3.6 doesn't save default gateway

« on: December 08, 2009, 06:30:24 pm »

I have 2 internet connections with both gateways configured under Ebox 1.3.6.  Whenever I reboot the server Ebox doesn't save the default gateway and changes it to my other internet connection that I don't want as default.  I'm running 1.3.6 on Jaunty.

42

Installation and Upgrades / Re: VPN has to reconnect every 2 minutes

« on: November 30, 2009, 08:36:55 pm »

I didn't think of this last night so I apologize for wasting your time.  This morning I decided to try setting the interface for the server to listen on since I have 2 internet connections.  For some reason the VPN never drops now that I defined the server to listen on eth0 only which makes me wonder why there is the option for all interfaces if that causes problems.  Or is it a bug that all interfaces doesn't work?  Anyway, it's fixed now but I was hoping to be able to use either of my 2 IP addresses in case a connection went down but that rarely happens so I won't worry about it.

43

Installation and Upgrades / Re: VPN has to reconnect every 2 minutes

« on: November 30, 2009, 06:44:52 pm »

Are you using the same certificate from two different connections?
I am using the same certificate but I'm not connecting both clients at the same time.

We have also seen issues in Linux when the same machine was trying to connect with two different process.
Are you saying 2 VPN daemons are running on the server?  If so, how did you fix it?

It has to be the above or an issue with your connectivity/port/ISP.
I actually had a VPN setup 2 years ago on a totally different machine, ISP, and I set it up manually cause this was before Ebox was in Ubuntu repositories.  I was experiencing the same problem and figured I configured something wrong.  However, now that I'm using Ebox with scripts perfected by developers I know the configuration is right but same problem exists.  I'm just cursed.     By the way, I'm using Ubuntu 9.04 and Ebox 1.3.6 (anxiously awaiting 1.3.10 in Jaunty's repositories).

44

Installation and Upgrades / VPN has to reconnect every 2 minutes

« on: November 30, 2009, 05:03:28 am »

I setup my VPN and it works perfectly (thank you very much for making it so easy to do).  However, I found that in the OpenVPN log the client is reconnecting every 2 minutes almost exactly to the second.  I tried it from 2 different clients each one having different internet connections.  Any ideas what would be causing this?  There isn't much work that can be done in 2 minutes (actually traffic starts to time out sooner cause the client starts the process of killing and reconnecting).  Also traffic is very slow while the connection is working.  Hardware is basically idle and internet connections are 6 down 3 up.

45

Installation and Upgrades / Re: User Corner login not working (eBox 1.3.6, Ubuntu 9.04)

« on: November 02, 2009, 08:41:32 pm »

I just wanted to let you know I can verify the problem.  I've had that error ever since I installed 1.3.3 on Jaunty a month ago and it persisted with 1.3.6.  Fortunately the user corner isn't a pressing issue for me right now so I can wait and figured it would be fixed by 1.4.