of course, its not like I am paying you... lol

 

obviously I understand that with so many things on my server it may work for you and I have something else that "bothers" it...

 

Let me know how it works for you to then see what we can try on mine. if anything write a PM to check this out more in depth.

On 6/9/2021 at 3:02 PM, ich777 said:

Then I can't help and you won't see it in luckyBackup because this is basically the default command that is run by luckyBackup with a Cron schedule.

 

But at least you can run the backups on a schedule for now this way...

 

Hey again!

I've reached out the developer of LuckyBackup on this, and we're trying to figure out what's happening.

It looks like the snapshots of the backups are created correctly, since they do appear in their correct folders. The issue seems to be the GUI itself, as it's not seeing the snapshots (or something is not informing the GUI about the snapshots)

 

If we find the cause for this, I'll let you know!

On 6/18/2021 at 1:03 PM, ich777 said:

is it possible that this happens because of Fix Common issues?

This does appear to be the case. Just got a warning about it and checked and sure enough:

 

This is the same template URL that replaced it last time. I'll be ignoring warning this time lol

Edited June 22, 20215 yr by rcm024

4 minutes ago, rcm024 said:

This is the same template URL that replaced it last time. I'll be ignoring warning this time lol

Click on Ignore Warning.

I'm using the chrome container and my chrome browser keeps crashing/restarting.  I enabled logging with --enable-logging with the additional parameter to see what  was happening. 

 

 

Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

 

To clarify, the docker doesn't restart, but I get a 'Chrome closed unexpectedly, click here to restore session' constantly. 

 

Any ideas? 

20 minutes ago, sataris said:

I'm using the chrome container and my chrome browser keeps crashing/restarting. 

Please post a screenshot from the Container log output where the error is visible, if possible also include a screenshot from the full Docker template.

 

I tried it now on a fresh installed instance and it runs flawlessly:

 

Log:

On 6/22/2021 at 11:29 AM, REllU said:

 

Hey again!

I've reached out the developer of LuckyBackup on this, and we're trying to figure out what's happening.

It looks like the snapshots of the backups are created correctly, since they do appear in their correct folders. The issue seems to be the GUI itself, as it's not seeing the snapshots (or something is not informing the GUI about the snapshots)

 

If we find the cause for this, I'll let you know!

 

I've now been in talks with the developer, and his initial thought is that there might be an issue with the file that has the info for the snapshots for GUI.

He's saying that it might be possible that since the GUI is open, said file is reserved for the GUI, and cannot be edited by UnRaid running the script.

 

Is there a way to close the GUI, while keeping the docker image running? Or is that just done by closing the remote access window?

 

Thanks in advance!

1 hour ago, REllU said:

Is there a way to close the GUI, while keeping the docker image running?

No, because otherwise the container is shutdown and the GUI must run.

 

Is it or better speaking was it working when you defined a Cron job inside the container itself so that you've saw what was synced?

 

Have you contact details from the developer?

On 6/18/2021 at 2:24 PM, ich777 said:

Thank you, will look into this after the weekend and report back, hope that's ok for you...

have you been able to check on the checkmk docker?

7 hours ago, ceyo14 said:

have you been able to check on the checkmk docker?

Not yet but it's on my todo list...

On 6/25/2021 at 3:39 PM, ich777 said:

No, because otherwise the container is shutdown and the GUI must run.

 

Is it or better speaking was it working when you defined a Cron job inside the container itself so that you've saw what was synced?

 

Have you contact details from the developer?

 

Hey again, sorry for such a slow response! Been a bit busy on my end.

 

Anyhow, here's the link to the forum post where the developer is:

 

https://sourceforge.net/p/luckybackup/discussion/873564/thread/5eba74ae4d/

 

Maybe I'll see you there?

I'm using the new Owncast plugin and discovered it now supports VA-API Hardware encoding. I added my GPU via the NVIDIA_VISIBLE_DEVICES key (all the same details I use for emby/handbrake) however I get this error in the Owncast log.

 

---Owncast v0.0.7 up-to-date---
---Preparing Server---
---Starting Server---
time="2021-06-29T12:26:19+01:00" level=info msg="Owncast v0.0.7-linux-64bit (3810ce4f63ecf7fb7a35c564af68f081c7e8b537)"
time="2021-06-29T12:26:19+01:00" level=info msg="Video transcoder started using VA-API with 1 stream variants."
time="2021-06-29T12:26:19+01:00" level=error msg="vaapi not enabled. either your copy of ffmpeg does not support it, your hardware does not support it, or you need to install additional drivers for your hardware."

time="2021-06-29T12:26:19+01:00" level=error msg="failed to set va-api device to /dev/dri/renderD128. your system is likely not properly configured for va-api"

time="2021-06-29T12:26:19+01:00" level=error msg="transcoding error. look at transcoder.log to help debug. your copy of ffmpeg may not support your selected codec of h264_vaapi https://owncast.online/docs/troubleshooting/#codecs"

Any one got this working with VA-API and the Nvidia plugin?

3 hours ago, Mr_Jay84 said:

Any one got this working with VA-API and the Nvidia plugin?

Have to look into this in the next few days.

Keep in mind that if you want to use the VA-API inside a contianer you have to pass through the device /dev/dri.

Don't forget to do a 'chmod -R 777 /dev/dri' first on the host

16 minutes ago, ich777 said:

Have to look into this in the next few days.

Keep in mind that if you want to use the VA-API inside a contianer you have to pass through the device /dev/dri.

Don't forget to do a 'chmod -R 777 /dev/dri' first on the host

I assumed just adding the variables from the Nvidia plugin would suffice. Its does mention something about FFMPEG may need to be compiled with nvenc.

