Hello!
As i see there in https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi-meet-prosody.postinst
if [ ! -f /var/lib/prosody/$JVB_HOSTNAME.crt ]; then
HOST="$( (hostname -s; echo localhost) | head -n 1)"
DOMAIN="$( (hostname -d; echo localdomain) | head -n 1)"
openssl req -new -newkey rsa:4096 -days 365 -nodes -x509 -subj \
“/O=$DOMAIN/OU=$HOST/CN=$JVB_HOSTNAME/emailAddress=webmaster@$HOST.$DOMAIN” \
-keyout /var/lib/prosody/$JVB_HOSTNAME.key -out /var/lib
fi
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
invoke-rc.d prosody restart
At this line: -keyout /var/lib/prosody/$JVB_HOSTNAME.key -out /var/lib
Should be: -keyout /var/lib/prosody/$JVB_HOSTNAME.key -out /var/lib/prosody/$JVB_HOSTNAME.crt
Thanks.
···
13.08.2014, 09:53, “Damian Minkov” damencho@jitsi.org:
Hi,
could you please check the folder /var/lib/prosody/, are all folders
existing and writable in that path, seems a problem creating the key
file in that folder.
Regards
damencho
On Tue, Aug 12, 2014 at 10:15 PM, v k v.karm@yandex.ru wrote:
Hello! Thanks for help. There is a new error…
All comands executes under sudo
Preparing to unpack …/jitsi-meet-prosody_1.0.1-50_all.deb …
Unpacking jitsi-meet-prosody (1.0.1-50) …
Selecting previously unselected package jitsi-meet.
Preparing to unpack …/jitsi-meet_1.0.1-50_all.deb …
Unpacking jitsi-meet (1.0.1-50) …
Selecting previously unselected package icedtea-7-jre-jamvm:amd64.
Preparing to unpack …/icedtea-7-jre-jamvm_7u55-2.4.7-1ubuntu1_amd64.deb …
Unpacking icedtea-7-jre-jamvm:amd64 (7u55-2.4.7-1ubuntu1) …
Setting up libjbig0:amd64 (2.0-2ubuntu4.1) …
Setting up libtiff5:amd64 (4.0.3-7ubuntu0.1) …
Setting up libxpm4:amd64 (1:3.5.10-1) …
Setting up libgd3:amd64 (2.1.0-3) …
Setting up libxslt1.1:amd64 (1.1.28-2build1) …
Setting up lua-sec:amd64 (0.5-1) …
Setting up nginx-common (1.4.6-1ubuntu3) …
Setting up prosody-modules-otalk (1.0-2) …
Setting up icedtea-7-jre-jamvm:amd64 (7u55-2.4.7-1ubuntu1) …
Processing triggers for ureadahead (0.100.0-16) …
Processing triggers for ufw (0.34~rc-0ubuntu2) …
Setting up nginx-core (1.4.6-1ubuntu3) …
Setting up nginx (1.4.6-1ubuntu3) …
Setting up jitsi-meet-prosody (1.0.1-50) …
Generating a 4096 bit RSA private key
…++
…++
writing new private key to ‘/var/lib/prosody/jitmeet.ares.com.key’
/var/lib: Is a directory
140516848748192:error:02001015:system library:fopen:Is a directory:bss_file.c:398:fopen(’/var/lib’,‘w’)
140516848748192:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
dpkg: error processing package jitsi-meet-prosody (–configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for libc-bin (2.19-0ubuntu6.1) ...
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)
12.08.2014, 19:08, “Damian Minkov” damencho@jitsi.org:
Hi,
the package has been updated, could you please update and see does it
solves the problem for you.
Thanks
damencho
On Tue, Aug 12, 2014 at 1:54 PM, v k v.karm@yandex.ru wrote:
Hello.
When i trying to install jitsi-meet, there is errors:
Ubuntu 14.04 x64
Setting up libtiff5:amd64 (4.0.3-7ubuntu0.1) …
Setting up libxpm4:amd64 (1:3.5.10-1) …
Setting up libgd3:amd64 (2.1.0-3) …
Setting up libxslt1.1:amd64 (1.1.28-2build1) …
Setting up lua-sec:amd64 (0.5-1) …
Setting up nginx-common (1.4.6-1ubuntu3) …
Setting up prosody-modules-otalk (1.0-2) …
Setting up icedtea-7-jre-jamvm:amd64 (7u55-2.4.7-1ubuntu1) …
Processing triggers for ureadahead (0.100.0-16) …
Processing triggers for ufw (0.34~rc-0ubuntu2) …
Setting up nginx-core (1.4.6-1ubuntu3) …
Setting up nginx (1.4.6-1ubuntu3) …
Setting up jitsi-meet-prosody (1.0.1-49) …
gzip: /usr/share/doc/jitsi-meet-prosody/prosody.cfg.lua-jvb.example.gz: No such file or directory
dpkg: error processing package jitsi-meet-prosody (–configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of jitsi-meet:
jitsi-meet depends on jitsi-meet-prosody; however:
Package jitsi-meet-prosody is not configured yet.
dpkg: error processing package jitsi-meet (–configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for libc-bin (2.19-0ubuntu6.1) ...
Errors were encountered while processing:
jitsi-meet-prosody
jitsi-meet
E: Sub-process /usr/bin/dpkg returned an error code (1)
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users
