Author Topic: Zentyal 3.4 Error After Most Recent Update  (Read 2651 times)

nontrivial

  • Zen Warrior
  • ***
  • Posts: 181
  • Karma: +16/-0
    • View Profile
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

benicula

  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #1 on: June 07, 2014, 06:36:44 pm »
I was just pondering the thought of upgrading to the 3.4.4 core.  I had the server setup and mostly configured, updated the system and all zentyal components, despite the warning, and sure enough, it broke my system.  I'm on a clean install of the 3.4 iso x64 and all-swell.

I would love to see more more posts from members or moderators as to which modules to update and when without breaking the system.

Help is much appreciated! Also, I hope the above member finds the solution to the problem.

cynthb

  • Zen Apprentice
  • *
  • Posts: 7
  • Karma: +1/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #2 on: June 09, 2014, 12:00:10 am »
I am also getting the prototype mismatch errors, as well as the same debugging messages in zentyal.log. I would love to hear of a solution.

Skymatix

  • Zen Apprentice
  • *
  • Posts: 27
  • Karma: +0/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #3 on: June 09, 2014, 07:12:32 am »
I am also getting this error now!

heretic

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #4 on: June 10, 2014, 08:13:35 am »
Same problem after update.

MLutrov

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #5 on: June 10, 2014, 11:06:42 am »
Gotten this error quite a bit after running an update

Prototype mismatch: sub EBox::Firewall::try () vs (&;$) at /usr/share/perl5/EBox/Firewall.pm line 50

Any help?

nontrivial

  • Zen Warrior
  • ***
  • Posts: 181
  • Karma: +16/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #6 on: June 10, 2014, 04:50:19 pm »
Not to worry, all we have to do now is wait three more weeks, delete 500+ emails, occasionally truncate the zentyal logs so they don't fill up the partition, and then we can install 3.5 with the added bonus of wiping out all our user information! Sounds like a great solution to me. :-)

James

nontrivial

  • Zen Warrior
  • ***
  • Posts: 181
  • Karma: +16/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #7 on: June 10, 2014, 07:55:33 pm »
There is a new update available. Whilst applying it I got the following error:

Setting up zentyal-core (3.4.5) ...
ERROR 1045 (28000): Access denied for user 'james'@'localhost' (using password: NO)

I don't know why it's trying to use my username instead of the admin user or root, but it seems to have fixed the firewall prototype mismatch error but not the the debug level logging issue. I guess if manage-logs is working now then it's not a critical issue, but it still makes tracking down future issues more difficult.

James

Skymatix

  • Zen Apprentice
  • *
  • Posts: 27
  • Karma: +0/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #8 on: June 10, 2014, 10:07:46 pm »
Thank you for the info... will check it out tomorrow sometime.

heretic

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #9 on: June 11, 2014, 07:58:35 am »
There is a new update available. Whilst applying it I got the following error:

Setting up zentyal-core (3.4.5) ...
ERROR 1045 (28000): Access denied for user 'james'@'localhost' (using password: NO)

I don't know why it's trying to use my username instead of the admin user or root, but it seems to have fixed the firewall prototype mismatch error but not the the debug level logging issue. I guess if manage-logs is working now then it's not a critical issue, but it still makes tracking down future issues more difficult.

James
same. it's  'root'@'localhost' for me.
« Last Edit: June 11, 2014, 08:03:11 am by heretic »

J. A. Calvo

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1986
  • Karma: +67/-3
    • View Profile
    • http://blogs.zentyal.org/jacalvo
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #10 on: June 11, 2014, 03:39:03 pm »
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?

Set debug = no in /etc/zentyal/zentyal.conf
Zentyal Server Lead Developer

nontrivial

  • Zen Warrior
  • ***
  • Posts: 181
  • Karma: +16/-0
    • View Profile
Re: Zentyal 3.4 Error After Most Recent Update
« Reply #11 on: June 12, 2014, 07:38:53 pm »
J. A.,

Thanks for the reply. I made that change and restarted most of the modules (samba in particular was generating a lot of DEBUG messages) and it seems to have worked.

James