Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 24 18:22:52 2020
|
Hi,
Before le pam module link, yes.
After adding it, I wait some seconds before new login window popups with password error message. |
Elogd crashes on search, posted by Laurent Jean-Rigaud on Fri Jan 31 15:17:04 2020
|
OS: CentOS 7 x86_64 up2date with RPM 3.14 x86_64
Connexion to ELOG
open one logbook and click search,
input "test" and click "Search" : BOOM
Firefox
can not connect anymore on ELOG.
The crash is met with several words now ("test", "post", "4.5", are the |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Fri Jan 31 15:34:56 2020
|
Hi Stefan,
The problem seems to be specific with our logbooks. Maybe one of the file is corrupted or bad string encoding ?! But how to find the source of
the problem ? |
|
Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 31 15:39:17 2020
|
FYI i added ACL on /etc/shadow file to allow elog user for reading. Testing from elog login shell is OK.
Any suggestion ?
|
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Mon Feb 3 13:31:15 2020
|
Hi Stefan.
I installed debuginfo and ran elogd with gdb attached.
(gdb) backtrace |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Tue Feb 4 13:56:51 2020
|
Hi Stefan,
My previous dump is useless as your elog-debuginfo rpm is stripped.
So i rebuild elog w/ -g , reinstall it and activate core generation. I restst a search of "test" and get this in gdb corefile . |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Tue Feb 4 17:07:02 2020
|
At #5, there is message_id=426 . You think it's this elog entries # 426 that is the source of crash ?
Laurent
Jean-Rigaud wrote:
Hi Stefan, |
|
Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Tue Feb 4 18:33:56 2020
|
Stefan,
I cut the log in two parts w/o modifying the content and the search runs. It seems that the size of this entrie 426 is closed to a limit (as
during testing, i met a message after clicking save to recompile elog to increase a size of something), so it could be the problem. |