Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: DeHaynes on March 10, 2014, 09:30:11 pm
-
I just finished installing Zentyal at home this weekend. I am reviewing the logs for issues and I noticed a lot of "Missing argument: objectGUID" in the log.
EBox::Exceptions::External::new('EBox::Exceptions::MissingArgument', 'Missing argument: objectGUID') called at /usr/share/perl5/EBox/Exceptions/MissingArgument.pm line 50
EBox::Exceptions::MissingArgument::new('EBox::Exceptions::MissingArgument', 'objectGUID') called at /usr/share/perl5/EBox/Exceptions/Base.pm line 91
EBox::Exceptions::Base::throw('EBox::Exceptions::MissingArgument', 'objectGUID') called at /usr/share/perl5/EBox/Samba.pm line 2404
EBox::Samba::ldbObjectByObjectGUID('EBox::Samba=HASH(0x4a830a8)') called at /usr/share/perl5/EBox/Users.pm line 1381
EBox::Users::groupExists('EBox::Users=HASH(0x48f8040)', 'Read-Only Domain Controllers') called at /usr/share/perl5/EBox/Users/Group.pm line 525
EBox::Users::Group::create('EBox::Users::Group', 'name', 'Read-Only Domain Controllers', 'parent', 'EBox::Users::OU=HASH(0x4c27288)', 'isSecurityGroup', 1, 'ignoreMods', 'ARRAY(0x4c4fdf0)', 'description', 'Members of this group are Read-Only Domain Controllers in the domain', 'gidNumber', 3000020, 'isSystemGroup', '', 'isInternal', 1) called at /usr/share/perl5/EBox/Samba/Group.pm line 216
eval {...} at /usr/share/perl5/EBox/Samba/Group.pm line 189
EBox::Samba::Group::addToZentyal('EBox::Samba::Group=HASH(0x4bde478)') called at /usr/share/zentyal-samba/s4sync line 240
eval {...} at /usr/share/zentyal-samba/s4sync line 239
2014/03/10 16:28:47 ERROR> Group.pm:225 EBox::Samba::Group::addToZentyal - Error loading group 'Read-Only Domain Controllers': Missing argument: objectGUID
Does anyone know what is causing this and how to fix it?
-
Hi, post your version and your module updates.
I usually just send a screen shot of the delete section of the sofware modules. It shows all installed with current installed module number.
Really is very dependent on version and updates.
-
I am using Zentyal 3.3.
I attached a screenshot of my modules. I typed them below anyways.
* Antivirus - 3.3
* Backup - 3.3.1
* Certification Authority - 3.3
* Common Library - 3.3.1
* Core - 3.3.4
* DHCP Service - 3.3
* DNS Service - 3.3
* FTP - 3.3
* File Sharing and Domain Services - 3.3.3
* Mail Filter - 3.3.1
* Mail Service - 3.3.1
* NTP Service - 3.3
* Network Configuration - 3.3
* Network Objects - 3.3.1
* Network Services - 3.3
* OpenChange Server - 3.3.3
* Printer Sharing Service - 3.3
* Software Management - 3.3.1
* Users and Computers - 3.3.2
* Web Mail Service - 3.3
* Web Server - 3.3
I REALLY appreciate the help.
-
I notice there is a 3.3.5 update, but I will hold off unless you say to update. I don't want to complicate things.
-
I notice there is a 3.3.5 update, but I will hold off unless you say to update. I don't want to complicate things.
I recommend you upgrade to version 4.1.5 of samba.
-
OK, I have 4.1.5 installed but still have the errors. See attached image with version and errors.
-
OK, I have 4.1.5 installed but still have the errors. See attached image with version and errors.
If you want I can help you remotely over SSH, send the data access ssh@pcready.cl
-
I sent you the info.
-
+1 pcready.cl
-
Were you able to get into the server? I received a new IP address today and I don't know if all the ports are available.
-
peterpugh. What does the +1 do?
-
Just Karma, often hit the Karma button. Good to see someone offer to help. So thought hey +1.
-
I have to go to bed. Have to get up for work in 6 hours. I will check here in the morning.
Again, thanks very much.
-
I have to go to bed. Have to get up for work in 6 hours. I will check here in the morning.
Again, thanks very much.
I could not connect today, I apologize.
Is he gets home from the office and did not have time to connect.
Send me the access data tomorrow and I connect immediately.
-
OK.
Just FYI, I used an LDAP browser and was able to browse port 389 without an issue. I tried to browse port 390 and when I tested the connection, it worked. When I tried to actually browse the information, it locked up the LDAP browser. This happened multiple times. There was a rule denying LDAP from my internal network. I changed it to ALLOW.
This did not fix anything.
OK, I am off to bed.
-
OK.
Just FYI, I used an LDAP browser and was able to browse port 389 without an issue. I tried to browse port 390 and when I tested the connection, it worked. When I tried to actually browse the information, it locked up the LDAP browser. This happened multiple times. There was a rule denying LDAP from my internal network. I changed it to ALLOW.
This did not fix anything.
OK, I am off to bed.
OK, bye!
-
When you want access, let me know. I will check on here periodically to see if you have responded.
-
Well, don't worry about the issue now. I re-installed Zentyal 3.4.