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.


Messages - itbungler

Pages: [1]
1
Installation and Upgrades / Re: can't log in Webadmin
« on: May 27, 2021, 09:44:56 am »
Hi,

meanwhile I can reproduce the issue.
Workaround is to restart Service zentyal.webadmin-uwsgi
After that you can logon the gui again.

my2cents
ITBungler

2
Installation and Upgrades / Re: can't log in Webadmin
« on: May 22, 2021, 10:08:20 pm »
Do you have restarted the host?
In general this looks like a DB/SQL Issue.
So reboot should fix this anyhow.
Otherwise or if a reboot is not possible I suggest to check mysql service.

my2cents
ITBungler

3
Directory and Authentication / gidNumber on Zentyal/DC
« on: May 22, 2021, 08:57:04 pm »
Hi Folks,

facing the following issue with my Zentyal Server.
My goal is to use a different primary group than 2513 for a AD User in my landscape.
In total I have 3 Domain Controller (2x ARM and 1x x86_64)
On the ARM Hosts everything works as expected, but not on my x86_64, that is my Zentyal Host.
When I call id for "my Test User" i get back the expected group that i maintained in sam.ldb as gidNumber.
sam.ldb get replicated fine, sam.ldb entries are the same on all 3 DCs as expected.
When I do the same on my Zentyal Host  I get back 2513, "Domain Users" and not the one I get on the ARM Hosts.
Example:
On ARM HOST: id myuser -> uid=xxxx(myuser) gid=yyyy(mygroup) groups=yyyy(mygroup),2513(domain users)
On Zentyal HOST: id myuser -> uid=xxxx(myDomain\myuser),gid=2513(myDomain\domain users) groups=2513(myDomain\domain users),yyyy(myDomain\mygroup)

I assume this is related to the authentication, as I use sssd on the ARM Hosts but not on Zentyal Host.
So any Idea what need to be done to bring Zentyalhost to give back the gidNumber instead of "Domain Users"?
Any feedback welcome, beside install sssd on Zentyal Host, what I want to avoid  ;D

BR
ITBungler


4
Wait until the upgrade boutton will be shown in the dashboard in the next days.

https://wiki.zentyal.org/wiki/Zentyal_6.0_Announcement#Upgrading

So stay tuned

ITBungler

5
Hi Folks,

I made a upgrade of my Zentyal from 4.1.12 to 5.0.
Zentyal failed because it can not connect to the redis server:

service zentyal stop
Reconnecting to redis server (1 try)... at /usr/share/perl5/EBox/Config/Redis.pm line 476.
Reconnecting to redis server (2 try)... at /usr/share/perl5/EBox/Config/Redis.pm line 476.
Reconnecting to redis server (3 try)... at /usr/share/perl5/EBox/Config/Redis.pm line 476.
Reconnecting to redis server (4 try)... at /usr/share/perl5/EBox/Config/Redis.pm line 476.
...
Redis command 'multi ' failed: [multi] NOAUTH Authentication required.,  at /usr/share/perl5/EBox/Config/Redis.pm line 453


The only thing I found was
https://forum.zentyal.org/index.php/topic,30923.msg106030.html#msg106030
but honestly I want avoid a new installation or restore a backup...
So any hints what I can do to make the Authentication to the redis server known by zentyal?

Thanks
ITBungler

Pages: [1]