Difference between revisions of "FAQkissdx"
(Created page with "= FAQFrequently Asked Questions = == Installing == ''Question'' How to detect which release of kissdx is currently running on a system ? ''Answer'' Use one of these metho...") |
(→QuestionWhy do I get a message about cygwin1.dll not being found?) |
||
| (52 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <u><i>Home </i></u> : [[Kissdx_manual_home|Home]] > | |
| + | <br> | ||
| − | == | + | == [[Image:FAQ.png|FAQ]]Frequently Asked Questions == |
| − | |||
| − | |||
| − | + | === Installing === | |
| − | + | ---- | |
| + | ==== [[Image:FAQ-Q.png|Question]]How to detect which release of kissdx is currently running on a system ? ==== | ||
| − | + | [[Image:FAQ-A.png|Answer]]Use one of these methods: | |
| − | |||
| − | |||
| − | + | * From a KiSS Player, select 'PC Link Server searching': The default signature specifies the release | |
| − | (on the server) netstat -ltp|grep kissdx (display which tcp ports kissdx listens on) | + | * Via a telnet access: Invoke help page with this command: '''kissdx -h''' |
| + | * Via a telnet access: Invoke status page of currently running process: [[Image:V0.14.png|(since kissdx.0.14.x)]] | ||
| + | kissdx -s GET_TXT_CONFIG -m localhost -p 8003 (kissdx must be listening for admin commands on port 8003) | ||
| + | (on the server) netstat -ltp|grep kissdx (display which tcp ports kissdx listens on) | ||
| + | ---- | ||
| − | == Question Which ports must I open in my firewall? == | + | ==== [[Image:FAQ-Q.png|Question]]Which ports must I open in my firewall? ==== |
| − | + | [[Image:FAQ-A.png|Answer]]The following ports are used by kissdx: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | {| border="1px" cellpadding="4" cellspacing="0" style="border-collapse:collapse; border-color:yellow; color:#404040; background-color:#ffffdf; text-align:left; line-height: 120%;" | ||
| + | !IP Protocol | ||
| + | !Port | ||
| + | !Purpose | ||
| + | !Description | ||
| + | |- | ||
| + | |TCP | ||
| + | |8000 | ||
| + | |PC-Link commands and data | ||
| + | |The KiSS player will send commands to this port, so it must be open. The kissdx server will send command responses and stream data back on the same connection. | ||
| + | |- | ||
| + | |UDP | ||
| + | |8000 | ||
| + | |PC-Link server discovery | ||
| + | |The KiSS player will send broadcast packets to this UDP port to discover PC-Link servers on the network, so it must be open for server discovery to work. The kissdx server will send a UDP response to the player address:port that the broadcast originated from. | ||
| + | |- | ||
| + | |TCP | ||
| + | |8888 | ||
| + | |KML commands and data | ||
| + | |'''Optional:''' When operating as a [[Configuration_options#KML_server|KML server]], kissdx will accept connections from players on this port, which must then be open. | ||
| + | |- | ||
| + | |TCP | ||
| + | |8003 | ||
| + | |Administration commands | ||
| + | |'''Optional:''' kissdx 0.14 and later can be managed remotely over this administration port. If administration is enabled and remote administration is desired, this port must be open. | ||
| + | |- | ||
| + | |} | ||
The firewall must allow incoming packets on TCP port 8000 and UDP port 8000 for kissdx to operate. | The firewall must allow incoming packets on TCP port 8000 and UDP port 8000 for kissdx to operate. | ||
| − | See a full description of the kissdx network architecture for more details. | + | See a full description of the [[Kissdx network architecture|kissdx network architecture]] for more details. |
| − | + | ---- | |
| − | |||
| − | + | ==== [[Image:FAQ-Q.png|Question]]Why do I get a message about cygwin1.dll not being found? ==== | |
| − | + | [[Image:FAQ-A.png|Answer]]The following message may appear when you start kissdx on Windows: | |
| − | |||
| − | + | This application has failed to start because cygwin1.dll was not found. | |
| − | + | Re-installing the application may fix this problem. | |
| − | |||
| − | |||
| − | |||
| − | + | Solution: Set up a batch file that will start kissdx in a proper cygwin environment. See the [[Win32_Installation#Installing_kissdx_on_Windows| Win32 install guide]] how to do that. | |
| + | ---- | ||
| + | |||
| + | === Configuring === | ||
| + | ---- | ||
| + | ==== [[Image:FAQ-Q.png|Question]]Should there be trailing slashes in the media paths in the config file? ==== | ||
| + | [[Image:FAQ-A.png|Answer]]The trailing slash is optional. Both cases, with and without, are supported.<br> | ||
A path with an erroneous double slash is in fact also supported. | A path with an erroneous double slash is in fact also supported. | ||
| − | [ | + | ---- |
| − | + | ==== [[Image:FAQ-Q.png|Question]]Why do I get the message "The .recent directories must be deleted or moved"? ==== | |
| − | + | [[Image:FAQ-A.png|Answer]]The ''.recent'' directory is used to store a set of symbolic links that allow a history view of media played in the [Recently used] folder. | |
| − | + | kissdx will create the .recent directory inside the media folder if persistentstoragepath has not been set in the configuration file. | |
| + | When persistentstoragepath ''is'' set, kissdx stores the .recent directory inside the directory specified there. | ||
So if you have been using kissdx without persistentstoragepath, and then decide to set it, kissdx will issue this message to help you manually migrate the .recent directory to its new location. | So if you have been using kissdx without persistentstoragepath, and then decide to set it, kissdx will issue this message to help you manually migrate the .recent directory to its new location. | ||
| − | In versions previous to 0.13.10a, the location of .recent inside a media fodler was undetected. Since this release, this 'bad' configuration is detected and kissdx is unable to start. | + | In versions previous to 0.13.10a, the location of .recent inside a media fodler was undetected. |
| + | Since this release, this 'bad' configuration is detected and kissdx is unable to start. | ||
Solution: | Solution: | ||
| − | + | * Remove the .recent directory in each media filesystem (audio, picture and video). | |
| − | + | * The result is loss of your media played history. | |
| − | |||
| − | |||
or | or | ||
| + | * Move those 3 directories to their new locations. If persistentstoragepath is ''/var/kissdx'' then move them to ''/var/kissdx/audio/.recent'', ''/var/kissdx/video/.recent'' and ''/var/kissdx/pictures/.recent''. | ||
| + | * This will preserve your media played history. | ||
| − | + | NOTE: The issues and solutions above are the exactly same for the .piccache folder as for the .recent folder. | |
| − | + | This .piccache directory stores resized pictures and affects only the media picture path. | |
| − | + | ==== [[Image:FAQ-Q.png|Question]]kissdx won't start but I don't see any error message ==== | |
| − | + | [[Image:FAQ-A.png|Answer]]If you are starting kissdx with the -d option and it doesn't start running, then check in your computer's log: | |
| − | + | * On Linux: Check in the syslog for messages from kissdx. | |
| − | + | * On Windows: Check in the Event Viewer (Application section) for messages from Cygwin or kissdx. | |
| − | + | ---- | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | === Streaming === | ||
| + | ---- | ||
No streaming related questions yet. | No streaming related questions yet. | ||
| − | + | ---- | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === Adminstration === | |
| + | ---- | ||
| + | ==== [[Image:FAQ-Q.png|Question]]Using kissdx in as a client administration, I get a 'connection refused'? ==== | ||
| + | [[Image:FAQ-A.png|Answer]]First, check that the administration server (port 8003 by default) is started correctly: Run kissdx in verbose mode and check that the following message appears in the log: "kissdx listener ADM.CMD TCP port 8003 open". | ||
| − | + | Second, the 'listenaddress' option may be configured to one of your network interfaces, and your client kissdx running on the same host as the administration server. Then the request is signed '127.0.0.1' and is rejected. | |
| − | + | A solution is to specify your client request, via -m option, to use the 'authorised' network interface. | |
| − | + | Example: kissdx.conf specifies the option 'listenaddress = 192.168.0.2' which is your second network card | |
| − | + | Client request command : ./kissdx -s MyCommand -m 192.168.0.2 | |
| − | |||
| − | |||
| − | |||
| − | + | ---- | |
| − | killall kissdx | + | === Trouble-shooting === |
| − | /opt/bin/kissdx -v >kissdx.log 2>&1 | + | ---- |
| + | ==== [[Image:FAQ-Q.png|Question]]How can I run kissdx to produce a log file for support? ==== | ||
| + | [[Image:FAQ-A.png|Answer]]If asked to produce a verbose log file, proceed as follows: | ||
| + | # Log in to the computer running kissdx (telnet, ssh, console or Cygwin command prompt). | ||
| + | # Run the commands listed below. | ||
| + | # Perform tests on the player to reproduce the issue. | ||
| + | # When tests are completed, press Ctrl+C to stop kissdx. | ||
| + | # Compress the log file (zip, 7z, gzip). | ||
| + | # Forward the log file as requested, e.g. upload to bug report or e-mail. | ||
| + | # Notify us about the new log file and what specific tests were made to produce it. | ||
| + | These commands will produce a log file called '''kissdx.log''' in the current directory: | ||
| + | killall kissdx | ||
| + | /opt/bin/kissdx -v >kissdx.log 2>&1 | ||
| + | Note: '''/opt/bin/kissdx''' is correct for Optware platforms. On other platforms try '''/bin/kissdx''' or just '''kissdx'''. | ||
| + | ---- | ||
| − | + | == [[Image:FAQ.png|FAQ]]Questions related to specific kissdx releases == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === Streaming === | |
| − | + | ---- | |
| − | + | ==== [[Image:FAQ-Q.png|Question]]Does the message 'iconv support' mean a bad and unsupported configuration ? ==== | |
| − | + | [[Image:FAQ-A.png|Answer]][[Image:V0.13-8.png|Special advice for v0.13.8 users]] The iconv message does not indicate an error. It's just for info, and is removed in the 0.13.10a release. | |
| − | + | ---- | |
| − | + | === Configuration === | |
| − | + | ---- | |
| + | ==== [[Image:FAQ-Q.png|Question]]How can I restrict excessive reloading of configuration with DP600/1600? ==== | ||
| + | [[Image:FAQ-A.png|Answer]][[Image:V0.13-10a.png|Special advice for v0.13.8 users]]The new KNAS firmware for the DP-600 and 1600 players broadcasts UDP packets very frequently to poll player status, adding to the risk of accidental re-reading of kissdx.conf. Since kissdx V0.14.0, the option 'configautoload = no' solve the issue. | ||
| + | ---- | ||
Latest revision as of 18:12, 14 May 2012
Home : Home >
Contents
Frequently Asked Questions
Installing
How to detect which release of kissdx is currently running on a system ?
Use one of these methods:
- From a KiSS Player, select 'PC Link Server searching': The default signature specifies the release
- Via a telnet access: Invoke help page with this command: kissdx -h
- Via a telnet access: Invoke status page of currently running process:
kissdx -s GET_TXT_CONFIG -m localhost -p 8003 (kissdx must be listening for admin commands on port 8003) (on the server) netstat -ltp|grep kissdx (display which tcp ports kissdx listens on)
Which ports must I open in my firewall?
The following ports are used by kissdx:
| IP Protocol | Port | Purpose | Description |
|---|---|---|---|
| TCP | 8000 | PC-Link commands and data | The KiSS player will send commands to this port, so it must be open. The kissdx server will send command responses and stream data back on the same connection. |
| UDP | 8000 | PC-Link server discovery | The KiSS player will send broadcast packets to this UDP port to discover PC-Link servers on the network, so it must be open for server discovery to work. The kissdx server will send a UDP response to the player address:port that the broadcast originated from. |
| TCP | 8888 | KML commands and data | Optional: When operating as a KML server, kissdx will accept connections from players on this port, which must then be open. |
| TCP | 8003 | Administration commands | Optional: kissdx 0.14 and later can be managed remotely over this administration port. If administration is enabled and remote administration is desired, this port must be open. |
The firewall must allow incoming packets on TCP port 8000 and UDP port 8000 for kissdx to operate.
See a full description of the kissdx network architecture for more details.
Why do I get a message about cygwin1.dll not being found?
The following message may appear when you start kissdx on Windows:
This application has failed to start because cygwin1.dll was not found. Re-installing the application may fix this problem.
Solution: Set up a batch file that will start kissdx in a proper cygwin environment. See the Win32 install guide how to do that.
Configuring
Should there be trailing slashes in the media paths in the config file?
The trailing slash is optional. Both cases, with and without, are supported.
A path with an erroneous double slash is in fact also supported.
Why do I get the message "The .recent directories must be deleted or moved"?
The .recent directory is used to store a set of symbolic links that allow a history view of media played in the [Recently used] folder.
kissdx will create the .recent directory inside the media folder if persistentstoragepath has not been set in the configuration file.
When persistentstoragepath is set, kissdx stores the .recent directory inside the directory specified there.
So if you have been using kissdx without persistentstoragepath, and then decide to set it, kissdx will issue this message to help you manually migrate the .recent directory to its new location.
In versions previous to 0.13.10a, the location of .recent inside a media fodler was undetected. Since this release, this 'bad' configuration is detected and kissdx is unable to start.
Solution:
- Remove the .recent directory in each media filesystem (audio, picture and video).
- The result is loss of your media played history.
or
- Move those 3 directories to their new locations. If persistentstoragepath is /var/kissdx then move them to /var/kissdx/audio/.recent, /var/kissdx/video/.recent and /var/kissdx/pictures/.recent.
- This will preserve your media played history.
NOTE: The issues and solutions above are the exactly same for the .piccache folder as for the .recent folder. This .piccache directory stores resized pictures and affects only the media picture path.
kissdx won't start but I don't see any error message
If you are starting kissdx with the -d option and it doesn't start running, then check in your computer's log:
- On Linux: Check in the syslog for messages from kissdx.
- On Windows: Check in the Event Viewer (Application section) for messages from Cygwin or kissdx.
Streaming
No streaming related questions yet.
Adminstration
Using kissdx in as a client administration, I get a 'connection refused'?
First, check that the administration server (port 8003 by default) is started correctly: Run kissdx in verbose mode and check that the following message appears in the log: "kissdx listener ADM.CMD TCP port 8003 open".
Second, the 'listenaddress' option may be configured to one of your network interfaces, and your client kissdx running on the same host as the administration server. Then the request is signed '127.0.0.1' and is rejected. A solution is to specify your client request, via -m option, to use the 'authorised' network interface.
Example: kissdx.conf specifies the option 'listenaddress = 192.168.0.2' which is your second network card Client request command : ./kissdx -s MyCommand -m 192.168.0.2
Trouble-shooting
How can I run kissdx to produce a log file for support?
If asked to produce a verbose log file, proceed as follows:
- Log in to the computer running kissdx (telnet, ssh, console or Cygwin command prompt).
- Run the commands listed below.
- Perform tests on the player to reproduce the issue.
- When tests are completed, press Ctrl+C to stop kissdx.
- Compress the log file (zip, 7z, gzip).
- Forward the log file as requested, e.g. upload to bug report or e-mail.
- Notify us about the new log file and what specific tests were made to produce it.
These commands will produce a log file called kissdx.log in the current directory:
killall kissdx /opt/bin/kissdx -v >kissdx.log 2>&1
Note: /opt/bin/kissdx is correct for Optware platforms. On other platforms try /bin/kissdx or just kissdx.
Questions related to specific kissdx releases
Streaming
Does the message 'iconv support' mean a bad and unsupported configuration ?
The iconv message does not indicate an error. It's just for info, and is removed in the 0.13.10a release.
Configuration
How can I restrict excessive reloading of configuration with DP600/1600?
The new KNAS firmware for the DP-600 and 1600 players broadcasts UDP packets very frequently to poll player status, adding to the risk of accidental re-reading of kissdx.conf. Since kissdx V0.14.0, the option 'configautoload = no' solve the issue.
