RuneAudio 0.5-beta for most Raspberry Pi models

Raspberry Pi related support

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby robd » 18 Jan 2019, 12:14

Thanks. now I see.
A good hint: either start the local browser or display on the splash screen the information that one have to log in via the network.
robd
 
Posts: 7
Joined: 22 Oct 2018, 21:13

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby FlexQ » 19 Jan 2019, 18:01

Hi Guys,

And thanks alot for the release.

However, I'm a first time user, moving from volumio as it - imho sucks.

There is just a little problem:

It stays at:

RuneAudio is starting-up
The page you are looking for is temporarily unavailable
Please try again later

I have been waiting for hours on end, and rebooted 3-4 times just to ensure that it was not configuring.

However, nothing happens.

My configuration is:

External 10A analog supply
Rasp.pi. 3B+
Hifiberry dac pro+
7" official raspberry screen.
Ethernet cable connected

I downloaded the lastest release, and can ssh into the berry. I checked the /var/log/ folder, but no informaion was present in any of the files.

I have reinstalled the SD card 3 times.

Do any of you awesome dudes know what i can do to fix this?

I would very much like to try runeaudio

/Q
FlexQ
 
Posts: 8
Joined: 19 Jan 2019, 17:53

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby jlynton » 19 Jan 2019, 19:54

FlexQ wrote:
There is just a little problem:

It stays at:

RuneAudio is starting-up
The page you are looking for is temporarily unavailable
Please try again later


When booting for the first time, one should wait at least 6 minutes before using the web access, did you do this?
jlynton
 
Posts: 40
Joined: 20 May 2016, 12:53

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby FlexQ » 19 Jan 2019, 20:05

jlynton wrote:
FlexQ wrote:
There is just a little problem:

It stays at:

RuneAudio is starting-up
The page you are looking for is temporarily unavailable
Please try again later


When booting for the first time, one should wait at least 6 minutes before using the web access, did you do this?


Hi jlynton,

As written:

I have been waiting for hours on end, and rebooted 3-4 times just to ensure that it was not configuring.


So yes, the ssh connection im working on right now is 2 hrs old

