June 28, 201511 yr Is it available now or are you still pushing the changes? it's still warm, lol. (that means it's ready)
June 28, 201511 yr Is it available now or are you still pushing the changes? your putting an autostart in the menu, i've done that with a file copy in the first startup....
June 28, 201511 yr Got the user/pass right on my first try. mythtv/mythtv oh yeah, that changed, lol.
June 28, 201511 yr Doesn't look like the backend is starting after I provide the password. I had to start it manually.
June 28, 201511 yr Doesn't look like the backend is starting after I provide the password. I had to start it manually. yeah that doesn't work...... the whole setup routine is run by a script and the start backend command is in that script , but it wants to start as root.... yet if i use root, it still doesn't work..... also now, the damn thing doesn't work after a reboot and the permissions are all fackered up for recording... people may think setting up myth is a pig, making a docker of it makes it look like just the pig's squeal in comparision.
June 28, 201511 yr Recording and timeshift seem to be working fine (as they did before). not for me, lol... damn thing... try and see if it survives a restart...
June 28, 201511 yr Recording and timeshift seem to be working fine (as they did before). not for me, lol... damn thing... try and see if it survives a restart... The recording functionality or the backend?
June 28, 201511 yr Restarted the container and the backend did not come back up. EDIT: I logged into the RDP session again and then refreshed mythweb and it was back. Weird. Not sure if it was just delayed or my RDP session kicked something into gear. EDIT2: I restarted it again and I'll see if the backenbd comes up without my RDP'ing in.
June 28, 201511 yr OK...the backend will not start until a desktop session is initiated. I guess this makes sense. The Startup Applications group probably works like the Startup folder in windows. Anything in it will not load until someone logs in. Need to find another way sparkly.
June 28, 201511 yr try this... in the rdp window start the terminal... cd ~ make a .sh file with the following content.. #!/bin/bash until [ "$( mysqladmin -u root status 2>&1 >/dev/null | grep -ci error:)" = "0" ] do sleep 2s done /usr/bin/mythbackend --logpath /var/log/mythtv & make it executable with chmod +x , and then find the startup application for mythbackend and point it at your .sh file... the until loop waits 2 seconds if the database isn't live...
June 28, 201511 yr OK...the backend will not start until a desktop session is initiated. I guess this makes sense. The Startup Applications group probably works like the Startup folder in windows. Anything in it will not load until someone logs in. Need to find another way sparkly. yeah, that's a bloody pain.....
June 28, 201511 yr ok plan 21312312312312312312312 in the rdp terminal sudo su password is mythtv cd /etc/my_init.d nano 005-bring-up-the-backend.sh put in #!/bin/bash echo "Checking whether database(s) are ready" until [ "$( mysqladmin -u root status 2>&1 >/dev/null | grep -ci error:)" = "0" ] do echo "waiting....." sleep 2s done exec /sbin/setuser mythtv /usr/bin/mythbackend --logpath /var/log/mythtv & save out and chmod +x 005-bring-up-the-backend.sh restart the container..... see if that works.
June 28, 201511 yr try this... in the rdp window start the terminal... cd ~ make a .sh file with the following content.. #!/bin/bash until [ "$( mysqladmin -u root status 2>&1 >/dev/null | grep -ci error:)" = "0" ] do sleep 2s done /usr/bin/mythbackend --logpath /var/log/mythtv & make it executable with chmod +x , and then find the startup application for mythbackend and point it at your .sh file... the until loop waits 2 seconds if the database isn't live... That was a no go. Moving onto plan 21312312312312312312312 now
June 28, 201511 yr plan 21312312312312312312312 is a no go also. not here, lol. i missed a bit though... had to comment out the lines that put the autostart file in....
June 28, 201511 yr maybe i'm messing up setting up the storage groups because i can't record I mapped /var/lib/mythtv --> /mnt/user/PVR Then in the storage groups, I added a path for Default (that is recordings...don't know why they called it that) as: /mnt/user/PVR/recordings
June 28, 201511 yr maybe i'm messing up setting up the storage groups because i can't record I mapped /usr/lib/mythtv --> /mnt/user/PVR Then in the storage groups, I added a path for Default (that is recordings...don't know why they called it that) as: /mnt/user/PVR/recordings ahhh, that's what i buggered up, i was mapping livetv....
June 28, 201511 yr working a new build.... won't be a crash and burn build though.... just one caveat when it's done, you'll have to remove that startup application and stop the container, then do the update.... just pushing build on docker hub now.
Archived
This topic is now archived and is closed to further replies.