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 - Javier Amor Garcia

Pages: 1 2 [3] 4 5 ... 79
I have talked with him and it was not 3.0

3.0 seems unaffected, so I have closed its pull request

3.0 may be unaffected. My test machine is working normally after updates and reboot.

Yes, mine is unaffected and I see the 'network raw' line in the base dhcpd apparmor file, which is untouched in 3.0 . In 2.2 I have checked both the error and the fix.

The failure was reported to me also in 3.0. I will ask that person to make sure it was 3.0 and not 2.2

Thanks for taking time for working on this.

I have made the pull request for the changes in the apparmor file:

Installation and Upgrades / Re: DHCP & apparmor issue
« on: June 03, 2013, 09:39:36 am »
Hello Christian,

I think you're affected by this upstream bug

As you see there were already apparmor changes in upstream to fix it but in some circumstances the problem contineus to be triggered.

Maybe you could told them your configuration?. 


if you upgrade to the last version of zentyal-users you will get likely a more explicit error.

Since the message error is very terse I have not idea of what is going on but we had recently problems with losing LDAP schemas. If you see that this is the problem, you can try to fix it with this command:

Code: [Select]
sudo -s # this will prompt your for password to get superuser access
perl -MEBox -MEBox::Global -e'EBox::init(); $mod = EBox::Global->modInstance('mailfilter'); $mod->performLDAPActions(); 1'
/usr/share/zentyal-mailfilter/mailfilter-ldap update
/etc/init.d/zentyal mailfilter restart
exit # exit superuser account

And always, like Christian says, you can disable the mailfilter to at least deliver mail

The reinstall command doe not take nay argument, so this is not the problem.

LDB is the samba's LDAP. I am not sure what is the error, so maybe going step-by-step  we could find it.

What about trying the following:

1. Reinstall command
2. Enable users module, save changes, create a user, check all is correct.
3. Then enable samba, check for errors.

When you get any error stop the process and paste it here.

As for the usercorner warning it was innocuous; it has nothing to do with this problem.

Thanks for reporting it, I have just fixed the code to not have longer it.


the sequences for fixing the schemas don't fix any thong for the Samba LDAP server. May I suggest you suer the reinstall command?.Or you have some data do you want to save?

Installation and Upgrades / Re: Error when I try to enter Zentyal.
« on: April 25, 2013, 05:15:34 pm »

this error has been fixed in the cloud side.

Anyway in zentyal-remoteservice >= 3.0.17 there is code to make this error less intrusive.

Installation and Upgrades / Re: Error when I try to enter Zentyal.
« on: April 25, 2013, 04:06:16 pm »
Can you DNS resolve ''?

I does not save any content, all is lost.

But after changing domain name, also the users and groups are lost.

In case there is only missing some schema for a particular module you can follow this instructions

Hi Nontrivial,

we had a lot of errors when the LDAP reprovisioning after the domain name change. Hopefully with the new code most of them would be fixed.

Anyway if you run in trouble you can do a reinstall of only LDAP based modules with the command "sudo /usr/share/zentyal-users/reinstall"

I am a bit hurry now, so just a quick clarification about the errata.

When the client connects to the server, the server is given routes to reach the client's connected internal networks using the client as gateway.  (it is not instantaneous because the client should give the server the notification through the VPN)

What is not explained in the documentation is that the routes for the internal networks which don't use private addresses are not given to the server.

This only in tunnel scenario. In roadwarrior no route is given to the server.

Aside of the glitch of the documentation, the typical error here is that hosts on one LAN don't have a return route to the other LAN. The easier way to rule this is to have the Zentyal server as default gateway; if this is not possible you have to create explicit routes to the other LAN using the Zentyal as gateway,

Pages: 1 2 [3] 4 5 ... 79