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 - caguiar

Pages: [1] 2
1
Email and Groupware / Re: archivemail in Zentyal 7 / Ubuntu 20
« on: April 16, 2021, 05:19:11 pm »
I used the autoexpunge=15d configuration in dovecot.conf.mas stub, and it works.
For an example of this feature see: https://notes.sagredo.eu/en/qmail-notes-185/expunging-expired-junk-and-trash-emails-with-dovecot-124.html

2
Email and Groupware / Re: archivemail in Zentyal 7 / Ubuntu 20
« on: April 09, 2021, 10:12:38 am »
Got the same issue.
@mscfw, have you got a solution yet?

3
Other modules / DNS - adding DKIM TXT records
« on: May 03, 2020, 02:48:27 pm »
Hi,

Can anybody point me out how to add DKIM TXT records on DNS of a Zentyal server version 6.1.2.

I have tried and failed miserably.

Any help is welcome.

4
Same issue.

Anybody has a solution?

5
Installation and Upgrades / Re: Zentyal 5 with Antivirus?
« on: February 04, 2017, 02:47:21 pm »
The same for me. Without mail filter or some clear how-to replacement, I can not upgrade to 5.0.

Clemente

6
Julio,

Thank you for the info.

When I run that command in my Zentyal system I get

# wbinfo --sid-to-name $(wbinfo --uid-to-sid 3000002)
failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND
Could not lookup sid S-1-5-18

Which means that that user does not exist.

Does that mean that there is something wrong with my Zentyal system? Or this is actually correct on Zentyal systems?

7
Can anybody explain why, when shares are created by Zentyal (v4.1), the directories created contain user and group 30000002?

For example:
getfacl Test/
# file: Test/
# owner: administrator
# group: administrators
user::rwx
user:administrator:rwx
user:3000002:rwx
group::rwx
group:adm:rwx
group:administrators:rwx
group:3000002:rwx
mask::rwx
other::---
default:user::rwx
default:user:administrator:rwx
default:user:3000002:rwx
default:group::---
default:group:adm:rwx
default:group:3000002:rwx
default:mask::rwx
default:other::---

8
Installation and Upgrades / Re: problem in cron.hourly
« on: November 23, 2014, 01:51:27 pm »
I have the same problem after I upgraded to ver. 4.
Did you solve this issue?

9
I am using version 1.4 master-slave configuration successfully, however some things don't work, such as the User corner on the slaves, others I have worked around.

All the problems I have found I have either posted on this forum and / or entered a bug request.

10
Don't you think that the problem has to do with this module starting before the module users (which starts the LDAP)? (remember that this machine is a slave)

11
When I reboot I get the following messages in ebox.log:

Code: [Select]
2010/06/09 16:42:47 INFO> Service.pm:625 EBox::Module::Service::restartService - Restarting service for module: monitor
2010/06/09 16:42:47 INFO> EventDaemon.pm:303 EBox::EventDaemon::_loadModules - EBox::Event::Dispatcher::Log loaded from registeredDispatchers
2010/06/09 16:42:52 ERROR> Ldap.pm:175 EBox::Ldap::anonymousLdapCon - Can't create ldapi connection
2010/06/09 16:42:52 ERROR> Service.pm:630 EBox::Module::Service::__ANON__ - Error restarting service: Can't create ldapi connection

12
We have a master-slave setup with several ebox 1.4.3 boxes.

On the mail server (and only the mail server) the Monitor modules fails to start at startup:

Code: [Select]
* Starting eBox module: network                                         [ OK ]
 * Starting eBox module: firewall                                        [ OK ]
 * Starting eBox module: antivirus                                       [ OK ]
 * Starting eBox module: events                                          [ OK ]
 * Starting eBox module: logs                                            [ OK ]
 * Starting eBox module: monitor                                         [ fail ]
 * Starting eBox module: ntp                                             [ OK ]
 * Starting eBox module: software                                        [ OK ]
 * Starting eBox module: users                                           [ OK ]
 * Starting eBox module: mailfilter                                      [OK]
 * Starting eBox module: webserver                                       [ OK ]
 * Starting eBox module: mail                                            [ OK ]
 * Starting eBox module: usercorner                                      [ OK ]
 * Starting eBox module: webmail                                         [ OK ]
 * Starting eBox module: apache                                          [ OK ]

On the "Module Status" on the ebox dashboard it says the following:
Code: [Select]
Monitor Stopped

However starting the Monitor manually afterwards works:

Code: [Select]
$ sudo /etc/init.d/ebox monitor start
 * Restarting eBox module: monitor                                       [ OK ]

Has anybody else seen this? Any pointers to why Monitor does not start at startup?

13
Installation and Upgrades / ebox 1.4.3 - system updates behaviour
« on: June 04, 2010, 03:40:20 pm »
We have a few ebox 1.4.3. boxes, and I have doubts regarding the "System Updates" feature.
When I look at "Software Management" -> " System Updates" I get the following result:

