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.
241
Installation and Upgrades / Configuration restore error
« on: April 12, 2010, 10:04:41 am »
Hello,
I have installed ebox 1.4 on a brand new server.
Restore the data from a 1.2 server to the new one it was ok
Restore the configuration from the 1.2 server to the new server, it has an error " Prefilter" missing.
This result that the ebox-printer module not start if we reboot the 1.4 server ( data users goups etc is ok )
We execute the following commands:
apt-get remove --purge ebox-printers
apt-get install ebox-printers
Reboot the new 1.4 server, the printer module is ok now and start.
There is still a problem, de definitions of the printers are not restored from the 1.2 server to the 1.4 server.
So we lost the printers in the new 1.4 server.
How can this be solved ?
Thanks,
Ian
I have installed ebox 1.4 on a brand new server.
Restore the data from a 1.2 server to the new one it was ok
Restore the configuration from the 1.2 server to the new server, it has an error " Prefilter" missing.
This result that the ebox-printer module not start if we reboot the 1.4 server ( data users goups etc is ok )
We execute the following commands:
apt-get remove --purge ebox-printers
apt-get install ebox-printers
Reboot the new 1.4 server, the printer module is ok now and start.
There is still a problem, de definitions of the printers are not restored from the 1.2 server to the 1.4 server.
So we lost the printers in the new 1.4 server.
How can this be solved ?
Thanks,
Ian
242
Installation and Upgrades / PostgreSQL 8.4 error
« on: April 10, 2010, 02:42:44 pm »
Hello,
On our eBox file and printserver 1.2.3, we have done an upgrade:
apt-get update
apt-get upgrade
The upgrade give some dpkg errors on postgresql
dpkg --confugure -a
does not solve the problem
apt-get install -f
does not solve the problem even.
rebooting the server give following error:
postgresql 8.4 database server failed to start
From now on, it is not possible to querry the samba logs in the eBox gui interface
This is what the errolog file postgresql-8.4-main.log says
2010-04-10 13:47:48 CEST FATAL: private key file "server.key" has group or world access
2010-04-10 13:47:48 CEST DETAIL: File must be owned by the database user or root, must have no write permission for "group", and must have no permissions for "other".
Please some help to solve this problem.
Thanks,
Ian
On our eBox file and printserver 1.2.3, we have done an upgrade:
apt-get update
apt-get upgrade
The upgrade give some dpkg errors on postgresql
dpkg --confugure -a
does not solve the problem
apt-get install -f
does not solve the problem even.
rebooting the server give following error:
postgresql 8.4 database server failed to start
From now on, it is not possible to querry the samba logs in the eBox gui interface
This is what the errolog file postgresql-8.4-main.log says
2010-04-10 13:47:48 CEST FATAL: private key file "server.key" has group or world access
2010-04-10 13:47:48 CEST DETAIL: File must be owned by the database user or root, must have no write permission for "group", and must have no permissions for "other".
Please some help to solve this problem.
Thanks,
Ian
243
Installation and Upgrades / Re: Samba Quota
« on: April 04, 2010, 11:09:52 am »
Hello,
Disable the quota limit in the general file sharing option.
Set for each user account individual the quota limit now ( 0 means unlimitted ).
This works fine in the release 1.2.
Best regards,
Ian
Disable the quota limit in the general file sharing option.
Set for each user account individual the quota limit now ( 0 means unlimitted ).
This works fine in the release 1.2.
Best regards,
Ian
244
Installation and Upgrades / Re: Web interface bug in release 1.2.3
« on: April 03, 2010, 04:38:22 pm »
Hello,
Problem solved, found the solution on this forum there was already a post for this bug.
In terminal or console mode execute following command:
sudo apt-get install ebox libebox
Executing this command, solve the problem.
Best regards,
Ian
Problem solved, found the solution on this forum there was already a post for this bug.
In terminal or console mode execute following command:
sudo apt-get install ebox libebox
Executing this command, solve the problem.
Best regards,
Ian
245
Installation and Upgrades / Web interface bug in release 1.2.3
« on: March 28, 2010, 05:09:53 pm »
Hello,
Since some time whe have a problem on our production server in our school.
The server is an eBox file and printserver release 1.2.3
When we start the web interface ( https://<server ip address>:443, and click on " File Sharing " an error appear in stead of the sharing menu's.
The error is in Dutch and says: " Er is een interne four m.b.t. een template opgetreden. Dit is een bug " Translated " An internal error related to a template occured. This is a bug ".
How can this be resolved ?
Thanks ian
Since some time whe have a problem on our production server in our school.
The server is an eBox file and printserver release 1.2.3
When we start the web interface ( https://<server ip address>:443, and click on " File Sharing " an error appear in stead of the sharing menu's.
The error is in Dutch and says: " Er is een interne four m.b.t. een template opgetreden. Dit is een bug " Translated " An internal error related to a template occured. This is a bug ".
How can this be resolved ?
Thanks ian
246
Installation and Upgrades / Re: Upgrade 1.2 to 1.4 printer module fails at boot
« on: February 12, 2010, 04:16:07 pm »
Hello,
Thanks , the problem is solved afther executing the commands
apt-get purge ebox-printers
apt-get install ebox printers.
This means that there is no problem to install an new 1.4 server from scratch, and by restoring the data and the configuration from the old 1.2 server to the new one, have a new ebox server release 1.4 with the data and configuration ( users groups shares etc ) from the old 1.2 production server and the production can be continued on the new server.
I have still a question about the new backup service in 1.4.
I already now thet it can be automated, but how van i store the backup file on a NAS server in my network ( the NAS server has no FTP on board ).
Thanks and best regards,
Ian
Thanks , the problem is solved afther executing the commands
apt-get purge ebox-printers
apt-get install ebox printers.
This means that there is no problem to install an new 1.4 server from scratch, and by restoring the data and the configuration from the old 1.2 server to the new one, have a new ebox server release 1.4 with the data and configuration ( users groups shares etc ) from the old 1.2 production server and the production can be continued on the new server.
I have still a question about the new backup service in 1.4.
I already now thet it can be automated, but how van i store the backup file on a NAS server in my network ( the NAS server has no FTP on board ).
Thanks and best regards,
Ian
247
Installation and Upgrades / Upgrade 1.2 to 1.4 printer module fails at boot
« on: February 11, 2010, 06:17:11 pm »
Hello,
Whey have upgraded our production platform from 1.2 to 1.4
1) Made a backup of the data, made a backup of the configuration.
2) Install a brand new server from scratch on an new computer, Ubuntu server 8.04.4 adapted sources.list and installed the needed eBox modules from the repository ( whey work with a PDC file and prinserver ).
3 ) Afther installation, the new server start up with no errors.
4) Activated the needed modules in the eBox managing interface.
5 ) Restored the data on the new server, restored the configuration on the new server.
So far so good, evrything seams to be ok ( users, groups, shares acces contol list etc. ).
6 ) Reboot the new server, the module ebox printers fails to start.
7 ) In eBox managing module dashboard try to restart the service printers, an error message appear " PreFilter " missing in " Printers.pm " the pinter service could not be started.
How can this be solved ?
An other question, is it possible to automate backups defined in the ebox managing backup option stored on a NAS serve in the network ?
Thanks,
Ian
Whey have upgraded our production platform from 1.2 to 1.4
1) Made a backup of the data, made a backup of the configuration.
2) Install a brand new server from scratch on an new computer, Ubuntu server 8.04.4 adapted sources.list and installed the needed eBox modules from the repository ( whey work with a PDC file and prinserver ).
3 ) Afther installation, the new server start up with no errors.
4) Activated the needed modules in the eBox managing interface.
5 ) Restored the data on the new server, restored the configuration on the new server.
So far so good, evrything seams to be ok ( users, groups, shares acces contol list etc. ).
6 ) Reboot the new server, the module ebox printers fails to start.
7 ) In eBox managing module dashboard try to restart the service printers, an error message appear " PreFilter " missing in " Printers.pm " the pinter service could not be started.
How can this be solved ?
An other question, is it possible to automate backups defined in the ebox managing backup option stored on a NAS serve in the network ?
Thanks,
Ian
248
Installation and Upgrades / Re: Windows 7 clients on eBox 1.2
« on: December 13, 2009, 10:59:32 am »
Thanks for the information.
I wait for the release 1.4 and will then upgrade our platform.
Hopely it is possible to upgrade the data and configuration from 1.2 to 1.4 with a backup of the data and configuration ( settings, shares, users, groups, computer client accounts etc. ) and restore this to a brand new eBox file and printserver release 1.4.
Thanks,
Ian
I wait for the release 1.4 and will then upgrade our platform.
Hopely it is possible to upgrade the data and configuration from 1.2 to 1.4 with a backup of the data and configuration ( settings, shares, users, groups, computer client accounts etc. ) and restore this to a brand new eBox file and printserver release 1.4.
Thanks,
Ian
249
Installation and Upgrades / Windows 7 clients on eBox 1.2
« on: December 12, 2009, 11:46:52 am »
Hello,
We have a eBox PDC file and printserver, with 40 windows Xp clients in the domain.
The release 1.2 has the lates updates.
Is it possible that we join a new windows client with os windows 7 to our domain ?
Do we need to upgrade de release 1.2 , so that we have the latest modules but still release 1.2 ?
sudo apt-get upgrade
Thanks and best regards,
Ian
We have a eBox PDC file and printserver, with 40 windows Xp clients in the domain.
The release 1.2 has the lates updates.
Is it possible that we join a new windows client with os windows 7 to our domain ?
Do we need to upgrade de release 1.2 , so that we have the latest modules but still release 1.2 ?
sudo apt-get upgrade
Thanks and best regards,
Ian
250
Installation and Upgrades / Re: Backup/restore
« on: October 27, 2009, 04:21:16 pm »
Hello Javi,
I did an extra test.
I have copyed ( in command mode ) the file Backup.pm on the new eBox server, build from scrath.
Then i hve restored the data from my operational server to the new one.
In the eBox admin console i did a restore of the configuration file of the operational server to the new one.
Result data , users groups shares etc are restored on the new server, but the acces list and access permissions are not restored.
So the file Backup.pm must be also copyed on the operational server , and you must make a new backup of the configuration on this server.
Then copy the file Backup.pm on the new server, and restore the new made configuration file on the new server.
This results in a new server with all ok inclusif the access control lists and the access to the files.
Best regards,
Ian
I did an extra test.
I have copyed ( in command mode ) the file Backup.pm on the new eBox server, build from scrath.
Then i hve restored the data from my operational server to the new one.
In the eBox admin console i did a restore of the configuration file of the operational server to the new one.
Result data , users groups shares etc are restored on the new server, but the acces list and access permissions are not restored.
So the file Backup.pm must be also copyed on the operational server , and you must make a new backup of the configuration on this server.
Then copy the file Backup.pm on the new server, and restore the new made configuration file on the new server.
This results in a new server with all ok inclusif the access control lists and the access to the files.
Best regards,
Ian
251
Installation and Upgrades / Re: Backup/restore
« on: October 27, 2009, 03:20:25 pm »
hello Javi,
Thanks for the support
Best regards,
Ian
Thanks for the support
Best regards,
Ian
252
Installation and Upgrades / Re: Ebox V1.2 upgrade
« on: October 27, 2009, 03:09:55 pm »
Hello sixstone,
Thanks for the information.
Best regards,
Ian
Thanks for the information.
Best regards,
Ian
253
Installation and Upgrades / Re: Backup/restore
« on: October 27, 2009, 11:08:43 am »
Hello Javi,
I think that the problem is solved.
The reason why i get the samba error on mij operational server was because i have copyed the nerw file " Backup.pm " using a file manager on the server ( i use lxde small desktop to make things easyer ) the old file " Backup.pm " was overwritten at that time and when i restarted eBox samba was not restarted again.
So the only thing to solve the samba problem was, in the eBox admin menu unselect all modules needed for a file and print server. Then in command mode remove ebox office ( sudo apt-get remove ebox-office ). Reboot the server, in command mode reïnstall ebox-office ( sudo apt-get install ebox-ofice ) then select all the needed modules for a file and printserver in the ebox admin application.
The server is ok now , evrything is working again.
Next step, on my operational server downloaded the new module " Backup.pm " and copyed the file in command mode ( cp -bf /tmp/Backup.pm /usr/share/perl5/EBox/backup.pm ), reboot the server, made a backup of the server configuration in the ebox admin interface.
Install a new eBox server from scratch, restore the data on the new server, restore the configuration backup and reboot the new server.Now the new server has all the data and cofiguration from the old server and works fine.
So the new " backup.pm " file has solved the access control list.
Sorry it was my fault, i did not correctly copyed the Backup.pm file
Thanks for the intervention,
Ian
I think that the problem is solved.
The reason why i get the samba error on mij operational server was because i have copyed the nerw file " Backup.pm " using a file manager on the server ( i use lxde small desktop to make things easyer ) the old file " Backup.pm " was overwritten at that time and when i restarted eBox samba was not restarted again.
So the only thing to solve the samba problem was, in the eBox admin menu unselect all modules needed for a file and print server. Then in command mode remove ebox office ( sudo apt-get remove ebox-office ). Reboot the server, in command mode reïnstall ebox-office ( sudo apt-get install ebox-ofice ) then select all the needed modules for a file and printserver in the ebox admin application.
The server is ok now , evrything is working again.
Next step, on my operational server downloaded the new module " Backup.pm " and copyed the file in command mode ( cp -bf /tmp/Backup.pm /usr/share/perl5/EBox/backup.pm ), reboot the server, made a backup of the server configuration in the ebox admin interface.
Install a new eBox server from scratch, restore the data on the new server, restore the configuration backup and reboot the new server.Now the new server has all the data and cofiguration from the old server and works fine.
So the new " backup.pm " file has solved the access control list.
Sorry it was my fault, i did not correctly copyed the Backup.pm file
Thanks for the intervention,
Ian
254
Installation and Upgrades / Re: Backup/restore
« on: October 26, 2009, 10:58:50 am »
Javi,
This error appears afther i have copyed the File on the eBox server and reboot the server, Samba wont start again and give the error.
P.s. i have copyed the file to the eBox server, where i will made a new backup of the configuration so that this configuration can be restored on a new eBox server build from scratch.
I did not tryed to copy the backup.pm file on the new installed server buid from scratch, and then restore the configuration.
So the problem is, afther copy the new backup.pm on the server and perform a reboot of the server Samba is not restarted, and give the errors.
Best regards,
Ian
This error appears afther i have copyed the File on the eBox server and reboot the server, Samba wont start again and give the error.
P.s. i have copyed the file to the eBox server, where i will made a new backup of the configuration so that this configuration can be restored on a new eBox server build from scratch.
I did not tryed to copy the backup.pm file on the new installed server buid from scratch, and then restore the configuration.
So the problem is, afther copy the new backup.pm on the server and perform a reboot of the server Samba is not restarted, and give the errors.
Best regards,
Ian
255
Installation and Upgrades / Re: Backup/restore
« on: October 25, 2009, 11:13:52 am »
Hello,
I have copy the file " Backup.pm " as explained on the server where i will backup the configuration, so i can restore the configuration backup file on a brand new eBox server.
Afther the copy i have restarted the server, but samba wont start again and give the following errors:
A really nasty bug has occurred
Exception
root command /etc/init.d/samba start failed. Error output: Command output: * Starting Samba daemons [80G [74G[[31mfail[39;49m] . Exit value: 1
Trace
root command /etc/init.d/samba start failed.
Error output:
Command output: * Starting Samba daemons [80G [74G[[31mfail[39;49m]
.
Exit value: 1 at /usr/share/perl5/Error.pm line 182
Error::throw('EBox::Exceptions::Sudo::Command', 'cmd', '/etc/init.d/samba start', 'output', 'ARRAY(0xaafb408)', 'error', 'ARRAY(0xaa7adb8)', 'exitValue', 1, ...) called at /usr/share/perl5/EBox/Sudo.pm line 190
EBox::Sudo::_rootError('/usr/bin/sudo -p sudo: /var/lib/ebox/tmp/TiVAq5aBTt.cmd 2> /v...', '/etc/init.d/samba start', 256, 'ARRAY(0xaafb408)', 'ARRAY(0xaa7adb8)') called at /usr/share/perl5/EBox/Sudo.pm line 157
EBox::Sudo::root('/etc/init.d/samba start') called at /usr/share/perl5/EBox/Module/Service.pm line 484
EBox::Module::Service::_startDaemon('EBox::Samba=HASH(0xa93428c)', 'HASH(0xb22a638)') called at /usr/share/perl5/EBox/Module/Service.pm line 523
EBox::Module::Service::_manageService('EBox::Samba=HASH(0xa93428c)', 'start') called at /usr/share/perl5/EBox/Module/Service.pm line 539
EBox::Module::Service::_startService('EBox::Samba=HASH(0xa93428c)') called at /usr/share/perl5/EBox/Module/Service.pm line 650
EBox::Module::Service::_enforceServiceState('EBox::Samba=HASH(0xa93428c)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 596
EBox::Module::Service::_regenConfig('EBox::Samba=HASH(0xa93428c)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 621
EBox::Module::Service::restartService('EBox::Samba=HASH(0xa93428c)') called at /usr/share/perl5/EBox/CGI/EBox/RestartService.pm line 51
EBox::CGI::EBox::RestartService::_process('EBox::CGI::EBox::RestartService=HASH(0xaa50b3c)') called at /usr/share/perl5/EBox/CGI/Base.pm line 261
EBox::CGI::Base::run('EBox::CGI::EBox::RestartService=HASH(0xaa50b3c)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'EBox/RestartService', '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(0xa9eedc0)') 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(0xaa50938)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xaa50938)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa9eedc0)') called at -e line 0
eval {...} called at -e line 0
Best regards
Ian
I have copy the file " Backup.pm " as explained on the server where i will backup the configuration, so i can restore the configuration backup file on a brand new eBox server.
Afther the copy i have restarted the server, but samba wont start again and give the following errors:
A really nasty bug has occurred
Exception
root command /etc/init.d/samba start failed. Error output: Command output: * Starting Samba daemons [80G [74G[[31mfail[39;49m] . Exit value: 1
Trace
root command /etc/init.d/samba start failed.
Error output:
Command output: * Starting Samba daemons [80G [74G[[31mfail[39;49m]
.
Exit value: 1 at /usr/share/perl5/Error.pm line 182
Error::throw('EBox::Exceptions::Sudo::Command', 'cmd', '/etc/init.d/samba start', 'output', 'ARRAY(0xaafb408)', 'error', 'ARRAY(0xaa7adb8)', 'exitValue', 1, ...) called at /usr/share/perl5/EBox/Sudo.pm line 190
EBox::Sudo::_rootError('/usr/bin/sudo -p sudo: /var/lib/ebox/tmp/TiVAq5aBTt.cmd 2> /v...', '/etc/init.d/samba start', 256, 'ARRAY(0xaafb408)', 'ARRAY(0xaa7adb8)') called at /usr/share/perl5/EBox/Sudo.pm line 157
EBox::Sudo::root('/etc/init.d/samba start') called at /usr/share/perl5/EBox/Module/Service.pm line 484
EBox::Module::Service::_startDaemon('EBox::Samba=HASH(0xa93428c)', 'HASH(0xb22a638)') called at /usr/share/perl5/EBox/Module/Service.pm line 523
EBox::Module::Service::_manageService('EBox::Samba=HASH(0xa93428c)', 'start') called at /usr/share/perl5/EBox/Module/Service.pm line 539
EBox::Module::Service::_startService('EBox::Samba=HASH(0xa93428c)') called at /usr/share/perl5/EBox/Module/Service.pm line 650
EBox::Module::Service::_enforceServiceState('EBox::Samba=HASH(0xa93428c)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 596
EBox::Module::Service::_regenConfig('EBox::Samba=HASH(0xa93428c)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 621
EBox::Module::Service::restartService('EBox::Samba=HASH(0xa93428c)') called at /usr/share/perl5/EBox/CGI/EBox/RestartService.pm line 51
EBox::CGI::EBox::RestartService::_process('EBox::CGI::EBox::RestartService=HASH(0xaa50b3c)') called at /usr/share/perl5/EBox/CGI/Base.pm line 261
EBox::CGI::Base::run('EBox::CGI::EBox::RestartService=HASH(0xaa50b3c)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'EBox/RestartService', '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(0xa9eedc0)') 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(0xaa50938)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xaa50938)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa9eedc0)') called at -e line 0
eval {...} called at -e line 0
Best regards
Ian