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.
1
Installation and Upgrades / Re: Failed installation of zentyal-network-2.2.7
« on: April 28, 2012, 07:04:14 pm »
Never mind.
After a couple of reboots it seems to having fixed itself.
This is the same upgrade right after rebooting the server:
I'm baffled but (moderately) happy.
After a couple of reboots it seems to having fixed itself.
This is the same upgrade right after rebooting the server:
Code: [Select]
root@zenbox:/home/zenadmin# aptitude -V safe-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following partially installed packages will be configured:
zentyal-core
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up zentyal-core (2.2.7) ...
Processing triggers for zentyal-core ...
* Restarting Zentyal module: apache [ OK ]
* Restarting Zentyal module: logs [ OK ]
* Restarting Zentyal module: events [ OK ]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
I'm baffled but (moderately) happy.
2
Installation and Upgrades / Re: Failed installation of zentyal-network-2.2.7
« on: April 28, 2012, 06:49:36 pm »
At this point, it is zentyal-core that is causing me trouble.
For whatever reason zentyal-network ended up installed, but then zentyal-core became the new problem.
Trying to upgrade, it still complains about not being able to connect to the redis server.
For whatever reason zentyal-network ended up installed, but then zentyal-core became the new problem.
Code: [Select]
root@zenbox:~# dpkg -l zentyal-core
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-====================================-====================================-========================================================================================
iF zentyal-core 2.2.7 Zentyal - Core
Trying to upgrade, it still complains about not being able to connect to the redis server.
Code: [Select]
root@zenbox:~# aptitude -V safe-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following partially installed packages will be configured:
zentyal-core
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up zentyal-core (2.2.7) ...
Could not connect to Redis server at 127.0.0.1:6380: Connection timed out at /usr/share/perl5/Redis.pm line 54
Redis::new('Redis', 'server', '127.0.0.1:6380') called at /usr/share/perl5/EBox/Config/Redis.pm line 744
EBox::Config::Redis::_respawn('EBox::Config::Redis=HASH(0x3a6bc90)') called at /usr/share/perl5/EBox/Config/Redis.pm line 54
EBox::Config::Redis::new('EBox::Config::Redis') called at /usr/share/perl5/EBox/GConfModule.pm line 45
EBox::GConfModule::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 70
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Apache/Singleton.pm line 19
Apache::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global') called at /usr/share/perl5/EBox/Global.pm line 76
EBox::Global::AUTOLOAD('EBox::Global', 'remoteservices') called at /usr/share/zentyal/sudoers-friendly line 39
dpkg: error processing zentyal-core (--configure):
subprocess installed post-installation script returned error exit status 110
Errors were encountered while processing:
zentyal-core
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up zentyal-core (2.2.7) ...
Could not connect to Redis server at 127.0.0.1:6380: Connection timed out at /usr/share/perl5/Redis.pm line 54
Redis::new('Redis', 'server', '127.0.0.1:6380') called at /usr/share/perl5/EBox/Config/Redis.pm line 744
EBox::Config::Redis::_respawn('EBox::Config::Redis=HASH(0x2120c90)') called at /usr/share/perl5/EBox/Config/Redis.pm line 54
EBox::Config::Redis::new('EBox::Config::Redis') called at /usr/share/perl5/EBox/GConfModule.pm line 45
EBox::GConfModule::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 70
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Apache/Singleton.pm line 19
Apache::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global') called at /usr/share/perl5/EBox/Global.pm line 76
EBox::Global::AUTOLOAD('EBox::Global', 'remoteservices') called at /usr/share/zentyal/sudoers-friendly line 39
dpkg: error processing zentyal-core (--configure):
subprocess installed post-installation script returned error exit status 110
Errors were encountered while processing:
zentyal-core
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
3
Installation and Upgrades / Failed installation of zentyal-network-2.2.7
« on: April 26, 2012, 10:12:37 pm »
Today I tried to upgrade the zentyal-network module from 2.2.6 to 2.2.7 through the web interface.
Somehow the installation got stuck and the interface stopped responding.
In ssh I saw that the installation was not progressing and decided to reboot.
After it I still had to remove the dpkg locks.
Now, for some reason, the network module upgrade caused some error with zentyal core which appears as a failed installation as well.
Here is the output when trying to configure these packages:
Here is the list of installed packages:
It claims that it cannot connect to the redis server, despite the fact that it is running.
Any hint? Please?
Somehow the installation got stuck and the interface stopped responding.
In ssh I saw that the installation was not progressing and decided to reboot.
After it I still had to remove the dpkg locks.
Now, for some reason, the network module upgrade caused some error with zentyal core which appears as a failed installation as well.
Here is the output when trying to configure these packages:
Code: [Select]
root@zenbox:~# dpkg --configure --pending
Setting up zentyal-core (2.2.7) ...
Could not connect to Redis server at 127.0.0.1:6380: Connection timed out at /usr/share/perl5/Redis.pm line 54
Redis::new('Redis', 'server', '127.0.0.1:6380') called at /usr/share/perl5/EBox/Config/Redis.pm line 744
EBox::Config::Redis::_respawn('EBox::Config::Redis=HASH(0x32baa48)') called at /usr/share/perl5/EBox/Config/Redis.pm line 54
EBox::Config::Redis::new('EBox::Config::Redis') called at /usr/share/perl5/EBox/GConfModule.pm line 45
EBox::GConfModule::_create('EBox::GlobalImpl', 'name', 'global', 'printableName', 'global') called at /usr/share/perl5/EBox/GlobalImpl.pm line 70
EBox::GlobalImpl::_new_instance('EBox::GlobalImpl') called at /usr/share/perl5/Apache/Singleton.pm line 19
Apache::Singleton::instance('EBox::GlobalImpl') called at /usr/share/perl5/EBox/Global.pm line 38
EBox::Global::new('EBox::Global') called at /usr/share/perl5/EBox/Global.pm line 76
EBox::Global::AUTOLOAD('EBox::Global', 'remoteservices') called at /usr/share/zentyal/sudoers-friendly line 39
dpkg: error processing zentyal-core (--configure):
subprocess installed post-installation script returned error exit status 110
Errors were encountered while processing:
zentyal-core
root@zenbox:~# netstat -ant4p |grep 6380
tcp 0 0 127.0.0.1:6380 0.0.0.0:* LISTEN 1401/redis-server
tcp 1 0 127.0.0.1:58136 127.0.0.1:6380 CLOSE_WAIT 2366/perl
Here is the list of installed packages:
Code: [Select]
root@zenbox:~# dpkg -l zentyal*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-========================-========================-================================================================
ii zentyal 2.2 Zentyal - Core metapackage
un zentyal-antivirus <none> (no description available)
ii zentyal-ca 2.2.2 Zentyal - Certification Authority
ii zentyal-common 2.2.3 Zentyal - Common Library
iF zentyal-core 2.2.7 Zentyal - Core
ii zentyal-dhcp 2.2.1 Zentyal - DHCP Service
ii zentyal-dns 2.2.1 Zentyal - DNS Service
ii zentyal-ebackup 2.2.4 Zentyal - Backup
ii zentyal-firewall 2.2 Zentyal - Firewall
un zentyal-ftp <none> (no description available)
un zentyal-ipsec <none> (no description available)
ii zentyal-monitor 2.2.3 Zentyal - Monitor
ii zentyal-network 2.2.7 Zentyal - Network Configuration
ii zentyal-objects 2.2 Zentyal - Network Objects
ii zentyal-openvpn 2.2.1 Zentyal - VPN Service
ii zentyal-pptp 2.2 Zentyal - PPTP
ii zentyal-samba 2.2 Zentyal - File Sharing Service
ii zentyal-services 2.2 Zentyal - Network Services
ii zentyal-software 2.2.4 Zentyal - Software Management
un zentyal-squid <none> (no description available)
ii zentyal-usercorner 2.2 Zentyal - User Corner
ii zentyal-users 2.2.5 Zentyal - Users and Groups
It claims that it cannot connect to the redis server, despite the fact that it is running.
Any hint? Please?
4
Installation and Upgrades / Re: Problems after upgrading from 2.0 to 2.2
« on: April 10, 2012, 10:28:53 am »
Lueghi, from my experience, there is no guarantee that any path will work.
I waited patiently for months that the new version was ironed out and when I thought it would be safe I upgraded and ended up in the mess that I reported.
It is my opinion that if Zentyal 2.0 serves your needs, there is no real reason to upgrade. After all, in a few months you will have Zentyal 3.0 and will have to start it all over again. Considering the amount of time I had to devote to solve all the issues that arose from the failed upgrade, it would have been cheaper to just buy Windows Server and get done with it, wasn't it my own bet in this technology.
If you go ahead, make sure you have a full backup of everything on an external device. Make configuration backups to folders on the server and to your own computer. Make a copy of the LDAP contents in LDIF format (this may allow you to make adjustments in plain text if necessary). Purge (not just remove) anything that you are not actually using, as previously installed packages and configurations may interfere with the upgrade.
Finally, use Clonezilla or some other software to actually mirror your disk, as it may be a lot faster to go back should something go terribly wrong.
Good luck.
I waited patiently for months that the new version was ironed out and when I thought it would be safe I upgraded and ended up in the mess that I reported.
It is my opinion that if Zentyal 2.0 serves your needs, there is no real reason to upgrade. After all, in a few months you will have Zentyal 3.0 and will have to start it all over again. Considering the amount of time I had to devote to solve all the issues that arose from the failed upgrade, it would have been cheaper to just buy Windows Server and get done with it, wasn't it my own bet in this technology.
If you go ahead, make sure you have a full backup of everything on an external device. Make configuration backups to folders on the server and to your own computer. Make a copy of the LDAP contents in LDIF format (this may allow you to make adjustments in plain text if necessary). Purge (not just remove) anything that you are not actually using, as previously installed packages and configurations may interfere with the upgrade.
Finally, use Clonezilla or some other software to actually mirror your disk, as it may be a lot faster to go back should something go terribly wrong.
Good luck.
6
Installation and Upgrades / Re: Cannot change invalid hostname, web frontend dont start
« on: March 16, 2012, 10:25:28 am »
Have you tried /usr/share/zentyal/change-hostname?
7
Installation and Upgrades / leftovers
« on: March 15, 2012, 09:09:28 pm »
When I uninstall a Zentyal module, it doesn't perform a great job at housekeeping. A number of configuration files and scripts are left in the system causing unexpected behavior. That happens even after purging the corresponding zentyal module.
For instance, in 2.0 I tested the mail systems and after purging them I still had configuration files and entries in LDAP.
In 2.2 I tested the IPSec module, and despite completely purging it I still have a bunch of init scripts and configuration files all over the place.
The system should be able to do some housekeeping and clean up after itself when modules are removed, otherwise it may turn out a nightmare.
It would be interesting to know how many people have noticed this issue, or they have just learnt to live with it.
For instance, in 2.0 I tested the mail systems and after purging them I still had configuration files and entries in LDAP.
In 2.2 I tested the IPSec module, and despite completely purging it I still have a bunch of init scripts and configuration files all over the place.
The system should be able to do some housekeeping and clean up after itself when modules are removed, otherwise it may turn out a nightmare.
It would be interesting to know how many people have noticed this issue, or they have just learnt to live with it.
8
Installation and Upgrades / Re: make-backup and restore-backup tools
« on: March 06, 2012, 08:21:45 pm »
Have you tried /usr/share/zentyal/global-action --action saveAllModules?
9
Installation and Upgrades / Re: PPTP: how to get it working?
« on: March 02, 2012, 07:12:12 pm »
Thanks for your feedback, Neru.
My thought as well, just hoping to avoid having to mess with routes. Too bad they are not set in the PPTP configuration itself.
I thought that someone might have already figured it out by now.
:S
My thought as well, just hoping to avoid having to mess with routes. Too bad they are not set in the PPTP configuration itself.
I thought that someone might have already figured it out by now.
:S
10
Installation and Upgrades / PPTP: how to get it working?
« on: March 02, 2012, 12:34:26 am »
Does anyone know how to get PPTP to work?
I have OpenVPN but I would like to have PPTP as well.
Instructions in the (available) documentation are clearly not enoough, something is missing.
I can connect to the PPTP server but, like many others, have access to the server only.
I can get resolve names to IPs, but I can't even ping other hosts.
Yes, I have already opened ports tcp/1723 and GRE (protocol 47), but I will assume it is a routing issue that is not properly setup on the server upon connecting.
Is there someting I need to consider in /etc/pptpd.conf or some other file?
Any hint?
I have OpenVPN but I would like to have PPTP as well.
Instructions in the (available) documentation are clearly not enoough, something is missing.
I can connect to the PPTP server but, like many others, have access to the server only.
I can get resolve names to IPs, but I can't even ping other hosts.
Yes, I have already opened ports tcp/1723 and GRE (protocol 47), but I will assume it is a routing issue that is not properly setup on the server upon connecting.
Is there someting I need to consider in /etc/pptpd.conf or some other file?
Any hint?
11
Installation and Upgrades / Re: Slowness in control panel Zentyal
« on: February 28, 2012, 12:15:12 am »
Replaced with Nginx? 
12
Installation and Upgrades / Re: [Partially solved] Error> Could not get lock for service: firewal
« on: February 27, 2012, 10:29:45 am »
I created a virtual machine and installed Zentyal 2.2 on it.
I activated the firewall module and created the same Facebook IP ranges and rules to log and block them.
It seems odd but this time the system had no problems.
I'm not telling this because I know the reasons for it, but just for the sake of ccompleteness.
Since my original system was migrated from 2.0 to 2.2, it may not be as clean as expected. I would need to investigate a little bit more.
I activated the firewall module and created the same Facebook IP ranges and rules to log and block them.
It seems odd but this time the system had no problems.
I'm not telling this because I know the reasons for it, but just for the sake of ccompleteness.
Since my original system was migrated from 2.0 to 2.2, it may not be as clean as expected. I would need to investigate a little bit more.
13
Installation and Upgrades / Re: Why don't Zentyal partitions resize after VM disk resizing (VirtualBox) ?
« on: February 25, 2012, 05:25:17 pm »
This is a common Linux systems administration task, not Zentyal's specific.
The filesystem is a logical structure.
What you have done is enlarging the "physical" support and now you need to do the same with the logical support.
If you are using LVM, you need to enlarge the volumes first.
You can read these docs:
The filesystem is a logical structure.
What you have done is enlarging the "physical" support and now you need to do the same with the logical support.
If you are using LVM, you need to enlarge the volumes first.
You can read these docs:
14
Installation and Upgrades / Re: [Partially solved] Error> Could not get lock for service: firewal
« on: February 23, 2012, 11:39:21 am »
I've hit this issue as well.
Trying to block access to Facebook by IP, I created a Network Object with all the reported ranges.
Firewall stopped responding any more, and after rebooting the server become unresponsive network-wise.
I had to disable the firewall service and enable the apache one in order to get in and clean up that mess.
Deleting the Network Object solved the issue, but I had to spend quite some time trying to figure out what went wrong (I did not immediately relate the firewall issues with the Facebook ranges).
But now I am concerned:
1. If blocking a few ranges cause these problems, it limits the usefulness of the firewall, right?
2. If there are practical limits to what the firewall can do, why doesn't Zentyal warn about it before allowing the user to commit the changes?
Trying to block access to Facebook by IP, I created a Network Object with all the reported ranges.
Firewall stopped responding any more, and after rebooting the server become unresponsive network-wise.
I had to disable the firewall service and enable the apache one in order to get in and clean up that mess.
Deleting the Network Object solved the issue, but I had to spend quite some time trying to figure out what went wrong (I did not immediately relate the firewall issues with the Facebook ranges).
But now I am concerned:
1. If blocking a few ranges cause these problems, it limits the usefulness of the firewall, right?
2. If there are practical limits to what the firewall can do, why doesn't Zentyal warn about it before allowing the user to commit the changes?
15
Installation and Upgrades / Re: 2.0 to 2.2 make me lost users
« on: February 21, 2012, 08:48:27 pm »
No, I'm not implying that those lines in the LDIF file are causing the problems in the upgrade, that is totally unrelated. The migration uses live data not the one in configuration backups.
Editing the LDIF files was a last resort to get the data back, since Zentyal 2.2 will not take the configuration of Zentyal 2.0.
I removed the Zarafa lines because they were left behind by the software (despite having uninstalled Zarafa a long time ago).
Editing the LDIF files was a last resort to get the data back, since Zentyal 2.2 will not take the configuration of Zentyal 2.0.
I removed the Zarafa lines because they were left behind by the software (despite having uninstalled Zarafa a long time ago).