Code: [Select]
The system components are up to date.
The component list was updated on 6/4/2010 14:22. It will be updated again at night or you can force the update with the console command 'ebox-software'

However when I run apt-get I get a few packages that need upgrade:

Code: [Select]
$ sudo apt-get -s upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages have been kept back:
  linux-image-server linux-server
The following packages will be upgraded:
  libc6 libkrb53 libpq5 postgresql postgresql-8.3 postgresql-client-8.3
6 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Inst libc6 [2.7-10ubuntu5] (2.7-10ubuntu6 Ubuntu:8.04/hardy-updates)
Conf libc6 (2.7-10ubuntu6 Ubuntu:8.04/hardy-updates)
Inst libkrb53 [1.6.dfsg.3~beta1-2ubuntu1.4] (1.6.dfsg.3~beta1-2ubuntu1.5 Ubuntu:8.04/hardy-updates)
Inst libpq5 [8.3.10-0ubuntu8.04.1] (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Inst postgresql-client-8.3 [8.3.10-0ubuntu8.04.1] (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Inst postgresql-8.3 [8.3.10-0ubuntu8.04.1] (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Inst postgresql [8.3.10-0ubuntu8.04.1] (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Conf libkrb53 (1.6.dfsg.3~beta1-2ubuntu1.5 Ubuntu:8.04/hardy-updates)
Conf libpq5 (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Conf postgresql-client-8.3 (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Conf postgresql-8.3 (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)
Conf postgresql (8.3.11-0ubuntu8.04 Ubuntu:8.04/hardy-updates)

Shouldn't these packages show up in the "System Updates" results?

14
Installation and Upgrades / ebox-make-backup warnings
« on: June 04, 2010, 10:52:29 am »
On a few 1.4.3 eBox boxes, I run /usr/share/ebox/ebox-make-backup daily through scripts to backup the configuration regularly,  but when run I get a lot of warnings.

For example:
Code: [Select]
$ sudo /usr/share/ebox/ebox-make-backup --description "Config backup run automatic"
Use of uninitialized value in subroutine entry at /usr/share/perl5/EBox/Gettext.pm line 48.
Use of uninitialized value in subroutine entry at /usr/share/perl5/EBox/Gettext.pm line 49.
Use of uninitialized value in subroutine entry at /usr/share/perl5/EBox/Gettext.pm line 72.
Use of uninitialized value in subroutine entry at /usr/share/perl5/EBox/Gettext.pm line 48.
Use of uninitialized value in subroutine entry at /usr/share/perl5/EBox/Gettext.pm line 49.
Use of uninitialized value in subroutine entry at /usr/share/perl5/EBox/Gettext.pm line 72.
Subroutine EBox::Loggerd::O_APPEND redefined at /usr/share/perl/5.8/Exporter.pm line 65.
 at /usr/lib/perl/5.8/POSIX.pm line 19
Subroutine EBox::Loggerd::O_CREAT redefined at /usr/share/perl/5.8/Exporter.pm line 65.
 at /usr/lib/perl/5.8/POSIX.pm line 19
Subroutine EBox::Loggerd::O_EXCL redefined at /usr/share/perl/5.8/Exporter.pm line 65.
 at /usr/lib/perl/5.8/POSIX.pm line 19
Subroutine EBox::Loggerd::O_RDWR redefined at /usr/share/perl/5.8/Exporter.pm line 65.
 at /usr/lib/perl/5.8/POSIX.pm line 19
Subroutine EBox::Loggerd::O_WRONLY redefined at /usr/share/perl/5.8/Exporter.pm line 65.
 at /usr/lib/perl/5.8/POSIX.pm line 19
Backup stored into file /var/lib/ebox/conf//backups/793883.tar

Is there a way to "clean" this up?

15
On a master-slave configuration, after a few groups where deleted I noticed that the sync was failing to one of the slaves, namely the PDC (samba). The sync worked on the two other which where not PDC.

On the master I have the following errors:
$ tail /var/log/ebox/ebox.log
2010/05/27 17:45:02 DEBUG> slave-sync:77 main::__ANON__ - Trying to run method delGroup with param Administrative on slave HASH(0x4200920) failed
2010/05/27 17:45:02 DEBUG> slave-sync:77 main::__ANON__ - Trying to run method delGroup with param Administration on slave HASH(0x4200920) failed
2010/05/27 17:45:03 DEBUG> slave-sync:77 main::__ANON__ - Trying to run method delGroup with param sysadmins on slave HASH(0x4200920) failed

And on the PDC slave I have the following errors:
$ tail /var/log/ebox/ebox.log
2010/05/27 17:45:02 DEBUG> Samba.pm:1241 EBox::Samba::_checkGroupExists - group Administrative does not exist.
2010/05/27 17:45:02 DEBUG> Samba.pm:1241 EBox::Samba::_checkGroupExists - group Administration does not exist.
2010/05/27 17:45:03 DEBUG> Samba.pm:1241 EBox::Samba::_checkGroupExists - group sysadmins does not exist.

How can we fix this problem?

Pages: [1] 2