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

Pages: [1] 2 3 ... 6
1
Because of some update-problems from my old zentyal 4.0 installation I have installed zentyal 6.2 as an additional domain controller in my small network. I moved service by service to the new installation except for the DC. What is the right way to do this now? I am a little scared that I will brake my installation and / or that my users will have trouble to use their files or I have to rejoin the computers to the domian.

Any hints?

2
Installation and Upgrades / Re: move of DC
« on: March 21, 2021, 03:11:51 pm »
I know the thread is an older one, but nevertheless my question at BerT666: did you found a solution for your question?

3
Installation and Upgrades / 6.2: db error
« on: February 11, 2021, 09:35:29 pm »
After solving my mail problem there is a new error :(:I have done a modification in the dhcp modul. After saving the changes I've got the error message:
Code: [Select]
connection db error:without any additional text after the colon.
In the logfile zentyal.log you can read the following:
Code: [Select]
2021/02/11 21:17:09 ERROR> Base.pm:117 EBox::Exceptions::Base::throw - Failed to execute /usr/bin/sudo -p sudo: /var/lib/zentyal/tmp/sTgD_33qUn.cmd 2> /var/l
EBox::Sudo::_rootError('/usr/bin/sudo -p sudo: /var/lib/zentyal/tmp/sTgD_33qUn.cmd 2> /var/lib/zentyal/tmp/stderr', '/bin/cat /var/lib/zentyal/conf/zentyal-m
EBox::Sudo::_root(1, '/bin/cat /var/lib/zentyal/conf/zentyal-mysql.passwd') called at /usr/share/perl5/EBox/Sudo.pm line 153
EBox::Sudo::root('/bin/cat /var/lib/zentyal/conf/zentyal-mysql.passwd') called at /usr/share/perl5/EBox/MyDBEngine.pm line 156
EBox::MyDBEngine::_dbpass('EBox::MyDBEngine=HASH(0x559f6bfcbc00)') called at /usr/share/perl5/EBox/MyDBEngine.pm line 196
eval {...} at /usr/share/perl5/EBox/MyDBEngine.pm line 195
EBox::MyDBEngine::_connect('EBox::MyDBEngine=HASH(0x559f6bfcbc00)') called at /usr/share/perl5/EBox/MyDBEngine.pm line 53
EBox::MyDBEngine::new('EBox::MyDBEngine') called at /usr/share/perl5/EBox/DBEngineFactory.pm line 41
EBox::DBEngineFactory::DBEngine at /usr/share/perl5/EBox/AuditLogging.pm line 49
EBox::AuditLogging::_db('EBox::AuditLogging=HASH(0x559f69eee748)') called at /usr/share/perl5/EBox/AuditLogging.pm line 189
EBox::AuditLogging::commit('EBox::AuditLogging=HASH(0x559f69eee748)') called at /usr/share/perl5/EBox/GlobalImpl.pm line 622
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x559f65b7f6f8)', 'progress', 'EBox::ProgressIndicator=HASH(0x559f69223150)') called at /usr/share/pe
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x559f69223300)', 'progress', 'EBox::ProgressIndicator=HASH(0x559f69223150)') called at /usr/share/zentyal/global-a
eval {...} at /usr/share/zentyal/global-action line 30
2021/02/11 21:17:09 ERROR> MyDBEngine.pm:200 EBox::MyDBEngine::_connect - Connection DB Error:
 at Connection DB Error:
 at /usr/share/perl5/EBox/MyDBEngine.pm line 200