Code: Select all
List of all running processes:
root        13  0.0  0.0      0     0 ?        S    07:29   0:00 [migration/1]
root        14  0.0  0.0      0     0 ?        S    07:29   0:00 [ksoftirqd/1]
root        16  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/1:0H]
root        17  0.0  0.0      0     0 ?        S    07:29   0:00 [cpuhp/2]
root        18  0.0  0.0      0     0 ?        S    07:29   0:00 [migration/2]
root        19  0.0  0.0      0     0 ?        S    07:29   0:00 [ksoftirqd/2]
root        21  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/2:0H]
root        22  0.0  0.0      0     0 ?        S    07:29   0:00 [cpuhp/3]
root        23  0.0  0.0      0     0 ?        S    07:29   0:00 [migration/3]
root        24  0.0  0.0      0     0 ?        S    07:29   0:00 [ksoftirqd/3]
root        26  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/3:0H]
root        27  0.0  0.0      0     0 ?        S    07:29   0:00 [kdevtmpfs]
root        28  0.0  0.0      0     0 ?        I<   07:29   0:00 [netns]
root        31  0.0  0.0      0     0 ?        I    07:29   0:00 [kworker/3:1]
root        33  0.0  0.0      0     0 ?        S    07:29   0:00 [khungtaskd]
root        34  0.0  0.0      0     0 ?        S    07:29   0:00 [oom_reaper]
root        35  0.0  0.0      0     0 ?        I<   07:29   0:00 [writeback]
root        36  0.0  0.0      0     0 ?        S    07:29   0:00 [kcompactd0]
root        37  0.0  0.0      0     0 ?        SN   07:29   0:00 [ksmd]
root        38  0.0  0.0      0     0 ?        I<   07:29   0:00 [crypto]
root        39  0.0  0.0      0     0 ?        I<   07:29   0:00 [kintegrityd]
root        40  0.0  0.0      0     0 ?        I<   07:29   0:00 [kblockd]
root        41  0.0  0.0      0     0 ?        I<   07:29   0:00 [md]
root        42  0.0  0.0      0     0 ?        I<   07:29   0:00 [watchdogd]
root        43  0.0  0.0      0     0 ?        I<   07:29   0:00 [rpciod]
root        44  0.0  0.0      0     0 ?        I<   07:29   0:00 [xprtiod]
root        58  0.0  0.0      0     0 ?        S    07:29   0:00 [kswapd0]
root        59  0.0  0.0      0     0 ?        I<   07:29   0:00 [nfsiod]
root        60  0.0  0.0      0     0 ?        S    07:29   0:00 [jfsIO]
root        61  0.0  0.0      0     0 ?        S    07:29   0:00 [jfsCommit]
root        62  0.0  0.0      0     0 ?        S    07:29   0:00 [jfsCommit]
root        63  0.0  0.0      0     0 ?        S    07:29   0:00 [jfsCommit]
root        64  0.0  0.0      0     0 ?        S    07:29   0:00 [jfsCommit]
root        65  0.0  0.0      0     0 ?        S    07:29   0:00 [jfsSync]
root        66  0.0  0.0      0     0 ?        I<   07:29   0:00 [xfsalloc]
root        67  0.0  0.0      0     0 ?        I<   07:29   0:00 [xfs_mru_cache]
root        78  0.0  0.0      0     0 ?        I<   07:29   0:00 [pencrypt]
root        79  0.0  0.0      0     0 ?        I<   07:29   0:00 [pdecrypt]
root        95  0.0  0.0      0     0 ?        I<   07:29   0:00 [kthrotld]
root        96  0.0  0.0      0     0 ?        I<   07:29   0:00 [iscsi_eh]
root        97  0.0  0.0      0     0 ?        I<   07:29   0:00 [dwc_otg]
root        98  0.0  0.0      0     0 ?        I<   07:29   0:00 [DWC Notificatio]
root        99  0.0  0.0      0     0 ?        I<   07:29   0:00 [raid5wq]
root       100  0.0  0.0      0     0 ?        I<   07:29   0:00 [dm_bufio_cache]
root       101  0.0  0.0      0     0 ?        I<   07:29   0:00 [kmpathd]
root       102  0.0  0.0      0     0 ?        I<   07:29   0:00 [kmpath_handlerd]
root       103  0.0  0.0      0     0 ?        S<   07:29   0:00 [vchiq-slot/0]
root       104  0.0  0.0      0     0 ?        S<   07:29   0:00 [vchiq-recy/0]
root       105  0.0  0.0      0     0 ?        S<   07:29   0:00 [vchiq-sync/0]
root       106  0.0  0.0      0     0 ?        S    07:29   0:00 [vchiq-keep/0]
root       107  0.0  0.0      0     0 ?        I<   07:29   0:00 [kstrp]
root       121  0.0  0.0      0     0 ?        S    07:29   0:00 [irq/92-mmc1]
root       122  0.0  0.0      0     0 ?        I    07:29   0:00 [kworker/2:3]
root       134  0.0  0.0      0     0 ?        S    07:29   0:00 [mmcqd/0]
root       153  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/1:1H]
root       154  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/2:1H]
root       156  0.0  0.0      0     0 ?        S    07:29   0:00 [jbd2/mmcblk0p2-]
root       157  0.0  0.0      0     0 ?        I<   07:29   0:00 [ext4-rsv-conver]
root       165  0.0  0.0      0     0 ?        S    07:29   0:00 [irq/169-usb-001]
root       166  0.0  0.0      0     0 ?        I<   07:29   0:00 [ipv6_addrconf]
root       186  0.0  0.0      0     0 ?        I    07:29   0:00 [kworker/1:2]
root       200  0.0  0.5  39352  5232 ?        Ss   07:29   0:00 /usr/lib/systemd/systemd-journald
root       213  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/3:1H]
root       214  0.0  0.5  21536  5640 ?        Ss   07:29   0:00 /usr/lib/systemd/systemd-udevd
root       215  0.0  0.0      0     0 ?        I    07:29   0:00 [kworker/3:2]
root       226  0.0  0.0      0     0 ?        S    07:29   0:00 [ft5406]
root       231  0.0  0.0      0     0 ?        I<   07:29   0:00 [cfg80211]
root       234  0.0  0.0      0     0 ?        I<   07:29   0:00 [brcmf_wq/mmc1:0]
root       235  0.0  0.0      0     0 ?        S    07:29   0:00 [brcmf_wdog/mmc1]
root       245  0.0  0.0      0     0 ?        I<   07:29   0:01 [kworker/u9:0]
root       246  0.0  0.0      0     0 ?        I<   07:29   0:00 [kworker/u9:1]
systemd+   255  0.0  0.4  10728  4184 ?        Ss   07:29   0:00 /usr/lib/systemd/systemd-resolved
root       258  0.0  0.0   1828   344 ?        Ss   07:29   0:00 /usr/bin/ifplugd -i eth0 -r /etc/ifplugd/netctl.
root       261  0.0  0.2   4832  2296 ?        Ss   07:29   0:00 /usr/bin/crond -n
dbus       262  0.0  0.2   6648  2876 ?        Ss   07:29   0:00 /usr/bin/dbus-daemon --system --address=systemd:
root       265  0.0  0.0   1868   324 ?        Ss   07:29   0:00 /usr/bin/hciattach -n /dev/ttyAMA0 bcm43xx 92160
root       266  0.0  0.4   7624  4280 ?        Ss   07:29   0:01 /usr/bin/haveged -F -w 1024 -v 1
root       267  0.1  1.8  24276 18636 ?        Ss   07:29   0:02 python /usr/share/amixer-webui/alsamixer_webui.p
avahi      269  0.0  0.2   6948  2848 ?        Ss   07:29   0:00 avahi-daemon: running [runeaudio.local]
chrony     278  0.0  0.2  13656  2968 ?        S    07:29   0:00 /usr/bin/chronyd
avahi      283  0.0  0.0   6948   296 ?        S    07:29   0:00 avahi-daemon: chroot helper
root       334  0.0  0.2   9400  2820 ?        Ss   07:29   0:00 wpa_supplicant -q -B -P /run/wpa_supplicant-wlan
root       336  0.0  0.0   1764    48 ?        Ss   07:29   0:00 wpa_actiond -p /run/wpa_supplicant -i wlan0 -P /
root       338  0.0  0.4   7020  4208 ?        Ss   07:29   0:00 /usr/bin/sshd -D
root       341  0.0  0.2  30392  2812 ?        Ssl  07:29   0:00 /usr/bin/redis-server 127.0.0.1:6379
root       347  0.0  0.1  22632  1792 ?        Ss   07:29   0:00 nginx: master process /usr/bin/nginx -g pid /run
root       348  0.0  0.2  23752  2628 ?        S    07:29   0:00 nginx: worker process
root       399  0.0  0.0   2228   208 ?        Ss   07:30   0:00 dhcpcd -4 -q -t 30 -L eth0
root       459  0.0  0.5   9828  5120 ?        Rs   07:35   0:00 sshd: root@pts/0
root       461  0.0  0.3   5336  3380 pts/0    Ss   07:35   0:00 -bash
root       478  0.0  0.0      0     0 ?        I    07:41   0:00 [kworker/u8:2]
root       483  0.0  0.0      0     0 ?        I    07:44   0:00 [kworker/1:0]
root       491  0.0  0.0      0     0 ?        I    07:56   0:00 [kworker/0:2]
root       492  0.0  0.0      0     0 ?        I    08:00   0:00 [kworker/2:1]
root       496  0.0  0.0      0     0 ?        I    08:00   0:00 [kworker/u8:1]
root       503  0.0  0.0      0     0 ?        I    08:01   0:00 [kworker/0:0]
root       507  0.0  0.0      0     0 ?        I    08:05   0:00 [kworker/2:0]
root       508  0.0  0.0      0     0 ?        I    08:06   0:00 [kworker/u8:0]
root       509  0.0  0.0      0     0 ?        I    08:06   0:00 [kworker/0:1]
root       511  0.0  0.2   7620  2772 pts/0    R+   08:07   0:00 ps aux
root       512  0.0  0.0      0     0 ?        I    08:07   0:00 [kworker/u8:3]



