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]
31
Directory and Authentication / Re: Version 3.5 missing
« on: May 02, 2016, 10:52:07 am »
I had to install manually some packages.  Namely: sssd, python-samba... etc.

Please, try installing the missing dependency packages: libsamba-perl, samba-vfs-modules and finally samba.

I really had a hard time, but it's working now for me

32
Directory and Authentication / Re: Version 3.5 missing
« on: May 02, 2016, 10:30:56 am »
Had the same problem with upgrading a 3.5 system yesterday.  Samba and Zentyal "Users, computers y file sharing" module had vanished from the system.

I was able to install zentyal-samba after doing the two following actions:

apt-get install libldb1=1:1.1.16-1
apt-get install python-ldb=1:1.1.16-1

Of course, you need to uninstall any previous versions.

Hope it helps, I was a whole hour running after this, while my client was unable to work at all.

33
Zentyal 4.2.2. Samba version: 4.3.4-Zentyal
Account lockout policies still not appliying.  Rest of policies seem to apply correctly.  Have to use pdbedit to set account lockout policies.
Still not implemented...?  Anyone can confirm, please?

34
Quote
Ok. Let's asume 3.19.0-79 solves the problem.

Will "apt-get upgrade" update the kernel after we did a rollback...?  Were kernel updates freezed with the rollback we did...? How to force kernel update back to normal?

Cannot find anything...

Thanks.
not sure where you got  3.19.0-79  kernel i though they where only up to 3.19.0-51
apt-get upgrade will not upgrade kernels.
You need apt-get dist-upgrade  to upgrade kernel.
If you edited /etc/default/grub as in my previous post .that will keep booting by default the kernel you set there.
If you purged the faulty kernel then yes if you dist-upgrade then it will boot with newer kernel that may be installed
If you hold down the shift key when booting you should get the grub boot screen and be able to choose different kernels

I've setup a VM to test around this problem.  Cloned production server.
Apt-get dist-upgrade does nothing and reports no updates are available.  Kernel version stays the same after running the command and re-booting.
I did not edit /etc/default/grub, it's untouched.
Thanks.

35
Ok. Let's asume 3.19.0-79 solves the problem.

Will "apt-get upgrade" update the kernel after we did a rollback...?  Were kernel updates freezed with the rollback we did...? How to force kernel update back to normal?

Cannot find anything...

Thanks.

36
I must add:  I have a third Zentyal 4.2.2 machine, with 3.19.0-49-generic kernel working without any problem since 12 days.  BUT THIS MACHINE HAS NO SAMBA SHARES.  The module is enabled, but no shares have been made (only working as Domain Controller + VirtualBox VM server).

37
Hi everyone.

Experienced the same problem on two different servers.  I had 2 lockups on the first one.  After some research, I decided to downgrade the kernel from 3.19.0-49-generic to 3.19.0-47-generic.  So far, no more lockups.

Today I experienced same behaviour on another server.  Checked kernel version, and it was 3.19.0-49-generic. Just downgraded too this one to 3.19.0-47-generic.

I'll keep you informed about results.  First server has not lockup since downgrade.

Both Zentyal 4.2.2 up to date.

How to downgrade:

Code: [Select]
sudo apt-get purge linux-image-3.19.0-49-generic
sudo update-grub

then reboot.

Second downgraded kernel server has been stable.  No more lockups after kernel downgrade.  Same with first server.  It seems that we have pinpointed the problem.

So what is happening...?  a Kernel bug...? Samba bug...?

38
Nope...  ;D

39
I may just add that one should ensure that the previous kernel is still "available". Auto-remove function of apt might have deleted it, no?
And finally, you need to put upgrade offers for the new kernel on hold...

Default config saves 2 to 3 kernels:

/etc/kernel/postinst.d/apt-auto-removal says:

# Mark as not-for-autoremoval those kernel packages that are:
#  - the currently booted version
#  - the kernel version we've been called for
#  - the latest kernel version (determined using rules copied from the grub
#    package for deciding which kernel to boot)
#  - the second-latest kernel version, if the booted kernel version is
#    already the latest and this script is called for that same version,
#    to ensure a fallback remains available in the event the newly-installed
#    kernel at this ABI fails to boot
# In the common case, this results in exactly two kernels saved, but it can
# result in three kernels being saved.  It's better to err on the side of
# saving too many kernels than saving too few.

So, in a default configuration, it should be safe. But you are right, one should check before deleting the kernel.  Anyway, i'm curious about what would happen if we try to remove the last kernel...


40
Hi everyone.

Experienced the same problem on two different servers.  I had 2 lockups on the first one.  After some research, I decided to downgrade the kernel from 3.19.0-49-generic to 3.19.0-47-generic.  So far, no more lockups.

Today I experienced same behaviour on another server.  Checked kernel version, and it was 3.19.0-49-generic. Just downgraded too this one to 3.19.0-47-generic.

I'll keep you informed about results.  First server has not lockup since downgrade.

Both Zentyal 4.2.2 up to date.

How to downgrade:

Code: [Select]
sudo apt-get purge linux-image-3.19.0-49-generic
sudo update-grub

then reboot.

Pages: 1 2 [3]