Hi,
Preface this with - I do not have good *NIX skills & am out of my depth. Appreciate some help if anyone has time
Background
- Long time Media Center user on Windows. Have been running on Raspberry Pi without issues - but dependent on articles by mwilliams, awesome donkey and hilton to get up and running
- I have built a FreeNAS Server. To summarise my set-up
- Freenas 9.10 running on an Intel Xeon machine
- VirtualBox (phpVirtualBox) installed in a Jail
- Debian 8 guest built within VirtualBox
- Debian guest has access to the NAS filesystem (via VirtualBox Guest Addins)
- JRiver MediaCenter 22 installed on Debian guest
- JRiver working perfectly. other JRiver instances, DLNA devices and JRemote all configured to access the library installed on the VM. Very happy household
When I need to access JRiver for tagging or other admin work I do so via a VNC client (TightVNC Viewer) on a Windows machine. The VNC client is using the IP address allocated to VirtualBox installation and the port allocated for the debian guest within VirtualBox (eg 192.168.2.150:9000). This works but the screen resolution is poor & it takes a lot of time to do things.
I thought about installing vncserver on the debian VM and accessing it directly (instead of via VirtualBox). So
- Installed vncserver on the Debian guest
- Started vncserver (& set the password)
- TightVNC Viewer successfully connects to debian guest (eg 192.168.2.99:1) Happy with the screen resolution
- Unable to start MediaCenter. syslog shows a segfault (see below)
Jan 17 21:58:20 deb64vm001 kernel: [ 105.948190] mediacenter22[1358]: segfault at 10 ip 0000000000eb1799 sp 00007fff713075a0 error 4 in mediacenter22[400000+1185000]
I'm at a bit of a loss at what to check / look at. I'm guessing I have setup vncserver incorrectly, but not skilled enough to progress further. Any thoughts?
Appreciate your help & sorry for the complex setup
Cheers,
Steve