/Q
FlexQ
 
Posts: 8
Joined: 19 Jan 2019, 17:53

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby janui » 19 Jan 2019, 21:06

Hi All,
RuneAudio is starting-up
The page you are looking for is temporarily unavailable
Please try again later
Just refresh the browser after a minute or so.

Rune will not refresh the browser after the 'RuneAudio is starting-up' screen has been displayed. The last line of the text say's 'Please try again later', normally this works fine.

janui
User avatar
janui
 
Posts: 566
Joined: 20 Dec 2014, 12:55
Location: Ollanda

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby FlexQ » 19 Jan 2019, 21:18

Hi,

On both webpage and in the android app it is the same.

and updating the page does not help /:

Is there any debug information you could use (and tell me how to gather)?

/Q

Code: Select all

RuneOs: Experimental Beta 0.5 20180903
RuneUI: 0.5b (gearhead)
Hw-env: RaspberryPi 2 / 3


FlexQ
 
Posts: 8
Joined: 19 Jan 2019, 17:53

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby janui » 20 Jan 2019, 15:19

Hi FlexQ,
Very strange, first could you confirm that your download has the correct SHA-256 checksum. Then could you run these commands at the command prompt via SSH and post the output:
Code: Select all
pstree
systemctl status php-fpm
systemctl status rune_PL_wrk
systemctl status rune_SY_wrk
And if the output of the last command says that it has failed, then also:
Code: Select all
/srv/http/command/rune_SY_wrk
Thanks.
While your waiting for my reply you could also try booting it without the screen installed, it should not make a difference, but I am interested.
janui
User avatar
janui
 
