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

Pages: 1 [2]
16
Installation and Upgrades / Re: HOWTO: Trusted Certificate
« on: April 23, 2014, 05:18:47 pm »
I'm quite sure changes have to be made here:
/var/lib/zentyal/conf/haproxy.cfg

but don't know how??

Please help me out!

Ray

If you'd like to edit how haproxy.cfg is generated, you will need to edit its stub. The stub is located in /usr/share/zentyal/stubs/core/haproxy.cfg.mas. You can view the file contents here: https://github.com/Zentyal/zentyal/blob/3.4/main/core/stubs/haproxy.cfg.mas

My fix was editing line 63 to point directly to my PEM file; however, this looks like it is some type of loop so this may not work for you. It worked fine for me because I wanted to use the same trusted SSL cert for the admin panel, webmail, etc.

17
While it isn't an official fix, I had this problem upgrading a test virtual machine I made. I installed fresh 3.3, installed all the security fixes and component updates, then hit the 3.4 upgrade button and ended with the same error. I ended up running this to get the machine to boot: https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair

I am running it in Hyper-V (single VHD, nothing really special).

18
Installation and Upgrades / Re: apt-get update can't get Zentyal ppa
« on: April 17, 2014, 10:49:32 pm »
Thanks for posting this Lonnie, I was about half an hour off from starting the upgrade in an effort to fix my botched LDAP schemas from the last component update wave.

I really don't understand the logic in the community edition updates. There is the obvious risk associated with using newly developed versions, but in my experience so far this has gone far beyond risk as every update seems to fail or botch things up in some way. With my LDAP schema issue, I decided to set up another 3.3.9 to compare and perhaps copy schemas over to "fix" the problem; however, the secondary server experienced the same problems without any customizations/configurations put into it. I then upgraded it to 3.4, only for the GRUB install to fail and require repair via an Ubuntu boot CD. At least once I got it going the LDAP problem had gone away.

I am thankful I installed this as a virtual machine, as being able to revert is my only saving grace. I only wish I would have done a snapshot before updating components. Lesson learned.

19
Installation and Upgrades / Re: Jabber message history
« on: April 16, 2014, 03:23:40 pm »
From what I researched, Zentyal uses ejabberd as its jabber service, and it can be configured to store logs via its config files; however, unless 3.4 has changed something since 3.3, I don't believe there is any log functionality in the webadmin interface.

I ended up running Openfire Jabber (which has message archiving and ability to view via web interface) on a separate server, and using Zentyal's LDAP for my user database without issues. If you go this route, remember Zentyal's LDAP is on port 390 and you may have to tweak a bit with the filter settings a bit to get it to separate users and groups properly.

20
Installation and Upgrades / Re: LDAP Issue after module update 3.3.7
« on: April 15, 2014, 08:00:05 pm »
After some more searching, I found the following is being output into syslog:

Code: [Select]
Apr 15 12:34:26 mail slapd[9062]: Entry (uid=testuser,ou=Users,dc=domain,dc=com): object class 'CourierMailAccount' requires attribute 'mail'
Apr 15 12:34:26 mail slapd[9062]: entry failed schema check: object class 'CourierMailAccount' requires attribute 'mail'

Based on this error and the above error (which shows the save is attempting to delete the 'mail' field for that user), how do I need to proceed? It seems logical that users with object class CourierMailAccount should have a set 'mail' attribute, so why is it attempting to remove it?

Thanks

21
Installation and Upgrades / LDAP Issue after module update 3.3.7
« on: April 08, 2014, 05:44:34 pm »
Hello,

I updated a few modules this morning (users, mail, jabber, antispam, and a couple other seemingly unrelated ones), and I get the following in /var/log/zentyal/zentyal.log when I attempt to update user info such as name/pass:

Code: [Select]
2014/04/08 10:40:06 ERROR> LdapObject.pm:283 EBox::Users::LdapObject::save - There was an error updating LDAP: The request specifies a change to an existing entry or the addition of a new
entry that does not comply with the servers schema
.<br/> Operation parameters:'modify [
  \'replace\',
  [
    \'quota\',
    [
      \'500\'
    ]
  ],
  \'replace\',
  [
    \'description\',
    [
      \'test\'
    ]
  ],
  \'delete\',
  [
    \'mail\',
    []
  ],
  \'replace\',
  [
    \'givenname\',
    [
      \'test\'
    ]
  ],
  \'replace\',
  [
    \'sn\',
    [
      \'test\'
    ]
  ],
  \'replace\',
  [
    \'cn\',
    [
      \'test test\'
    ]
  ]
]

I attempted to follow the directions at https://wiki.zentyal.org/wiki/Missing_LDAP_Schemas to fix, but no go. I have a couple hundred users and would really like to not clear my entire LDAP to fix this.

On the test user I have made, updates seem to "stick", I just get that error. If I delete the test user's mailbox, updates work without errors. If I assign the user a mailbox, they start to error out again.

Any ideas?

Thanks!

22
https://forum.zentyal.org/index.php/topic,20933.msg80402.html#msg80402 :)
Not sure I understand what you are trying to say. Are you saying the package will be backported eventually, or that I should just wait for 3.4?

here's my quick workaround:
  • download the libclamav-xs-perl from here:
    https://launchpad.net/~zentyal/+archive/3.2/+sourcepub/3956678/+listing-archive-extra
    get the .deb format according to your version of zentyal. for 32-bit, get the i386 version, the 64-bit get the amd64 version.
  • use sftp to upload that file to your home directory on the server
  • ssh to the server, go to your home directory, then execute accordingly:
    for 64-bit version: sudo dpkg -i libclamav-xs-perl_0.01_amd64.deb
    for 32-bit version: sudo dpkg -i libclamav-xs-perl_0.01_i386.deb
the package should be installed, then you can proceed to update tha antivirus module :)

Awesome. The deb installed and the component updated without issues. Thanks!

23
Hello,

When I attempt to update the Antivirus component from 3.3 to 3.3.1 (on Zentyal 3.3 Community Edition) it fails. All other components have updated fine. My /var/log/zentyal/software.log shows the following:

Code: [Select]
2014-03-10 11:35:25> Zentyal apt-wrapper install started
2014-03-10 11:35:25> Reading package lists...
2014-03-10 11:35:26> Building dependency tree...
2014-03-10 11:35:26> Reading state information...
2014-03-10 11:35:26> Some packages could not be installed. This may mean that you have
2014-03-10 11:35:26> requested an impossible situation or if you are using the unstable
2014-03-10 11:35:26> distribution that some required packages have not yet been created
2014-03-10 11:35:26> or been moved out of Incoming.
2014-03-10 11:35:26> The following information may help to resolve the situation:
2014-03-10 11:35:26>
2014-03-10 11:35:26> The following packages have unmet dependencies:
2014-03-10 11:35:26>  zentyal-antivirus : Depends: libclamav-xs-perl but it is not installable
2014-03-10 11:35:26> E: Unable to correct problems, you have held broken packages.
2014-03-10 11:35:26> Zentyal apt-wrapper install finished

If I attempt to install libclamav-xs-perl by hand using apt-get install, I get the following:

Code: [Select]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libclamav-xs-perl is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libclamav-xs-perl' has no installation candidate

I have updated apt and I haven't messed with the sources in this install. Does anyone have any ideas?

Thanks!

Pages: 1 [2]