EBox::MyDBEngine::_connect('EBox::MyDBEngine=HASH(0x559f6bfcbc00)') called at /usr/share/perl5/EBox/MyDBEngine.pm line 53
EBox::MyDBEngine::new('EBox::MyDBEngine') called at /usr/share/perl5/EBox/DBEngineFactory.pm line 41
EBox::DBEngineFactory::DBEngine at /usr/share/perl5/EBox/AuditLogging.pm line 49
EBox::AuditLogging::_db('EBox::AuditLogging=HASH(0x559f69eee748)') called at /usr/share/perl5/EBox/AuditLogging.pm line 189
EBox::AuditLogging::commit('EBox::AuditLogging=HASH(0x559f69eee748)') called at /usr/share/perl5/EBox/GlobalImpl.pm line 622
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x559f65b7f6f8)', 'progress', 'EBox::ProgressIndicator=HASH(0x559f69223150)') called at /usr/share/pe
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x559f69223300)', 'progress', 'EBox::ProgressIndicator=HASH(0x559f69223150)') called at /usr/share/zentyal/global-a
eval {...} at /usr/share/zentyal/global-action line 30
For me it seems that zentyal has lost the connection to the mysql database. What can / have I do do fix this?

4
Installation and Upgrades / [solved] Re: 6.2: Mail Error
« on: February 11, 2021, 09:27:01 pm »
The solution was easier than I expectet: after manually restarted the died service postfix the email modul works again. So at this moment the thead is solved  :D . But I still not yet understand what happend. Why started the service manually but not when zentyal did an reboot? Hope it will work in future ...

