Bug 28053 – Join-Scripte brechen nicht ab wenn udm Aufrufe fehlschlagen

Bug 28053 - Join-Scripte brechen nicht ab wenn udm Aufrufe fehlschlagen


Summary:	Join-Scripte brechen nicht ab wenn udm Aufrufe fehlschlagen

Status:	RESOLVED DUPLICATE of bug 27753

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-07-24 15:20 CEST by Janis Meybohm
Modified:	2012-07-24 16:03 CEST (History)
CC List:	1 user (show)

See Also:
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
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 Janis Meybohm

2012-07-24 15:20:28 CEST

+++ This bug was initially created as a clone of Bug #28052 +++

Configure 34univention-management-console-server.inst 
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
Configure 35univention-management-console-module-join.inst 
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
Configure 35univention-management-console-module-lib.inst 
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
Configure 35univention-management-console-module-mrtg.inst 
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
Configure 35univention-management-console-module-packages.inst 
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)
E: Can`t find running daemon after 10 Seconds. (No socketfile)

Comment 1 Janis Meybohm

2012-07-24 15:36:21 CEST

Wie man den udm cli Fehler provozieren kann steht an bug2363

Comment 2 Alexander Kläser

2012-07-24 16:03:35 CEST

Ich denke das fällt in die Kategorie von Bug 27753.

*** This bug has been marked as a duplicate of bug 27753 ***