Posts: 566
Joined: 20 Dec 2014, 12:55
Location: Ollanda

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby FlexQ » 20 Jan 2019, 16:11

janui wrote:Hi FlexQ,
Very strange, first could you confirm that your download has the correct SHA-256 checksum. Then could you run these commands at the command prompt via SSH and post the output:
Code: Select all
pstree
systemctl status php-fpm
systemctl status rune_PL_wrk
systemctl status rune_SY_wrk
And if the output of the last command says that it has failed, then also:
Code: Select all
/srv/http/command/rune_SY_wrk
Thanks.
While your waiting for my reply you could also try booting it without the screen installed, it should not make a difference, but I am interested.
janui


I'm sorry to have wasted your time Mate, but the checksum was wrong. I downloaded the same file again, flashed it, and now it works.

After 5 reflashes of the old file :s

Thanks alot for your time and effort !
FlexQ
 
Posts: 8
Joined: 19 Jan 2019, 17:53

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby evilcurt » 20 Jan 2019, 22:41

Hello everyone,

I'm a new be to this, but I was able to get everything up and running just fine after a few trial by errors.
What I would like to do is to make the album art larger and the time and volume smaller and moving them up on the HMI.
Is this possible and if so is there any instructions on how to?
Image
I really don't know anything about programing.

Thank you

Curt
evilcurt
 
Posts: 5
Joined: 19 Jan 2019, 22:24

Re: RuneAudio 0.5-beta for most Raspberry Pi models

Postby robd » 21 Jan 2019, 19:54

Hi all,
Finally ... a Pi project that works right out of the box like a charm
With a really intuitive ui
Fully functional
Easy to configure
A consistent layout over ui, dev-ui, website and forum
consisten layout and scaling over all devices and screen formats
Thank you very much and I’m going to donate.

But I still have a bit of a challenge:
My pi is in network A and my Nas is in network B and the two are connected via internet.
Connecting via NFS means opening ports, one doesn’t want to open.
So, is there an opportunity to change the nfs ports on the pi side or any other suggestion solving this problem?
Or should I go for DLNA?
Last edited by robd on 24 Jan 2019, 21:04, edited 1 time in total.
robd
 
Posts: 7
Joined: 22 Oct 2018, 21:13

support RuneAudio Donate with PayPal

PreviousNext

Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 1 guest