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

Pages: [1] 2
Installation and Upgrades / Re: upgrade 6.2 to 7.0 - CA problem
« on: March 12, 2022, 03:48:59 am »
Setting ownership on that file resolved the same issue for me. Thanks!

Installation and Upgrades / Re: samba-common - update
« on: June 27, 2017, 01:25:49 am »
As a workaround, I performed the following:
  • Create a root session with the command:
    sudo -s -H
  • Switch to the root home directory:
    cd ~
  • Download the samba-common package for my architecture (i386) & Zentyal version (4.0) using wget:
  • Create a temporary directory:
    mkdir tmp
  • Extract the deb file into this directory:
    dpkg-deb -R  samba-common_4.1.17+dfsg-1~zentyal5_all.deb tmp
  • Edit the DEBIAN/control file and change the version of this package from 3:4.1.17+dfsg-1~zentyal5 to 3:4.1.17+dfsg-1~zentyal1:
    nano tmp/DEBIAN/control
  • Repackage the deb file, with a filename reflecting the changed version:
    dpkg-deb -b tmp samba-common_4.1.17+dfsg-1~zentyal1_all.deb
  • Install this deb file manually:
    dpkg -i samba-common_4.1.17+dfsg-1~zentyal1_all.deb
  • Install the zentyal packages that had the unmet dependencies:
    apt install zentyal-samba zentyal-printers

Not ideal, but it works until the repository is fixed - provided that you do not upgrade samba-common!

Installation and Upgrades / Re: samba-common - update
« on: June 26, 2017, 10:41:08 pm »
BTW, it appears that this is a fault with Zentyal's samba packaging:

