Hi, I run into start up problem after removing directories /var/log/sssd and /var/lib/sss - as I wanted clean startup. It was obviousely not good idea, as sssd can not start again: .... sssd -d 9 -i (Thu Jan 23 12:14:22:790562 2014) [sssd] [check_file] (0x0400): lstat for [/var/run/nscd/socket] failed: [2][No such file or directory]. (Thu Jan 23 12:14:22:800765 2014) [sssd] [ldb] (0x0400): ltdb: tdb(/var/lib/sss/db/config.ldb): tdb_open_ex: could not open file /var/lib/sss/db/config.ldb: No such file or directory (Thu Jan 23 12:14:22:800886 2014) [sssd] [ldb] (0x0020): Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800942 2014) [sssd] [ldb] (0x0020): Failed to connect to '/var/lib/sss/db/config.ldb' with backend 'tdb': Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800988 2014) [sssd] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb] (Thu Jan 23 12:14:22:801105 2014) [sssd] [load_configuration] (0x0010): The confdb initialization failed (Thu Jan 23 12:14:22:801184 2014) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. .... How can I make initial start for sssd again??? Best, Longina
On (23/01/14 11:20), Longina Przybyszewska wrote:
Hi, I run into start up problem after removing directories /var/log/sssd and /var/lib/sss - as I wanted clean startup.
You should not remove content of direcory /var/lib/sss, because subdirectories /var/lib/sss/db and /var/lib/sss/mc will not be created by sssd. You need to create it yourself with correct permissions,
[root]# ls -l /var/lib/sss/ total 125716 drwx------. 2 root root 4096 Jan 23 11:27 db drwxr-xr-x. 2 root root 4096 Jan 23 11:27 mc drwxr-xr-x. 3 root root 4096 Jan 23 11:27 pipes drwxr-xr-x. 3 root root 4096 Jan 23 13:23 pubconf
LS
It was obviousely not good idea, as sssd can not start again: .... sssd -d 9 -i (Thu Jan 23 12:14:22:790562 2014) [sssd] [check_file] (0x0400): lstat for [/var/run/nscd/socket] failed: [2][No such file or directory]. (Thu Jan 23 12:14:22:800765 2014) [sssd] [ldb] (0x0400): ltdb: tdb(/var/lib/sss/db/config.ldb): tdb_open_ex: could not open file /var/lib/sss/db/config.ldb: No such file or directory (Thu Jan 23 12:14:22:800886 2014) [sssd] [ldb] (0x0020): Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800942 2014) [sssd] [ldb] (0x0020): Failed to connect to '/var/lib/sss/db/config.ldb' with backend 'tdb': Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800988 2014) [sssd] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb] (Thu Jan 23 12:14:22:801105 2014) [sssd] [load_configuration] (0x0010): The confdb initialization failed (Thu Jan 23 12:14:22:801184 2014) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. .... How can I make initial start for sssd again??? Best, Longina
sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
On Thu, Jan 23, 2014 at 01:33:12PM +0100, Lukas Slebodnik wrote:
On (23/01/14 11:20), Longina Przybyszewska wrote:
Hi, I run into start up problem after removing directories /var/log/sssd and /var/lib/sss - as I wanted clean startup.
You should not remove content of direcory /var/lib/sss, because subdirectories /var/lib/sss/db and /var/lib/sss/mc will not be created by sssd. You need to create it yourself with correct permissions,
[root]# ls -l /var/lib/sss/ total 125716 drwx------. 2 root root 4096 Jan 23 11:27 db drwxr-xr-x. 2 root root 4096 Jan 23 11:27 mc drwxr-xr-x. 3 root root 4096 Jan 23 11:27 pipes drwxr-xr-x. 3 root root 4096 Jan 23 13:23 pubconf
LS
It was obviousely not good idea, as sssd can not start again: .... sssd -d 9 -i (Thu Jan 23 12:14:22:790562 2014) [sssd] [check_file] (0x0400): lstat for [/var/run/nscd/socket] failed: [2][No such file or directory]. (Thu Jan 23 12:14:22:800765 2014) [sssd] [ldb] (0x0400): ltdb: tdb(/var/lib/sss/db/config.ldb): tdb_open_ex: could not open file /var/lib/sss/db/config.ldb: No such file or directory (Thu Jan 23 12:14:22:800886 2014) [sssd] [ldb] (0x0020): Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800942 2014) [sssd] [ldb] (0x0020): Failed to connect to '/var/lib/sss/db/config.ldb' with backend 'tdb': Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800988 2014) [sssd] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb] (Thu Jan 23 12:14:22:801105 2014) [sssd] [load_configuration] (0x0010): The confdb initialization failed (Thu Jan 23 12:14:22:801184 2014) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. .... How can I make initial start for sssd again??? Best, Longina
I think the simplest way would be to reinstall the packages to let the package manager recreate the directories owned by the package.
On Fedora/RHEL this would be "yum reinstall sssd"
Thanks, It worked with creating directories as Lukas suggested and one more:
mkdir /var/lib/sss/pipes/private
Longina
-----Original Message----- From: sssd-users-bounces@lists.fedorahosted.org [mailto:sssd-users-bounces@lists.fedorahosted.org] On Behalf Of Jakub Hrozek Sent: 23. januar 2014 13:44 To: sssd-users@lists.fedorahosted.org Subject: Re: [SSSD-users] sssd upstart in Saucy
On Thu, Jan 23, 2014 at 01:33:12PM +0100, Lukas Slebodnik wrote:
On (23/01/14 11:20), Longina Przybyszewska wrote:
Hi, I run into start up problem after removing directories /var/log/sssd and /var/lib/sss - as I wanted clean startup.
You should not remove content of direcory /var/lib/sss, because subdirectories /var/lib/sss/db and /var/lib/sss/mc will not be created by sssd. You need to create it yourself with correct permissions,
[root]# ls -l /var/lib/sss/ total 125716 drwx------. 2 root root 4096 Jan 23 11:27 db drwxr-xr-x. 2 root root 4096 Jan 23 11:27 mc drwxr-xr-x. 3 root root 4096 Jan 23 11:27 pipes drwxr-xr-x. 3 root root 4096 Jan 23 13:23 pubconf
LS
It was obviousely not good idea, as sssd can not start again: .... sssd -d 9 -i (Thu Jan 23 12:14:22:790562 2014) [sssd] [check_file] (0x0400): lstat for [/var/run/nscd/socket] failed: [2][No such file or directory]. (Thu Jan 23 12:14:22:800765 2014) [sssd] [ldb] (0x0400): ltdb: tdb(/var/lib/sss/db/config.ldb): tdb_open_ex: could not open file /var/lib/sss/db/config.ldb: No such file or directory (Thu Jan 23 12:14:22:800886 2014) [sssd] [ldb] (0x0020): Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800942 2014) [sssd] [ldb] (0x0020): Failed to connect to '/var/lib/sss/db/config.ldb' with backend 'tdb': Unable to open tdb '/var/lib/sss/db/config.ldb' (Thu Jan 23 12:14:22:800988 2014) [sssd] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb] (Thu Jan 23 12:14:22:801105 2014) [sssd] [load_configuration] (0x0010): The confdb initialization failed (Thu Jan 23 12:14:22:801184 2014) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. .... How can I make initial start for sssd again??? Best, Longina
I think the simplest way would be to reinstall the packages to let the package manager recreate the directories owned by the package.
On Fedora/RHEL this would be "yum reinstall sssd" _______________________________________________ sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
On Thu, Jan 23, 2014 at 12:53:54PM +0000, Longina Przybyszewska wrote:
Thanks, It worked with creating directories as Lukas suggested and one more:
mkdir /var/lib/sss/pipes/private
Longina
I'm glad it worked!
btw the reason I suggested to use distro tool was that mkdir would just create the directories with the default permissions, while the package might create them with more restrictive..
sssd-users@lists.fedorahosted.org
-
Jakub Hrozek -
Longina Przybyszewska -
Lukas Slebodnik