Author Topic: Zentyal 7.0.4 viewing log files  (Read 369 times)

ecc

  • Zen Apprentice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Zentyal 7.0.4 viewing log files
« on: June 14, 2022, 11:48:16 am »
A new an updated Z 7.0.4 throws this error when viewing any log file:

DBD::mysql::st execute failed: The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior. at /usr/share/perl5/EBox/MyDBEngine.pm line 478. ...propagated at /usr/share/perl5/EBox/CGI/Base.pm line 321. at /usr/share/perl5/EBox/CGI/Run.pm line 105

Anybody know a fix?

turalyon

  • Zen Warrior
  • ***
  • Posts: 108
  • Karma: +12/-0
    • View Profile
Re: Zentyal 7.0.4 viewing log files
« Reply #1 on: June 16, 2022, 12:43:07 pm »
Hi,

It's a bug. Below you have the link to the issue and the workaround.

* https://github.com/zentyal/zentyal/issues/2055#issuecomment-932964974

--

“This world is ours, and by the Holy Light we will keep it safe, now and forever".

dzidek23

  • Zen Apprentice
  • *
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: Zentyal 7.0.4 viewing log files
« Reply #2 on: June 27, 2022, 11:57:09 am »
Hi,

I also get this error every now and again. I noticed that it happens if I leave the Web Admin console open and let it expiry (overnight). Next morning I have to run 'zs webadmin restart' over ssh to get it sorted.

So remember to always logout ;)
« Last Edit: June 27, 2022, 12:03:45 pm by dzidek23 »

ecc

  • Zen Apprentice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: Zentyal 7.0.4 viewing log files
« Reply #3 on: June 27, 2022, 05:31:51 pm »
Thanks.

Latest round of updates doesn't seem top have fixed it which is disappointing.

Will have to use the workaround  :-[

Andy

dzidek23

  • Zen Apprentice
  • *
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Re: Zentyal 7.0.4 viewing log files
« Reply #4 on: June 28, 2022, 09:37:30 am »
That's funny (not) that I had problems with DBagent expiry only on expired system login. After reading this thread it started to happen regularly just like with everyone else.  :-\
Let see what's the workaround worth.