libnss-winbind, libpam-smbpass, libpam-winbind, samba, samba-common-bin and smbclient all depend on samba-common version 3:4.1.17+dfsg-1~zentyal1 (= 3:4.1.17+dfsg-1~zentyal1), but samba-common is only available as version 3:4.1.17+dfsg-1~zentyal5. (This is in

Hence the unmet dependencies. :-(

Installation and Upgrades / Re: samba-common - update
« on: June 26, 2017, 10:16:07 pm »
Grrr... Same issue here. I was running a previously stable Zentyal 4.0 server. Updated today, and discovered samba, zentyal-samba, zentyal-dns, zentyal-printers and zentyal-ntp (plus who knows what else) had all been removed due to unmet dependencies.

I was able to reinstall zentyal-ntp and zentyal-dns (the lack of the latter in particular caused total mayhem as nothing could be resolved), but the others result in errors in the samba dependencies:

root# apt install zentyal-samba
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 zentyal-samba : Depends: samba (>= 2:4.1.13) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Now trying to downgrade to previous release... :-(

Installation and Upgrades / Re: Update 3.3 to 3.4 failure
« on: April 22, 2014, 08:30:02 pm »
Hi jbahillo,

I'm not going to try upgrading again, right now. I lost too much time the last time I tried it, and ended up with a system I couldn't even login to from the console (I couldn't even get the USB keyboard driver working). If I get some time this coming weekend, I might try upgrading a standalone box and see how far I get.

Thanks for getting back to me...


Installation and Upgrades / Re: Update 3.3 to 3.4 failure
« on: April 22, 2014, 07:56:37 pm »
Hi jbahillo,

I was able to reproduce the problem by upgrading from 3.3 to 3.4  ;)  Refer to the upgrade log file attached to my earlier post.

I've reinstalled my system from scratch, using Ubuntu 12.04/Zentyal 3.3. After installing the zentyal-ips package, and enabling the IDS/IPS module within Zentyal, I can confirm that the suricata daemon is started. My /etc/default/suricata file is attached. However, the daemon fails during start-up with the following error:

Code: [Select]
* NFQUEUE support not found !
 * Please ensure the ntnetlink_queue module is loaded or built in kernel

Hope this helps!


Installation and Upgrades / Re: Update 3.3 to 3.4 failure
« on: April 22, 2014, 06:14:41 pm »
I couldn't get my server back up and running with Ubuntu 13.10/Zentyal 3.4 and ended up reinstalling Ubuntu 12.04 LTS/Zentyal 3.3, then importing my previously saved 3.3 configuration settings. I now have a working Ubuntu 12.04/Zentyal 3.3 server. Hurrah!

However, I'll not be upgrading to Zentyal 3.4 anytime soon after this experience.

The "suricata" issue is a known Ubuntu bug (see, for which patches exist, but which is not fixed in any release right now. (Applying the patch let's you start suricata, but does nothing to assist with the upgrade from 3.3 to 3.4.)

I would like to know whether the upgrade fails for everyone who is using the Intrusion Prevention Zentyal module (zentyal-ips). It might be worth removing zentyal-ips (and suricata) before attempting to perform the upgrade from 3.3 to 3.4 and seeing if that is successful - but I've wasted enough time on this upgrade, so I'll leave that to someone with more time on their hands.  ;)

Hi guys,

i have the same problem here under Ubuntu 14.04 and Zentyal 3.4.
After Upgrade to 3.4 webadmin fails to start.

I'm fairly certain that Ubuntu 14.04 - the latest LTS release - is currently not supported by any version of Zentyal. Zentyal 3.4 requires Ubuntu 13.10.

Installation and Upgrades / Re: Update 3.3 to 3.4 failure
« on: April 16, 2014, 10:46:11 pm »
I have had a similar problem with suricata (but not zentyal-ids, which I also have installed) during the upgrade procedure. The log file is attached...

My server is running, but without networking or USB keyboard support - so it might as well not exist. I have tried SystemRescue CD and the rescue system feature of Ubuntu Server 13.10 and have attempted to complete the upgrade manually, but with no luck. I can't login on the server, because the USB keyboard isn't being recognized.

This has been a total disaster of an upgrade, so far. :-(

Any suggestions?


Thanks for getting back to me!  I can well imagine your surprise!   :D

Is it possible this was done by the script that upgraded Zentyal from version 2.0 to 2.2?  The dates of the copied directories would seem to tally with the time I did that upgrade.

Incidentally, could you let me know which of these directories - if any - within /var/lib/zentyal I need to keep:

zentyal\ (yes, this is /var/lib/zentyal/zentyal and contains an extra-backup-data directory)

Thanks for your assistance!



I've recently been investigating why some of my zentyal-controlled backups are so huge, and I've made some interesting discoveries.

I have jenkins (continuous integration server software) installed on the same server as zentyal.  Jenkins stuff is stored in /var/lib/jenkins - but an old copy of that data is also present in /var/lib/zentyal/jenkins.  Similarly, an old copy of the PostgreSQL database files, the current version of which resides in /var/lib/postgresql, has somehow been copied to /var/lib/zentyal/postgresql.  Same with nfs and some other products that aren't directly controlled by zentyal.

Any ideas why this is happening?  Is it safe for me to delete these copies (which don't seem to have been updated in a while).

Best Regards,


News and Announcements / Re: Zentyal 3.0 available!
« on: September 13, 2012, 03:39:13 pm »
Excellent news!  Looking forward to the new release!

Is there an upgrade utility from 2.2 to 3.0?  Also, is it necessary to update from Ubuntu 10.04LTS to 12.04LTS?

News and Announcements / Re: Usage of eBox Platform
« on: August 25, 2009, 05:41:43 pm »
eBox is an excellent piece of software!  It has simplified my life enormously!

As for improvements (and I may be a little out-of-date here, so apologies if you've already done any of these), I'd be grateful if you could consider:
  • Making the LDAP base name configurable.  It would be nice to have something other than "dc=ebox".
  • Improving security.  Since eBox provides CA capabilities, it would be nice if we could tie this in to restrictring network services to using SSL/TLS only.
  • Integration of kerberos for single-sign on across a domain.
  • Having an eBox client that simplifies configuration of a client machine to use an eBox server.
  • Providing a better customization mechanism.  Currently, any modifications to the eBox configuration get zapped when the next software update is performed.

Keep up the good work!

Installation and Upgrades / Re: Add a new printer PROBLEM
« on: December 31, 2008, 05:26:26 pm »
Aha!  Fixed it!

It appears that I had an old eBox repository field in my Ububtu /etc/apt/sources.list file.  This is what I had:

deb hardy main

Here's what I should have had:

deb hardy main

After running "apt-get update" and "apt-get dist-upgrade", everything works just fine and I get hpijs as a driver for my printer!  (I had more work to do to actually share my printer, but at least it works...)

I guess the repository for Ubuntu eBox packages changed since I set up eBox.

Pages: [1] 2