Changes between Version 7 and Version 8 of SolarisInstallation

Author:

T_oo (IP: 127.0.0.1)

Timestamp:

31.12.2009 12:40:14 (3 years ago)

Comment:

--

SolarisInstallation

@@ -1 @@
-
-
-
+
+
+
+
+
+
+
+
+
+
+
-
-This document gives a brief overview on how to install Coherence on (Open)Solaris.
-
-
+
+
-There is a mimimum set of dependencies that Coherence needs to be able to run. Thanks to the built-in package manager this is very easy. Either use the Package Manager GUI tool in Gnome or a root shell like this:
-{{{
+#!bash
-  Mike@Sisyphos:~$ pkg install <package-name>
-}}}
-Variant 1:
-{{{
+#!bash
-  Mike@Sisyphos:~$ su
-  Mike@Sisyphos:~$ password:
-Variant 2:
-{{{
+#!bash
-  Mike@Sisyphos:/$ cd ~
-  Mike@Sisyphos:~$ mkdir Development
-Both variants will leave you with an executable in /usr/bin which can be run from any location by just typing
-{{{
+#!bash
-  Mike@Sisyphos:~$ coherence
-}}}
-1) Create user and group for the server (we assume upnp/nas here), if you don't want to reuse an existing user. The group should be allowed to access your media files. If you have setup your box as a file server then you probably have already a dedicated group for accessing it, which would be a good candidate. If not do
-{{{
+#!bash
-  Mike@Sisyphos:~$ groupadd nas
-  Mike@Sisyphos:~$ useradd -g nas -d /var/coherence upnp
-2) Create a private folder for Coherence. There we store the config file, the log file and a lock file which prevents more than one instance to start (if started via start script).
-{{{
+#!bash
-  Mike@Sisyphos:~$ mkdir /var/coherence
-  Mike@Sisyphos:~$ chown upnp:nas /var/coherence
-3) Copy the [[attachment:coherence.conf config file]] into that folder and give proper permissions.
-{{{
+#!bash
-  Mike@Sisyphos:~$ cd /var/coherence
-  Mike@Sisyphos:/var/coherence$ chown upnp:nas coherence.conf
-
-4) Copy the socalled [[attachment:coherence.sh method script]] (a script to control the server) to /lib/svc/method/coherence (no extension) and set permissions. This file is used by the Service Management Facility (SMF) to control the service.
-
+
+
+
-  Mike@Sisyphos:~$ chmod 555 /lib/svc/method/coherence
-}}}
-
-6) Import the service description to add the new service.
-
+
+
+
-  Mike@Sisyphos:~$ svccfg import /var/svc/manifest/application/coherence.xml
-}}}
-
-The service is now ready and only needs to be started. Check that it is really there:
-
+
+
+
-  Mike@Sisyphos:~$ svcs coherence
-  STATE          STIME    FMRI
-
-Enable the service and you are done.
-
+
+
+
-  Mike@Sisyphos:~$ svcadmin enable coherence
-  Mike@Sisyphos:~$ svcs coherence
-
-== Troubleshooting ==
+
-In case something goes wrong you have several means to look for a reason.
-
-1) If your service doesn't want to go online and stays offline or in maintenance mode check if all dependencies (of the service, not coherence itself) are met:
-
+
+
+
-  Mike@Sisyphos:~$ svcs -l coherence
-  fmri         svc:/application/upnp/coherence:default
-  dependency   require_all/none svc:/system/filesystem/local:default (online)
-}}}
+
-Spend special attention to the dependencies. All four must be "online". Use the next command to find other info (only useful if the service makes trouble).
-
+
+
+
-  Mike@Sisyphos:~$ svcs -x coherence
-  svc:/application/upnp/coherence:default (Coherence UPNP/DLNA media server)
-
-A good pool of information is also the set of properties assigned to the service. You get them via:
-
+
+
+
-  Mike@Sisyphos:~$ svcprop coherence
-  coherence/config astring /var/coherence/coherence.conf
-
-3) If the service enters the maintenance state and you receive a "could not set context for method" error in the service log, make sure the service account has a home directory set.  Note the attempt to change directories.
-
+
+
+
-  [ Apr 28 21:55:26 Executing start method ("/lib/svc/method/coherence start"). ]
-  svc.startd could not set context for method: chdir: No such file or directory
-
-The solution is to add a sensible home directory to the service account:
-
+
+
+
-  [jmccune@rain ~]$ pfexec usermod -d /var/coherence upnp
-}}}