Re: [SlimDevices: Unix] Announce: Squeezelite - a small headless squeezeplay emulator for linux (alsa only)
kllngtme wrote: Any idea why it's not updated on google code? Or was this changed to being hosted somewhere else? Squeezelite 1.5 is only available.. https://code.google.com/p/squeezelite/downloads/list See the home page of the project - it gives the new download site for binaries https://code.google.com/p/squeezelite/ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeezelite - a small headless squeezeplay emulator for linux (alsa only)
Triode wrote: I've updated the Squeezelite binaries to version 1.6.4. Any idea why it's not updated on google code? Or was this changed to being hosted somewhere else? Squeezelite 1.5 is only available.. https://code.google.com/p/squeezelite/downloads/list kllngtme's Profile: http://forums.slimdevices.com/member.php?userid=30198 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: JiveLite - cut down squeezebox control application
Hello Triode and everybody, I am trying set up a notebook as a stand alone music center using LMS, Squeezelite and Jivelite. I don't listen to internet radios so both wired and wireless interfaces are down. LMS and Squeezelite (as local player) start and run both perfectly. However when I launch Jivelite, it is unable to find the player: After 'Scanning for Players' has timed out, screen 'Choose Player' displays option 'Set Up Receiver' which does nothing. Coming back to 'Home' and choosing again 'Choose Player' displays nothing (screen is empty). If I activate the wireless interface Squeezelite appears as an option on screen 'Choose Player' straight after the interface is up and then everything works fine. However activating the wired interface alone does not enable Jivelive in finding the player. How or what can I do so that Jivelite connects to Squeezelite when only the loopback interface is up ? Thanks a lot in advance for any help ! pierreh's Profile: http://forums.slimdevices.com/member.php?userid=56559 View this thread: http://forums.slimdevices.com/showthread.php?t=98156 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Triode wrote: Try it now - I think you should not be able to have multiple items. I've also taken out the addition of noauto,x-systemd.automount to the default options of remote file systems to see if it works connecting to them at boot. OK, you can now add both a NFS and CIFS share. The correct mounts are made as show by journalctl: Code: [root@alarm soa-aur]# journalctl -f -- Logs begin at Sun 2014-07-13 17:02:10 BST. -- Jul 14 17:30:36 alarm systemd[1]: Started RPC security service for NFS server. Jul 14 17:30:36 alarm systemd[1]: Started RPC security service for NFS client and server. Jul 14 17:30:36 alarm sudo[22124]: pam_unix(sudo:session): session closed for user root Jul 14 17:30:36 alarm sudo[22127]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/mount -t nfs -o ro 192.168.0.20:/media/allmusic/Test /mnt/disk1 Jul 14 17:30:36 alarm sudo[22127]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:30:36 alarm kernel: RPC: AUTH_GSS upcall timed out. Please check user daemon is running. Jul 14 17:30:37 alarm sudo[22127]: pam_unix(sudo:session): session closed for user root Jul 14 17:30:37 alarm sudo[22154]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/cp /tmp/config.tmp-luagui /etc/fstab Jul 14 17:30:38 alarm sudo[22154]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:30:38 alarm sudo[22154]: pam_unix(sudo:session): session closed for user root Jul 14 17:31:24 alarm sudo[25124]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/cp /tmp/config.tmp /etc/credentials/cifs-mnt-disk2 Jul 14 17:31:24 alarm sudo[25124]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:31:24 alarm sudo[25124]: pam_unix(sudo:session): session closed for user root Jul 14 17:31:25 alarm sudo[25127]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/chown root.root /etc/credentials/cifs-mnt-disk2 Jul 14 17:31:25 alarm sudo[25127]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:31:25 alarm sudo[25127]: pam_unix(sudo:session): session closed for user root Jul 14 17:31:25 alarm sudo[25131]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/chmod 600 /etc/credentials/cifs-mnt-disk2 Jul 14 17:31:25 alarm sudo[25131]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:31:25 alarm sudo[25131]: pam_unix(sudo:session): session closed for user root Jul 14 17:31:26 alarm sudo[25136]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/mount -t cifs -o defaults,_netdev,credentials=/etc/credentials/cifs-mnt-disk2 //192.168.0.50/archdata /mnt/disk2 Jul 14 17:31:26 alarm sudo[25136]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:31:26 alarm sudo[25136]: pam_unix(sudo:session): session closed for user root Jul 14 17:31:27 alarm sudo[25148]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/cp /tmp/config.tmp-luagui /etc/fstab Jul 14 17:31:27 alarm sudo[25148]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 14 17:31:27 alarm sudo[25148]: pam_unix(sudo:session): session closed for user root The correct entries are made in /etc/fstab: Code: [root@alarm soa-aur]# cat /etc/fstab # # /etc/fstab: static file system information # # file system dir type options dump pass # start added by soa-web 192.168.0.20:/media/allmusic/Test /mnt/disk1 nfs4ro 0 0 //192.168.0.50/archdata /mnt/disk2 cifs defaults,_netdev,credentials=/etc/credentials/cifs-mnt-disk20 0 # end added by soa-web Shares reconnect on reboot: '[image: http://s11.postimg.org/5z71m6z2n/soa28.jpg]' (http://postimg.org/image/5z71m6z2n/) Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Triode, A couple of other questions re: the actions triggered on the stoarge page: 1. Removing a CIFS mount does not remove the associated credentials file - should it? 2. First time you add a NFS additional services are enabled and started. If another new NFS is added the same services are enabled and started again. Or, if the first NFS mount is removed and then added again same extra services are enabled and started again. Does this matter? 3. Using a NFS share can result in this timeout message appearing in journalctl: Code: [root@alarm credentials]# journalctl | grep AUTH_GSS upcall timed out Jul 13 17:26:40 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 13 17:29:00 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 13 20:34:04 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 13 21:06:23 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 13 21:48:56 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 13 22:18:38 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 13 22:30:32 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 14 17:30:36 alarm kernel: RPC: AUTH_GSS upcall timed out. This appears related to arhclinux wiki entry on nfs and the need for Clients with a kernel version prior to 3.12.7-2 (the current linux-lts for example) MUST start rpc-gssd.service to avoid an approx 15 seconds delay with an accompanying error in dmesg that reads, RPC: AUTH_GSS upcall timed out due to a kernel bug. 4. When selecting mount type nfs, the share should not be mounted as nfs4 as it currently is. An NFs mount should default to vers=3. Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: JiveLite - cut down squeezebox control application
pierreh wrote: Hello Triode and everybody, I am trying set up a notebook as a stand alone music center using LMS, Squeezelite and Jivelite. What OS are you using? You could either turn media sensing off, so the IP stack stays active even though there's no ethernet cable plugged in, or install / configure a loopback interface. Liam liam.whiteside's Profile: http://forums.slimdevices.com/member.php?userid=14546 View this thread: http://forums.slimdevices.com/showthread.php?t=98156 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: JiveLite - cut down squeezebox control application
liam.whiteside wrote: What OS are you using? You could either turn media sensing off, so the IP stack stays active even though there's no ethernet cable plugged in, or install / configure a loopback interface. Liam I am using Debian Jessie. The loopback interface is running. pierreh's Profile: http://forums.slimdevices.com/member.php?userid=56559 View this thread: http://forums.slimdevices.com/showthread.php?t=98156 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Krisbee wrote: Triode, 1. Removing a CIFS mount does not remove the associated credentials file - should it? Should now be fixed. 2. First time you add a NFS additional services are enabled and started. If another new NFS is added the same services are enabled and started again. Or, if the first NFS mount is removed and then added again same extra services are enabled and started again. Does this matter? I'm not sure this is a concern - let me know if you find a problem. 3. Using a NFS share can result in this timeout message appearing in journalctl: Code: [root@alarm credentials]# journalctl | grep AUTH_GSS upcall timed out Jul 13 17:26:40 alarm kernel: RPC: AUTH_GSS upcall timed out. Jul 14 17:30:36 alarm kernel: RPC: AUTH_GSS upcall timed out. This looks harder to work around as the suggested target can't be enabled on its own (so we would need to start it from another service?) 4. When selecting mount type nfs, the share should not be mounted as nfs4 as it currently is. An NFs mount should default to vers=3. The web interface is correctly passing the type selected to mount - are you suggesting the case when no type is specified? If so the behaviour will be whatever mount does... Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeezelite - a small headless squeezeplay emulator for linux (alsa only)
Hello, I run out of idea, I've installed squeezelite on various linux and it always went all right but now I'm stuck. My plan is to install squeezelite on my cubox with debian. It plays wonderfully with flacs and mp3, web radios but after a few minutes I have no music. On LMS everything seems to play normally but no sound ! Same configuration on cubox Archlinux, Squeezelite plays perfectly. I don't want to stay on Archlinux because SQ is not as good as with debian but debian doesn't want to play more than 20 minutes... my command : ./squeezelite-armv6hf -o hw:CARD=S20 -n cubox -f /var/log/squeezelite.log -z but I have no log when the cubox becomes dumb I've tried to compile my version of squeezelite, same issue Tried to use volumio as a OS and add squeezelite... same issue (I understand that volumio is based on debian) With archlinux, no problem Please can someone help MyNaim's Profile: http://forums.slimdevices.com/member.php?userid=37113 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Triode wrote: Should now be fixed. I'm not sure this is a concern - let me know if you find a problem. This looks harder to work around as the suggested target can't be enabled on its own (so we would need to start it from another service?) The web interface is correctly passing the type selected to mount - are you suggesting the case when no type is specified? If so the behaviour will be whatever mount does... Please look again at the image and /etc/fstab as posted above in #278 . The share was type select was NFS, but it is mounted as NFS4, Surely that's an error? Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Krisbee wrote: Please look again at the image and /etc/fstab as posted above in #278 . The share was type select was NFS, but it is mounted as NFS4, Surely that's an error? I'm reasonably sure I am passing the selected type to mount, but then it stores and displays what mount returns. Can you run soa-web.lua manually with --debug and see what it is doing? (killall luajit then start it manually from the command line with --debug) Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Triode wrote: I'm reasonably sure I am passing the selected type to mount, but then it stores and displays what mount returns. Can you run soa-web.lua manually with --debug and see what it is doing? (killall luajit then start it manually from the command line with --debug) Running soa-web.lua manually with --debug. Data entered on screen was: Code: Mountpoint: /mnt/disk1 Network Share: 192.168.0.20:/media/allmusic/Test Type: nfs Options: ro Debug output when a NFS share is added: Code: D 2014/07/14 21:12:01] execute: sudo systemctl enable nfs-client.target [D 2014/07/14 21:12:05] execute: sudo systemctl start nfs-client.target [D 2014/07/14 21:12:06] capture: sudo mount -t nfs -o ro 192.168.0.20:/media/allmusic/Test /mnt/disk1 [D 2014/07/14 21:12:07] capture: mount [D 2014/07/14 21:12:07] execute: sudo cp /tmp/config.tmp-luagui /etc/fstab [D 2014/07/14 21:12:07] execute: rm /tmp/config.tmp-luagui [D 2014/07/14 21:12:07] wrote and updated fstab [D 2014/07/14 21:12:07] capture: mount [S 2014/07/14 21:12:08] [web.lua] 200 OK POST /storage.html (192.168.0.20) 6422ms the output from mount includes this: Code: 192.168.0.20:/media/allmusic/Test on /mnt/disk1 type nfs4 (ro,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.204,local_lock=none,addr=192.168.0.20) and /etc/fstab is this: Code: [root@alarm ~]# cat /etc/fstab # # /etc/fstab: static file system information # # file system dir type options dump pass # start added by soa-web 192.168.0.20:/media/allmusic/Test /mnt/disk1 nfs4ro 0 0 # end added by soa-web Note NFS is mounted as NFS4. Only when vers-3 is entered as an option do you actaully get a nfs mount when you select share type nfs. Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Krisbee wrote: Running soa-web.lua manually with --debug. Data entered on screen was: Code: Mountpoint: /mnt/disk1 Network Share: 192.168.0.20:/media/allmusic/Test Type: nfs Options: ro Debug output when a NFS share is added: Code: D 2014/07/14 21:12:01] execute: sudo systemctl enable nfs-client.target [D 2014/07/14 21:12:05] execute: sudo systemctl start nfs-client.target [D 2014/07/14 21:12:06] capture: sudo mount -t nfs -o ro 192.168.0.20:/media/allmusic/Test /mnt/disk1 [D 2014/07/14 21:12:07] capture: mount [D 2014/07/14 21:12:07] execute: sudo cp /tmp/config.tmp-luagui /etc/fstab [D 2014/07/14 21:12:07] execute: rm /tmp/config.tmp-luagui [D 2014/07/14 21:12:07] wrote and updated fstab [D 2014/07/14 21:12:07] capture: mount [S 2014/07/14 21:12:08] [web.lua] 200 OK POST /storage.html (192.168.0.20) 6422ms the output from mount includes this: Code: 192.168.0.20:/media/allmusic/Test on /mnt/disk1 type nfs4 (ro,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.204,local_lock=none,addr=192.168.0.20) and /etc/fstab is this: Code: [root@alarm ~]# cat /etc/fstab # # /etc/fstab: static file system information # # file system dir type options dump pass # start added by soa-web 192.168.0.20:/media/allmusic/Test /mnt/disk1 nfs4ro 0 0 # end added by soa-web Note NFS is mounted as NFS4. Only when vers-3 is entered as an option do you actaully get a nfs mount when you select share type nfs. Ok so it is doing what I expected. So this questions do we need separate nfs and nfs4 types, can we just leave it to the user to specify the type as an option field? Why are there different mount.nfs and mount.nfs4 if they both do nfs4 by default? I dont use nfs so really looking for what an nfs user would want if the default operation of mount is nfs4? Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: Squeeze on Arch - developer version
Triode wrote: Ok so it is doing what I expected. So this questions do we need separate nfs and nfs4 types, can we just leave it to the user to specify the type as an option field? Why are there different mount.nfs and mount.nfs4 if they both do nfs4 by default? I dont use nfs so really looking for what an nfs user would want if the default operation of mount is nfs4? It's true that currently if you select type nfs4 but specifiy vers=3 as an option you also end up with a NFS mount. It seems to me there are two obvious webui design choices here. 1. You have a only one nfs type in the drop down selection. It should be labeled nfs but the storage page help must say this will default to NFS4 unless the user enters the option vers=3 or 2. You leave both nfs and nfs4 as selectable share types and ensure when the user selects nfs as the share type the option vers=3 is added to the mount command and /etc/fstab entry in the background. I would argue the second is preferable as the on screen selectable share type choices are immediately obvious to the user who may know little about possible nfs options, but at least knows there's a difference between nfs and nfs4 and which version is running on their nfs server. Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
