9.3 How to build and install LMS 7.9 from scratch

Status
Not open for further replies.

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
Hi,

This is about building and installing the LMS 7.9. inside a jail.

It supersedes the procedure described in
https://forums.freenas.org/index.ph...8-7-9-for-freenas-9-2-1-6-from-scratch.22359/

Prerequisites:
- A running 9.3 installation
- Willingness to do things on the CLI

I've used two jails here:
- A temporary jail for building, called build_jail in this howto
- The "real" jail where LMS is to be run, called install_jail in this howto

The referred versions of various packages have been current on 26th January 2015. They will change in the future.

- Create the install_jail (VIMAGE checked)
- Create the build_jail (VIMAGE checked)
- Make sure both jails are running

Inside build_jail:
Code:
pkg update
pkg upgrade

pkg install bash-4.3.33
pkg install gmake-4.1_1
pkg install rsync-3.1.1_3
pkg install nasm-2.11.06,1
pkg install wget-1.16
pkg install libgd-2.1.0_5,1


Ignore the fdescfs message bash complains about.
Code:
mkdir /tmp/somedir
cd /tmp/somedir


From http://downloads.slimdevices.com/nightly/index.php?ver=7.9 download "Logitech Media Server: Unix Tarball (for Perl 5.8-5.18, i386, x86_64, i386 FreeBSD, ARM EABI, PowerPC)" (the build number may be different now):
Code:
wget http://downloads.slimdevices.com/nightly/7.9/sc/17d0715/logitechmediaserver-7.9.0-1421917265.tgz
tar xf logitechmediaserver-7.9.0-1421917265.tgz


Get the build sources:
Code:
git clone https://github.com/Logitech/slimserver-vendor -b public/7.9


The buildme.sh script does not require modifications anymore, so build the whole thing:
Code:
cd /tmp/somedir/slimserver-vendor/CPAN
./buildme.sh | tee /tmp/somedir/buildme.sh.log


The build output is logged in /tmp/somedir/buildme.sh.log so it might be a good idea to check it for errors or warnings...

Copy the build into the downloaded LMS package:
Code:
cd /tmp/somedir/logitechmediaserver-7.9.0-1421917265/CPAN/arch/5.18
cp -Rp /tmp/somedir/slimserver-vendor/CPAN/build/arch/5.18/amd64-freebsd-thread-multi .


As of 26.01.2015 the used perl package is 5.18 (This might change to 5.20 one day). In case the build succeeded under a different perl version, do not copy it under the 5.18 branch, but under the branch of the version you were using...

Remove the other build targets for the used perl perl version (5.18 here):
Code:
cd /tmp/somedir/logitechmediaserver-7.9.0-1421917265/CPAN/arch/5.18
rm -rf i386-linux-thread-multi
rm -rf i386-linux-thread-multi-64int
rm -rf x86_64-linux-thread-multi


Remove the unused perl branches:
Code:
cd /tmp/somedir/logitechmediaserver-7.9.0-1421917265/CPAN/arch
rm -rf 5.8
rm -rf 5.10
rm -rf 5.12
rm -rf 5.14
rm -rf 5.16
rm -rf 5.20


Tar the modified LMS package:
Code:
cd /tmp/somedir
tar cf logitechmediaserver-7.9.0-1421917265_with_fbsd.tar logitechmediaserver-7.9.0-1421917265


Exit build_jail

Copy the tarball into the install_jail:
Code:
cp /path/to/build_jail/tmp/somedir/logitechmediaserver-7.9.0-1421917265_with_fbsd.tar /path/to/install_jail/tmp


Inside install_jail:
Code:
pkg update
pkg upgrade


Create a user and group under which the LMS-process will be running. I use lms with id 30001. If you change the user or group name do not forget to change it in the startup script (see below), too.
Code:
pw groupadd -n lms -g 30001
pw useradd -n lms -u 30001 -g lms -s /usr/sbin/nologin -c "Logitech Media Server" -d /nonexistent


Create the installation directory:
Code:
mkdir /usr/local/lms


