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 / Re: Adding many users in bulk to multiple groups.
« on: September 01, 2013, 01:23:26 pm »
Last script works, but needs groups, that are beeing assinged to user, to be created earlier.
I try to modify it adding:
but API returns:
Any ideas how to deal with it?
I try to modify it adding:
Code: [Select]
my $group = new EBox::UsersAndGroups::Group->create($groupname);but API returns:
Quote
Missing argument: entry|dn|ldifk
Any ideas how to deal with it?
2
Installation and Upgrades / Re: WAN: Single IP address for WAN with /32 netmask not possible?
« on: December 21, 2011, 08:42:44 pm »
I know how the subnet works, and what it does need. Unfortunately this ip address I have is only provided at isp dhcp (adsl modem) level, which sets it with /32 mask, and designated gateway in routing table entry.
For me it looks that gw is from another address pool, unless the isp is using /16 network for its dhcp leases.
I'd rather not put /16 netmask in my configuration, and if You can not see any other way, I'll write some script to set interface address and routing on start, and leave the interface without configuration in zentyal, though loosing all gui-friendly firewall/proxy/etc.. features on
For me it looks that gw is from another address pool, unless the isp is using /16 network for its dhcp leases.
I'd rather not put /16 netmask in my configuration, and if You can not see any other way, I'll write some script to set interface address and routing on start, and leave the interface without configuration in zentyal, though loosing all gui-friendly firewall/proxy/etc.. features on
3
Installation and Upgrades / WAN: Single IP address for WAN with /32 netmask not possible?
« on: December 19, 2011, 10:52:27 pm »
I have adsl line attached to my zentyal WAN interface that is configured with bridge mode. I have static IP address provided by my ISP, but normally it is provided by modem with dhcp.
Since it is not very reliable, I tried to manually configure the WAN interface, with that IP address, but 32(255.255.255.255) netmak value is not possible to configure through gui.
Is there any other way to cofigure the interface the way I want, and be sure that my configuration won't be overriden next time I change some things with zentyal gui?
Right now I do it manually with ip addr, and route, but it is not permament solution.
Since it is not very reliable, I tried to manually configure the WAN interface, with that IP address, but 32(255.255.255.255) netmak value is not possible to configure through gui.
Is there any other way to cofigure the interface the way I want, and be sure that my configuration won't be overriden next time I change some things with zentyal gui?
Right now I do it manually with ip addr, and route, but it is not permament solution.
4
Installation and Upgrades / Re: Critical(?) eBox 1rc2 () problems
« on: February 24, 2009, 02:01:39 pm »
Just let me know, what privilidges You need.
5
Installation and Upgrades / Re: Critical(?) eBox 1rc2 () problems
« on: February 24, 2009, 11:22:11 am »
OK, I managed to run that host for a week without hang. Unfortunately it is because, I log in every few hours and kill 90manageEBoxLog processes.
This is temoprary solution, but better than nothing. On the other hand, this way I'm almost sure that there is something wrong with this module. Is there any way to manually disable start of this service, or is it critical and should not be touched?
This is temoprary solution, but better than nothing. On the other hand, this way I'm almost sure that there is something wrong with this module. Is there any way to manually disable start of this service, or is it critical and should not be touched?
6
Installation and Upgrades / Re: Critical(?) eBox 1rc2 () problems
« on: February 13, 2009, 09:19:50 am »
I've disabled log module, but there still exists process that takes full working time of two processors and almost 2GB of ram. It is 90manageEBoxLog.
The good thing is that, the dashboard shows some more info after turning debug on.
When I try to generate debug report I get PageNotFound error. Can this be because of disabled log module?
Dashboar error:
No such daemon: ebox.postgrey
\n
\n$VAR1 = bless( {
'-stacktrace' => 'No such daemon: ebox.postgrey at /usr/share/perl5/EBox/Service.pm line 74
EBox::Service::running(\'ebox.postgrey\') called at /usr/share/perl5/EBox/ServiceModule/ServiceInterface.pm line 277
EBox::ServiceModule::ServiceInterface::_isDaemonRunning(\'EBox::Mail=HASH(0x9560f2c)\', \'ebox.postgrey\') called at /usr/share/perl5/EBox/ServiceModule/ServiceInterface.pm line 330
EBox::ServiceModule::ServiceInterface::isRunning(\'EBox::Mail=HASH(0x9560f2c)\') called at /usr/share/perl5/EBox/SysInfo.pm line 69
EBox::SysInfo::modulesWidget(\'EBox::SysInfo=HASH(0xa48236c)\', \'EBox::Dashboard::Widget=HASH(0xab76b74)\', \'undef\') called at /usr/share/perl5/EBox/Module.pm line 690
EBox::Module::widget(\'EBox::SysInfo=HASH(0xa48236c)\', \'modules\') called at /usr/share/perl5/EBox/CGI/Dashboard/Index.pm line 56
EBox::CGI::Dashboard::Index::masonParameters(\'EBox::CGI::Dashboard::Index=HASH(0xa3e779c)\') called at /usr/share/perl5/EBox/CGI/Base.pm line 508
EBox::CGI::Base::_process(\'EBox::CGI::Dashboard::Index=HASH(0xa3e779c)\') called at /usr/share/perl5/EBox/CGI/Base.pm line 261
EBox::CGI::Base::run(\'EBox::CGI::Dashboard::Index=HASH(0xa3e779c)\') called at /usr/share/perl5/EBox/CGI/Run.pm line 86
EBox::CGI::Run::run(\'EBox::CGI::Run\', \'Dashboard/Index\') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler(\'Apache2::RequestRec=SCALAR(0x9005b38)\') 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(0x93e8148)\') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler(\'ModPerl::Registry=HASH(0x93e8148)\') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler(\'ModPerl::Registry\', \'Apache2::RequestRec=SCALAR(0x9005b38)\') called at -e line 0
eval {...} called at -e line 0
',
'-file' => '/usr/share/perl5/EBox/Service.pm',
'-text' => 'No such daemon: ebox.postgrey',
'-line' => 74,
'-package' => 'EBox::Service'
}, 'EBox::Exceptions::Internal' );
\n
\n
The good thing is that, the dashboard shows some more info after turning debug on.
When I try to generate debug report I get PageNotFound error. Can this be because of disabled log module?
Dashboar error:
No such daemon: ebox.postgrey
\n
\n$VAR1 = bless( {
'-stacktrace' => 'No such daemon: ebox.postgrey at /usr/share/perl5/EBox/Service.pm line 74
EBox::Service::running(\'ebox.postgrey\') called at /usr/share/perl5/EBox/ServiceModule/ServiceInterface.pm line 277
EBox::ServiceModule::ServiceInterface::_isDaemonRunning(\'EBox::Mail=HASH(0x9560f2c)\', \'ebox.postgrey\') called at /usr/share/perl5/EBox/ServiceModule/ServiceInterface.pm line 330
EBox::ServiceModule::ServiceInterface::isRunning(\'EBox::Mail=HASH(0x9560f2c)\') called at /usr/share/perl5/EBox/SysInfo.pm line 69
EBox::SysInfo::modulesWidget(\'EBox::SysInfo=HASH(0xa48236c)\', \'EBox::Dashboard::Widget=HASH(0xab76b74)\', \'undef\') called at /usr/share/perl5/EBox/Module.pm line 690
EBox::Module::widget(\'EBox::SysInfo=HASH(0xa48236c)\', \'modules\') called at /usr/share/perl5/EBox/CGI/Dashboard/Index.pm line 56
EBox::CGI::Dashboard::Index::masonParameters(\'EBox::CGI::Dashboard::Index=HASH(0xa3e779c)\') called at /usr/share/perl5/EBox/CGI/Base.pm line 508
EBox::CGI::Base::_process(\'EBox::CGI::Dashboard::Index=HASH(0xa3e779c)\') called at /usr/share/perl5/EBox/CGI/Base.pm line 261
EBox::CGI::Base::run(\'EBox::CGI::Dashboard::Index=HASH(0xa3e779c)\') called at /usr/share/perl5/EBox/CGI/Run.pm line 86
EBox::CGI::Run::run(\'EBox::CGI::Run\', \'Dashboard/Index\') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler(\'Apache2::RequestRec=SCALAR(0x9005b38)\') 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(0x93e8148)\') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler(\'ModPerl::Registry=HASH(0x93e8148)\') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler(\'ModPerl::Registry\', \'Apache2::RequestRec=SCALAR(0x9005b38)\') called at -e line 0
eval {...} called at -e line 0
',
'-file' => '/usr/share/perl5/EBox/Service.pm',
'-text' => 'No such daemon: ebox.postgrey',
'-line' => 74,
'-package' => 'EBox::Service'
}, 'EBox::Exceptions::Internal' );
\n
\n
7
Installation and Upgrades / Re: Critical(?) eBox 1rc2 () problems
« on: February 12, 2009, 09:01:31 pm »
I'll try english with debug turned on tommorow. System went down once again, and I do not have currently access to it.
As for tracking processes with top, I think that I saw that ebox logger was kind a memory and processor hog. But I'll confirm that also tommorow.
As for tracking processes with top, I think that I saw that ebox logger was kind a memory and processor hog. But I'll confirm that also tommorow.
8
Installation and Upgrades / Critical(?) eBox 1rc2 () problems
« on: February 12, 2009, 08:40:15 am »
Hello
I've a week ago updated my ebox 0.12.3-1 box, to unstable 1rc2 version. Update process went seamlessly, but them problems started.
First of all dashboard does not work at all. On dashboard page I get two errors (I give You my own English translation since I use Polish as eBox language):
- Internal error occurred. You'll find more information in log files.
- Schema internal error occured. You'll find more information in log files.
But the worst thing is that now the system that was working for the last 6 months 24h/7 without any problems is hanging every few hours. Only hard reset helps to reinitialize system for the next few hours.
Currently I'm using only basic functionality - firewall, squid, traffic shaping, dns and dhcp.
Error logs are to big to be attached. Please let me know where to send those if You need it.
I've a week ago updated my ebox 0.12.3-1 box, to unstable 1rc2 version. Update process went seamlessly, but them problems started.
First of all dashboard does not work at all. On dashboard page I get two errors (I give You my own English translation since I use Polish as eBox language):
- Internal error occurred. You'll find more information in log files.
- Schema internal error occured. You'll find more information in log files.
But the worst thing is that now the system that was working for the last 6 months 24h/7 without any problems is hanging every few hours. Only hard reset helps to reinitialize system for the next few hours.
Currently I'm using only basic functionality - firewall, squid, traffic shaping, dns and dhcp.
Error logs are to big to be attached. Please let me know where to send those if You need it.
Pages: [1]