Hi,
sorry for showing up late, but these days I am most of my time about 200 miles afar from my server and don't want to complicate the installation by remote accesses. So, please don't wonder if I need days to fiddle around with the installation. First of all thanks for your support! I am still interested in a solution and will do my very best to answer your questions.
My installation results in quite similar error messages like given by you, cf. my first entry in this thread. Instead of an incomplete screenshot I repeat the relevant installation messages below. But, since you pointed out that missing access rights might be the problem, I've also checked the results on my server. And even though the installation routine logs in as user "root", the installed directory belongs to my second admin account "EDJ" in group "hdusers", as I have listed below as well. I've tried the usual commands to correct that (chown, chgrp, chmod) after the installation, but it seems to be too late for that. Also, uninstalling the previous twonky version, deleting the entire directory in advance and setting up them manually with users/ groups and access rights assigned correctly before installing the software doesn’t help. Even worse, user EDJ has exactly the same rights as root, so I do neither understand what went wrong during the installation nor why any access problems should remain. May be that I am following the wrong track, but as of now this is the only hint about the problem I've found out.
Any ideas how to solve that?
Regards
Jurgen
------------------
Log from NASSetup:
Installing from 192.168.2.3 (PC) to 192.168.2.2 (LINKSTATIONLIVE)
[…]
EDJH_Server login:
root
Password:
No mail.
root@EDJH_Server:~#
sh /mnt/disk1/share/twonky/nas-uninstaller /mnt/disk1/sha
</disk1/share/twonky/nas-uninstaller /mnt/disk1/shar 0x08 0x08 0x08 0x08 0x08
try to kill all old stuff, ignore error messages that might occur …
killall: mediaserver: no process killed
killall: twonkymusic: no process killed
kill: usage kill [s sigspec | -n signum | -sigspec] pid | jobspec … or kill –l [sigspec]
1
2
3
killall: twonkymedia: no process killed
kill: usage kill [s sigspec | -n signum | -sigspec] pid | jobspec … or kill –l [sigspec]
killall: twonkymusic: no process killed
kill: usage kill [s sigspec | -n signum | -sigspec] pid | jobspec … or kill –l [sigspec]
killall: twonkymediaserver: no process killed
killall: twonkymusicserver: no process killed
seems that all old stuff has been removed now
nas-uninstaller exit
root@edjh_Server:~#
sh
/mnt/disk1/share/twonky/nas-installer 192.168.2.3:9000
</disk1/share/twonky/nas-installer 192.168.2.3:9000 0x08 0x08 0x08 0x08 0x0
<staller 192.168.2.3:9000 /mnt/disk1/share/twonky /e 0x08 0x08 0x08 0x08 0x0
<mnt/disk1/share/twonky /etc/init.d/twonky twonkymed 0x08 0x08 0x08 0x08 0x
grep: twonkymedia-server-default.ini: No such file or directory
grep: twonkymedia-server-default.ini: No such file or directory
grep: twonkymedia-server-default.ini: No such file or directory
grep: twonkymedia-server-default.ini: No such file or directory
grep: twonkymedia-server-default.ini: No such file or directory
grep: twonkymedia-server-default.ini: No such file or directory
cp: cannot stat '/mnt/disk1/share/twonky/twonkymedia-server-default.ini': No such file or directo
root@EDJH_Server:~#
starting twonkymedia
sh
The server has been started.
The server is installed at /mnt/disk1/share/twonky on your LINKSTATIONLIVE.
The autostart script at /etc/init.d/twonky on your LINKSTATIONLIVE.
The web interface is at
http://192.168.2.2:9000/configpage/index.html
------------------
Results on the server:
root@EDJH_Server:~# ps - w | grep twonky
13139 root 1696 S /mnt/disk1/share/twonky/twonkymedia
16739 root Z [twonkymediaserver]
16797 root 3368 R grep twonky
root@EDJH_Server:~# ls -al /mnt/disk1/share/twonky
drwxrwxrwx 5 root root 153 May 30 10:42 .
[...]
-rwxrwxrwx 1 EDJ hdusers 5332 Feb 16 18:24 /mnt/disk1/share/twonky/twonkymedia