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.
16
Installation and Upgrades / Not using Zental after 2+ years.
« on: August 03, 2014, 04:05:09 pm »
So after playing with Zentyal 3.5 for over a week, I've decided that I have to stop using Zentyal and go back to using straight Ubuntu. Basically I think the openchange and sogo stuff is not ready and likely will not be ready for years. I have been using EGroupware, and it is AMAZING. It even offers activesync support if you are willing to pay for it. I installed the latest version of Egroupware on the latest version of Ubuntu and it Just Worked. I have been trying for three days to get it to work on Zentyal 3.5 without success. I believe it has something to do with haproxy hijacking the ports and some part of Egroupware expecting to be on a standard port, but I can't be sure. And unfortunately haproxy is now a fundamental part of zentyal. You can't even uninstall the webserver module and manage apache yourself, haproxy prevents you from doing that, which is yet another deal breaker for when Zentyal 4.0 comes out.
So I am going to miss the convenience of Zentyal, especially when it comes to the firewall and network management, but if I have choose between Zentyal and using apache/Egroupware I'm going to have to choose apache/Egroupware.
James
So I am going to miss the convenience of Zentyal, especially when it comes to the firewall and network management, but if I have choose between Zentyal and using apache/Egroupware I'm going to have to choose apache/Egroupware.
James
17
Installation and Upgrades / Upgrade Zentyal 3.4 to 3.5: Total Fail
« on: July 30, 2014, 04:48:27 am »
I upgraded my company server from Zentyal 3.3 to 3.4 without any issues. Then I upgraded it from 3.4 to 3.5 and the result is a total failure:
I was pleasantly surprised that everything seemed to go OK at first, and even the users made it over. All the users lost their email account and content, so I had to go to each user and add their email account back, and /var/vmail had been wiped clean. I considered that getting off light, so after fixing that I tried sending myself a test email. Which failed. After checking the mail log there was a constant stream of "virtual_alias_maps map lookup problem" errors. I mean constant, it was filling up my log partition. Unfortunately with 3.5 there is no magic script to reinstall everything user related, so I tried reinstalling user module, which of course meant that everything that depends on it like jabber and webserver.
There were no error messages on the console during the reinstall, but the zentyal log was another matter, and it wasn't pretty. So now my entire company email is down and I am going to have to get up at the butt crack of dawn early, drive to my hosting company, and install Zentyal from scratch and restore all the data from backups. Awesome! Thanks Zentyal!
I think I'm going to be keeping my customers on 3.3 for a while longer, at least until I can schedule some SERIOUS downtime with each of them.
James
Typical mail log errors:
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: 08A732A0427: message-id=<20140730014729.08A732A0427@ns1.nontrivial.net>
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: warning: dict_ldap_lookup: Search error 1: Operations error
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: warning: ldap:valiases lookup error for "root@ns1.nontrivial.net"
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: warning: 08A732A0427: virtual_alias_maps map lookup problem for root@ns1.nontrivial.net -- message not accepted, try again later
Typical zentyal log errors:
2014/07/29 21:32:51 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (1 attempts)
2014/07/29 21:33:01 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (100 attempts)
2014/07/29 21:33:11 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (200 attempts)
2014/07/29 21:33:21 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (300 attempts)
2014/07/29 21:33:22 DEBUG> Ldap.pm:219 EBox::Ldap::safeConnect - FATAL: Could not connect to samba LDAP server: connect: No such file or directory at FATAL: Could not connect to samba LDAP server: connect: No such file or directory at /usr/share/perl5/EBox/Ldap.pm line 219
EBox::Ldap::safeConnect('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Ldap.pm line 173
EBox::Ldap::connection('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Ldap.pm line 505
EBox::Ldap::rootDse('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Samba/FSMO.pm line 125
EBox::Samba::FSMO::getSchemaMaster('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 84
EBox::Module::LDAP::_connectToSchemaMaster('EBox::Samba=HASH(0xa3d7524)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 215
EBox::Module::LDAP::_loadSchemasFiles('EBox::Samba=HASH(0xa3d7524)', 'ARRAY(0xa40f44c)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 207
EBox::Module::LDAP::_loadSchemas('EBox::Samba=HASH(0xa3d7524)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 269
EBox::Module::LDAP::_performSetup('EBox::Samba=HASH(0xa3d7524)') called at /usr/share/perl5/EBox/Samba.pm line 836
EBox::Samba::_regenConfig('EBox::Samba=HASH(0xa3d7524)', 'restart', 1, 'restartModules', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 999
eval {...} at /usr/share/perl5/EBox/Module/Service.pm line 998
EBox::Module::Service::restartService('EBox::Samba=HASH(0xa3d7524)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 129
eval {...} at /usr/share/perl5/EBox/Util/Init.pm line 127
EBox::Util::Init::moduleAction('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 255
EBox::Util::Init::moduleRestart('samba') called at /etc/init.d/zentyal line 59
main::main at /etc/init.d/zentyal line 80
2014/07/29 21:33:22 ERROR> Service.pm:1001 EBox::Module::Service::restartService - Error restarting service: FATAL: Could not connect to samba LDAP server: connect: No such file or directory
2014/07/29 21:33:22 ERROR> Service.pm:1003 EBox::Module::Service::restartService - FATAL: Could not connect to samba LDAP server: connect: No such file or directory at FATAL: Could not connect to samba LDAP server: connect: No such file or directory at /usr/share/perl5/EBox/Module/Service.pm line 1003
EBox::Module::Service::restartService('EBox::Samba=HASH(0xa3d7524)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 129
eval {...} at /usr/share/perl5/EBox/Util/Init.pm line 127
EBox::Util::Init::moduleAction('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 255
EBox::Util::Init::moduleRestart('samba') called at /etc/init.d/zentyal line 59
main::main at /etc/init.d/zentyal line 80
I was pleasantly surprised that everything seemed to go OK at first, and even the users made it over. All the users lost their email account and content, so I had to go to each user and add their email account back, and /var/vmail had been wiped clean. I considered that getting off light, so after fixing that I tried sending myself a test email. Which failed. After checking the mail log there was a constant stream of "virtual_alias_maps map lookup problem" errors. I mean constant, it was filling up my log partition. Unfortunately with 3.5 there is no magic script to reinstall everything user related, so I tried reinstalling user module, which of course meant that everything that depends on it like jabber and webserver.
There were no error messages on the console during the reinstall, but the zentyal log was another matter, and it wasn't pretty. So now my entire company email is down and I am going to have to get up at the butt crack of dawn early, drive to my hosting company, and install Zentyal from scratch and restore all the data from backups. Awesome! Thanks Zentyal!
I think I'm going to be keeping my customers on 3.3 for a while longer, at least until I can schedule some SERIOUS downtime with each of them.
James
Typical mail log errors:
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: 08A732A0427: message-id=<20140730014729.08A732A0427@ns1.nontrivial.net>
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: warning: dict_ldap_lookup: Search error 1: Operations error
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: warning: ldap:valiases lookup error for "root@ns1.nontrivial.net"
Jul 29 20:47:29 ns1 postfix/cleanup[15542]: warning: 08A732A0427: virtual_alias_maps map lookup problem for root@ns1.nontrivial.net -- message not accepted, try again later
Typical zentyal log errors:
2014/07/29 21:32:51 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (1 attempts)
2014/07/29 21:33:01 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (100 attempts)
2014/07/29 21:33:11 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (200 attempts)
2014/07/29 21:33:21 WARN> Ldap.pm:215 EBox::Ldap::safeConnect - Could not connect to Samba LDB: connect: No such file or directory, retrying. (300 attempts)
2014/07/29 21:33:22 DEBUG> Ldap.pm:219 EBox::Ldap::safeConnect - FATAL: Could not connect to samba LDAP server: connect: No such file or directory at FATAL: Could not connect to samba LDAP server: connect: No such file or directory at /usr/share/perl5/EBox/Ldap.pm line 219
EBox::Ldap::safeConnect('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Ldap.pm line 173
EBox::Ldap::connection('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Ldap.pm line 505
EBox::Ldap::rootDse('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Samba/FSMO.pm line 125
EBox::Samba::FSMO::getSchemaMaster('EBox::Samba::FSMO=HASH(0xb705214)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 84
EBox::Module::LDAP::_connectToSchemaMaster('EBox::Samba=HASH(0xa3d7524)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 215
EBox::Module::LDAP::_loadSchemasFiles('EBox::Samba=HASH(0xa3d7524)', 'ARRAY(0xa40f44c)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 207
EBox::Module::LDAP::_loadSchemas('EBox::Samba=HASH(0xa3d7524)') called at /usr/share/perl5/EBox/Module/LDAP.pm line 269
EBox::Module::LDAP::_performSetup('EBox::Samba=HASH(0xa3d7524)') called at /usr/share/perl5/EBox/Samba.pm line 836
EBox::Samba::_regenConfig('EBox::Samba=HASH(0xa3d7524)', 'restart', 1, 'restartModules', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 999
eval {...} at /usr/share/perl5/EBox/Module/Service.pm line 998
EBox::Module::Service::restartService('EBox::Samba=HASH(0xa3d7524)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 129
eval {...} at /usr/share/perl5/EBox/Util/Init.pm line 127
EBox::Util::Init::moduleAction('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 255
EBox::Util::Init::moduleRestart('samba') called at /etc/init.d/zentyal line 59
main::main at /etc/init.d/zentyal line 80
2014/07/29 21:33:22 ERROR> Service.pm:1001 EBox::Module::Service::restartService - Error restarting service: FATAL: Could not connect to samba LDAP server: connect: No such file or directory
2014/07/29 21:33:22 ERROR> Service.pm:1003 EBox::Module::Service::restartService - FATAL: Could not connect to samba LDAP server: connect: No such file or directory at FATAL: Could not connect to samba LDAP server: connect: No such file or directory at /usr/share/perl5/EBox/Module/Service.pm line 1003
EBox::Module::Service::restartService('EBox::Samba=HASH(0xa3d7524)', 'restartModules', 1) called at /usr/share/perl5/EBox/Util/Init.pm line 129
eval {...} at /usr/share/perl5/EBox/Util/Init.pm line 127
EBox::Util::Init::moduleAction('samba', 'restartService', 'restart') called at /usr/share/perl5/EBox/Util/Init.pm line 255
EBox::Util::Init::moduleRestart('samba') called at /etc/init.d/zentyal line 59
main::main at /etc/init.d/zentyal line 80
18
Installation and Upgrades / Roadmap Questions
« on: July 27, 2014, 12:16:15 am »
I just looked over the 4.0 roadmap and I am confused. Can anybody please help me understand?
Stabilization and improvement of all the current features:
- Support for shared calendars & contacts
- User management
- Virtual Domain hosting
Umm, aren't these already available in 3.5?
Other:
- Improved Q&A processes, tools and incident follow up method
Huh? Is this some sort of internal Zentyal process?
- Configuration backup on the Zentyal Server UI (no Free Zentyal Account registration required)
Huh? I already do not use a Zentyal account. Does this mean my configuration will be backed up automatically whether I want it to be or not, or else backed up locally, or what? I prefer to back up my own servers in a manner I understand and trust, so I hope this "feature" will be optional.
- Removal of the Webserver and Webmail module (Roundcube)
I understand removing the Webmail module, but also the web server module? Does that mean that Zentyal will no longer be managing apache anymore? If so that's pretty crappy.
James
PS Something like user corner is extremely useful.
Stabilization and improvement of all the current features:
- Support for shared calendars & contacts
- User management
- Virtual Domain hosting
Umm, aren't these already available in 3.5?
Other:
- Improved Q&A processes, tools and incident follow up method
Huh? Is this some sort of internal Zentyal process?
- Configuration backup on the Zentyal Server UI (no Free Zentyal Account registration required)
Huh? I already do not use a Zentyal account. Does this mean my configuration will be backed up automatically whether I want it to be or not, or else backed up locally, or what? I prefer to back up my own servers in a manner I understand and trust, so I hope this "feature" will be optional.
- Removal of the Webserver and Webmail module (Roundcube)
I understand removing the Webmail module, but also the web server module? Does that mean that Zentyal will no longer be managing apache anymore? If so that's pretty crappy.
James
PS Something like user corner is extremely useful.
19
Installation and Upgrades / OpenChange and Evolution?
« on: July 20, 2014, 11:15:01 pm »
I have been running Zentyal 3.5 on my personal server and besides a few issues like no apparent way to preserve users when upgrading, User Corner missing, and there being a boatload of errors in the Zentyal log, it seems stable enough. I run Ubuntu on my workstation and few years ago I switched from Evolution to Thunderbird. One of the features of Evolutions was that it could natively talk to Exchange servers, and since OpenChange is now available I was wondering if anybody has had any experience using Evolution with OpenChange?
James
James
20
Installation and Upgrades / Zentyal 3.5 Answers
« on: July 08, 2014, 10:38:49 pm »
Hello,
I recently posted about my adventures installing 3.5 in another post (https://forum.zentyal.org/index.php/topic,22473.0.html) but didn't get any of my questions answered. So I had some more time to investigate, and I have answered two out of the three:
* How do I change what the default shell for a domain user?
You can use "getent passwd" to list all users, samba-tool to add users, and ldbmodify to modify users settings. But ldbmodify is a pain to use, so what I did was make sure PAM was enabled for LDAP users and then just used "chsh -s /bin/bash". You get an error about the user not existing in /etc/passwd, but it works.
* I assume the difference between Webmail and OE Webmail is
you don't get shared anything with plain old Webmail?
Yes, you get all the groupware goodness only if you use OE Webmail instead of regular Webmail. Except for some lack of customization (org name on login, login URL) I actually like OE Webmail a lot.
* What happened to User Corner? How do folks change their
password now?
I'm still not sure what happened to User Corner, how users can change their own passwords, or how to set up fetchmail in 3.5.
James
PS The LDAP user group changed from "__USERS__" to "domain users", and the email is now stored in "/var/vmail/domain/user/Maildir" instead of "/var/vmail/domain/user".
I recently posted about my adventures installing 3.5 in another post (https://forum.zentyal.org/index.php/topic,22473.0.html) but didn't get any of my questions answered. So I had some more time to investigate, and I have answered two out of the three:
* How do I change what the default shell for a domain user?
You can use "getent passwd" to list all users, samba-tool to add users, and ldbmodify to modify users settings. But ldbmodify is a pain to use, so what I did was make sure PAM was enabled for LDAP users and then just used "chsh -s /bin/bash". You get an error about the user not existing in /etc/passwd, but it works.
* I assume the difference between Webmail and OE Webmail is
you don't get shared anything with plain old Webmail?
Yes, you get all the groupware goodness only if you use OE Webmail instead of regular Webmail. Except for some lack of customization (org name on login, login URL) I actually like OE Webmail a lot.
* What happened to User Corner? How do folks change their
password now?
I'm still not sure what happened to User Corner, how users can change their own passwords, or how to set up fetchmail in 3.5.
James
PS The LDAP user group changed from "__USERS__" to "domain users", and the email is now stored in "/var/vmail/domain/user/Maildir" instead of "/var/vmail/domain/user".
21
Installation and Upgrades / Zentyal 3.5 Installation Experience
« on: July 06, 2014, 11:54:18 pm »
I just got done installing Zentyal 3.5 and I wanted to let you know how it went. Basically it was painful but it have it up and running now. I haven't installed openchange yet because I wanted to make sure that the system was stable first. First the questions I have:
* How do I change what the default shell for a domain user?
* I assume the difference between Webmail and OE Webmail is
you don't get shared anything with plain old Webmail?
* What happened to User Corner? How do folks change their
password now?
Next up is a few issues I ran into and had to overcome:
* The domain users group has changed from "__USERS__" to
"domain users". Yes, including the very annoying space in the name.
* The mail is stored in a different place. It has moved from
"/var/vmail/domain/user/" to "/var/vmail/domain/user/Maildir". This
means restoring user email after the upgrade has become more
challenging, and I need to update a few maintenance scripts.
* I am getting a lot of "SmartWatch is experimental" in my perl scripts.
This is due to using a newer version of perl in 14.04, not Zentyal.
* When booting I get a "diskfilter writes are not supported" error. This
is due to some issue with grub and using a RAID array. As far as I can
tell this is a harmless issue.
* I have three interfaces on my server (int wired, int wireless, and ext),
and the Zentyal portion of the install blew up rather spectacularly when
it got to the network configuration. The system was unusable until I
disabled an interface, saved, and enabled it again.
Finally, I am getting a LOT of errors in the Zentyal log. I believe I have
examples of all I have seen below:
2014/07/06 14:32:27 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $hostname in substitution (s///) at /usr/share/perl5/EBox/DHCP.pm line 1076.
2014/07/06 14:32:28 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $dir_path in concatenation (.) or string at /usr/share/perl5/HTML/Mason/Tools.pm line 117.
2014/07/06 14:34:24 WARN> zentyal.psgi:43 main::__ANON__ - Smartmatch is experimental at /usr/share/perl5/EBox/HAProxy/Model/HAProxyServices.pm line 693.
2014/07/06 14:40:06 WARN> zentyal.psgi:43 main::__ANON__ - Missing argument in sprintf at /usr/share/perl5/EBox/Model/DataForm.pm line 765, <GEN0> line 523.
2014/07/06 14:55:11 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value in numeric lt (<) at /usr/share/zentyal/templates/ajax/setter/textSetter.mas line 11.
2014/07/06 15:23:05 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $params{"uid"} in numeric ge (>=) at /usr/share/perl5/EBox/Samba/CGI/AddUser.pm line 81, <GEN0> line 2366.
2014/07/06 15:28:22 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value in string ne at /usr/share/zentyal/templates/mail/alias.mas line 230.
So I'm not sure if I would recommend upgrading to 3.5 yet.
James
* How do I change what the default shell for a domain user?
* I assume the difference between Webmail and OE Webmail is
you don't get shared anything with plain old Webmail?
* What happened to User Corner? How do folks change their
password now?
Next up is a few issues I ran into and had to overcome:
* The domain users group has changed from "__USERS__" to
"domain users". Yes, including the very annoying space in the name.
* The mail is stored in a different place. It has moved from
"/var/vmail/domain/user/" to "/var/vmail/domain/user/Maildir". This
means restoring user email after the upgrade has become more
challenging, and I need to update a few maintenance scripts.
* I am getting a lot of "SmartWatch is experimental" in my perl scripts.
This is due to using a newer version of perl in 14.04, not Zentyal.
* When booting I get a "diskfilter writes are not supported" error. This
is due to some issue with grub and using a RAID array. As far as I can
tell this is a harmless issue.
* I have three interfaces on my server (int wired, int wireless, and ext),
and the Zentyal portion of the install blew up rather spectacularly when
it got to the network configuration. The system was unusable until I
disabled an interface, saved, and enabled it again.
Finally, I am getting a LOT of errors in the Zentyal log. I believe I have
examples of all I have seen below:
2014/07/06 14:32:27 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $hostname in substitution (s///) at /usr/share/perl5/EBox/DHCP.pm line 1076.
2014/07/06 14:32:28 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $dir_path in concatenation (.) or string at /usr/share/perl5/HTML/Mason/Tools.pm line 117.
2014/07/06 14:34:24 WARN> zentyal.psgi:43 main::__ANON__ - Smartmatch is experimental at /usr/share/perl5/EBox/HAProxy/Model/HAProxyServices.pm line 693.
2014/07/06 14:40:06 WARN> zentyal.psgi:43 main::__ANON__ - Missing argument in sprintf at /usr/share/perl5/EBox/Model/DataForm.pm line 765, <GEN0> line 523.
2014/07/06 14:55:11 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value in numeric lt (<) at /usr/share/zentyal/templates/ajax/setter/textSetter.mas line 11.
2014/07/06 15:23:05 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $params{"uid"} in numeric ge (>=) at /usr/share/perl5/EBox/Samba/CGI/AddUser.pm line 81, <GEN0> line 2366.
2014/07/06 15:28:22 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value in string ne at /usr/share/zentyal/templates/mail/alias.mas line 230.
So I'm not sure if I would recommend upgrading to 3.5 yet.
James
22
Installation and Upgrades / My Zentyal 3.4 Mail Server is Spamming Me!
« on: June 17, 2014, 05:06:22 pm »
OK, when I tried to upgrade from 3.3 to 3.4 it didn't go very well. To make a long story short, I eventually had to run the zentyal-users reinstall script and essentially start over from scratch. But at least everything was working again. At least I thought it was, but now my mail server is forwarding to me a notifications about undeliverable email. I might have been hacked, but I suspect with all my other Zentyal issues that it is some configuration issue. The really weird think is they come in a single batch a day of about 30 to a hundred. Does anybody have any suggestions?
James
James
23
Installation and Upgrades / Zentyal 3.4 Error After Most Recent Update
« on: June 07, 2014, 04:13:00 pm »
After the most recent Zentyal 3.4 update I am getting the following error on an hourly basis:
etc/cron.hourly/90zentyal-manage-logs:
Prototype mismatch: sub EBox::Firewall::try () vs (&;$) at /usr/share/perl5/EBox/Firewall.pm line 50
I am also getting a ridiculous amount of errors in zentyal.log, a constant stream of all types of errors. Exactly what was in the last update and how do I fix it? Here are a sample of some of the other errors I am getting:
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.redis-usercorner'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.slapd'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'zentyal.heimdal-kdc'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'zentyal.heimdal-kpasswd'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - cat /var/run/apache2/apache2.pid
2014/06/07 09:09:14 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'dovecot'
2014/06/07 09:09:14 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.postgrey'
2014/06/07 09:09:14 WARN> zentyal.psgi:43 main::__ANON__ - Odd number of elements in hash assignment at /usr/share/perl5/EBox/Dashboard/ModuleStatus.pm line 47, <GEN0> line 129.
2014/06/07 09:09:14 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.fetchmail'
2014/06/07 09:09:14 WARN> zentyal.psgi:43 main::__ANON__ - Odd number of elements in hash assignment at /usr/share/perl5/EBox/Dashboard/ModuleStatus.pm line 47, <GEN0> line 129.
2014/06/07 09:09:14 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $_[7] in list assignment at /usr/share/perl5/EBox/Dashboard/ModuleStatus.pm line 47, <GEN0> line 129.
2014/06/07 09:09:18 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - dpkg --clear-avail
2014/06/07 09:09:40 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal-samba/s4sync (pid: 21188) - /sbin/status 'zentyal.s4sync'
2014/06/07 09:09:40 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal-samba/s4sync (pid: 21188) - /sbin/status 'samba-ad-dc'
2014/06/07 09:09:40 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal-samba/s4sync (pid: 21188) - /sbin/status 'nmbd'
Actually it looks like one of the problems is debug mode is turned on, which is filling up my log and making it impossible to troubleshoot the firewall issue. How do I turn that off?
James
etc/cron.hourly/90zentyal-manage-logs:
Prototype mismatch: sub EBox::Firewall::try () vs (&;$) at /usr/share/perl5/EBox/Firewall.pm line 50
I am also getting a ridiculous amount of errors in zentyal.log, a constant stream of all types of errors. Exactly what was in the last update and how do I fix it? Here are a sample of some of the other errors I am getting:
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.redis-usercorner'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.slapd'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'zentyal.heimdal-kdc'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'zentyal.heimdal-kpasswd'
2014/06/07 09:09:13 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - cat /var/run/apache2/apache2.pid
2014/06/07 09:09:14 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'dovecot'
2014/06/07 09:09:14 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.postgrey'
2014/06/07 09:09:14 WARN> zentyal.psgi:43 main::__ANON__ - Odd number of elements in hash assignment at /usr/share/perl5/EBox/Dashboard/ModuleStatus.pm line 47, <GEN0> line 129.
2014/06/07 09:09:14 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - /sbin/status 'ebox.fetchmail'
2014/06/07 09:09:14 WARN> zentyal.psgi:43 main::__ANON__ - Odd number of elements in hash assignment at /usr/share/perl5/EBox/Dashboard/ModuleStatus.pm line 47, <GEN0> line 129.
2014/06/07 09:09:14 WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $_[7] in list assignment at /usr/share/perl5/EBox/Dashboard/ModuleStatus.pm line 47, <GEN0> line 129.
2014/06/07 09:09:18 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 5891) - dpkg --clear-avail
2014/06/07 09:09:40 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal-samba/s4sync (pid: 21188) - /sbin/status 'zentyal.s4sync'
2014/06/07 09:09:40 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal-samba/s4sync (pid: 21188) - /sbin/status 'samba-ad-dc'
2014/06/07 09:09:40 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal-samba/s4sync (pid: 21188) - /sbin/status 'nmbd'
Actually it looks like one of the problems is debug mode is turned on, which is filling up my log and making it impossible to troubleshoot the firewall issue. How do I turn that off?
James
24
Installation and Upgrades / Zentyal 3.4 Squid Log Error
« on: April 21, 2014, 03:44:27 pm »
Hello,
Once I upgraded to Zentyal 3.4 I started getting several errors when cron.daily scripts ran. I have managed to work through all of them except one. I believe it is a Squid error:
/etc/cron.daily/logrotate:
2014/04/21 07:44:56| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) '127.0.0.0/8'
2014/04/21 07:44:56| WARNING: because of this '127.0.0.0/8' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '127.0.0.0/8' from the ACL named 'to_localhost'
2014/04/21 07:44:56| WARNING: (B) '::1' is a subnetwork of (A) '::1'
2014/04/21 07:44:56| WARNING: because of this '::1' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '::1' from the ACL named 'to_localhost'
2014/04/21 07:44:56| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) '127.0.0.0/8'
2014/04/21 07:44:56| WARNING: because of this '127.0.0.0/8' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '127.0.0.0/8' from the ACL named 'to_localhost'
2014/04/21 07:44:56| WARNING: (B) '::1' is a subnetwork of (A) '::1'
2014/04/21 07:44:56| WARNING: because of this '::1' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '::1' from the ACL named 'to_localhost'
Any help would be greatly appreciated.
James
Once I upgraded to Zentyal 3.4 I started getting several errors when cron.daily scripts ran. I have managed to work through all of them except one. I believe it is a Squid error:
/etc/cron.daily/logrotate:
2014/04/21 07:44:56| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) '127.0.0.0/8'
2014/04/21 07:44:56| WARNING: because of this '127.0.0.0/8' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '127.0.0.0/8' from the ACL named 'to_localhost'
2014/04/21 07:44:56| WARNING: (B) '::1' is a subnetwork of (A) '::1'
2014/04/21 07:44:56| WARNING: because of this '::1' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '::1' from the ACL named 'to_localhost'
2014/04/21 07:44:56| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) '127.0.0.0/8'
2014/04/21 07:44:56| WARNING: because of this '127.0.0.0/8' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '127.0.0.0/8' from the ACL named 'to_localhost'
2014/04/21 07:44:56| WARNING: (B) '::1' is a subnetwork of (A) '::1'
2014/04/21 07:44:56| WARNING: because of this '::1' is ignored to keep splay tree searching predictable
2014/04/21 07:44:56| WARNING: You should probably remove '::1' from the ACL named 'to_localhost'
Any help would be greatly appreciated.
James
25
Installation and Upgrades / NTP Issue
« on: April 06, 2014, 05:33:15 pm »
On Zentyal 3.2 I get this error when rebooting or restarting NTP:
2014/04/06 10:30:24 INFO> Service.pm:987 EBox::Module::Service::restartService - Restarting service for module: ntp
2014/04/06 10:30:28 ERROR> ConfigureDispatchers.pm:354 EBox::Events::Model::ConfigureDispatchers::acquireConfModel - When loading dispatcher EBox::Event::Dispatcher::Mail: Can't locate EBox/Event/Dispatcher/Mail.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at (eval 1019) line 2, <GEN0> line 9.
BEGIN failed--compilation aborted at (eval 1019) line 2, <GEN0> line 9.
2014/04/06 10:30:28 DEBUG> HasMany.pm:336 EBox::Types::HasMany::__ANON__ - {data} {value} does not exist. at /usr/share/perl5/EBox/Types/HasMany.pm line 336
EBox::Types::HasMany::_restoreFromHash('EBox::Types::HasMany=HASH(0x972c880)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Types/Abstract.pm line 521
EBox::Types::Abstract::restoreFromHash('EBox::Types::HasMany=HASH(0x972c880)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Types/Union.pm line 460
EBox::Types::Union::_restoreFromHash('EBox::Types::Union=HASH(0x9776d30)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Types/Abstract.pm line 521
EBox::Types::Abstract::restoreFromHash('EBox::Types::Union=HASH(0x9776d30)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Model/DataTable.pm line 900
EBox::Model::DataTable::_setRowElement('EBox::Types::Union=HASH(0x9776d30)', 'EBox::Model::Row=HASH(0x9776d6c)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Model/DataTable.pm line 884
EBox::Model::DataTable::row('EBox::Events::Model::ConfigureDispatchers=HASH(0x9716138)', 'cnfgrd4') called at /usr/share/perl5/EBox/Model/DataTable.pm line 1404
EBox::Model::DataTable::enabledRows('EBox::Events::Model::ConfigureDispatchers=HASH(0x9716138)') called at /usr/share/perl5/EBox/EventDaemon.pm line 266
EBox::EventDaemon::_loadModules('EBox::EventDaemon=HASH(0x833f9a4)', 'dispatcher') called at /usr/share/perl5/EBox/EventDaemon.pm line 205
EBox::EventDaemon::_mainDispatcherLoop('EBox::EventDaemon=HASH(0x833f9a4)') called at /usr/share/perl5/EBox/EventDaemon.pm line 121
EBox::EventDaemon::run('EBox::EventDaemon=HASH(0x833f9a4)') called at /usr/share/perl5/EBox/EventDaemon.pm line 490
Anybody?
2014/04/06 10:30:24 INFO> Service.pm:987 EBox::Module::Service::restartService - Restarting service for module: ntp
2014/04/06 10:30:28 ERROR> ConfigureDispatchers.pm:354 EBox::Events::Model::ConfigureDispatchers::acquireConfModel - When loading dispatcher EBox::Event::Dispatcher::Mail: Can't locate EBox/Event/Dispatcher/Mail.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at (eval 1019) line 2, <GEN0> line 9.
BEGIN failed--compilation aborted at (eval 1019) line 2, <GEN0> line 9.
2014/04/06 10:30:28 DEBUG> HasMany.pm:336 EBox::Types::HasMany::__ANON__ - {data} {value} does not exist. at /usr/share/perl5/EBox/Types/HasMany.pm line 336
EBox::Types::HasMany::_restoreFromHash('EBox::Types::HasMany=HASH(0x972c880)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Types/Abstract.pm line 521
EBox::Types::Abstract::restoreFromHash('EBox::Types::HasMany=HASH(0x972c880)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Types/Union.pm line 460
EBox::Types::Union::_restoreFromHash('EBox::Types::Union=HASH(0x9776d30)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Types/Abstract.pm line 521
EBox::Types::Abstract::restoreFromHash('EBox::Types::Union=HASH(0x9776d30)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Model/DataTable.pm line 900
EBox::Model::DataTable::_setRowElement('EBox::Types::Union=HASH(0x9776d30)', 'EBox::Model::Row=HASH(0x9776d6c)', 'HASH(0x972c7cc)') called at /usr/share/perl5/EBox/Model/DataTable.pm line 884
EBox::Model::DataTable::row('EBox::Events::Model::ConfigureDispatchers=HASH(0x9716138)', 'cnfgrd4') called at /usr/share/perl5/EBox/Model/DataTable.pm line 1404
EBox::Model::DataTable::enabledRows('EBox::Events::Model::ConfigureDispatchers=HASH(0x9716138)') called at /usr/share/perl5/EBox/EventDaemon.pm line 266
EBox::EventDaemon::_loadModules('EBox::EventDaemon=HASH(0x833f9a4)', 'dispatcher') called at /usr/share/perl5/EBox/EventDaemon.pm line 205
EBox::EventDaemon::_mainDispatcherLoop('EBox::EventDaemon=HASH(0x833f9a4)') called at /usr/share/perl5/EBox/EventDaemon.pm line 121
EBox::EventDaemon::run('EBox::EventDaemon=HASH(0x833f9a4)') called at /usr/share/perl5/EBox/EventDaemon.pm line 490
Anybody?
26
Installation and Upgrades / CLI Updgrade?
« on: April 04, 2014, 06:17:57 pm »
Hello folks, I have several servers that I want to upgrade from 3.2 to 3.3 so that I can (hopefully) upgrade them to 3.4 more easily in the future. I would prefer to do this from the command line if at all possible because, well, that's how I roll. For my initial attempt I tried just updating sources.list and doing a dist-upgrade, but that didn't go well. I ended up having resinstall from scratch and add the users by hand. Needless to say I am trying to avoid that for the next few servers, since some of them have hundreds of users.
So my questions are:
* What is executed when you click the "upgrade to 3.3" button from the web interface?
* Can I run that command from the command line?
* Is there any way to add users from list? I used to be able to with EBox::UsersAndGroups::User, but that doesn't appear to work anymore.
Thanks,
James
So my questions are:
* What is executed when you click the "upgrade to 3.3" button from the web interface?
* Can I run that command from the command line?
* Is there any way to add users from list? I used to be able to with EBox::UsersAndGroups::User, but that doesn't appear to work anymore.
Thanks,
James
27
Installation and Upgrades / Unable to install antivirus in Zentyal 3.3 [SOLVED]
« on: March 10, 2014, 09:10:29 pm »
I just installed a fresh copy of Zentyal 3.3 and I am unable to install zentyal-antivirus. There isn't much detail in the popup or zentyal log, but when I try to install by hand I get this:
apt-get install zentyal-antivirus
The following packages have unmet dependencies:
zentyal-antivirus : Depends: libclamav-xs-perl but it is not installable
Whoops, just realized this was a duplicate: https://forum.zentyal.org/index.php/topic,20936.msg80424.html
James
apt-get install zentyal-antivirus
The following packages have unmet dependencies:
zentyal-antivirus : Depends: libclamav-xs-perl but it is not installable
Whoops, just realized this was a duplicate: https://forum.zentyal.org/index.php/topic,20936.msg80424.html
James
28
Installation and Upgrades / Shared Contacts and Calendars with Zentyal 3.3
« on: March 05, 2014, 08:37:34 pm »
Hello folks,
I recently upgraded my personal server from Zentyal 3.2 to 3.3 in order to check out the new OpenChange stuff. The upgrade seemed to go well and I installed the OpenChange module, but when I log into RoundCube I don't see any support for calendars or shared contacts. Am I missing something? Should I try reinstalling the webmail module?
James
I recently upgraded my personal server from Zentyal 3.2 to 3.3 in order to check out the new OpenChange stuff. The upgrade seemed to go well and I installed the OpenChange module, but when I log into RoundCube I don't see any support for calendars or shared contacts. Am I missing something? Should I try reinstalling the webmail module?
James
29
Installation and Upgrades / Static IP Address for PPPoE?
« on: February 18, 2014, 07:20:14 pm »
Unfortunately I am dealing with AT&T for the first time, and they only offer a router not a modem, and that router is profoundly brain dead. I can bridge the modem and set up a (dynamic?) PPPoE connection with Zentyal 3.2 just fine. But there is no way to tell the router to hand out a particular IP address and I can't figure out how to tell Zentyal that I have a static IP address and want to use it. I have tried modifying /etc/ppp/chap-secrets and /etc/ppp/peers/zentyal-ppp-eth1 with hook files, but I think I am missing something fundamental about PPPoE on linux here. Can anybody please tell me how one is supposed to set up a static IP address on linux using PPPoE?
James
James
30
Installation and Upgrades / Domain Controller DNS Issue
« on: January 27, 2014, 03:02:18 am »
I have a Zentyal 3.2 primary domain controller (ie server1) with a public and a private IP address (192.168.1.1), and I have a Zentyal 3.2 additional domain controller (ie server2) with a different public IP address but the same private IP address (192.168.1.1) at a different physical location. They are firewalled and communicate via the public internet. When logged into server 2, it always returns the correct IP addresses, but for any DHCP client after some amount of time after rebooting server2 or restarting it's dns server, it starts serving the clients dns values from server1. This is fatal because when a client wants to talk to server1 (the PDC) it gets handed an IP of 192.168.1.1 instead of it's public IP address as it should. Also, if a client wants to talk to server2 (the ADA), it gets handed the correct public address.
So my current workaround is a cron job that restarts the DNS server every thirty minutes, which isn't a great work around. Unfortunately I can't really try random things during business hours, so I am hoping somebody can shed some light on what the problem is. The existing samba documentation (http://trac.zentyal.org/wiki/Documentation/Community/Document/SambaScenario) is a bit out of date because you can no longer edit the network DNS settings if the DNS module is installed.
The next few things I am going to try are listed below, and I was also hoping to get some feedback as to whether or not anybody think they will have any effect.
* Toggling "Transparent DNS Cache" on and off.
* Adding 127.0.0.1 to the list of forwarders.
* Designating the public IP of server2 for DHCP client DNS and WINS.
Another thing is that every few minutes in the server2 (ADA) log, I get:
SysvolSync.pm:175 EBox::Samba::SysvolSync::sync - Synchronizing sysvol share from server1
SysvolSync.pm:187 EBox::Samba::SysvolSync::sync - child exited with value 255
If anybody could offer some advice on that, it would be greatly appreciated as well.
TIA,
James
So my current workaround is a cron job that restarts the DNS server every thirty minutes, which isn't a great work around. Unfortunately I can't really try random things during business hours, so I am hoping somebody can shed some light on what the problem is. The existing samba documentation (http://trac.zentyal.org/wiki/Documentation/Community/Document/SambaScenario) is a bit out of date because you can no longer edit the network DNS settings if the DNS module is installed.
The next few things I am going to try are listed below, and I was also hoping to get some feedback as to whether or not anybody think they will have any effect.
* Toggling "Transparent DNS Cache" on and off.
* Adding 127.0.0.1 to the list of forwarders.
* Designating the public IP of server2 for DHCP client DNS and WINS.
Another thing is that every few minutes in the server2 (ADA) log, I get:
SysvolSync.pm:175 EBox::Samba::SysvolSync::sync - Synchronizing sysvol share from server1
SysvolSync.pm:187 EBox::Samba::SysvolSync::sync - child exited with value 255
If anybody could offer some advice on that, it would be greatly appreciated as well.
TIA,
James