5
Installation and Upgrades / Re: 6.2: Mail Error
« on: February 05, 2021, 09:09:40 pm »
@doncamilo: Thanks for your help.
The log file shows me something about DNS difficulties:
Code: [Select]
2021/02/05 20:43:09 ERROR> Service.pm:971 EBox::Module::Service::restartService - Die DNS-Abfrage ist fehlgeschlagen: NXDOMAIN (Verwendung des Nameservers 127.0.0.1, /etc/resolv.conf war
2021/02/05 20:43:09 ERROR> RestartService.pm:61 EBox::SysInfo::CGI::RestartService::_process - Restart of E-Mail from dashboard failed: Die DNS-Abfrage ist fehlgeschlagen: NXDOMAIN (Verwendung des Nameservers 127.0.0.1, /etc/resolv.conf war
'# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# and managed by Zentyal.
#
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
#
nameserver 127.0.0.1
search lueghi-net.home
'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - /sbin/mii-tool > /var/lib/zentyal/tmp/linkstatus
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status ebox.openvpn.server.vpn-android | grep 'Loaded: loaded'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'ebox.openvpn.server.vpn-android' | grep 'Active: active (running)'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status ebox.openvpn.server.vpn-zentyal | grep 'Loaded: loaded'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'ebox.openvpn.server.vpn-zentyal' | grep 'Active: active (running)'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status ebox.openvpn.client.stefan | grep 'Loaded: loaded'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'ebox.openvpn.client.stefan' | grep 'Active: active (running)'
2021/02/05 20:43:09 WARN> zentyal.psgi:43 Plack::Sandbox::_2fusr_2fshare_2fzentyal_2fpsgi_2fzentyal_2epsgi::__ANON__ - Use of uninitialized value $addr in concatenation (.) or string at /usr/share/perl5/EBox/OpenVPN/Client.pm line 565.
2021/02/05 20:43:09 WARN> zentyal.psgi:43 Plack::Sandbox::_2fusr_2fshare_2fzentyal_2fpsgi_2fzentyal_2epsgi::__ANON__ - Use of uninitialized value $port in concatenation (.) or string at /usr/share/perl5/EBox/OpenVPN/Client.pm line 565.
2021/02/05 20:43:09 WARN> zentyal.psgi:43 Plack::Sandbox::_2fusr_2fshare_2fzentyal_2fpsgi_2fzentyal_2epsgi::__ANON__ - Use of uninitialized value $proto in uc at /usr/share/perl5/EBox/OpenVPN/Client.pm line 565.
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status amavis | grep 'Loaded: loaded'
2021/02/05 20:43:09 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'amavis' | grep 'Active: active (running)'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status clamav-daemon | grep 'Loaded: loaded'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'clamav-daemon' | grep 'Active: active (running)'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status isc-dhcp-server | grep 'Loaded: loaded'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'isc-dhcp-server' | grep 'Active: active (running)'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status tftpd-hpa | grep 'Loaded: loaded'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'tftpd-hpa' | grep 'Active: active (running)'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status bind9 | grep 'Loaded: loaded'
2021/02/05 20:43:10 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'bind9' | grep 'Active: active (running)'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status postfix@- | grep 'Loaded: loaded'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'postfix@-' | grep 'Active: active (running)'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status amavis | grep 'Loaded: loaded'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'amavis' | grep 'Active: active (running)'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status zentyal.learnspamd | grep 'Loaded: loaded'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'zentyal.learnspamd' | grep 'Active: active (running)'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status amavis | grep 'Loaded: loaded'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'amavis' | grep 'Active: active (running)'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status ntp | grep 'Loaded: loaded'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'ntp' | grep 'Active: active (running)'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status samba-ad-dc | grep 'Loaded: loaded'
2021/02/05 20:43:11 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'samba-ad-dc' | grep 'Active: active (running)'
2021/02/05 20:43:12 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status zentyal.samba-sync | grep 'Loaded: loaded'
2021/02/05 20:43:12 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'zentyal.samba-sync' | grep 'Active: active (running)'
2021/02/05 20:43:12 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status sogo | grep 'Loaded: loaded'
2021/02/05 20:43:12 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - systemctl status 'sogo' | grep 'Active: active (running)'
2021/02/05 20:43:12 INFO> Index.pm:187 EBox::Dashboard::CGI::Index::masonParameters - dashboard1
2021/02/05 20:43:15 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - dpkg --clear-avail
2021/02/05 20:43:43 DEBUG> Sudo.pm:189 EBox::Sudo::_root - /usr/share/zentyal/psgi/zentyal.psgi (pid: 32062) - /sbin/mii-tool > /var/lib/zentyal/tmp/linkstatus
...
I had to shorten the log because of length restricton.
For /etc/resolv.conf there is a link to /run/resolvconf/resolv.conf.
But I#m sorry: I don't know what to do or what to check now? My network seems to work well. From my clientc I can ping everything in my domain (by name) and the internet works too ...
The logfile mail.log doesn't exist in my installation  :o .
The output of
Code: [Select]
sudo  systemctl status postfix@-.service postfix.service
Code: [Select]
postfix@-.service - Postfix Mail Transport Agent (instance -)
   Loaded: loaded (/lib/systemd/system/postfix@.service; indirect; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:postfix(1)

● postfix.service - Postfix Mail Transport Agent
   Loaded: loaded (/lib/systemd/system/postfix.service; disabled; vendor preset: enabled)
   Active: inactive (dead)


6
Installation and Upgrades / [solved] 6.2: Mail Error
« on: February 04, 2021, 03:11:06 pm »
I've just installed a complete new (virtual) Server with Zentyal. I'm trying to configure the system as a replacement for my Zentyal 4.0 installation. I don't know what happend but since a couple of days the mail module has an error:
Code: [Select]
2021/02/04 14:47:12 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: logs
2021/02/04 14:47:12 INFO> Base.pm:231 EBox::Module::Base::save - Restarting service for module: sogo
2021/02/04 14:47:17 ERROR> GlobalImpl.pm:728 EBox::GlobalImpl::saveAllModules - The following modules failed while saving their changes, their state is unknown: mail  at The following modules failed while saving their changes, their state is unknown: mail  at /usr/share/perl5/EBox/GlobalImpl.pm line 728
EBox::GlobalImpl::saveAllModules('EBox::GlobalImpl=HASH(0x55a069f8b810)', 'progress', 'EBox::ProgressIndicator=HASH(0x55a06d62e4b8)') called at /usr/share/perl5/EBox/Global.pm line 95
EBox::Global::AUTOLOAD('EBox::Global=HASH(0x55a06954d740)', 'progress', 'EBox::ProgressIndicator=HASH(0x55a06d62e4b8)') called at /usr/share/zentyal/global-action line 32
eval {...} at /usr/share/zentyal/global-action line 30
I've deinstalled and deleted the mail module. After that I have done a reinstall. But no success  :( . Can someone tell me what to do to get the module working? Is there perhaps a currupted config file?

7
German / Re: Update 4.0 -> 5.0: HowTo verfügbar?
« on: January 08, 2021, 01:00:08 pm »
Da ich im englischsprachigen Teil keine Hilfe bekommen habe, versuche ich das Problem hier auch noch mal zu schildern in der Hoffnung auf Hilfe:
Ich versuche gerade, meinen Server von Version 4.0 auf 6.2 zu aktualisieren. Ich habe die Updates in einer virtuellen Maschine getestet (allerdings nur mit einer Zentyal-Grundkonfiguration). Das Update von 4.0 auf 5.0 hat ohne Probleme funktioniert. Jetzt bekomme ich bei meinem realen Server eine Fehlermeldung laut Samba:
Code: [Select]
Die folgenden Pakete haben unerfüllte Abhängigkeiten :
 zentyal-samba : Hängt ab von: samba (>= 2:4.6.7+dfsg-1), sollte aber nicht installiert werden
                 Hängt ab von: samba-vfs-modules, sollte aber nicht installiert werden
                 Hängt ab von: samba-dsdb-modules, sollte aber nicht installiert werden
                 Hängt ab von: winbind, sollte aber nicht installiert werden
                 Hängt ab von: libnss-winbind, sollte aber nicht installiert werden
                 Hängt ab von: libpam-winbind, sollte aber nicht installiert werden
E: Probleme können nicht behoben werden, Sie haben fehlerhafte Pakete behalten.
Download fehlgeschlagen, erneuter Versuch in 5 Sekunden...

Die Ausgabe von apt-cache unmet samba:
Code: [Select]
Paket samba Version 3:4.1.17+dfsg-1~zentyal5 hat eine unerfüllte Abhängigkeit:
 Ersetzt: libsamdb0 (< 4.0.0~alpha17~)
 Ersetzt: libsamdb0:i386 (< 4.0.0~alpha17~)
 Ersetzt: python-samba (< 2:4.1.4+dfsg-3)
 Ersetzt: python-samba:i386 (< 2:4.1.4+dfsg-3)
 Ersetzt: samba-ad-dc
 Ersetzt: samba-ad-dc:i386
 Ersetzt: samba-common (<= 2.0.5a-2)
 Ersetzt: samba-common:i386 (<= 2.0.5a-2)
 Ersetzt: samba-doc (< 2:4.0.5~)
 Ersetzt: samba-doc:i386 (< 2:4.0.5~)
 Ersetzt: samba-libs (< 2:4.1.4+dfsg-2)
 Ersetzt: samba-libs:i386 (< 2:4.1.4+dfsg-2)
 Ersetzt: samba4 (< 3:4.1.13)
 Ersetzt: samba4:i386 (< 3:4.1.13)
Es sieht für mich so aus, dass das System einige Abhängigkeiten zu samba von zentyal5 hat.
Meine Frage ist also: Was kann ich tun, um dieses Problem zu beheben? Welche zusätzlichen Informationen benötigt ihr, um mir einen Tipp zu geben?

Habe noch einige zusätzliche Test gemacht. Ausgabe von  dpkg -l | samba:
Code: [Select]
adminuser@zentyal1 12:52 ~ > dpkg -l | grep samba
ii  libsamba-perl                         0.11+2~8                                   amd64        Perl bindings for samba 4.0
ii  python-samba                          3:4.1.17+dfsg-1~zentyal5                   amd64        Python bindings for Samba
ii  samba                                 3:4.1.17+dfsg-1~zentyal5                   amd64        SMB/CIFS file, print, and login server for Unix
ii  samba-common                          3:4.1.17+dfsg-1~zentyal5                   all          common files used by both the Samba server and client
ii  samba-common-bin                      3:4.1.17+dfsg-1~zentyal5                   amd64        Samba common files used by both the server and the client
ii  samba-dsdb-modules                    3:4.1.17+dfsg-1~zentyal5                   amd64        Samba Directory Services Database
ii  samba-libs:amd64                      3:4.1.17+dfsg-1~zentyal5                   amd64        Samba core libraries
ii  samba-vfs-modules                     3:4.1.17+dfsg-1~zentyal5                   amd64        Samba Virtual FileSystem plugins
ii  zentyal-samba                         4.0.11                                     all          Zentyal - Domain Controller and File Sharing
adminuser@zentyal1 21:56 ~ >
Für mich scheint es so, dass es einen erfolglosen Versuch gab, zentyal5 zu installieren. Dies muss vor langer Zeit geschehen sein, weil ich mich nicht daran erinnern kann :(. Und mein aktuelles System mit zentyal 4.0 funktioniert seit Jahren einwandfrei. Meine Frage ist also, ob ich richtig liege: wenn ich die Samba-Teile von *zentyal5* entfernen kann, wird das "normale" Upgrade wieder funktionieren. Aber wie kann ich die kaputten zentyal5-Abhängigkeiten entfernen? Ich bin kein Linux-Guru, aber ich kann die Kommandozeile verwenden.


8
Is there really no one here in the forum who can give me a hint / tip  :( ?

9
German / Update 4.0 -> 5.0: HowTo verfügbar?
« on: December 29, 2020, 12:08:20 pm »
Hallo Zentyal-Freunde,
gibt es so etwas wie ein HowTo das die besonderen Stolperfallen aufzeigt und Lösungen wie man sie umschiffen kann? Ein direktes Update aus des System heraus läuft bei mir auf einen Fehler?
[edit]Link auf Fehlerbeitrag ergänzt[/edit]

10
I've checked some additiional things. Output of dpkg -l | samba:
Code: [Select]
adminuser@zentyal1 12:52 ~ > dpkg -l | grep samba
ii  libsamba-perl                         0.11+2~8                                   amd64        Perl bindings for samba 4.0
ii  python-samba                          3:4.1.17+dfsg-1~zentyal5                   amd64        Python bindings for Samba
ii  samba                                 3:4.1.17+dfsg-1~zentyal5                   amd64        SMB/CIFS file, print, and login server for Unix
ii  samba-common                          3:4.1.17+dfsg-1~zentyal5                   all          common files used by both the Samba server and client
ii  samba-common-bin                      3:4.1.17+dfsg-1~zentyal5                   amd64        Samba common files used by both the server and the client
ii  samba-dsdb-modules                    3:4.1.17+dfsg-1~zentyal5                   amd64        Samba Directory Services Database
ii  samba-libs:amd64                      3:4.1.17+dfsg-1~zentyal5                   amd64        Samba core libraries
ii  samba-vfs-modules                     3:4.1.17+dfsg-1~zentyal5                   amd64        Samba Virtual FileSystem plugins
ii  zentyal-samba                         4.0.11                                     all          Zentyal - Domain Controller and File Sharing
adminuser@zentyal1 21:56 ~ >
For me it seems that there was an unsuccessvul try to install zentyal5. This must be happened long time ago because I don't remember this. And my actual system with zentyal 4.0 works fine since years.So my question is if I'm right: if can I remove the samba parts of *zentyal5* the "normal" upgrade will work. But how can I remove the bad zentyal5-dependencies? I'm not a linux guru but I can use the commandline.

So my next steps are dependend from your hints. Please help me ....

11
Installation and Upgrades / Zentyal 4.0: problem to upgrade, samba error
« on: December 23, 2020, 04:29:43 pm »
I'm just trying to update my server from version 4.0 to 6.2. I have tested the updates in a virtual machine (but only with an basic zentyal configuration). The update from 4.0 to 5.0 worked without problems. Now with my real server I get an error message according to samba (I have translated most of the german output, it's not original):
Code: [Select]
The following packages have unfulfilled dependencies :
 zentyal-samba : Depends on: samba (>= 2:4.6.7+dfsg-1) but should not be installed
                 Depends on: samba-vfs-modules but should not be installed
                 Depends on: samba-dsdb-modules but should not be installed
                 Depends on: winbind but should not be installed
                 Depends on: libnss-winbind but should not be installed
                 Depends on: libpam-winbind but should not be installed
E: Problems cannot be corrected, you have retained defective packages.
Download failed, retrying in 5 seconds...
The output of apt-cache unmet samba is:
Code: [Select]
Paket samba Version 3:4.1.17+dfsg-1~zentyal5 has an unfulfilled dependency:
 Replaces: libsamdb0 (< 4.0.0~alpha17~)
 Replaces: libsamdb0:i386 (< 4.0.0~alpha17~)
 Replaces: python-samba (< 2:4.1.4+dfsg-3)
 Replaces: python-samba:i386 (< 2:4.1.4+dfsg-3)
 Replaces: samba-ad-dc
 Replaces: samba-ad-dc:i386
 Replaces: samba-common (<= 2.0.5a-2)
 Replaces: samba-common:i386 (<= 2.0.5a-2)
 Replaces: samba-doc (< 2:4.0.5~)
 Replaces: samba-doc:i386 (< 2:4.0.5~)
 Replaces: samba-libs (< 2:4.1.4+dfsg-2)
 Replaces: samba-libs:i386 (< 2:4.1.4+dfsg-2)
 Replaces: samba4 (< 3:4.1.13)
 Replaces: samba4:i386 (< 3:4.1.13)
For me it seems that the system has some dependencies to samba of zentyal5.
So my question is: what can I do to fix this problem? Which additional information you need to give me a tip?

12
Ok, I've resolved the issue some time ago. Now I'm back here to share the fix with you.
...
Thank you so much for sharing the solution. It works fine. And I hope the responsible people will add this samba-fix to the update description. This would be helpfull for a lot of people ....

13
Email and Groupware / Re: openchange and mail don't start anymore
« on: November 21, 2016, 08:45:09 pm »
And after the last post I understand now why all my users had problems to log in month ago. I had reset the passwords and everything worked fine then. But now I know the real reason  :) .
For the administrator account I had set the password later than for the users. And for that reason this account was disabled now.
So my circle of understanding has been closed  8) .

Thanks for your help.

Regards,
Stefan

14
Email and Groupware / Re: openchange and mail don't start anymore
« on: November 18, 2016, 07:39:57 pm »
Hi BerT666

sorry for the late reply, I was rather busy this week.

Yes, I believe you have got it. I can't login as administrator  :( . But I can't remember of setting an expire date ..... ?

I've reactivated the account and Zentyal mail module is starting again. What an easy solution .... I you know what to do  ;) .

Thanks a lot for your help  8) !!

Now I have some more questions:

Why has the password expired? Is there somewhere an option for that? Will it happen again in the future?

Regards,
Stefan

15
Email and Groupware / [solved] openchange and mail don't start anymore
« on: November 16, 2016, 05:19:12 am »
After a long time without problems on my 4.0 version I need some help.

The above mentioned modules don't start anymore. In the zentyal.log I found the following:
Code: [Select]
2016/11/15 22:18:43 INFO> Service.pm:997 EBox::Module::Service::restartService - Restarting service for module: mail
2016/11/15 22:18:50 ERROR> AuthKrbHelper.pm:172 EBox::Samba::AuthKrbHelper::_getTicketUsingKeytab - Could not get ticket: could not acquire credentials using an initial credentials context: Password has expired
2016/11/15 22:18:50 ERROR> Service.pm:1001 EBox::Module::Service::restartService - Error restarting service: Could not get ticket: could not acquire credentials using an initial credentials context: Password has expired
2016/11/15 22:18:50 ERROR> Service.pm:1003 EBox::Module::Service::restartService - Could not get ticket: could not acquire credentials using an initial credentials context: Password has expired

I don't know what the log want to tell me, which password is required :( ?

What I did before:
Two days ago I installed ecodms on the server additional to zentyal. First everything worked well. But after a reboot of the server mail and openchange module will not start again. I tried it a couple of times, everytime the same situation. When I try to restart the modul manually same result.

ecodms has installed a postgresql-db. Could this be part of the problem?

Pages: [1] 2 3 ... 6