Extract the tarball from the jails /tmp directory into the installation directory and copy the files around:
Code:
tar xf /tmp/logitechmediaserver-7.9.0-1421917265_with_fbsd.tar -C /usr/local/lms
mv /usr/local/lms/logitechmediaserver-7.9.0-1421917265/* /usr/local/lms
rmdir /usr/local/lms/logitechmediaserver-7.9.0-1421917265


Change owner and group to lms:
Code:
chown -R lms:lms /usr/local/lms


-------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------
From here on the howto has been modified. You can still use the steps below, but I would suggest using this post.
-------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------

Create the startup file /usr/local/etc/rc.d/lms with the following content:
Code:
#!/bin/sh
#
# This script is a slightly modified version with hardcoded values of:
# $FreeBSD: branches/RELENG_9_2_0/audio/squeezeboxserver/files/squeezeboxserver.in 302141 2012-08-05 23:19:36Z dougb $
#

# PROVIDE: lms
# REQUIRE: LOGIN
# KEYWORD: shutdown

#
# Add the following lines to /etc/rc.conf to enable lms:
#
#lms_enable="YES"
#

. /etc/rc.subr

name=lms
start_precmd="lms_start_precmd"
stop_postcmd="lms_stop_postcmd"
rcvar=lms_enable

command=/usr/local/lms/slimserver.pl
command_interpreter=/usr/bin/perl
pidfile=/var/run/${name}/${name}.pid
logdir=/var/log/${name}
statedir=/var/db/${name}
cachedir=${statedir}/cache
prefsdir=${statedir}/prefs
playlistdir=${statedir}/playlists
charset=UTF-8
u=lms
g=lms
command_args="--daemon --pidfile=${pidfile} --logdir=${logdir} --cachedir=${cachedir} --prefsdir=${prefsdir} --charset=${charset}"
lms_user=${u}
lms_group=${g}

lms_start_precmd()
{
    # This is stuff is here and not in pkg-install because
    # /var/run may be destroyed at any time and we've had issues
    # with permissions on the various directories under /var getting
    # screwed up in the past.

    mkdir -p /var/run/${name}
    chown -RH ${u}:${g} /var/run/${name}

    mkdir -p ${logdir}
    chown -RH ${u}:${g} ${logdir}

    mkdir -p ${statedir}
    mkdir -p ${cachedir}
    mkdir -p ${prefsdir}
    mkdir -p ${playlistdir}
    chown -RH ${u}:${g} ${statedir}
    export LC_CTYPE=en_US.UTF-8
}

lms_stop_postcmd()
{
    pids=`pgrep -u $u`
    if [ -n "${pids}" ]; then
        sleep 1
        kill $pids > /dev/null 2>&1
    fi
    pids=`pgrep -u $u`
    if [ -n "${pids}" ]; then
        wait_for_pids $pids
    fi
}

load_rc_config ${name}

lms_enable=${lms_enable:-"NO"}
lms_flags=${lms_flags:-""}

run_rc_command "$1"


FYI: The startup script uses command line parameters to set the
* prefs
* cache
* (playlists)
* log
directories below /var, i.e. it creates the directories and sets the permissions, so that
the lms process (running as user lms) can use them. Unfortunatelly there is no parameter for
the playlists directory, but one can set it up during the initial setup in the web interface.

Finally set the owner and permissions of the startup script, and make the lms service start during jail startup:
Code:
chown root:wheel /usr/local/etc/rc.d/lms
chmod 555 /usr/local/etc/rc.d/lms
echo 'lms_enable="YES"' >> /etc/rc.conf
 
Last edited:

mrMuppet

Contributor
Joined
Mar 14, 2014
Messages
192
After i copied my old Prefs dir (like i did it with every update before) i get an error in server.log:
Code:
[15-02-05 21:46:41.2323] Carp::Clan::__ANON__ (214) Warning: Carp::Clan::__ANON__(): Carp::Clan::__ANON__(): DBI Connection failed: DBI connect('dbname=/usr/local/lms/Cache/library.db','slimserver',...) failed: unable to open database file at /usr/local/lms/CPAN/DBIx/Class/Storage/DBI.pm line 999.


What can i do?

Edit: [SOLVED] I changed the path to Cache-dir in my Server-prefs. now its working!
 
Last edited:

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
@mrMuppet:
Thanks, I've corrected the typo.

Regarding your cache-dir issue, "my" solution uses the startup script to configure (and create) the directories.
You ran into the above issue because your configured directory /usr/local/lms/Cache didn't exist.
Maybe you should check whether the other dirs under /var/db/lms are being used correctly....

rw
 

Levissy

Cadet
Joined
Jan 25, 2015
Messages
9
@Roger Wilco

Hello Roger

I followed your guide precisely step-by-step ...
...and finally restart may freenas (9.3) and I go to the 'install_jail' ip:9000 in the chrome and I see this: this webpage is not available
Please help for me. What could be the reason?
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
Hi,

what does the LMS log file (/var/log/lms/server.log) in the jail say?

Is there any output if you stop and start LMS manually?
In the jail:
Code:
service lms stop (in case lms is not running, this will output that, erm, LMS is not running...)
service lms start
 

Levissy

Cadet
Joined
Jan 25, 2015
Messages
9
root@lms_1:/ # service lms stop
env: /usr/local/etc/rc.d/lms: No such file or directory

"Create the startup file /usr/local/etc/rc.d/lms with the following content:"
re: I create a file,,, FILENAME: lms (no extension) in the /usr/local/etc/rc.d/ dir with 'Code (text)' content
Here is my fault?
(I don't find server.log in the/var/log/lms/,,, I do not have /lms/ library)
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
Yes, you need to create a startup script called lms in the directory /usr/local/etc/rc.d/ (in the jail).
This file together with the lms_enable="YES" in /etc/rc.conf starts up the LMS service when the jail is started.

So copy the content as is into the lms file, check whether you've really done all described steps (it's you who has said that you had followed the guide precisely step-by-step :) ) and try to start the service manually (service lms start)

Right now you do not have the mentioned log file, as the log directory (/var/log/lms) is created during the first run of the startup script.
 

Levissy

Cadet
Joined
Jan 25, 2015
Messages
9
Ok , I found one fault. I Bad procedure created the lms file. It's okay yet, but now:

root@lms_1:/usr/local/etc # service lms start
Starting lms.
The following modules failed to load: DBI EV XML::Parser::Expat HTML::Parser JSO
N::XS Digest::SHA1 YAML::XS Sub::Name

*******

NOTE:

If you're running some unsupported Linux/Unix platform, please use the buildme.s
h
script located here:

https://github.com/Logitech/slimserver-vendor/tree/public/7.9/CPAN

If 7.9 is outdated by the time you read this, Replace "7.9" with the major versi
on
You should never need to do this if you're on Windows or Mac OSX. If the install
ers
don't work for you, ask for help and/or report a bug.

*******
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
@Levissy

What Perl version do you have inside the jail?
Code:
perl -v
 

Levissy

Cadet
Joined
Jan 25, 2015
Messages
9
This is perl 5, version 18, subversion 4 (v5.18.4) built for amd64-freebsd-threa
d-multi
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
@Levissy

Hm,

your Perl cannot load those modules. Let's stick with the module DBI for now.

LMS things work this way:
During LMS startup (via the /usr/local/lms/slimserver.pl script) the script sets the PERL5LIB environment variable.
Perl uses this variable for paths of additional module repositories.

FYI, to see where perl looks for modules by default, type
Code:
perl -V

The "V" is capital.


Let's do manually what /usr/local/lms/slimserver.pl does:
Do the following in your install_jail (that's the one we are talking about all the time, aren't we?):
Code:
perl
use DBI;


You should get errors, that the module couldn't be loaded.

Now set PERL5LIB to /usr/local/lms/CPAN/arch/5.18/. That's the path of the module repository LMS wants to use (in case you did all steps correctly, and things haven't changed since I've written the guide).

In csh do
Code:
setenv PERL5LIB /usr/local/lms/CPAN/arch/5.18/


In bash do
Code:
export PERL5LIB=/usr/local/lms/CPAN/arch/5.18/


perl -V should now show the new repository path too, and

Code:
perl
use DBI;


should load the module (i.e. show no errors).
This will probably not work for you, as LMS would load fine otherwise...
 

Shakies

Cadet
Joined
Feb 17, 2015
Messages
1
Hi Roger,

Thank you very much for your clear and concise installation guide for LMS!

Got everything up and running and enjoying the music on my new Freenas box.

Regards,

Shakies
 

Giant Robot

Cadet
Joined
Feb 28, 2015
Messages
1
Just signed up to say thanks for this very well put together guide as well. The only change I had to make (other than finding the current build number for logitechmediaserver-7.9.0) was that the only available version of nasm is now this:
Code:
pkg install nasm-2.11.08,1


Also, maybe this is common knowledge, but don't try making a jail with a space in the name. It prevented any of my jails from opening shells through the web UI, and I had to go to the CLI to delete the bad jail (even after deleting it from the web UI), after which everything went smoothly.
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
@Shakies
@Giant Robot
Hi,
happy to hear that the guide works for others, too :)

Actually I am not happy with the startup script (/usr/local/etc/rc.d/lms) anymore - the user configurable parameters should go into /etc/rc.conf instead of having to modify variables inside the script.
I hope I can post an updated version soon...

Secondly, as there is no jail-update-mechanism (yet?) I think the following configuration will make future updates quite painless:
- I have the audio files mounted into the jail through nullfs (configured the UI Jails -> Storage, I use /mnt/audio inside the jail (readonly storage))
- The "dynamic lms data" (cache, prefs, playlists) is also on a dataset mounted into the jail via Jails -> Storage (this one needs write access). I use /mnt/lmsdata inside the jail.

So whenever the jail needs to be updated, I'll simply
- create a temporary jail and build lms in there
- delete the two Jail Storages
- delete the current lms jail and create a new one (this is actually the "update")
- install the lms build in the new jail
- Create the two Jail Storages
- update the /etc/rc.conf

...and things should be working again...

This is actually the same for Plex (which has a quite nicer startup-script....)

bye,
rw
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
This is an update on the howto. Do everything as written in the original post until it tells you to do it the following way.

Create the startup file /usr/local/etc/rc.d/lms with the following content:
Code:
#!/bin/sh

# This script is a modified version of:
# $FreeBSD: branches/RELENG_9_2_0/audio/squeezeboxserver/files/squeezeboxserver.in 302141 2012-08-05 23:19:36Z dougb $

# PROVIDE: lms
# REQUIRE: LOGIN
# KEYWORD: shutdown

# Add the following lines to /etc/rc.conf to enable lms on startup:
# lms_enable="YES"

# Optional configuration parameters:
# Directory where lms writes it's logs to.
# lms_logdir="/var/log/lms"
#
# Directory where lms stores it's cache files.
# lms_cachedir="/var/db/lms/cache"
#
# Directory where lms stores it's configuration.
# lms_prefsdir="/var/db/lms/prefs"
#
# Directory where lms stores the playlists. THIS NEEDS TO BE CONFIGURED THROUGH THE UI.
# lms_playlistdir="/var/db/lms/playlists"
#
# Additional parameters, e.g. "--noimage --novideo"
# lms_flags=""
#
# The charset lms uses.
# lms_charset="UTF-8"
#
# The LC_CTYPE envvar which is necessary to get rid of the warning
# """
# Your locale was detected as C, you may have problems with non-Latin filenames.
# Consider changing your LANG variable to the correct locale, i.e. en_US.utf8.
# """
# See https://forums.freenas.org/index.php?threads/logitech-media-server-for-freenas-9-2-1-1.19044/page-3#post-132872 
# lms_lc_ctype="en_US.UTF.8"

. /etc/rc.subr

name=lms
rcvar=lms_enable

pidfile=/var/run/${name}/${name}.pid
lms_user=lms
lms_group=lms

load_rc_config ${name}

: ${lms_enable="NO"}
: ${lms_logdir="/var/log/${name}"}
: ${lms_cachedir="/var/db/${name}/cache"}
: ${lms_prefsdir="/var/db/${name}/prefs"}
: ${lms_playlistdir="/var/db/${name}/playlists"}
: ${lms_flags=""}
: ${lms_charset="UTF-8"}
: ${lms_lc_ctype="en_US.UTF-8"}

command_interpreter=/usr/bin/perl
command=/usr/local/lms/slimserver.pl
command_args="\
--daemon \
--pidfile=${pidfile} \
--logdir=${lms_logdir} \
--cachedir=${lms_cachedir} \
--prefsdir=${lms_prefsdir} \
--charset=${lms_charset} \
${lms_flags}"

start_precmd="lms_start_precmd"
stop_postcmd="lms_stop_postcmd"

lms_start_precmd()
{
    export LC_CTYPE="${lms_lc_ctype}"

    if [ ! -d "${pidfile%/*}" ]; then   
        install -d -o ${lms_user} -g ${lms_group} ${pidfile%/*};
    fi

    if [ ! -d "${lms_logdir}" ]; then
        install -d -o ${lms_user} -g ${lms_group} "${lms_logdir}";
    fi

    if [ ! -d "${lms_cachedir}" ]; then
        install -d -o ${lms_user} -g ${lms_group} "${lms_cachedir}";
    fi

    if [ ! -d "${lms_prefsdir}" ]; then
        install -d -o ${lms_user} -g ${lms_group} "${lms_prefsdir}";
    fi

    if [ ! -d "${lms_playlistdir}" ]; then
        install -d -o ${lms_user} -g ${lms_group} "${lms_playlistdir}";
    fi
}

lms_stop_postcmd()
{
    pids=`pgrep -u ${lms_user}`
    if [ -n "${pids}" ]; then
        sleep 1
        kill $pids > /dev/null 2>&1
    fi
    pids=`pgrep -u ${lms_user}`
    if [ -n "${pids}" ]; then
        wait_for_pids $pids
    fi
}

run_rc_command "$1"


Set the owner and permissions of the startup script:
Code:
chown root:wheel /usr/local/etc/rc.d/lms
chmod 555 /usr/local/etc/rc.d/lms


Enable automatic start of LMS:
Code:
echo 'lms_enable="YES"' >> /etc/rc.conf


The startup script offers the following optional configuration parameters which can be set through /etc/rc.conf:
Code:
lms_logdir
lms_cachedir
lms_prefsdir
lms_playlistdir
lms_flags
lms_charset
lms_lc_ctype


Some of the parameters define directories, which will be created during the first invocation in case they do not exist.
The ownership of the created directories will be set to user lms and group lms.

The parameter lms_playlistdir is not passed to LMS and will create the configured directory only. In order to use the directory for playlists, it needs to be configured through the LMS WebUI.

The parameter lms_flags is used to pass arbitrary parameters to LMS (search the sources or the internet).

The default values of the optional parameters are defined in the startup script above.


Now LMS should be working....
From here on it is just FYI (do whatever you want). I have set my installation this way:

- I use LMS for audio only and all files are on the dataset zfspool/audio (this is NOT inside the jail)
- This unix dataset has 755 permissions, owner+group is user1
- The audio files in there have 644 permissions, owner+group is user1
- For LMS' own data I have the unix dataset zfspool/data_lms, the permissions are 755, owner+group is root:wheel (again not inside the jail)
- I have two jail storages:
- From /mnt/zfspool/audio to /mnt/audio inside the jail (readonly (not necessary, as the file permissions are readonly already))
- From /mnt/zfspool/data_lms to /mnt/data_lms inside the jail (read/write)
- My /etc/rc.conf inside the jail looks like this:
Code:
lms_enable="YES"
lms_cachedir="/mnt/data_lms/cache"
lms_prefsdir="/mnt/data_lms/prefs"
lms_playlistdir="/mnt/data_lms/playlists"
lms_flags="--noimage --novideo --noupnp -notranscoding"


The naming data_lms is quite handy as I also have Plex and PostgreSQL configured in a similar way (data_plex and data_postgres) - all data-datasets are listed next to each other in the UI or CLI.

IMO it is also a good idea to pull as much data out of the jail - I do not want to backup the whole jail - only the data-dataset.
Future updates of the jail will be easy - I can delete the whole jail, create a new one, install the application from packages (or manually like LMS), copy over the /etc/rc.conf file, and it will work again.
And finally backups can be done quite easy - the readonly datasets can use regular snapshot/replication. For the data-datasets one should shutdown the service first and snapshot/replicate manually from the CLI. Yep, this is ugly yet. There's a discussion about "Manual Replication Tasks" on Features, which would solve it...

Bye,
rw
 

Fraoch

Patron
Joined
Aug 14, 2014
Messages
395
Thank you so much, it works!! :D

One problem for me - LMS does not start automatically. I feel very noobish about this, but nothing I can see is preventing it from starting automatically...

- lms_enable="YES" is in /etc/rc.conf
- /usr/local/etc/rc.d/lms exists
- LMS manually starts without errors
- the LMS log doesn't show any errors

I can also manually start /usr/local/etc/rc.d/lms/ without errors though I have to use:

Code:
./lms start


which doesn't seem unusual.

It seems like I'm missing something basic. Is there a commented line in /usr/local/etc/rc.d/lms that I should have uncommented? I didn't uncomment any of the optional parameters or add anything other than lms_enable="YES" to /etc/rc.conf and LMS runs fine...just not automatically.
 

Roger Wilco

Explorer
Joined
Jul 17, 2014
Messages
65
@Fraoch

Hi,

what does happen when you start lms manually with
Code:
service lms start


This is how the "rc.d" mechanism works.

In case there is something wrong with your /etc/rc.conf the above will not work (but will tell you).
You should then be able to start it with
Code:
service lms onestart


This starts the service, but doesn't require the lms_enable="YES" in the jail's /etc/rc.conf.
You did put the lms_enable="YES" into the jail's /etc/rc.conf and not the FreeNAS' one, didn't you?

The counterparts to stop the service are
Code:
service lms onestop

and
Code:
service lms stop


Maybe you should delete the log-files, to see if they are re-created on LMS-startup, and post what LMS logs (should be in /var/logs/lms/server.log, as well as what LMS writes to the terminal on start up.

-rw
 

Fraoch

Patron
Joined
Aug 14, 2014
Messages
395
Thanks for your reply!
what does happen when you start lms manually with
Code:
service lms start
Code:
# service lms start
Starting lms.
[15-04-02 08:39:34.3887] main::init (394) Starting Logitech Media Server (v7.9.0, 1427377805, Tue Mar 31 04:18:15 UTC 2015) perl 5.018004

Seems fine?
You should then be able to start it with
Code:
service lms onestart
(after stopping LMS)
Code:
# service lms onestart
Starting lms.
[15-04-02 08:41:44.3059] main::init (394) Starting Logitech Media Server (v7.9.0, 1427377805, Tue Mar 31 04:18:15 UTC 2015) perl 5.018004

Also seems fine.
You did put the lms_enable="YES" into the jail's /etc/rc.conf and not the FreeNAS' one, didn't you?
I sure did:
Code:
root@install_jail:~ # cat /etc/rc.conf
portmap_enable="NO"
sshd_enable="YES"
sendmail_enable="NO"
sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"
hostname="install_jail"
hostname="install_jail"
devfs_enable="YES"
devfs_system_ruleset="devfsrules_common"
inet6_enable="YES"
ip6addrctl_enable="YES"
lms_enable="YES"

and this is in install_jail as you see from the prompt.
Maybe you should delete the log-files, to see if they are re-created on LMS-startup, and post what LMS logs (should be in /var/logs/lms/server.log, as well as what LMS writes to the terminal on start up.
I stopped LMS and deleted the log. On startup:
Code:
# service lms start
Starting lms.
[15-04-02 09:06:52.6222] main::init (394) Starting Logitech Media Server (v7.9.0, 1427377805, Tue Mar 31 04:18:15 UTC 2015) perl 5.018004

The log reads:
Code:
[15-04-02 09:06:52.6223] main::init (394) Starting Logitech Media Server (v7.9.0, 1427377805, Tue Mar 31 04:18:15 UTC 2015) perl 5.018004
[15-04-02 09:06:54.4680] Slim::Web::Cometd::handler (422) errorNeedsClient: [some MAC address], status, -, 10, menu:menu, useContextMenu:1, subscribe:600

I'm pretty sure that last error is unrelated - it's trying to find a player, but the server is up and running fine.

It just won't start up automatically, and I can see no reason why it doesn't...

I notice that it needs to be started as root, do I need to provide my password somewhere? Do I uncomment and set my login in the "REQUIRE: LOGIN" line in /usr/local/etc/rc.d/lms?
 
Status
Not open for further replies.
Top