There is always a cause, things do not happen magically in IT.
My power gate started playing weird a few days ago. It would stop randomly, sometimes it would work in one direction, stop in the other one. The cause - an overgrown nettle started blocking the optical gate randomly. No magic.
Just like your software. If you have a good network connection between the machines (check with ping), and now your shares cannot connect, there was some change.
Troubleshoot step by step, from lowest layers to the upper ones.
1. confirm working network connection from your daphile (D) to your win machine (W) - ping
2. log-in to daphile remotely via ssh, try to run the mount manually (mount -t cifs.... Samba/SambaClientGuide - Community Help Wiki
Daphile is a pre-configured linux with read-only filesystem setup, no magic. Unfortunately it is next to impossible to make a device where everything works out of the box in a constantly changing environment.
My power gate started playing weird a few days ago. It would stop randomly, sometimes it would work in one direction, stop in the other one. The cause - an overgrown nettle started blocking the optical gate randomly. No magic.
Just like your software. If you have a good network connection between the machines (check with ping), and now your shares cannot connect, there was some change.
Troubleshoot step by step, from lowest layers to the upper ones.
1. confirm working network connection from your daphile (D) to your win machine (W) - ping
2. log-in to daphile remotely via ssh, try to run the mount manually (mount -t cifs.... Samba/SambaClientGuide - Community Help Wiki
Daphile is a pre-configured linux with read-only filesystem setup, no magic. Unfortunately it is next to impossible to make a device where everything works out of the box in a constantly changing environment.
Have you recently added new media which may have long filenames or excessive tag data which corrupt the initial daphile media scan and indexing. The consequences may cause a memory corruption which is not immediately obvious. Check your daphile log files. Also running daphile rt could also have issues. Try the static form if the problem repeats.
Hi guys, it started working after a restart of all network hardware and the server and client, as the post and screenshot on the previous page shows.
But after 15 hours powered on, the drives no longer recognised any more. Zero, absolutely zero changes between the two times. The settings page does not load (I gave up after 15 minutes of seeing a spinning wheel) and neither does the 'Network drives' entry under Music Folder. Info page does not open, it's like the machine has basically hung, as the browser does not respond to most of the commands - except the power menu - which works fine and instantly recognises the command so the backend is working though only partially. Ping works fine though. But nada after the media server page - which by the way, also does not load. Restarting the PC de-recognises the drives, with the dreaded red icon.
LMS running on the Windows server meantime does not skip a beat and continues working fine - note that the database is exactly the same (works off the same drives and same folders) so corruption is not a possibility else LMS would also hang up its boots.
The basic diagnosis is impossible because there are no changes between a working setup and a broken one. To repeat, no changes, no new files, nothing that can precipitate the issues except a night of sleeping. Hope I am allowed that.
Please note, and I repeat, the network is functioning perfectly, the folders are recognised by every single machine on the network and the files read properly, LMS running on the server connects to all clients just fine and runs everything off the same folders and does not bug out.
For some reason Daphile is bugging out after a few hours of running, all by itself. The fault is definitely in the Daphile LMS configuration itself - that much is certain. The client side, as I mentioned earlier, is running fine but the server side is either corrupting its own database or requires some kind of interaction with the database that is not happening and hence it is dying.
I am really close to dumping Daphile and moving to a pure LMS+Squeezelite Player setup. I never found Daphile fiddly, it just seems the new versions are not properly made. A pity, because it does sound pretty good.
But after 15 hours powered on, the drives no longer recognised any more. Zero, absolutely zero changes between the two times. The settings page does not load (I gave up after 15 minutes of seeing a spinning wheel) and neither does the 'Network drives' entry under Music Folder. Info page does not open, it's like the machine has basically hung, as the browser does not respond to most of the commands - except the power menu - which works fine and instantly recognises the command so the backend is working though only partially. Ping works fine though. But nada after the media server page - which by the way, also does not load. Restarting the PC de-recognises the drives, with the dreaded red icon.
LMS running on the Windows server meantime does not skip a beat and continues working fine - note that the database is exactly the same (works off the same drives and same folders) so corruption is not a possibility else LMS would also hang up its boots.
The basic diagnosis is impossible because there are no changes between a working setup and a broken one. To repeat, no changes, no new files, nothing that can precipitate the issues except a night of sleeping. Hope I am allowed that.
Please note, and I repeat, the network is functioning perfectly, the folders are recognised by every single machine on the network and the files read properly, LMS running on the server connects to all clients just fine and runs everything off the same folders and does not bug out.
For some reason Daphile is bugging out after a few hours of running, all by itself. The fault is definitely in the Daphile LMS configuration itself - that much is certain. The client side, as I mentioned earlier, is running fine but the server side is either corrupting its own database or requires some kind of interaction with the database that is not happening and hence it is dying.
I am really close to dumping Daphile and moving to a pure LMS+Squeezelite Player setup. I never found Daphile fiddly, it just seems the new versions are not properly made. A pity, because it does sound pretty good.
Your description seems not much to do with network drives, but with the overall functionality of the daphile built-in web site.
Why would a problem with database lead to non responding script listing settings?
When the problem occurs, specifically what/which pages/features do work on that machine?
You should be able to learn more from logs. Command dmesg, looking at /var/log/syslog will tell you about hw status of the machine. IMO you need to log into your daphile for more troubleshooting, just the GUI will not suffice. If you want to delve into this troubleshooting...
phofman,
First of all, I appreciate the assistance. However, I am not keen to have to delve into the console. My last time did not end happily (with other linux server attempts). For those who have been doing this for a few years it's probably okay, I just want things to work properly and there is really no easy way to find my way around the syntax and file structure. I spent six months trying to get a nice headless ARM server with Linux running and in the end I had to bin it because I ran out of talent troubleshooting it.
To your question, the power options works. When selecting 'File Manager', the 'Network drives' option does not respond. The other two (RAM drive and local drive) do respond, but they are both empty as no music is stored on them and I get blank screens.
I will try powering off Daphile and leaving it powered down overnight, and then checking if it works on cold boot. Seemed to work the last time I did something similar.
There seems to be no problem with the database or individual files. LMS handles it just fine, and even Daphile is okay (at least, seems to be) unless it is left powered on, in which case it bugs out. That is the only way I can create the fault condition.
To eliminate any possibility of Daphile's internal functioning being problematic, I shall remove the network drive mapping and see if it works properly afterwards. Since all options relating to the shared resources (settings page, info page and Network drives) do not operate I am 100% sure it is just that and nothing else.
It's just that the library has 84k tracks and takes quite a while to scan the library and rebuild all playlists. I will delete network drives only after I have exhausted all other options.
First of all, I appreciate the assistance. However, I am not keen to have to delve into the console. My last time did not end happily (with other linux server attempts). For those who have been doing this for a few years it's probably okay, I just want things to work properly and there is really no easy way to find my way around the syntax and file structure. I spent six months trying to get a nice headless ARM server with Linux running and in the end I had to bin it because I ran out of talent troubleshooting it.
To your question, the power options works. When selecting 'File Manager', the 'Network drives' option does not respond. The other two (RAM drive and local drive) do respond, but they are both empty as no music is stored on them and I get blank screens.
I will try powering off Daphile and leaving it powered down overnight, and then checking if it works on cold boot. Seemed to work the last time I did something similar.
There seems to be no problem with the database or individual files. LMS handles it just fine, and even Daphile is okay (at least, seems to be) unless it is left powered on, in which case it bugs out. That is the only way I can create the fault condition.
To eliminate any possibility of Daphile's internal functioning being problematic, I shall remove the network drive mapping and see if it works properly afterwards. Since all options relating to the shared resources (settings page, info page and Network drives) do not operate I am 100% sure it is just that and nothing else.
It's just that the library has 84k tracks and takes quite a while to scan the library and rebuild all playlists. I will delete network drives only after I have exhausted all other options.
Thanks rif, find below
[Begin Server Log]
[18-06-24 06:48:21.6559] main::init (387) Starting Logitech Media Server (v7.9.1, gitd424bbe9f, Daphile 17.09-x86_64-rt) perl 5.024001 - x86_64-linux-thread-multi
[18-06-24 16:40:49.1933] main::init (387) Starting Logitech Media Server (v7.9.1, gitd424bbe9f, Daphile 17.09-x86_64-rt) perl 5.024001 - x86_64-linux-thread-multi
[18-06-25 07:49:54.2997] Slim::Utils::Scanner::Local::rescan (181) Discovering audio files in /srv/mediaserver/music
[18-06-25 07:49:54.3323] Slim::Utils::Scanner::Local::__ANON__ (193) Start processing found tracks
[18-06-25 07:49:54.3330] Slim::Utils::Scanner::Local::__ANON__ (201) Connect do DB
[18-06-25 07:49:54.3337] Slim::Utils::Scanner::Local::__ANON__ (204) Get latest ID
[18-06-25 07:49:54.3348] Slim::Utils::Scanner::Local::__ANON__ (226) Delete temporary table if exists
[18-06-25 07:49:54.3360] Slim::Utils::Scanner::Local::__ANON__ (229) Re-build temporary table
[18-06-25 07:49:57.1323] Slim::Utils::Scanner::Local::__ANON__ (278) Get deleted tracks count
[18-06-25 07:49:57.1330] Slim::Utils::Scanner::Local::__ANON__ (285) Get new tracks count
[18-06-25 07:49:57.1341] Slim::Utils::Scanner::Local::__ANON__ (290) Get changed tracks count
[18-06-25 07:50:00.9930] Slim::Utils::Scanner::Local::__ANON__ (296) Removing deleted audio files (0)
[18-06-25 07:50:00.9937] Slim::Utils::Scanner::Local::__ANON__ (374) Scanning new audio files (0)
[18-06-25 07:50:00.9944] Slim::Utils::Scanner::Local::__ANON__ (454) Rescanning changed audio files (0)
[18-06-25 07:50:41.5935] Slim::Utils::Scanner::Local::rescan (181) Discovering audio files in /srv/mediaserver/music/Network Drives
[18-06-25 08:04:48.8076] Slim::Utils::Scanner::Local::__ANON__ (193) Start processing found tracks
[18-06-25 08:04:48.8090] Slim::Utils::Scanner::Local::__ANON__ (201) Connect do DB
[18-06-25 08:04:48.8103] Slim::Utils::Scanner::Local::__ANON__ (204) Get latest ID
[18-06-25 08:04:48.8121] Slim::Utils::Scanner::Local::__ANON__ (226) Delete temporary table if exists
[18-06-25 08:04:48.8139] Slim::Utils::Scanner::Local::__ANON__ (229) Re-build temporary table
[18-06-25 08:04:51.5521] Slim::Utils::Scanner::Local::__ANON__ (278) Get deleted tracks count
[18-06-25 08:04:51.5529] Slim::Utils::Scanner::Local::__ANON__ (285) Get new tracks count
[18-06-25 08:04:51.5551] Slim::Utils::Scanner::Local::__ANON__ (290) Get changed tracks count
[18-06-25 08:04:55.4171] Slim::Utils::Scanner::Local::__ANON__ (296) Removing deleted audio files (0)
[18-06-25 08:04:55.4181] Slim::Utils::Scanner::Local::__ANON__ (374) Scanning new audio files (0)
[18-06-25 08:04:55.4190] Slim::Utils::Scanner::Local::__ANON__ (454) Rescanning changed audio files (0)
[18-06-25 08:06:04.4241] Slim::Utils::Scanner::Local::rescan (181) Discovering audio files in /srv/mediaserver/music/Network Drives/Test
[18-06-25 08:06:04.4453] Slim::Utils::Scanner::Local::__ANON__ (193) Start processing found tracks
[18-06-25 08:06:04.4462] Slim::Utils::Scanner::Local::__ANON__ (201) Connect do DB
[18-06-25 08:06:04.4469] Slim::Utils::Scanner::Local::__ANON__ (204) Get latest ID
[18-06-25 08:06:04.4480] Slim::Utils::Scanner::Local::__ANON__ (226) Delete temporary table if exists
[18-06-25 08:06:04.4493] Slim::Utils::Scanner::Local::__ANON__ (229) Re-build temporary table
[18-06-25 08:06:07.0175] Slim::Utils::Scanner::Local::__ANON__ (278) Get deleted tracks count
[18-06-25 08:06:07.0183] Slim::Utils::Scanner::Local::__ANON__ (285) Get new tracks count
[18-06-25 08:06:07.0194] Slim::Utils::Scanner::Local::__ANON__ (290) Get changed tracks count
[18-06-25 08:06:09.6081] Slim::Utils::Scanner::Local::__ANON__ (296) Removing deleted audio files (0)
[18-06-25 08:06:09.6091] Slim::Utils::Scanner::Local::__ANON__ (374) Scanning new audio files (0)
[18-06-25 08:06:09.6098] Slim::Utils::Scanner::Local::__ANON__ (454) Rescanning changed audio files (0)
[18-06-25 10:34:07.3932] Slim::Web::JSONRPC::requestMethod (443) 5a:9b:d7:9e:ea:29: request not dispatchable!
[End Log]
(I tried to start the player unsuccessfully around 1pm)
Scanner log does not appear in dropdown. Only the device logs and Media Server. For scan I used the page linked to in the menu below, that page is attached as a screenshot.
[Begin Server Log]
[18-06-24 06:48:21.6559] main::init (387) Starting Logitech Media Server (v7.9.1, gitd424bbe9f, Daphile 17.09-x86_64-rt) perl 5.024001 - x86_64-linux-thread-multi
[18-06-24 16:40:49.1933] main::init (387) Starting Logitech Media Server (v7.9.1, gitd424bbe9f, Daphile 17.09-x86_64-rt) perl 5.024001 - x86_64-linux-thread-multi
[18-06-25 07:49:54.2997] Slim::Utils::Scanner::Local::rescan (181) Discovering audio files in /srv/mediaserver/music
[18-06-25 07:49:54.3323] Slim::Utils::Scanner::Local::__ANON__ (193) Start processing found tracks
[18-06-25 07:49:54.3330] Slim::Utils::Scanner::Local::__ANON__ (201) Connect do DB
[18-06-25 07:49:54.3337] Slim::Utils::Scanner::Local::__ANON__ (204) Get latest ID
[18-06-25 07:49:54.3348] Slim::Utils::Scanner::Local::__ANON__ (226) Delete temporary table if exists
[18-06-25 07:49:54.3360] Slim::Utils::Scanner::Local::__ANON__ (229) Re-build temporary table
[18-06-25 07:49:57.1323] Slim::Utils::Scanner::Local::__ANON__ (278) Get deleted tracks count
[18-06-25 07:49:57.1330] Slim::Utils::Scanner::Local::__ANON__ (285) Get new tracks count
[18-06-25 07:49:57.1341] Slim::Utils::Scanner::Local::__ANON__ (290) Get changed tracks count
[18-06-25 07:50:00.9930] Slim::Utils::Scanner::Local::__ANON__ (296) Removing deleted audio files (0)
[18-06-25 07:50:00.9937] Slim::Utils::Scanner::Local::__ANON__ (374) Scanning new audio files (0)
[18-06-25 07:50:00.9944] Slim::Utils::Scanner::Local::__ANON__ (454) Rescanning changed audio files (0)
[18-06-25 07:50:41.5935] Slim::Utils::Scanner::Local::rescan (181) Discovering audio files in /srv/mediaserver/music/Network Drives
[18-06-25 08:04:48.8076] Slim::Utils::Scanner::Local::__ANON__ (193) Start processing found tracks
[18-06-25 08:04:48.8090] Slim::Utils::Scanner::Local::__ANON__ (201) Connect do DB
[18-06-25 08:04:48.8103] Slim::Utils::Scanner::Local::__ANON__ (204) Get latest ID
[18-06-25 08:04:48.8121] Slim::Utils::Scanner::Local::__ANON__ (226) Delete temporary table if exists
[18-06-25 08:04:48.8139] Slim::Utils::Scanner::Local::__ANON__ (229) Re-build temporary table
[18-06-25 08:04:51.5521] Slim::Utils::Scanner::Local::__ANON__ (278) Get deleted tracks count
[18-06-25 08:04:51.5529] Slim::Utils::Scanner::Local::__ANON__ (285) Get new tracks count
[18-06-25 08:04:51.5551] Slim::Utils::Scanner::Local::__ANON__ (290) Get changed tracks count
[18-06-25 08:04:55.4171] Slim::Utils::Scanner::Local::__ANON__ (296) Removing deleted audio files (0)
[18-06-25 08:04:55.4181] Slim::Utils::Scanner::Local::__ANON__ (374) Scanning new audio files (0)
[18-06-25 08:04:55.4190] Slim::Utils::Scanner::Local::__ANON__ (454) Rescanning changed audio files (0)
[18-06-25 08:06:04.4241] Slim::Utils::Scanner::Local::rescan (181) Discovering audio files in /srv/mediaserver/music/Network Drives/Test
[18-06-25 08:06:04.4453] Slim::Utils::Scanner::Local::__ANON__ (193) Start processing found tracks
[18-06-25 08:06:04.4462] Slim::Utils::Scanner::Local::__ANON__ (201) Connect do DB
[18-06-25 08:06:04.4469] Slim::Utils::Scanner::Local::__ANON__ (204) Get latest ID
[18-06-25 08:06:04.4480] Slim::Utils::Scanner::Local::__ANON__ (226) Delete temporary table if exists
[18-06-25 08:06:04.4493] Slim::Utils::Scanner::Local::__ANON__ (229) Re-build temporary table
[18-06-25 08:06:07.0175] Slim::Utils::Scanner::Local::__ANON__ (278) Get deleted tracks count
[18-06-25 08:06:07.0183] Slim::Utils::Scanner::Local::__ANON__ (285) Get new tracks count
[18-06-25 08:06:07.0194] Slim::Utils::Scanner::Local::__ANON__ (290) Get changed tracks count
[18-06-25 08:06:09.6081] Slim::Utils::Scanner::Local::__ANON__ (296) Removing deleted audio files (0)
[18-06-25 08:06:09.6091] Slim::Utils::Scanner::Local::__ANON__ (374) Scanning new audio files (0)
[18-06-25 08:06:09.6098] Slim::Utils::Scanner::Local::__ANON__ (454) Rescanning changed audio files (0)
[18-06-25 10:34:07.3932] Slim::Web::JSONRPC::requestMethod (443) 5a:9b:d7:9e:ea:29: request not dispatchable!
[End Log]
(I tried to start the player unsuccessfully around 1pm)
Scanner log does not appear in dropdown. Only the device logs and Media Server. For scan I used the page linked to in the menu below, that page is attached as a screenshot.
@ sangram
There is no ssh access on standard versions of Daphile.
It is only available when using the beta versions..
https://www.daphile.com/download/FAQ.txt
Q13. Can I access Daphile with ssh?
A13. Only the beta versions have ssh server and root password enabled.
Root password is "zaq" without quotes. Beta versions are
available here: Index of /firmware/beta
There is no ssh access on standard versions of Daphile.
It is only available when using the beta versions..
https://www.daphile.com/download/FAQ.txt
Q13. Can I access Daphile with ssh?
A13. Only the beta versions have ssh server and root password enabled.
Root password is "zaq" without quotes. Beta versions are
available here: Index of /firmware/beta
Yes....and ....no. Download and write the beta to a pendrive and boot it to see if it works and solves the problem....
Yes and guessing here that the developer has tried to reduce the support tickets by creating a closed version for normal users and a beta for power users..?
It is a free o/s after all....
Why a memory leak? It would eat all RAM eventually. Why should a different kernel solve this problem with lockup against some upgraded windows share?
IMO his cifs client needs some parameters to connect, it may lock while mounting and the control web server software (php, python?) does not recover from this failure. Or some hw problem. A look at proper logs would likely reveal the problem.
IMO his cifs client needs some parameters to connect, it may lock while mounting and the control web server software (php, python?) does not recover from this failure. Or some hw problem. A look at proper logs would likely reveal the problem.
I have been using Daphile for a couple years. I have both ntfs and cifs mounts and never have any issues. Most of the time I leave on 7/24 and I only need to reboot when updates!
I am using Daphile now for several years and I am very happy with it.
Recently I got a fanless PC, so I can get rid of the fan noise of my current PC.
Installing Daphile on this PC was quite easy, but for some reason my WaveIO USB card is not recognized. I tried all USB2 and USB3 ports, but WaveIO (Luckit) is not visible under audio devices.
When I switch back to the old PC, everything works fine.
Any suggestions?
Fanless PC:
Smart View Medical Station-ZEUS series, Fanless slim panel PC, Healthcare Infotainment, Android Medical Tablet, Medical display, Medical PC, Mobile Computing Cart.
Recently I got a fanless PC, so I can get rid of the fan noise of my current PC.
Installing Daphile on this PC was quite easy, but for some reason my WaveIO USB card is not recognized. I tried all USB2 and USB3 ports, but WaveIO (Luckit) is not visible under audio devices.
When I switch back to the old PC, everything works fine.
Any suggestions?
Fanless PC:
Smart View Medical Station-ZEUS series, Fanless slim panel PC, Healthcare Infotainment, Android Medical Tablet, Medical display, Medical PC, Mobile Computing Cart.
I suggest you contact daphile using the contact link on Daphile – Digital Music Convenience for Audiophiles.