Burkhard99
Anmeldungsdatum: 2. Juli 2014
Beiträge: Zähle...
|
Guten Morgen, Vor einiger Zeit habe ich das Programm Jitsi installiert, um es als Alternative zu Zoom auszuprobieren. Da ich es aber nicht brauche, habe ich versucht, es im Anwendungsbereich zu entfernen (deinstallieren), was aber nicht gelingt.
Das wäre ja vielleicht nicht weiter schlimm, wenn mir das Programm nicht die Installation anderen Programme verhindert.
Kann es sein, dass Jitsi von mir eine configuration erwartet, die immer dann noch mal als erstes kommt, wenn ich andere Programme installieren will? Als letztes Beispiel dazu wollte ich neulich ein update des HP Druckertreibers hplip installieren und habe dazu alte hplip Versionen mit
| sudo apt purge hplip hplip-data
|
entfernt. Da kommt dann im Terminal im Ergebnis dieses Befehls zunächst einige Löschungsbestätigungen von hplip Dateien (die ich jetzt hier nicht wiedergebe) und am Schluss der Verweis auf die jitsi Einrichtung und eine Fehlermeldung. 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26 | [.....]
jitsi-meet-prosody (1.0.4466-1) wird eingerichtet ...
The given hostname does not exist in the config
The given hostname does not exist in the config
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet-prosody (--configure):
»installiertes jitsi-meet-prosody-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von jitsi-meet:
jitsi-meet hängt ab von jitsi-meet-prosody (= 1.0.4466-1); aber:
Paket jitsi-meet-prosody ist noch nicht konfiguriert.
dpkg: Error while editing the package jitsi-meet (--configure):
dependency problems - is unconfigured
dpkg: Dependency problems prevent configuration of jitsi-meet-turnserver:
jitsi-meet-turnserver depends on jitsi-meet-prosody; but:
package jitsi-meet-prosody is not configured yet.
dpkg: Error while editing the package jitsi-meet-turnserver (--configure):
dependency problems - is unconfigured
Processing triggers for dbus (1.12.2-1ubuntu1.2) ...
Processing triggers for cups (2.2.7-1ubuntu2.8) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Errors occurred while editing:
jitsi-meet-prosody
jitsi-meet
jitsi-meet-turnserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
|
MEINE FRAGE ist nun: Wie bekomme ich diese Jitsi reste und Jitsi selbst entfernt (deinstallliert)? Herzliche Grüße Burkhard
Moderiert von sebix: Thema in einen passenden Forenbereich verschoben. Bitte beachte die als wichtig markierten Themen („Welche Themen gehören hier her und welche nicht?“) in jedem Forenbereich. Danke.
|
tomtomtom
Supporter
Anmeldungsdatum: 22. August 2008
Beiträge: 52312
|
Was zeigt sudo dpkg --configura -a an?
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
tomtomtom schrieb: Was zeigt sudo dpkg --configura -a an?
zeigt folgendes Ergebnis:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21 | jitsi-meet-prosody (1.0.4466-1) wird eingerichtet ...
The given hostname does not exist in the config
The given hostname does not exist in the config
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet-prosody (--configure):
»installiertes jitsi-meet-prosody-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von jitsi-meet:
jitsi-meet hängt ab von jitsi-meet-prosody (= 1.0.4466-1); aber:
Paket jitsi-meet-prosody ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von jitsi-meet-turnserver:
jitsi-meet-turnserver hängt ab von jitsi-meet-prosody; aber:
Paket jitsi-meet-prosody ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet-turnserver (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
jitsi-meet-prosody
jitsi-meet
jitsi-meet-turnserver
|
|
tomtomtom
Supporter
Anmeldungsdatum: 22. August 2008
Beiträge: 52312
|
Burkhard99 schrieb: jitsi-meet-prosody (1.0.4466-1) wird eingerichtet ...
The given hostname does not exist in the config
The given hostname does not exist in the config
dpkg: Fehler beim Bearbeiten des Paketes jitsi-meet-prosody (--configure):
»installiertes jitsi-meet-prosody-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Na dann wäre der Inhalt interessant (und ob der zu dem beanstandeten Hostname gehört). cat $(ls /var/lib/dpkg/info/jitsi-meet-prosody*)
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
tomtomtom schrieb:
Na dann wäre der Inhalt interessant (und ob der zu dem beanstandeten Hostname gehört). cat $(ls /var/lib/dpkg/info/jitsi-meet-prosody*)
Dieser Befehl bring das folgende Ergebnis: 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421 | /.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/jitsi-meet-prosody
/usr/share/doc/jitsi-meet-prosody/README
/usr/share/doc/jitsi-meet-prosody/README.Debian
/usr/share/doc/jitsi-meet-prosody/changelog.Debian.gz
/usr/share/doc/jitsi-meet-prosody/copyright
/usr/share/jitsi-meet
/usr/share/jitsi-meet/prosody-plugins
/usr/share/jitsi-meet/prosody-plugins/ext_events.lib.lua
/usr/share/jitsi-meet/prosody-plugins/mod_auth_token.lua
/usr/share/jitsi-meet/prosody-plugins/mod_conference_duration.lua
/usr/share/jitsi-meet/prosody-plugins/mod_conference_duration_component.lua
/usr/share/jitsi-meet/prosody-plugins/mod_filter_iq_jibri.lua
/usr/share/jitsi-meet/prosody-plugins/mod_filter_iq_rayo.lua
/usr/share/jitsi-meet/prosody-plugins/mod_jibri_queue.lua
/usr/share/jitsi-meet/prosody-plugins/mod_jibri_queue_component.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_allowners.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_call.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_domain_mapper.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_lobby_rooms.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_max_occupants.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_meeting_id.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_poltergeist.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_size.lua
/usr/share/jitsi-meet/prosody-plugins/mod_muc_transcription_filter.lua
/usr/share/jitsi-meet/prosody-plugins/mod_poltergeist_component.lua
/usr/share/jitsi-meet/prosody-plugins/mod_presence_identity.lua
/usr/share/jitsi-meet/prosody-plugins/mod_smacks.lua
/usr/share/jitsi-meet/prosody-plugins/mod_speakerstats.lua
/usr/share/jitsi-meet/prosody-plugins/mod_speakerstats_component.lua
/usr/share/jitsi-meet/prosody-plugins/mod_token_verification.lua
/usr/share/jitsi-meet/prosody-plugins/mod_turncredentials.lua
/usr/share/jitsi-meet/prosody-plugins/mod_websocket_session_event.patch
/usr/share/jitsi-meet/prosody-plugins/mod_websocket_smacks.patch
/usr/share/jitsi-meet/prosody-plugins/muc_owner_allow_kick.patch
/usr/share/jitsi-meet/prosody-plugins/poltergeist.lib.lua
/usr/share/jitsi-meet/prosody-plugins/token
/usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua
/usr/share/jitsi-meet/prosody-plugins/util.lib.lua
/usr/share/jitsi-meet-prosody
/usr/share/jitsi-meet-prosody/prosody.cfg.lua-jvb.example
038711af2fd30f26a551fb01de2a59d5 usr/share/doc/jitsi-meet-prosody/README
27be2c0bb7a6d621908b1e29615605ba usr/share/doc/jitsi-meet-prosody/README.Debian
7fb7f8e199ac356596e455919acabeac usr/share/doc/jitsi-meet-prosody/changelog.Debian.gz
670f81b855b4ebc5f03ccb278d5b203f usr/share/doc/jitsi-meet-prosody/copyright
a46066f9663368215c4113d3942ffa9a usr/share/jitsi-meet-prosody/prosody.cfg.lua-jvb.example
22aeb3add43d969669a5d5dbd0c8b9c2 usr/share/jitsi-meet/prosody-plugins/ext_events.lib.lua
60aa5a8810e6e2ff2c013db1b67941e8 usr/share/jitsi-meet/prosody-plugins/mod_auth_token.lua
6b4730c3ede11fdc7efea65500e47648 usr/share/jitsi-meet/prosody-plugins/mod_conference_duration.lua
01ebbae572f7d6253a44993c713228ee usr/share/jitsi-meet/prosody-plugins/mod_conference_duration_component.lua
799fd6ef76b9d06b5e367754aaf554a7 usr/share/jitsi-meet/prosody-plugins/mod_filter_iq_jibri.lua
f38f31e8f644e2d737f48b148084a2b1 usr/share/jitsi-meet/prosody-plugins/mod_filter_iq_rayo.lua
c61333e9120b79744092fc75784a8b0b usr/share/jitsi-meet/prosody-plugins/mod_jibri_queue.lua
488b478f0d5a040dda2db19e7071ea6a usr/share/jitsi-meet/prosody-plugins/mod_jibri_queue_component.lua
6ebd612c4ee7da8353df87a518a02c0a usr/share/jitsi-meet/prosody-plugins/mod_muc_allowners.lua
6b2b60915114386fd63f04642b9175c9 usr/share/jitsi-meet/prosody-plugins/mod_muc_call.lua
ce62752195cc4f2d5e61e4535bb8af77 usr/share/jitsi-meet/prosody-plugins/mod_muc_domain_mapper.lua
626342195b5625370f5af58f025c8258 usr/share/jitsi-meet/prosody-plugins/mod_muc_lobby_rooms.lua
0281dc18a6b53f28313dc6a5cf9c8d93 usr/share/jitsi-meet/prosody-plugins/mod_muc_max_occupants.lua
a4f1087a99b07707a24f5cc316d44458 usr/share/jitsi-meet/prosody-plugins/mod_muc_meeting_id.lua
f50dd101e8711b18d5bc4d7f3d24b25e usr/share/jitsi-meet/prosody-plugins/mod_muc_poltergeist.lua
2e16d7d0a818f4a9ced2c88f532cf43a usr/share/jitsi-meet/prosody-plugins/mod_muc_size.lua
0234244a32fc2bfc39b376390139dabe usr/share/jitsi-meet/prosody-plugins/mod_muc_transcription_filter.lua
41a0d89fbe07cf83e5736e2ee6222e90 usr/share/jitsi-meet/prosody-plugins/mod_poltergeist_component.lua
7227aca51ca7d2984635eb098b77283d usr/share/jitsi-meet/prosody-plugins/mod_presence_identity.lua
11cf8bed290f5377c16c8f15be333b10 usr/share/jitsi-meet/prosody-plugins/mod_smacks.lua
ad07754e2267d1f6424d8ff813041a8d usr/share/jitsi-meet/prosody-plugins/mod_speakerstats.lua
152d6493e586f8a2b382d5fd288d7169 usr/share/jitsi-meet/prosody-plugins/mod_speakerstats_component.lua
6059b56c300c2af36dfd38829a07dc30 usr/share/jitsi-meet/prosody-plugins/mod_token_verification.lua
68d209c3ec87df2fd3bc291fd19f0712 usr/share/jitsi-meet/prosody-plugins/mod_turncredentials.lua
c61ee17e52021dc71554ab0a57caeaf3 usr/share/jitsi-meet/prosody-plugins/mod_websocket_session_event.patch
bb335deb22b6931eceb6645bc13c6ecd usr/share/jitsi-meet/prosody-plugins/mod_websocket_smacks.patch
97ce3779e469708ac9bfd0cb7525c71c usr/share/jitsi-meet/prosody-plugins/muc_owner_allow_kick.patch
c94c197e05b530985c49546f9078e05c usr/share/jitsi-meet/prosody-plugins/poltergeist.lib.lua
50c21c23787b272492207b27e8cfd62c usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua
5b28743cd97317d5740edcff045a60eb usr/share/jitsi-meet/prosody-plugins/util.lib.lua
#!/bin/bash
# postinst script for jitsi-meet-prosody
#
# see: dh_installdeb(1)
set -e
# summary of how this script can be called:
# * <postinst> `configure' <most-recently-configured-version>
# * <old-postinst> `abort-upgrade' <new version>
# * <conflictor's-postinst> `abort-remove' `in-favour' <package>
# <new-version>
# * <postinst> `abort-remove'
# * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
# <failed-install-package> <version> `removing'
# <conflicting-package> <version>
# for details, see http://www.debian.org/doc/debian-policy/ or
# the debian-policy package
function generateRandomPassword() {
cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 16
}
case "$1" in
configure)
# loading debconf
. /usr/share/debconf/confmodule
# try to get host from jitsi-videobridge
db_get jitsi-videobridge/jvb-hostname
if [ -z "$RET" ] ; then
# server hostname
db_set jitsi-videobridge/jvb-hostname "localhost"
db_input critical jitsi-videobridge/jvb-hostname || true
db_go
fi
JVB_HOSTNAME="$RET"
db_get jitsi-videobridge/jvbsecret
if [ -z "$RET" ] ; then
db_input critical jitsi-videobridge/jvbsecret || true
db_go
fi
JVB_SECRET="$RET"
db_get jicofo/jicofo-authuser
if [ -z "$RET" ] ; then
db_input critical jicofo/jicofo-authuser || true
db_go
fi
JICOFO_AUTH_USER="$RET"
db_get jicofo/jicofo-authpassword
if [ -z "$RET" ] ; then
# if password is missing generate it, and store it
JICOFO_AUTH_PASSWORD=`generateRandomPassword`
db_set jicofo/jicofo-authpassword "$JICOFO_AUTH_PASSWORD"
else
JICOFO_AUTH_PASSWORD="$RET"
fi
db_get jicofo/jicofosecret
if [ -z "$RET" ] ; then
# if secret is missing generate it, and store it
JICOFO_SECRET=`generateRandomPassword`
db_set jicofo/jicofosecret "$JICOFO_SECRET"
else
JICOFO_SECRET="$RET"
fi
JICOFO_AUTH_DOMAIN="auth.$JVB_HOSTNAME"
# detect dpkg-reconfigure, just delete old links
db_get jitsi-meet-prosody/jvb-hostname
JVB_HOSTNAME_OLD=$RET
if [ -n "$RET" ] && [ ! "$JVB_HOSTNAME_OLD" = "$JVB_HOSTNAME" ] ; then
rm -f /etc/prosody/conf.d/$JVB_HOSTNAME_OLD.cfg.lua
rm -f /etc/prosody/certs/$JVB_HOSTNAME_OLD.key
rm -f /etc/prosody/certs/$JVB_HOSTNAME_OLD.crt
fi
# stores the hostname so we will reuse it later, like in purge
db_set jitsi-meet-prosody/jvb-hostname "$JVB_HOSTNAME"
db_get jitsi-meet-prosody/turn-secret
if [ -z "$RET" ] ; then
# 8-chars random secret used for the turnserver
TURN_SECRET=`generateRandomPassword`
db_set jitsi-meet-prosody/turn-secret "$TURN_SECRET"
else
TURN_SECRET="$RET"
fi
# and we're done with debconf
db_stop
PROSODY_CONFIG_PRESENT="true"
PROSODY_CREATE_JICOFO_USER="false"
PROSODY_HOST_CONFIG="/etc/prosody/conf.avail/$JVB_HOSTNAME.cfg.lua"
PROSODY_CONFIG_OLD="/etc/prosody/prosody.cfg.lua"
# if there is no prosody config extract our template
# check for config in conf.avail or check whether it wasn't already configured in main config
if [ ! -f $PROSODY_HOST_CONFIG ] && ! grep -q "VirtualHost \"$JVB_HOSTNAME\"" $PROSODY_CONFIG_OLD; then
PROSODY_CONFIG_PRESENT="false"
mkdir -p /etc/prosody/conf.avail/
mkdir -p /etc/prosody/conf.d/
cp /usr/share/jitsi-meet-prosody/prosody.cfg.lua-jvb.example $PROSODY_HOST_CONFIG
sed -i "s/jitmeet.example.com/$JVB_HOSTNAME/g" $PROSODY_HOST_CONFIG
sed -i "s/focusSecret/$JICOFO_SECRET/g" $PROSODY_HOST_CONFIG
sed -i "s/focusUser/$JICOFO_AUTH_USER/g" $PROSODY_HOST_CONFIG
sed -i "s/__turnSecret__/$TURN_SECRET/g" $PROSODY_HOST_CONFIG
if [ ! -f /etc/prosody/conf.d/$JVB_HOSTNAME.cfg.lua ]; then
ln -s $PROSODY_HOST_CONFIG /etc/prosody/conf.d/$JVB_HOSTNAME.cfg.lua
fi
PROSODY_CREATE_JICOFO_USER="true"
# on some distributions main prosody config doesn't include configs
# from conf.d folder enable it as this where we put our config by default
if ! grep -q "Include \"conf\.d\/\*\.cfg.lua\"" $PROSODY_CONFIG_OLD; then
echo -e "\nInclude \"conf.d/*.cfg.lua\"" >> $PROSODY_CONFIG_OLD
fi
fi
if [ "$PROSODY_CREATE_JICOFO_USER" = "true" ]; then
# create 'focus@auth.domain' prosody user
prosodyctl register $JICOFO_AUTH_USER $JICOFO_AUTH_DOMAIN $JICOFO_AUTH_PASSWORD
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
USER_EXISTS_CHECK=`prosodyctl adduser jvb@$JICOFO_AUTH_DOMAIN < /dev/null || true`
if [ ! "$USER_EXISTS_CHECK" = "That user already exists" ]; then
prosodyctl register jvb $JICOFO_AUTH_DOMAIN $JVB_SECRET || true
fi
# Check whether prosody config has the internal muc, if not add it,
# as we are migrating configs
if [ -f $PROSODY_HOST_CONFIG ] && ! grep -q "internal.auth.$JVB_HOSTNAME" $PROSODY_HOST_CONFIG; then
echo -e "\nComponent \"internal.auth.$JVB_HOSTNAME\" \"muc\"" >> $PROSODY_HOST_CONFIG
echo -e " storage = \"memory\"" >> $PROSODY_HOST_CONFIG
echo -e " modules_enabled = { \"ping\"; }" >> $PROSODY_HOST_CONFIG
echo -e " admins = { \"$JICOFO_AUTH_USER@auth.$JVB_HOSTNAME\", \"jvb@auth.$JVB_HOSTNAME\" }" >> $PROSODY_HOST_CONFIG
fi
if [ ! -f /var/lib/prosody/$JVB_HOSTNAME.crt ]; then
# prosodyctl takes care for the permissions
# echo for using all default values
echo | prosodyctl cert generate $JVB_HOSTNAME
ln -sf /var/lib/prosody/$JVB_HOSTNAME.key /etc/prosody/certs/$JVB_HOSTNAME.key
ln -sf /var/lib/prosody/$JVB_HOSTNAME.crt /etc/prosody/certs/$JVB_HOSTNAME.crt
fi
PRTRUNK_INSTALL_CHECK="$(dpkg-query -f '${Status}' -W 'prosody-trunk' 2>/dev/null | awk '{print $3}' || true)"
PR10_INSTALL_CHECK="$(dpkg-query -f '${Status}' -W 'prosody-0.10' 2>/dev/null | awk '{print $3}' || true)"
PR_VER_INSTALLED=$(dpkg-query -f='${Version}\n' --show prosody 2>/dev/null || true)
if [ "$PRTRUNK_INSTALL_CHECK" = "installed" ] \
|| [ "$PRTRUNK_INSTALL_CHECK" = "unpacked" ] ; then
if [ -f $PROSODY_HOST_CONFIG ]; then
sed -i 's/storage = \"memory\"/storage = \"null\"/g' $PROSODY_HOST_CONFIG
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
fi
if [ "$PR10_INSTALL_CHECK" = "installed" ] \
|| [ "$PR10_INSTALL_CHECK" = "unpacked" ] \
|| dpkg --compare-versions "$PR_VER_INSTALLED" gt "0.10" ; then
# if the version is 0.10.X (>0.10 and <0.11)
if [ -f $PROSODY_HOST_CONFIG ] \
&& dpkg --compare-versions "$PR_VER_INSTALLED" lt "0.11" ; then
sed -i 's/storage = \"memory\"/storage = \"none\"/g' $PROSODY_HOST_CONFIG
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
fi
if [ ! -f /var/lib/prosody/$JICOFO_AUTH_DOMAIN.crt ]; then
# prosodyctl takes care for the permissions
# echo for using all default values
echo | prosodyctl cert generate $JICOFO_AUTH_DOMAIN
AUTH_KEY_FILE="/etc/prosody/certs/$JICOFO_AUTH_DOMAIN.key"
AUTH_CRT_FILE="/etc/prosody/certs/$JICOFO_AUTH_DOMAIN.crt"
ln -sf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.key $AUTH_KEY_FILE
ln -sf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.crt $AUTH_CRT_FILE
ln -sf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.crt /usr/local/share/ca-certificates/$JICOFO_AUTH_DOMAIN.crt
# we need to force updating certificates, in some cases java trust
# store not get re-generated with latest changes
update-ca-certificates -f
# don't fail on systems with custom config ($PROSODY_HOST_CONFIG is missing)
if [ -f $PROSODY_HOST_CONFIG ]; then
# now let's add the ssl cert for the auth. domain (we use # as a sed delimiter cause filepaths are confused with default / delimiter)
sed -i "s#VirtualHost \"$JICOFO_AUTH_DOMAIN\"#VirtualHost \"$JICOFO_AUTH_DOMAIN\"\n ssl = {\n key = \"$AUTH_KEY_FILE\";\n certificate = \"$AUTH_CRT_FILE\";\n \}#g" $PROSODY_HOST_CONFIG
fi
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
if [ "$PROSODY_CONFIG_PRESENT" = "false" ]; then
invoke-rc.d prosody restart || true
fi
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
exit 1
;;
esac
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
exit 0
#!/bin/sh
# postrm script for jitsi-meet-prosody
#
# see: dh_installdeb(1)
set -e
# summary of how this script can be called:
# * <postrm> `remove'
# * <postrm> `purge'
# * <old-postrm> `upgrade' <new-version>
# * <new-postrm> `failed-upgrade' <old-version>
# * <new-postrm> `abort-install'
# * <new-postrm> `abort-install' <old-version>
# * <new-postrm> `abort-upgrade' <old-version>
# * <disappearer's-postrm> `disappear' <overwriter>
# <overwriter-version>
# for details, see http://www.debian.org/doc/debian-policy/ or
# the debian-policy package
# Load debconf
. /usr/share/debconf/confmodule
case "$1" in
remove)
if [ -x "/etc/init.d/prosody" ]; then
invoke-rc.d prosody reload || true
fi
;;
purge)
db_get jitsi-meet-prosody/jvb-hostname
JVB_HOSTNAME=$RET
if [ -n "$RET" ]; then
rm -f /etc/prosody/conf.avail/$JVB_HOSTNAME.cfg.lua
rm -f /etc/prosody/conf.d/$JVB_HOSTNAME.cfg.lua
JICOFO_AUTH_DOMAIN="auth.$JVB_HOSTNAME"
# clean up generated certificates
rm -f /etc/prosody/certs/$JVB_HOSTNAME.crt
rm -f /etc/prosody/certs/$JVB_HOSTNAME.key
rm -f /etc/prosody/certs/$JICOFO_AUTH_DOMAIN.crt
rm -f /etc/prosody/certs/$JICOFO_AUTH_DOMAIN.key
rm -rf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.*
rm -rf /var/lib/prosody/$JVB_HOSTNAME.*
# clean created users, replace '.' with '%2e', replace '-' with '%2d'
rm -rf /var/lib/prosody/`echo $JICOFO_AUTH_DOMAIN | sed -e "s/\./%2e/g"| sed -e "s/-/%2d/g"`
# clean the prosody cert from the trust store
rm -rf /usr/local/share/ca-certificates/$JICOFO_AUTH_DOMAIN.*
update-ca-certificates -f
fi
# Clear the debconf variable
db_purge
;;
upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
;;
*)
echo "postrm called with unknown argument \`$1'" >&2
exit 1
;;
esac
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
# Automatically added by dh_installdebconf/11.1.6ubuntu2
if [ "$1" = purge ] && [ -e /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
db_purge
fi
# End automatically added section
db_stop
exit 0
Template: jitsi-meet-prosody/jvb-hostname
Type: string
Description: The hostname of the current installation:
The value for the hostname that is set in Jitsi Videobridge installation.
Template: jitsi-videobridge/jvb-hostname
Type: string
Description: The hostname of the current installation:
The value for the hostname that is set in Jitsi Videobridge installation.
Template: jitsi-videobridge/jvbsecret
Type: password
Description: Jitsi Videobridge Component secret:
The secret used by Jitsi Videobridge to connect to xmpp server as component.
Template: jicofo/jicofo-authuser
Type: string
Default: focus
Description: Jicofo username:
The jicofo needs an authenticated admin user to connect to xmpp server.
Template: jicofo/jicofo-authpassword
Type: password
Description: Jicofo user password:
The secret used to connect to xmpp server as jicofo user.
Template: jicofo/jicofosecret
Type: password
Description: Jicofo Component secret:
The secret used to connect to xmpp server as component
Template: jitsi-meet-prosody/turn-secret
Type: string
Description: The turn server secret
The secret used to connect to turnserver server.
|
|
tomtomtom
Supporter
Anmeldungsdatum: 22. August 2008
Beiträge: 52312
|
Das hier dürfte der für uns relevante Abschnitt sein: #!/bin/bash
# postinst script for jitsi-meet-prosody
#
# see: dh_installdeb(1)
set -e
# summary of how this script can be called:
# * <postinst> `configure' <most-recently-configured-version>
# * <old-postinst> `abort-upgrade' <new version>
# * <conflictor's-postinst> `abort-remove' `in-favour' <package>
# <new-version>
# * <postinst> `abort-remove'
# * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
# <failed-install-package> <version> `removing'
# <conflicting-package> <version>
# for details, see http://www.debian.org/doc/debian-policy/ or
# the debian-policy package
function generateRandomPassword() {
cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 16
}
case "$1" in
configure)
# loading debconf
. /usr/share/debconf/confmodule
# try to get host from jitsi-videobridge
db_get jitsi-videobridge/jvb-hostname
if [ -z "$RET" ] ; then
# server hostname
db_set jitsi-videobridge/jvb-hostname "localhost"
db_input critical jitsi-videobridge/jvb-hostname || true
db_go
fi
JVB_HOSTNAME="$RET"
db_get jitsi-videobridge/jvbsecret
if [ -z "$RET" ] ; then
db_input critical jitsi-videobridge/jvbsecret || true
db_go
fi
JVB_SECRET="$RET"
db_get jicofo/jicofo-authuser
if [ -z "$RET" ] ; then
db_input critical jicofo/jicofo-authuser || true
db_go
fi
JICOFO_AUTH_USER="$RET"
db_get jicofo/jicofo-authpassword
if [ -z "$RET" ] ; then
# if password is missing generate it, and store it
JICOFO_AUTH_PASSWORD=`generateRandomPassword`
db_set jicofo/jicofo-authpassword "$JICOFO_AUTH_PASSWORD"
else
JICOFO_AUTH_PASSWORD="$RET"
fi
db_get jicofo/jicofosecret
if [ -z "$RET" ] ; then
# if secret is missing generate it, and store it
JICOFO_SECRET=`generateRandomPassword`
db_set jicofo/jicofosecret "$JICOFO_SECRET"
else
JICOFO_SECRET="$RET"
fi
JICOFO_AUTH_DOMAIN="auth.$JVB_HOSTNAME"
# detect dpkg-reconfigure, just delete old links
db_get jitsi-meet-prosody/jvb-hostname
JVB_HOSTNAME_OLD=$RET
if [ -n "$RET" ] && [ ! "$JVB_HOSTNAME_OLD" = "$JVB_HOSTNAME" ] ; then
rm -f /etc/prosody/conf.d/$JVB_HOSTNAME_OLD.cfg.lua
rm -f /etc/prosody/certs/$JVB_HOSTNAME_OLD.key
rm -f /etc/prosody/certs/$JVB_HOSTNAME_OLD.crt
fi
# stores the hostname so we will reuse it later, like in purge
db_set jitsi-meet-prosody/jvb-hostname "$JVB_HOSTNAME"
db_get jitsi-meet-prosody/turn-secret
if [ -z "$RET" ] ; then
# 8-chars random secret used for the turnserver
TURN_SECRET=`generateRandomPassword`
db_set jitsi-meet-prosody/turn-secret "$TURN_SECRET"
else
TURN_SECRET="$RET"
fi
# and we're done with debconf
db_stop
PROSODY_CONFIG_PRESENT="true"
PROSODY_CREATE_JICOFO_USER="false"
PROSODY_HOST_CONFIG="/etc/prosody/conf.avail/$JVB_HOSTNAME.cfg.lua"
PROSODY_CONFIG_OLD="/etc/prosody/prosody.cfg.lua"
# if there is no prosody config extract our template
# check for config in conf.avail or check whether it wasn't already configured in main config
if [ ! -f $PROSODY_HOST_CONFIG ] && ! grep -q "VirtualHost \"$JVB_HOSTNAME\"" $PROSODY_CONFIG_OLD; then
PROSODY_CONFIG_PRESENT="false"
mkdir -p /etc/prosody/conf.avail/
mkdir -p /etc/prosody/conf.d/
cp /usr/share/jitsi-meet-prosody/prosody.cfg.lua-jvb.example $PROSODY_HOST_CONFIG
sed -i "s/jitmeet.example.com/$JVB_HOSTNAME/g" $PROSODY_HOST_CONFIG
sed -i "s/focusSecret/$JICOFO_SECRET/g" $PROSODY_HOST_CONFIG
sed -i "s/focusUser/$JICOFO_AUTH_USER/g" $PROSODY_HOST_CONFIG
sed -i "s/__turnSecret__/$TURN_SECRET/g" $PROSODY_HOST_CONFIG
if [ ! -f /etc/prosody/conf.d/$JVB_HOSTNAME.cfg.lua ]; then
ln -s $PROSODY_HOST_CONFIG /etc/prosody/conf.d/$JVB_HOSTNAME.cfg.lua
fi
PROSODY_CREATE_JICOFO_USER="true"
# on some distributions main prosody config doesn't include configs
# from conf.d folder enable it as this where we put our config by default
if ! grep -q "Include \"conf\.d\/\*\.cfg.lua\"" $PROSODY_CONFIG_OLD; then
echo -e "\nInclude \"conf.d/*.cfg.lua\"" >> $PROSODY_CONFIG_OLD
fi
fi
if [ "$PROSODY_CREATE_JICOFO_USER" = "true" ]; then
# create 'focus@auth.domain' prosody user
prosodyctl register $JICOFO_AUTH_USER $JICOFO_AUTH_DOMAIN $JICOFO_AUTH_PASSWORD
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
USER_EXISTS_CHECK=`prosodyctl adduser jvb@$JICOFO_AUTH_DOMAIN < /dev/null || true`
if [ ! "$USER_EXISTS_CHECK" = "That user already exists" ]; then
prosodyctl register jvb $JICOFO_AUTH_DOMAIN $JVB_SECRET || true
fi
# Check whether prosody config has the internal muc, if not add it,
# as we are migrating configs
if [ -f $PROSODY_HOST_CONFIG ] && ! grep -q "internal.auth.$JVB_HOSTNAME" $PROSODY_HOST_CONFIG; then
echo -e "\nComponent \"internal.auth.$JVB_HOSTNAME\" \"muc\"" >> $PROSODY_HOST_CONFIG
echo -e " storage = \"memory\"" >> $PROSODY_HOST_CONFIG
echo -e " modules_enabled = { \"ping\"; }" >> $PROSODY_HOST_CONFIG
echo -e " admins = { \"$JICOFO_AUTH_USER@auth.$JVB_HOSTNAME\", \"jvb@auth.$JVB_HOSTNAME\" }" >> $PROSODY_HOST_CONFIG
fi
if [ ! -f /var/lib/prosody/$JVB_HOSTNAME.crt ]; then
# prosodyctl takes care for the permissions
# echo for using all default values
echo | prosodyctl cert generate $JVB_HOSTNAME
ln -sf /var/lib/prosody/$JVB_HOSTNAME.key /etc/prosody/certs/$JVB_HOSTNAME.key
ln -sf /var/lib/prosody/$JVB_HOSTNAME.crt /etc/prosody/certs/$JVB_HOSTNAME.crt
fi
PRTRUNK_INSTALL_CHECK="$(dpkg-query -f '${Status}' -W 'prosody-trunk' 2>/dev/null | awk '{print $3}' || true)"
PR10_INSTALL_CHECK="$(dpkg-query -f '${Status}' -W 'prosody-0.10' 2>/dev/null | awk '{print $3}' || true)"
PR_VER_INSTALLED=$(dpkg-query -f='${Version}\n' --show prosody 2>/dev/null || true)
if [ "$PRTRUNK_INSTALL_CHECK" = "installed" ] \
|| [ "$PRTRUNK_INSTALL_CHECK" = "unpacked" ] ; then
if [ -f $PROSODY_HOST_CONFIG ]; then
sed -i 's/storage = \"memory\"/storage = \"null\"/g' $PROSODY_HOST_CONFIG
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
fi
if [ "$PR10_INSTALL_CHECK" = "installed" ] \
|| [ "$PR10_INSTALL_CHECK" = "unpacked" ] \
|| dpkg --compare-versions "$PR_VER_INSTALLED" gt "0.10" ; then
# if the version is 0.10.X (>0.10 and <0.11)
if [ -f $PROSODY_HOST_CONFIG ] \
&& dpkg --compare-versions "$PR_VER_INSTALLED" lt "0.11" ; then
sed -i 's/storage = \"memory\"/storage = \"none\"/g' $PROSODY_HOST_CONFIG
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
fi
if [ ! -f /var/lib/prosody/$JICOFO_AUTH_DOMAIN.crt ]; then
# prosodyctl takes care for the permissions
# echo for using all default values
echo | prosodyctl cert generate $JICOFO_AUTH_DOMAIN
AUTH_KEY_FILE="/etc/prosody/certs/$JICOFO_AUTH_DOMAIN.key"
AUTH_CRT_FILE="/etc/prosody/certs/$JICOFO_AUTH_DOMAIN.crt"
ln -sf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.key $AUTH_KEY_FILE
ln -sf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.crt $AUTH_CRT_FILE
ln -sf /var/lib/prosody/$JICOFO_AUTH_DOMAIN.crt /usr/local/share/ca-certificates/$JICOFO_AUTH_DOMAIN.crt
# we need to force updating certificates, in some cases java trust
# store not get re-generated with latest changes
update-ca-certificates -f
# don't fail on systems with custom config ($PROSODY_HOST_CONFIG is missing)
if [ -f $PROSODY_HOST_CONFIG ]; then
# now let's add the ssl cert for the auth. domain (we use # as a sed delimiter cause filepaths are confused with default / delimiter)
sed -i "s#VirtualHost \"$JICOFO_AUTH_DOMAIN\"#VirtualHost \"$JICOFO_AUTH_DOMAIN\"\n ssl = {\n key = \"$AUTH_KEY_FILE\";\n certificate = \"$AUTH_CRT_FILE\";\n \}#g" $PROSODY_HOST_CONFIG
fi
# trigger a restart
PROSODY_CONFIG_PRESENT="false"
fi
if [ "$PROSODY_CONFIG_PRESENT" = "false" ]; then
invoke-rc.d prosody restart || true
fi
;;
abort-upgrade|abort-remove|abort-deconfigure)
;;
*)
echo "postinst called with unknown argument \`$1'" >&2
exit 1
;;
esac
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
exit 0 Bei der Abarbeitung gab es also einen Fehler. Ja, sehr informativ. 😉 Was steht denn in der Host-Config?
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
tomtomtom schrieb:
Was steht denn in der Host-Config?
Sorry, wie find ich das raus?
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
Burkhard99 schrieb: tomtomtom schrieb:
Was steht denn in der Host-Config?
Sorry, wie find ich das raus?
Hallo tomtomtom,
Tut mir leid, meine Frage ist wahrscheinlich ganz banal, aber ich stehe irgendwie auf dem Schlauch, was gemeint ist. Ist die Host-Config, von der du sprichst, eine Config, die auf meinem Rechner sein müsste? Wenn ja, mit welchem Befehl öffne ich sie? Oder geht es um eine Config bei jemandem, der dieses "Jitsi meet" hosted? Letzteres glaube ich nicht. Denn wenn ich das richtig verstanden habe, kann man mit Jitsi meet etwas tun, um selbst zum Host zu werden (also um unsichere Host Provider zu umgehen). Aber vielleicht verstehe ich auch das ganze Prinzip nicht. Und das heißt, ich hätte es nie anfangen sollen.... Nachdem ich nun den Fehler begangen habe, frage ich mich eigentlich nur noch, gibt es eine Weg, alles was auf die unvollendete Installation/Configuration von Jitsi Meet hinweist (und damit jeden meiner Versuche, ein anderes Programm neu zu installieren in die Sackgasse führt und unmöglich macht), rückstandslos zu beseitigen? Bitte entschuldige meine Verwirrung.
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19527
|
Siehe mal https://manpages.ubuntu.com/manpages/xenial/man5/host.conf.5.html Zeige tomtomtom also
cat /etc/host.conf
cat /etc/resolv.conf
cat /etc/hosts Gruß Stephan
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
Zeige tomtomtom also
cat /etc/host.conf
cat /etc/resolv.conf
cat /etc/hosts
cat /etc/host.conf bringt: | > # The "order" line is only used by old versions of the C library.
> order hosts,bind
> multi on
|
cat /etc/resolv.conf zeigt: | # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
search fritz.box
|
und cat /etc/hosts zeigt: | 127.0.0.1 localhost
127.0.1.1 burkhard-TUXEDO-InfinityBook-14-v2
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
|
Was sagt mir das? Gruß
Burkhard
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19527
|
Zeige noch hostname sowie dpkg -l jitsi* ls /var/lib/dpkg/info/jitsi* grep -P '^[ \t]*[^#[ \t]+' /etc/apt/sources.list /etc/apt/sources.list.d/*.list
|
Streifenschmerle
Anmeldungsdatum: 5. April 2006
Beiträge: 451
|
Hallo Burkhard, wolltest Du einen eigenen Jitsi-Server hosten? Wenn Du Jitsi einfach nur als Client nutzen willst, brauchst Du gar keine Extra-Software - ein Webbrowser (Firefox, Chromium etc.) reicht aus, um an Videochats teilzunehmen. Die Installation von jitsi-meet bzw. das Einbinden des Fremdquellen-Repository von jitsi.org macht meines Wissen nur Sinn, wenn Du tatsächlich eine eigene Jitsi-Instanz hosten willst - dafür ist das ganze gedacht. Zu Deiner Frage, wie Du die Jitsi-Pakete, die Probleme machen, wieder deinstallieren kannst: Laut dem Self-Hosting Guide von Jitsi (Sektion "Uninstall") sollte Dir mit sudo apt purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge2 geholfen sein. Bei Fehler während der Deinstallation ggf. den Befehl ein zweites Mal ausführen. Und anschließend die Fremdquelle unter /etc/apt/sources.list.d/jitsi-stable.list wieder entfernen. Viele Grüße,
Jan
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
Kellerkind_2009 schrieb: Zeige noch hostname sowie dpkg -l jitsi* ls /var/lib/dpkg/info/jitsi* grep -P '^[ \t]*[^#[ \t]+' /etc/apt/sources.list /etc/apt/sources.list.d/*.list
hostname ist: | burkhard-TUXEDO-InfinityBook-14-v2
|
dpkg -l jitsi* 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16 | Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-==============-============-============-=================================
rc jitsi 2.10.5550-1 amd64 VoIP and Instant Messaging client
rc jitsi-archive- 1.0.1 all The public key for the Jitsi pack
iU jitsi-meet 2.0.5142-1 all WebRTC JavaScript video conferenc
iF jitsi-meet-pro 1.0.4466-1 all Prosody configuration for Jitsi M
un jitsi-meet-tok <keine> <keine> (keine Beschreibung vorhanden)
iU jitsi-meet-tur 1.0.4466-1 all Configures coturn to be used with
ii jitsi-meet-web 1.0.4466-1 all WebRTC JavaScript video conferenc
ii jitsi-meet-web 1.0.4466-1 all Configuration for web serving of
rc jitsi-videobri 1126-1 amd64 WebRTC compatible Selective Forwa
ii jitsi-videobri 2.1-376-g9f1 all WebRTC compatible Selective Forwa
|
ls /var/lib/dpkg/info/jitsi* ergibt: 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35 | /var/lib/dpkg/info/jitsi-archive-keyring.list
/var/lib/dpkg/info/jitsi.list
/var/lib/dpkg/info/jitsi-meet.list
/var/lib/dpkg/info/jitsi-meet.md5sums
/var/lib/dpkg/info/jitsi-meet.postrm
/var/lib/dpkg/info/jitsi-meet-prosody.list
/var/lib/dpkg/info/jitsi-meet-prosody.md5sums
/var/lib/dpkg/info/jitsi-meet-prosody.postinst
/var/lib/dpkg/info/jitsi-meet-prosody.postrm
/var/lib/dpkg/info/jitsi-meet-prosody.templates
/var/lib/dpkg/info/jitsi-meet-turnserver.list
/var/lib/dpkg/info/jitsi-meet-turnserver.md5sums
/var/lib/dpkg/info/jitsi-meet-turnserver.postinst
/var/lib/dpkg/info/jitsi-meet-turnserver.postrm
/var/lib/dpkg/info/jitsi-meet-turnserver.templates
/var/lib/dpkg/info/jitsi-meet-web-config.config
/var/lib/dpkg/info/jitsi-meet-web-config.list
/var/lib/dpkg/info/jitsi-meet-web-config.md5sums
/var/lib/dpkg/info/jitsi-meet-web-config.postinst
/var/lib/dpkg/info/jitsi-meet-web-config.postrm
/var/lib/dpkg/info/jitsi-meet-web-config.templates
/var/lib/dpkg/info/jitsi-meet-web.list
/var/lib/dpkg/info/jitsi-meet-web.md5sums
/var/lib/dpkg/info/jitsi.postrm
/var/lib/dpkg/info/jitsi-videobridge2.conffiles
/var/lib/dpkg/info/jitsi-videobridge2.config
/var/lib/dpkg/info/jitsi-videobridge2.list
/var/lib/dpkg/info/jitsi-videobridge2.md5sums
/var/lib/dpkg/info/jitsi-videobridge2.postinst
/var/lib/dpkg/info/jitsi-videobridge2.postrm
/var/lib/dpkg/info/jitsi-videobridge2.prerm
/var/lib/dpkg/info/jitsi-videobridge2.templates
/var/lib/dpkg/info/jitsi-videobridge.list
/var/lib/dpkg/info/jitsi-videobridge.postrm
|
grep -P '^[ \t]*[^#[ \t]+' /etc/apt/sources.list /etc/apt/sources.list.d/*.list ergibt: | /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
/etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
/etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse
/etc/apt/sources.list:deb https://dl.winehq.org/wine-builds/ubuntu/ bionic main
/etc/apt/sources.list.d/graphics-tuxedo.list:deb http://graphics.tuxedocomputers.com/ubuntu bionic main
/etc/apt/sources.list.d/jitsi-stable.list:deb https://download.jitsi.org stable/
/etc/apt/sources.list.d/oibaf-tuxedo.list:deb http://oibaf.tuxedocomputers.com/ubuntu bionic main
/etc/apt/sources.list.d/opera-stable.list:deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
/etc/apt/sources.list.d/teams.list:deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
/etc/apt/sources.list.d/tuxedo-computers.list:deb http://deb.tuxedocomputers.com/ubuntu bionic main
/etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-bionic.list:deb http://ppa.launchpad.net/ubuntubudgie/backports/ubuntu bionic main
|
Gruß
Burkhard
|
Kellerkind_2009
Anmeldungsdatum: 26. November 2009
Beiträge: 19527
|
Moin Burkhard, gehe nun mal nach der Anweisung von KaiserClaudius vor und Versuche zu Deinstallieren. Falls es nach mehreren Versuchen Scheitert zeige bitte die Terminal Ausgabe. Gruß Stephan
|
Burkhard99
(Themenstarter)
Anmeldungsdatum: 2. Juli 2014
Beiträge: 31
|
Kellerkind_2009 schrieb: Moin Burkhard, gehe nun mal nach der Anweisung von KaiserClaudius vor und Versuche zu Deinstallieren. Falls es nach mehreren Versuchen Scheitert zeige bitte die Terminal Ausgabe. Gruß Stephan
Moin und vielen Dank!
Es scheint zu deinstallieren bis auf die eine Warnung ganz am Schluss | sudo apt purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge2
|
führt zu: 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194 | [sudo] Passwort für burkhard:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paket »jigasi« ist nicht installiert, wird also auch nicht entfernt.
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
coturn libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386
libdrm-radeon1:i386 libdrm2:i386 libelf1:i386 libevent-core-2.1-6
libevent-extra-2.1-6 libevent-openssl-2.1-6 libevent-pthreads-2.1-6 libfwup1
libglvnd0:i386 libhiredis0.13 libllvm9 libmysqlclient20 libpciaccess0:i386
libsane-hpaio libsensors4:i386 libx11-xcb1:i386 libxcb-dri2-0:i386
libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386
libxdamage1:i386 libxshmfence1:i386 linux-hwe-5.4-headers-5.4.0-42
linux-hwe-5.4-headers-5.4.0-45 linux-hwe-5.4-headers-5.4.0-47
linux-hwe-5.4-headers-5.4.0-48 linux-hwe-5.4-headers-5.4.0-51
linux-hwe-5.4-headers-5.4.0-52 lua-bitop lua-event lua-expat lua-filesystem
lua-sec lua-socket lua5.1 mysql-common nginx prosody python3-pexpect
python3-ptyprocess python3-renderpm python3-reportlab
python3-reportlab-accel tuxedo-keyboard-dkms
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden Pakete werden ENTFERNT:
jicofo* jitsi-meet* jitsi-meet-prosody* jitsi-meet-turnserver*
jitsi-meet-web* jitsi-meet-web-config* jitsi-videobridge2*
0 aktualisiert, 0 neu installiert, 7 zu entfernen und 5 nicht aktualisiert.
3 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 126 MB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] J
(Lese Datenbank ... 425899 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von jitsi-meet (2.0.5142-1) ...
Entfernen von jitsi-meet-turnserver (1.0.4466-1) ...
Entfernen von jitsi-meet-prosody (1.0.4466-1) ...
Entfernen von jicofo (1.0-644-1) ...
Entfernen von jitsi-meet-web (1.0.4466-1) ...
Entfernen von jitsi-meet-web-config (1.0.4466-1) ...
Entfernen von jitsi-videobridge2 (2.1-376-g9f12bfe2-1) ...
(Lese Datenbank ... 425298 Dateien und Verzeichnisse sind derzeit installiert.)
Löschen der Konfigurationsdateien von jitsi-videobridge2 (2.1-376-g9f12bfe2-1) ...
Benutzer »jvb« wird entfernt …
Fertig.
Löschen der Konfigurationsdateien von jitsi-meet (2.0.5142-1) ...
Löschen der Konfigurationsdateien von jitsi-meet-web-config (1.0.4466-1) ...
Löschen der Konfigurationsdateien von jitsi-meet-turnserver (1.0.4466-1) ...
Löschen der Konfigurationsdateien von jitsi-meet-prosody (1.0.4466-1) ...
Clearing symlinks in /etc/ssl/certs...
done.
Updating certificates in /etc/ssl/certs...
138 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
Replacing debian:ACCVRAIZ1.pem
Replacing debian:AC_RAIZ_FNMT-RCM.pem
Replacing debian:Actalis_Authentication_Root_CA.pem
Replacing debian:AffirmTrust_Commercial.pem
Replacing debian:AffirmTrust_Networking.pem
Replacing debian:AffirmTrust_Premium.pem
Replacing debian:AffirmTrust_Premium_ECC.pem
Replacing debian:Amazon_Root_CA_1.pem
Replacing debian:Amazon_Root_CA_2.pem
Replacing debian:Amazon_Root_CA_3.pem
Replacing debian:Amazon_Root_CA_4.pem
Replacing debian:Atos_TrustedRoot_2011.pem
Replacing debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
Replacing debian:Baltimore_CyberTrust_Root.pem
Replacing debian:Buypass_Class_2_Root_CA.pem
Replacing debian:Buypass_Class_3_Root_CA.pem
Replacing debian:CA_Disig_Root_R2.pem
Replacing debian:CFCA_EV_ROOT.pem
Replacing debian:COMODO_Certification_Authority.pem
Replacing debian:COMODO_ECC_Certification_Authority.pem
Replacing debian:COMODO_RSA_Certification_Authority.pem
Replacing debian:Certigna.pem
Replacing debian:Certum_Trusted_Network_CA.pem
Replacing debian:Certum_Trusted_Network_CA_2.pem
Replacing debian:Chambers_of_Commerce_Root_-_2008.pem
Replacing debian:Comodo_AAA_Services_root.pem
Replacing debian:Cybertrust_Global_Root.pem
Replacing debian:D-TRUST_Root_Class_3_CA_2_2009.pem
Replacing debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
Replacing debian:DST_Root_CA_X3.pem
Replacing debian:DigiCert_Assured_ID_Root_CA.pem
Replacing debian:DigiCert_Assured_ID_Root_G2.pem
Replacing debian:DigiCert_Assured_ID_Root_G3.pem
Replacing debian:DigiCert_Global_Root_CA.pem
Replacing debian:DigiCert_Global_Root_G2.pem
Replacing debian:DigiCert_Global_Root_G3.pem
Replacing debian:DigiCert_High_Assurance_EV_Root_CA.pem
Replacing debian:DigiCert_Trusted_Root_G4.pem
Replacing debian:E-Tugra_Certification_Authority.pem
Replacing debian:EC-ACC.pem
Replacing debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
Replacing debian:Entrust_Root_Certification_Authority.pem
Replacing debian:Entrust_Root_Certification_Authority_-_EC1.pem
Replacing debian:Entrust_Root_Certification_Authority_-_G2.pem
Replacing debian:GDCA_TrustAUTH_R5_ROOT.pem
Replacing debian:GeoTrust_Global_CA.pem
Replacing debian:GeoTrust_Primary_Certification_Authority.pem
Replacing debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
Replacing debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
Replacing debian:GeoTrust_Universal_CA.pem
Replacing debian:GeoTrust_Universal_CA_2.pem
Replacing debian:GlobalSign_ECC_Root_CA_-_R4.pem
Replacing debian:GlobalSign_ECC_Root_CA_-_R5.pem
Replacing debian:GlobalSign_Root_CA.pem
Replacing debian:GlobalSign_Root_CA_-_R2.pem
Replacing debian:GlobalSign_Root_CA_-_R3.pem
Replacing debian:Global_Chambersign_Root_-_2008.pem
Replacing debian:Go_Daddy_Class_2_CA.pem
Replacing debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
Replacing debian:Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.pem
Replacing debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem
Replacing debian:Hellenic_Academic_and_Research_Institutions_RootCA_2015.pem
Replacing debian:Hongkong_Post_Root_CA_1.pem
Replacing debian:ISRG_Root_X1.pem
Replacing debian:IdenTrust_Commercial_Root_CA_1.pem
Replacing debian:IdenTrust_Public_Sector_Root_CA_1.pem
Replacing debian:Izenpe.com.pem
Replacing debian:Microsec_e-Szigno_Root_CA_2009.pem
Replacing debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
Replacing debian:Network_Solutions_Certificate_Authority.pem
Replacing debian:OISTE_WISeKey_Global_Root_GB_CA.pem
Replacing debian:QuoVadis_Root_CA.pem
Replacing debian:QuoVadis_Root_CA_1_G3.pem
Replacing debian:QuoVadis_Root_CA_2.pem
Replacing debian:QuoVadis_Root_CA_2_G3.pem
Replacing debian:QuoVadis_Root_CA_3.pem
Replacing debian:QuoVadis_Root_CA_3_G3.pem
Replacing debian:SSL.com_EV_Root_Certification_Authority_ECC.pem
Replacing debian:SSL.com_EV_Root_Certification_Authority_RSA_R2.pem
Replacing debian:SSL.com_Root_Certification_Authority_ECC.pem
Replacing debian:SSL.com_Root_Certification_Authority_RSA.pem
Replacing debian:SZAFIR_ROOT_CA2.pem
Replacing debian:SecureSign_RootCA11.pem
Replacing debian:SecureTrust_CA.pem
Replacing debian:Secure_Global_CA.pem
Replacing debian:Security_Communication_RootCA2.pem
Replacing debian:Security_Communication_Root_CA.pem
Replacing debian:Sonera_Class_2_Root_CA.pem
Replacing debian:Staat_der_Nederlanden_EV_Root_CA.pem
Replacing debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
Replacing debian:Starfield_Class_2_CA.pem
Replacing debian:Starfield_Root_Certificate_Authority_-_G2.pem
Replacing debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
Replacing debian:SwissSign_Gold_CA_-_G2.pem
Replacing debian:SwissSign_Silver_CA_-_G2.pem
Replacing debian:T-TeleSec_GlobalRoot_Class_2.pem
Replacing debian:T-TeleSec_GlobalRoot_Class_3.pem
Replacing debian:TUBITAK_Kamu_SM_SSL_Kok_Sertifikasi_-_Surum_1.pem
Replacing debian:TWCA_Global_Root_CA.pem
Replacing debian:TWCA_Root_Certification_Authority.pem
Replacing debian:TeliaSonera_Root_CA_v1.pem
Replacing debian:TrustCor_ECA-1.pem
Replacing debian:TrustCor_RootCert_CA-1.pem
Replacing debian:TrustCor_RootCert_CA-2.pem
Replacing debian:Trustis_FPS_Root_CA.pem
Replacing debian:USERTrust_ECC_Certification_Authority.pem
Replacing debian:USERTrust_RSA_Certification_Authority.pem
Replacing debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem
Replacing debian:VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.pem
Replacing debian:VeriSign_Universal_Root_Certification_Authority.pem
Replacing debian:XRamp_Global_CA_Root.pem
Replacing debian:certSIGN_ROOT_CA.pem
Replacing debian:ePKI_Root_Certification_Authority.pem
Replacing debian:thawte_Primary_Root_CA.pem
Replacing debian:thawte_Primary_Root_CA_-_G2.pem
Replacing debian:thawte_Primary_Root_CA_-_G3.pem
Adding debian:GlobalSign_Root_CA_-_R6.pem
Adding debian:OISTE_WISeKey_Global_Root_GC_CA.pem
Adding debian:Certigna_Root_CA.pem
Adding debian:certSIGN_Root_CA_G2.pem
Adding debian:emSign_ECC_Root_CA_-_C3.pem
Adding debian:emSign_ECC_Root_CA_-_G3.pem
Adding debian:emSign_Root_CA_-_C1.pem
Adding debian:emSign_Root_CA_-_G1.pem
Adding debian:Entrust_Root_Certification_Authority_-_G4.pem
Adding debian:e-Szigno_Root_CA_2017.pem
Adding debian:GTS_Root_R1.pem
Adding debian:GTS_Root_R2.pem
Adding debian:GTS_Root_R3.pem
Adding debian:GTS_Root_R4.pem
Adding debian:Hongkong_Post_Root_CA_3.pem
Adding debian:Microsoft_ECC_Root_Certificate_Authority_2017.pem
Adding debian:Microsoft_RSA_Root_Certificate_Authority_2017.pem
Adding debian:Trustwave_Global_Certification_Authority.pem
Adding debian:Trustwave_Global_ECC_P256_Certification_Authority.pem
Adding debian:Trustwave_Global_ECC_P384_Certification_Authority.pem
Adding debian:UCA_Extended_Validation_Root.pem
Adding debian:UCA_Global_G2_Root.pem
done.
done.
Löschen der Konfigurationsdateien von jicofo (1.0-644-1) ...
Benutzer »jicofo« wird entfernt …
Fertig.
dpkg: Warnung: Während Entfernens von jicofo ist Verzeichnis »/etc/jitsi/jicofo« nicht leer, wird daher nicht gelöscht
Trigger für systemd (237-3ubuntu10.43) werden verarbeitet ...
|
Oder muss ich auf die Warnung noch irgendwie reagieren? Gruss
Burkhard
|