4 minutes ago, Mr_Jay84 said:

I assumed just adding the variables from the Nvidia plugin would suffice. Its does mention something about FFMPEG may need to be compiled with nvenc.

Yes, it's also possible that I don't have the necessary codecs in the contianer, but I will fix that ASAP, have to first look into this, give me a few days.

12 minutes ago, ich777 said:

Yes, it's also possible that I don't have the necessary codecs in the contianer, but I will fix that ASAP, have to first look into this, give me a few days.

Excellent news! Looking forward to it! 😁

On 6/29/2021 at 5:14 PM, Mr_Jay84 said:

Excellent news! Looking forward to it! 😁

Can you please try to switch the branch to :test like this:

 

and also pass throught the path /dev/dri like this (please be sure to do a: 'chmod -R 777 /dev/dri' first on a Unraid console):

 

 

I've tried it with my Intel iGPU and it works flawlessly in the test branch Container:

On 6/28/2021 at 10:31 PM, ceyo14 said:

have you been able to check on the checkmk docker?

I tested it now on a new set up 6.9.2 machine and have no problems (can you try to turn on the advanced view in your Docker template and remove '--ulimit nofile=1024' at extra parameters):

 

Please report back if it works for you.

On 6/30/2021 at 5:08 PM, ich777 said:

Can you please try to switch the branch to :test like this:

 

and also pass throught the path /dev/dri like this (please be sure to do a: 'chmod -R 777 /dev/dri' first on a Unraid console):

 

 

I've tried it with my Intel iGPU and it works flawlessly in the test branch Container:

Dind't work on this occasion...

 

---Checking if UID: 99 matches user---
---Checking if GID: 100 matches user---
---Setting umask to 0000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---Version Check---

---Owncast v0.0.7 up-to-date---
---Preparing Server---
---Starting Server---
time="2021-07-02T03:18:53+01:00" level=info msg="Owncast v0.0.7-linux-64bit (3810ce4f63ecf7fb7a35c564af68f081c7e8b537)"
time="2021-07-02T03:18:53+01:00" level=info msg="Video transcoder started using VA-API with 1 stream variants."
time="2021-07-02T03:18:54+01:00" level=error msg="[AVHWDeviceContext @ 0x560bcc2f4980] libva: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)"

time="2021-07-02T03:18:54+01:00" level=error msg="[AVHWDeviceContext @ 0x560bcc2f4980] Failed to initialise VAAPI connection: -1 (unknown libva error)."

time="2021-07-02T03:18:54+01:00" level=error msg="Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error"

time="2021-07-02T03:18:54+01:00" level=error msg="transcoding error. look at transcoder.log to help debug. your copy of ffmpeg may not support your selected codec of h264_vaapi https://owncast.online/docs/troubleshooting/#codecs"

time="2021-07-02T03:18:54+01:00" level=info msg="RTMP is accepting inbound streams on port 1935."
time="2021-07-02T03:18:54+01:00" level=info msg="Web server is listening on port 8080."
time="2021-07-02T03:18:54+01:00" level=info msg="The web admin interface is available at /admin."

 

2 hours ago, Mr_Jay84 said:

Dind't work on this occasion...

The problem with this is that Owncast only works with VAAPI and if you are passing through a Nvidia card normally with the usual entries in the template VAAPI wouldn't work anyways because if you do so you will only have NVENC, CUDA and all the other Nvidia proprietarry things passed through to the container.

 

This would only work if you are on a dedicated machine I think with with Owncast installed.

I'll have to take a deeper look into this.

What kind of hardware are you running Unraid on?

8 hours ago, ich777 said:

The problem with this is that Owncast only works with VAAPI and if you are passing through a Nvidia card normally with the usual entries in the template VAAPI wouldn't work anyways because if you do so you will only have NVENC, CUDA and all the other Nvidia proprietarry things passed through to the container.

 

This would only work if you are on a dedicated machine I think with with Owncast installed.

I'll have to take a deeper look into this.

What kind of hardware are you running Unraid on?

I have a variety of Nvidia cars installed but the one used for the dockers is a GTX 1060 G6B
 

M/B: ASRockRack EP2C612 WS Version - s/n: 157265490000126

BIOS: American Megatrends Inc. Version P2.50. Dated: 03/22/2018

CPU: Genuine Intel® CPU @ 2.00GHz

HVM: Enabled

IOMMU: Enabled

Cache: 768 KiB, 3 MB, 30 MB, 768 KiB, 3 MB, 30 MB

Memory: 128 GiB DDR4 Multi-bit ECC (max. installable capacity 512 GiB)

Network: bond0: fault-tolerance (active-backup), mtu 1500
 eth0: 1000 Mbps, full duplex, mtu 1500
 eth1: 1000 Mbps, full duplex, mtu 1500

Kernel: Linux 5.10.28-Unraid x86_64

2 minutes ago, Mr_Jay84 said:

CPU: Genuine Intel® CPU @ 2.00GHz

I'm more interested in you Intel CPU does it have a iGPU?

If yes, you could easily use it for transcoding with VAAPI.

Unfortunately it doesn't. These are ES Xeons with no iGPU.

3 hours ago, Mr_Jay84 said:

Unfortunately it doesn't. These are ES Xeons with no iGPU.

I will loom into this but give me some time please, I will push the update for now that is working with Intel in the next few days and report back to you what my findings are in Nvidia.

1 hour ago, ich777 said:

I will loom into this but give me some time please, I will push the update for now that is working with Intel in the next few days and report back to you what my findings are in Nvidia.

No rush mate. Thank you looking into this.