Forum Replies Created
10. April 2018 at 22:47 #35113
I have downloaded and reinstalled the Jessie image (and updated as suggested on first boot) and the filesystem mount works, LMS works and the printserver works. Yay!
I’ll keep it as it is for a while without updating anything.
Thanks for your help and keep up the good work.
Tim25. März 2018 at 12:03 #34721
The stretch image works!
Share mounted OK (only seems to like lower case share name?)
LMS 7.9 nightly installed ok
Music and spotify ok
CUPS Printserver not accepting user = root, password = max2play –
I put it in over and over again without being able to get in to set up printserver –
eventually it gives up and just tells me that I am forbidden and can’t do anything.
I’ve also tried User = pi, password = raspberry and a few others.
I’m using Chrome and have also tried Edge.
(Could it be something to do with the certificate not being recognised so https isn’t available)
Any help appreciated.
22. März 2018 at 14:55 #34657
- This reply was modified 5 years, 8 months ago by TJH.
I did update Max2Play to beta and reinstall the latest nightly 7.9 on 19 March but LMS wouldn’t start as per my last post.
Is the latest nightly 7.9 LMS not as up to date as the version in Max2Play beta?
I’ll try redoing the beta Max2Play update without any LMS update and see if the LMS sent with the beta will start.
In future I’ll just not bother with updates!12. März 2018 at 18:28 #34351
I hope you had a good holiday (and aren’t sitting with two snowboarding broken wrists like me).
Worse and worse I’m afraid.
I am trying to start again from scratch.
1) Latest Max2Play image downloaded and burned onto formatted SC card, Max2Play updated
2) Pi kernel and packages updated via Max2Play
3) Max2Play gives error when trying to fix IP address:
Debug: Saving WPA-Supplicant (Successfully initialized wpa_supplicant Could not read interface wlan0 flags: No such device WEXT: Could not set interface ‚wlan0‘ UP wlan0: Failed to initialize driver interface )
IP-Address set to 192.168.0.21
Restarting Interface (especially WLAN0) might take some time (up to 1 minute)!
4) Share moved and renamed on Seagate NAS (public share called SMusic, running services SMB, NFS and FTP).
5) New user max2play added to server users, password max2play.
6) Share won’t mount using cifs
mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Mountpoint NOT added! Please refer to the description below!
7) Share will mount using nfs
Mountpoint successfully added
Options (left blank)
8) Latest Squeezeserver 7.9 nightly installed
9) Max2Play wont’t start Squeezeserver
Trying to launch … NOT successful Click here to show detailed information
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
sudo: no tty present and no askpass program specified
10) Haven’t tried getting the printserver working yet
Any ideas?9. März 2018 at 13:41 #34296
Heiner – it’s all gone again!
Yesterday I updated everything on the Pi, remounted the NAS share, rebooted (as per lat post) and all my music became visible, got indexed and was available to play. This morning it’s all gone again.
The music is on a Seagate NAS at //192.168.0.6/Media/Music/Final and then into folders /Artist_Name
//192.168.0.6/Media is mounted OK in Max2Play as /mnt/media
Squeezebox server sees /mnt/media/Music/Final but does not see any /Artist_Name folders and does not see or index any music files
Spotify and podcasts keep on working, it’s just my local network music library that gets lost.
Any ideas?8. März 2018 at 20:40 #34287
All seems ok now.
I removed the filesystem mount add in, rebooted the pi, put the filesystem mount back, updated Squeezebox Server to the latest nightly, deleted and readded the NAS share with the same name and credentials.
Squeezebox Server now sees the files and folders and is busy reindexing 9269 files.
Who knows what it was, but it’s sorted. Maybe a glitch in the old SBox Server version?7. März 2018 at 15:46 #34263
The share is open to all on my home network and did not need a login.
It worked with:
in the filesystem mount box.
Now either shows as mounted ok in the filesystem mount but the files and folders aren’t visible in Squeezebox.
I’ll try your suggestions tonight.25. November 2017 at 22:02 #32636
Danged if I can get the ImageBurner plugin to work as m.max2play suggests:
utilise my NAS as backup target for all my Max2Play devices.
I have mounted the NAS backup destination directory apparently successfully (same way I mounted the NAS music directory which Squeezeserver sees OK).
I have put the mountpoint and a filename into the box at the bottom of the imageburner page (/mnt/Max2Play/Pi.img)
I get this:
Installation started – This Messages refreshes every 3 seconds to show current installation status. When finished this message disappears.
START creating Image to /home/pi/PiServer25-11-17.img
No valid Device choosen – must be sda or sdb
The destination in the message (/home/pi/PiServer25-11-17.img) is not what I put in the box (/mnt/Max2Play/PiServer25-11-17.img)
The flashing message keeps going and going till I refresh the webpage, when it is replaced by the message that the burn failed and the progressfile is being deleted.
The debug file contains
#### FILESYSTEMS SD-CARD ####
fdisk: cannot open /dev/: Is a directory
I am obviously missing something important. Any advice?20. November 2017 at 16:51 #32551
Did a clean install of the latest Max2Play image and all now updates OK.
3 RPis, 3 installs = a whole day reconfiguring (Server Pi2 with HiFiberry Dac+ phone, Zero player with HiFiberry Digi, Pi3 with screen as controller, plus Squezebox and SB Radio). A way of preserving and passing on things like player/server name, fixed IP address, WIFi login, Squeezebox login and plugins details, Spotify login etc etc would save a lot of time. Is there any way Max2Play could ask about these during installation and load them up? (As if you haven’t enough to do already!)
Thanks for a great system keeping home streaming alive and affordable (ie for those of us not in the Sonos league).28. September 2016 at 2:58 #23233
I’ve just set „Soundcard = sysdefault-snd_hifiberry_dacplus…“ in Squeezelight advanced settings (it was equal-equal)
Not only does Squeezelight start, but there is great sound coming from the HifiBerry digi+
I have no idea why or how or what it all means.
Justink – Why not try this too and see if it works for you? Good luck.
(I can go to sleep late but happy)28. September 2016 at 2:34 #23229
I have a similar problem with a digi+ headphone socket output.
New Pi3 + HifiBerry Digi+ (jack socket version)
Clean install of latest Max2Play
No sound at all from Digi+ output – only from Pi’s own headphone socket.
I’ve tried all the suggestions – disabled the Pi’s own output, disabled bluetooth, activated the USB soundcard in audioplayer advanced settings, rebooted several times – nothing.
And now even worse Squeezelight won’t start – error message:
„Trying to launch … NOT successful Click here to show detailed information
squeezelite: pcm_params.c:170: snd1_pcm_hw_param_get_min: Assertion `!snd_interval_empty(i)‘ failed.“
Any help out there please would be appreciated.
I’ve mounted the HifiBerry using nylon spacers rather than metal ones. I hope all the conncections between Pi and HifiBerry are via the header pins and metal spacers are not required for a ground connection!
Also the HifiBerry worked OK when it was in a Pi2, just not in my shiny new Pi3 🙁