Jakub Hrozek wrote:
> Please file a bug so that we can take a look.
>
> It would be nice to:
> - edit /etc/sssd/sssd.conf
> - add:
>[kcm]
>debug_level = 10
> - systemctl restart sssd # to regenerate the configuration
> - systemctl restart sssd-kcm # restart the KCM deamon
> - attach
> On 20 Sep 2018, at 06:47, Alexander Bokovoy wrote:
>
> On ke, 19 syys 2018, Björn Persson wrote:
>> Alexander Bokovoy wrote:
>>> Can you provide output from
>>>
>>> export KRB5_TRACE=/dev/stderr
>>> klist -A
>>> kinit
>>> fedpkg build
>>>
>>> ?
>>
>> The log is attached. I tried it twice
On ke, 19 syys 2018, Björn Persson wrote:
Michal Toman wrote:
Exit codes with top bit set to 1 (IOW higher than 127) usually mean
unhandled signal. In your case 141 & 127 = 13 (or 141 - 128 = 13 if you
want) indicating the app got SIGPIPE and died on it.
That's a good point. And apparently no
On ke, 19 syys 2018, Björn Persson wrote:
Alexander Bokovoy wrote:
Can you provide output from
export KRB5_TRACE=/dev/stderr
klist -A
kinit
fedpkg build
?
The log is attached. I tried it twice as Tony Nelson suggested. The
first attempt failed as usual, but the second attempt was
Michal Toman wrote:
> Exit codes with top bit set to 1 (IOW higher than 127) usually mean
> unhandled signal. In your case 141 & 127 = 13 (or 141 - 128 = 13 if you
> want) indicating the app got SIGPIPE and died on it.
That's a good point. And apparently no message is printed for the PIPE
signal.
Alexander Bokovoy wrote:
> Can you provide output from
>
> export KRB5_TRACE=/dev/stderr
> klist -A
> kinit
> fedpkg build
>
> ?
The log is attached. I tried it twice as Tony Nelson suggested. The
first attempt failed as usual, but the second attempt was successful.
Björn Persson
[beorn@tag
Björn Persson wrote:
> Tony Nelson wrote:
> > No, but googling "kinit 141" leads to
> > https://bugzilla.redhat.com/show_bug.cgi?id=1537866
> > which suggests trying the kinit command twice in a row.
>
> I would think I must have tried at least twice the first time I had
> this problem, but at
Exit codes with top bit set to 1 (IOW higher than 127) usually mean
unhandled signal. In your case 141 & 127 = 13 (or 141 - 128 = 13 if you
want) indicating the app got SIGPIPE and died on it.
This is not 100% reliable since you can deliberately exit your app with
>127 code but most apps do not
On su, 16 syys 2018, Björn Persson wrote:
I have a Kerberos authentication problem.
On one computer running Fedora 27, I run kinit to authenticate to the
Fedora servers. After I enter my passphrase, kinit returns exit status
141. Then I run "fedpkg build", and get these error messages:
Tony Nelson wrote:
> No, but googling "kinit 141" leads to
> https://bugzilla.redhat.com/show_bug.cgi?id=1537866
> which suggests trying the kinit command twice in a row.
I would think I must have tried at least twice the first time I had
this problem, but at least that thread gives me some ideas
Jan Pazdziora wrote:
> Can you check the current time on the problematic machine? Is it in
> sync?
It looks pretty well synced I think:
chronyc> sources
210 Number of sources = 18
MS Name/IP address Stratum Poll Reach LastRx Last sample
On Sun, Sep 16, 2018 at 11:53:08PM +0200, Björn Persson wrote:
> I have a Kerberos authentication problem.
>
> On one computer running Fedora 27, I run kinit to authenticate to the
> Fedora servers. After I enter my passphrase, kinit returns exit status
> 141. Then I run "fedpkg build", and get
On 18-09-16 17:53:08, Björn Persson wrote:
I have a Kerberos authentication problem.
On one computer running Fedora 27, I run kinit to authenticate to the
Fedora servers. After I enter my passphrase, kinit returns exit status
141. Then I run "fedpkg build", and get these error messages:
I have a Kerberos authentication problem.
On one computer running Fedora 27, I run kinit to authenticate to the
Fedora servers. After I enter my passphrase, kinit returns exit status
141. Then I run "fedpkg build", and get these error messages:
Kerberos authentication fails: (-1765328352,
14 matches
Mail list logo
