Hi Vladimir
From your profile you’re close to the more well known Vladivostok - and VERY far from where I am, in Switzerland… 
24h restore “should” be possible! (Heads up motivation!)
First question: Where are the 2 TB Mails now?
On the reinstalled server?
Is this a native installation, or are you using virtualization in some form? (Proxmox, Hyper-V, VMWare, XEN…)
Andy
We have 2TB mail on failed server.
It native (dedicated computer in office).
OK, so the mails are on your older, now not booting server…
But the files / folders are still there, just the server won’t boot now…
You now have a newly installed “rescue” server standing more or less next to the old server, in the same network.
Your NethServer is NOT your firewall, that is another box.
Are these assumptions correct?
It running. Work fine but I cannot autorize on it by mail client (web or standalone) - sssd service corruped.
I’m reinstall it but it not work.
Other info in first post.
I have accces to console to execute commands. I have access to files on this server. But I have not access to mail using mail client.
Ah, OK.
You reinstalled NethServer OVER the not working server, is this correct?
Your Mails are on that very server, but you can’t access them AND your LDAP Account Provider is not working.
PS: As this is an english forum, it would greatly help if you could log in to your NethServer in english, just to make screenshots anyone can read…
If it were just verbaltim cryllic text, I could copy / paste into Google translate…
But that doesn’t work with images!
Have you checked if there are unfinished yum transactions?
There ARE version mismatches, like here:
So I assume the server had been halfway updated, then an unexpected reboot…
Database updated, library not…
My 2 cents
Andy
It work over 6 month. Today it rebooted while updating. I recover boot files (on Boot partion) but SSSD service corrupted. I reinstall this service but no results.
I finish all transations using YUM (yum-complete-transaction). System is Up-to-date.
[root@**** ~]# yum-complete-transaction
Loaded modules: fastestmirror, langpacks, nethserver_events
Loading mirror speeds from cached hostfile
* ce-base: mirror.mi.incx.net
* ce-extras: mirror.mi.incx.net
* ce-sclo-rh: mirror.mi.incx.net
* ce-sclo-sclo: mirror.mi.incx.net
* ce-updates: mirror.mi.incx.net
* epel: ftp-stud.hs-esslingen.de
* nethforge: nethserver.interlin.nl
* nethserver-base: nethserver.interlin.nl
* nethserver-updates: nethserver.interlin.nl
No unfinished transactions left.
Maybe removing the LDAP Account Provider, and then reinstalling that would work (ie set the db and files right).
File shares are “public” when using LDAP as a provider. (seems so from what I see above…)
Andy
What could be the losses resulting from this operation? Is it safe for mail files?
Files are actually kept, same goes if you were using AD.
Mail folders are NOT touched! At least not with this option removing your Account Provider and reinstalling it.
Still, as you have NO backup, it might be a good idea to hook up a spare disk to that server and copy the whole mail folder over, just as a point in time backup (!).
Rule One in IT:
Better a backup too many, than one too little (Meaning NO backup!)…
Andy
yum reinstall sssd-common
Loading moduled: changelog, fastestmirror, langpacks, nethserver_events
Loading mirror speeds from cached hostfile
* ce-base: repo.uk.bigstepcloud.com
* ce-extras: repo.uk.bigstepcloud.com
* ce-sclo-rh: repo.uk.bigstepcloud.com
* ce-sclo-sclo: repo.uk.bigstepcloud.com
* ce-updates: repo.uk.bigstepcloud.com
* epel: epel.mirrors.arminco.com
* nethforge: nethserver.interlin.nl
* nethserver-base: nethserver.interlin.nl
* nethserver-updates: nethserver.interlin.nl
Resolution deps
--> Checing scenario
---> Package sssd-common.x86_64 0:1.16.4-21.el7_7.3 marked for update
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package: sssd-ipa-1.16.4-21.el7_7.3.x86_64
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package:: sssd-proxy-1.16.4-21.el7_7.3.x86_64
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package:: sssd-ldap-1.16.4-21.el7_7.3.x86_64
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package:: sssd-common-pac-1.16.4-21.el7_7.3.x86_64
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package:: sssd-krb5-common-1.16.4-21.el7_7.3.x86_64
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package:: sssd-ad-1.16.4-21.el7_7.3.x86_64
--> Handle dependence: sssd-common = 1.16.4-21.el7_7.3 from package:: sssd-krb5-1.16.4-21.el7_7.3.x86_64
---> Package sssd-common.x86_64 0:1.16.4-37.el7_8.3 marked as update
---> Package sssd-common.x86_64 0:1.16.4-37.el7_8.3 marked for removing
--> Check deps completed
Error: Package: sssd-common-pac-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Remove: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
Error: Package: sssd-ldap-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Removing: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
Error: Package: sssd-ipa-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Removing: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
Error: Package: sssd-krb5-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Removing: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
Error: Package: sssd-proxy-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Removing: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
Error: Package: sssd-ad-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Removing: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
Error: Package: sssd-krb5-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
Need: sssd-common = 1.16.4-21.el7_7.3
Removing: sssd-common-1.16.4-21.el7_7.3.x86_64 (@ce-updates)
sssd-common = 1.16.4-21.el7_7.3
Update: sssd-common-1.16.4-37.el7_8.3.x86_64 (ce-updates)
sssd-common = 1.16.4-37.el7_8.3
Available: sssd-common-1.16.4-37.el7.x86_64 (ce-base)
sssd-common = 1.16.4-37.el7
you can try --skip-broken to avoid this problem
How to fix it?
Hi Markus
Maybe you’ve got a tip here, I recall reading you battle with version conflicts recently…
Thx
Andy
Now I need concrete instructions.
You could try to reinstall only the corrupted packages, if any.
First you need to update everything, I do not know why you have problems, probably some broken transaction.
Blind shot:
yum --disablerepo=* --enablerepo=nethserver-updates,nethserver-base,base,updates update
I just fixed a machine with the same problem:
rm -f /usr/lib64/ldb/modules/ldb/paged_results.so
systemctl restart sssd
Thank you, master) All work fine. You save my workplace.
I think this is the best and greatest impact of the wonderful support here.
I’ve had and still have the same problem: SSSD exit code 1 e.g.
Jun 18 10:07:37 sits-srv03 httpd: [ERROR] NethServer\Tool\GroupProvider: Account provider generic error: SSSD exit code 1
is shown in the messages log file located in var/log:
No Users/Groups are shown anymore 
and as a consequence, no file sharing is possible any more 
! didn’t check other things, that are also not working accordingly.
This happened after an Update in the Software Center a few days ago.
Then I had the idea, to restore a Configuration Backup from before the update and as a result, anything worked fine again 
BUT when I a do a reboot, the SSSD exit code 1 error is back 
I really haven’t any idea how to solve this problem. What could be the reason for this error and how can I correct it?
