Bug 36715 – System services module shows heimdal-kdc as stopped when it is actually running

Bug 36715 - System services module shows heimdal-kdc as stopped when it is actually running


Summary:	System services module shows heimdal-kdc as stopped when it is actually running

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - System services
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 minor (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-14 16:27 CET by Dmitry Galkin
Modified:	2019-01-03 07:16 CET (History)
CC List:	3 users (show)

See Also:	29614
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
heimdal-kdc state is shown always as 'stopped' (332.02 KB, image/png) 2014-11-14 16:27 CET, Dmitry Galkin	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dmitry Galkin

2014-11-14 16:27:13 CET

Created attachment 6377 [details]
heimdal-kdc state is shown always as 'stopped'

The 'heimdal-kdc'* is shown as stopped in the system services module, even when it is actually running.
Logging out, closing the tab, etc. does not helps (See screen-shot).

And the service is actually running:

root@master4:~# ps aux | grep heimdal-kdc
root     22218  0.0  0.5  72232  5396 ?        S    20:56   0:00 /usr/lib/heimdal-servers/kdc --config-file=/etc/heimdal-kdc/kdc.conf
root     22540  0.0  0.1   7852  1840 pts/0    S+   21:07   0:00 grep heimdal-kdc


Its log in /var/log/heimdal-kdc.log is also updated.


* Have not checked if it happens with all/any other services too;
* Tried in Chromium (ver. 37.0.2062.120);
* Cannot reproduce the problem on UCS 3.2-3.

Comment 1 Florian Best

2014-11-17 09:59:35 CET

heimdal consts of 2 daemons: /usr/lib/heimdal-servers/kdc and /usr/lib/heimdal-servers/kpasswdd. If one of them doesn't run the service is shown as stopped.

Comment 2 Dmitry Galkin

2014-11-17 10:41:09 CET

(In reply to Florian Best from comment #1)
> heimdal consts of 2 daemons: /usr/lib/heimdal-servers/kdc and
> /usr/lib/heimdal-servers/kpasswdd. If one of them doesn't run the service is
> shown as stopped.

Ok, I guess on a system with Samba4, even when samba is stopped the 'kpasswdd' won't run -> thus 'stopped' status. In case with S3 it works fine for me.

Comment 3 Dmitry Galkin

2014-11-17 12:01:42 CET

(In reply to Dmitry Galkin from comment #2)
> Ok, I guess on a system with Samba4, even when samba is stopped the
> 'kpasswdd' won't run -> thus 'stopped' status.

Hmm, however, on UCS 3.2-3 with Samba4 it also works fine, there the Heimdal password server 'kpasswdd' is running/starting OK. The heimdal init scripts are the same in the UCS 3.2-3 and UCS 4.0, so might be something wrong with 'kpasswdd' in 4.0.

Comment 4 Stefan Gohmann

2019-01-03 07:16:46 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.