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

Pages: 1 [2] 3
16
Directory and Authentication / Re: zentyal bacup restore
« on: November 13, 2018, 07:44:01 am »
This might happen because when you installed Zentyal before restore, you used the same admin username as in the original installation.  Re-install with a different username for admin and it should work.

17
Found a solution, but don't know why it's behaving this way.

On the DHCP module, the WINS server option was enabled, setting "local Zentyal" as WINS server.

Setting WINS server to "none" completely solved the problem.

18
During the wait periods, there is no disk activity, not network activity, neither on the source nor on the zentyal server.

Smells like a timeout trying to find something...

Five Windows 10 workstations with exactly the same behaviour.

19
Hi,

Just installed my first Zentyal 6, after many years using previous versions.

First login of users (profile creation) from Windows 10 takes more than 10 minutes.  Logins after use up to 2-3 minutes.

Any user/permission related action is very slow (like 2-3 minutes.  For example, delete an admin installed shortcut in the desktop from a non admin account.  It takes ages to ask for an admin account.

Any clues? Thanks

20
Thanks for pointing the missing wget, I've edited the post.

About the Zentyal 5.1 repositories, nothing "happened" to them, there was no change at all in their content in the last days (mainly because the team was focused in the release of Zentyal 6.0). In fact, those "conflicting packages" (libapt-pkg5.0 and libapt-inst2.0) have been there for a full year (introduced as dependencies of the samba 4.7 packages from a newer version of Ubuntu before the release of Zentyal 5.1) causing no problem at all during this whole year.

The problem arose the other day as a result of the release of newer apt packages to the Ubuntu xenial-updates repo, and as the version from libapt-pkg5.0 in the Zentyal repo was greater than the correct one in xenial-updates, apt was left in a broken state after the upgrade. The solution has been just deleting those packages from the repo, as they were no longer needed because currently with the newer packages from Ubuntu all the dependencies were already satisfied.

Finally, as I said in my previous post, the "real fix" is not having any packages with newer version in the Zentyal repo than in the Ubuntu ones in the newest Zentyal 6.0, so this release is definitely "protected" against these problems.

Hope this clarifies the issue.

Hi,

For me, it does clarify very well.  Thanks for you prompt and clear answer.  Sure it means a lot to the community who relies in a stable Zentyal.

thanks a lot.

Gracias por tu buen talante.

21
Great news to know you have solved your mistake.  Yesterday I found the solution on my own, after several hours fighting, and having several servers afected.

By the way, you might like to correct your quote about a solution:  you are missing a "wget".  The original poster did include the wget.

Would you care to explain exactly what happened to the repositories you maintain?  What was the procedure that went wrong?  This is a relevant error and the community would be grateful if you could explain, not only what went wrong, but what did/will you do to ensure it will not happen again.

I'm sure a complete explanation from you will benefit the Zentyal organization, showing a transparent communication.

Thanks in advance.

22
I cannot afford to disable root mails, so I've gone through this solutions instead.

Code: [Select]
* * * * * root /usr/bin/net cache flush &>/dev/null
But I'm still worried about the error messages...

23
I would not remove this entry.  Zentyal team has put it there for some powerful reason...  you don't clean the cache every minute for nothing...

24
More about this here: https://forum.zentyal.org/index.php?topic=27113.0

But that is back to November 2015...

25
Ok then.  This s**t was introduced by zentyal-samba 4.2.3.  >:(

26
OK.  I forgot I had another server which I have not upgraded this module to 4.2.3.

THERE IS NO /etc/cron.d/zentyal-samba IN 4.2.2!!!

What kind of problem Zentyal has that it has to clear the cache EVERY MINUTE???  It's an insane method...

27
I guess we could modify the line like this

Code: [Select]
* * * * * root /usr/bin/net cache flush &>/dev/null
to get rid of the mails,

BUT: How relevant are this messages?  Could not find any info on them...

Anybody has a 4.2.2 module and check if there is this cronjob there too...?

28
Why do the system needs to do this cron job every minute...

* * * * * root /usr/bin/net cache flush

It's in /etc/cron.d/zentyal-samba.

I MEAN: EVERY MINUTE?????????

29
Since sunday, when I upgraded TWO servers modules "Domain controller and file sharing" to version 4.2.3 i'm getting mails to the root account every couple of minutes with contents like this, on both servers:

Couldn't delete entry! key = IDMAP/UID2SID/3000002
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-21-4072495981-2812427868-577415633-1104
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-18
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-21-4072495981-2812427868-577415633-512
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-32-544
Couldn't delete entry! key = IDMAP/GID2SID/2512
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-21-4072495981-2812427868-577415633-1126
Couldn't delete entry! key = IDMAP/UID2SID/2502
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-21-4072495981-2812427868-577415633-500
Couldn't delete entry! key = IDMAP/UID2SID/2500
Couldn't delete entry! key = IDMAP/SID2XID/S-1-5-21-4072495981-2812427868-577415633-513
Couldn't delete entry! key = IDMAP/GID2SID/2513
Couldn't delete entry! key = IDMAP/GID2SID/3000002
Couldn't delete entry! key = IDMAP/GID2SID/3126
Couldn't delete entry! key = IDMAP/GID2SID/4

It says is coming from "/usr/bin/net cache flush" cron job

Info is different every time...

30
Directory and Authentication / Re: Version 3.5 missing
« on: May 02, 2016, 11:51:17 am »
Here you have the libs.

Anyway, I did:

Code: [Select]
apt-cache policy python-ldb
python-ldb:
  Installed: 1:1.1.16-1
  Candidate: 1:1.1.24-0ubuntu0.14.04.1
  Version table:
     1:1.1.24-0ubuntu0.14.04.1 0
        500 http://es.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
 *** 1:1.1.16-1 0
        500 http://es.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

I though version 1.1.16-1 was available from the respositories...   :o

This libraries can be found also at http://www.ubuntuupdates.org

Pages: 1 [2] 3