[[Support] Josh5 - Steam (Headless)]

21 minutes ago, Josh.5 said:

It's not vnc that is the issue. It is the Xserver. Your other containers are running a framebuffer Xserver. But they do not support GPU acceleration. This container is running an X11 server that supports your GPU, so it needs exclusive access to that hardware. If anything else is using that hardware, it will not start.
When you show me the X server log I'll have a better idea.
Take a look at the logs in /var/log/supervisor

Oh well that might be it. I have one GPU and it's being used sometimes by Plex .. maybe that's the case?

I've restarted Unraid and it's working again so I'll see if maybe when Plex starts transcoding it'll die out which forces me to restart the server.

It doesn't look like i have any log in supervisor though..

 

[[Support] Josh5 - Steam (Headless)]

9 hours ago, Josh.5 said:

12 hours ago, HellraiserOSU said:

Hello! I am back to having this error... clean install too.. I deleted app_data for steam headless
 

2022-01-29 17:58:16,090 INFO spawned: 'novnc' with pid 1502022-01-29 17:58:16,091 INFO spawned: 'x11vnc' with pid 1512022-01-29 17:58:16,091 INFO spawned: 'desktop' with pid 1522022-01-29 17:58:16,099 INFO reaped unknown pid 169 (exit status 0)2022-01-29 17:58:16,113 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:17,083 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:17,087 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,087 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,088 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,093 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,093 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:17,186 INFO spawned: 'desktop' with pid 3122022-01-29 17:58:17,195 INFO reaped unknown pid 317 (exit status 0)2022-01-29 17:58:17,209 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:18,250 INFO spawned: 'x11vnc' with pid 3292022-01-29 17:58:19,257 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:19,258 INFO spawned: 'desktop' with pid 3302022-01-29 17:58:19,258 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:19,259 INFO spawned: 'x11vnc' with pid 3312022-01-29 17:58:19,268 INFO reaped unknown pid 336 (exit status 0)2022-01-29 17:58:19,280 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:20,266 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:20,266 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:21,095 INFO spawned: 'x11vnc' with pid 3482022-01-29 17:58:22,105 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:22,106 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:23,109 INFO spawned: 'x11vnc' with pid 3492022-01-29 17:58:23,110 INFO spawned: 'desktop' with pid 3502022-01-29 17:58:23,121 INFO reaped unknown pid 355 (exit status 0)2022-01-29 17:58:23,136 INFO exited: desktop (exit status 1; not expected)2022-01-29 17:58:23,866 INFO gave up: desktop entered FATAL state, too many start retries too quickly2022-01-29 17:58:24,116 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:24,117 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:25,120 INFO spawned: 'x11vnc' with pid 3672022-01-29 17:58:26,127 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:26,128 INFO exited: x11vnc (exit status 1; not expected)2022-01-29 17:58:27,130 INFO spawned: 'x11vnc' with pid 3682022-01-29 17:58:28,137 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2022-01-29 17:58:28,138 INFO exited: x11vnc (exit status 1; not expected)

 

 
I am running as host..

 
I've tried secondary display, :0 as  display ID, changing WebUi to a different port..

 
I can't get it to run again..
 
--Update--
Opening Desktop.err.log I'm getting
 
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'
 

Changing to a different number gave the same error
and changing it to :0 gave the same
xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused

Is xorg starting?

Hmm how would I know that?

I have no problems with VNC on VMs and other containers such as krusader and calibre

[[Support] Josh5 - Steam (Headless)]

Hello! I am back to having this error... clean install too.. I deleted app_data for steam headless

 

2022-01-29 17:58:16,090 INFO spawned: 'novnc' with pid 150
2022-01-29 17:58:16,091 INFO spawned: 'x11vnc' with pid 151
2022-01-29 17:58:16,091 INFO spawned: 'desktop' with pid 152
2022-01-29 17:58:16,099 INFO reaped unknown pid 169 (exit status 0)
2022-01-29 17:58:16,113 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:17,083 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:17,087 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,087 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,088 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,093 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,093 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:17,186 INFO spawned: 'desktop' with pid 312
2022-01-29 17:58:17,195 INFO reaped unknown pid 317 (exit status 0)
2022-01-29 17:58:17,209 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:18,250 INFO spawned: 'x11vnc' with pid 329
2022-01-29 17:58:19,257 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:19,258 INFO spawned: 'desktop' with pid 330
2022-01-29 17:58:19,258 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:19,259 INFO spawned: 'x11vnc' with pid 331
2022-01-29 17:58:19,268 INFO reaped unknown pid 336 (exit status 0)
2022-01-29 17:58:19,280 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:20,266 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:20,266 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:21,095 INFO spawned: 'x11vnc' with pid 348
2022-01-29 17:58:22,105 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:22,106 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:23,109 INFO spawned: 'x11vnc' with pid 349
2022-01-29 17:58:23,110 INFO spawned: 'desktop' with pid 350
2022-01-29 17:58:23,121 INFO reaped unknown pid 355 (exit status 0)
2022-01-29 17:58:23,136 INFO exited: desktop (exit status 1; not expected)
2022-01-29 17:58:23,866 INFO gave up: desktop entered FATAL state, too many start retries too quickly
2022-01-29 17:58:24,116 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:24,117 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:25,120 INFO spawned: 'x11vnc' with pid 367
2022-01-29 17:58:26,127 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:26,128 INFO exited: x11vnc (exit status 1; not expected)
2022-01-29 17:58:27,130 INFO spawned: 'x11vnc' with pid 368
2022-01-29 17:58:28,137 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-01-29 17:58:28,138 INFO exited: x11vnc (exit status 1; not expected)

 

I am running as host..

 

I've tried secondary display, :0 as  display ID, changing WebUi to a different port..

 

I can't get it to run again..

 

--Update--

Opening Desktop.err.log I'm getting

 

ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':55'

 

Changing to a different number gave the same error

and changing it to :0 gave the same

xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused
xrdb: Can't open display ':0'
Unable to init server: Could not connect: Connection refused
ln: failed to create symbolic link '/etc/alternatives/desktop-background': Permission denied
xrdb: Connection refused

[[Support] Josh5 - Steam (Headless)]

18 hours ago, Josh.5 said:

No, the hostname param will do nothing to solve this. However, you should be running the container on the host network.

If you are running into issues, please first make sure you are using the most up-to-date template published in the CA store. Also be sure to follow through the setup guide in the first post of this forum thread.

 

Hmm so I didn't do anything and it seems to be working again. It asked me to reboot again because of new nvidia drivers..  And I tried rebooting the server before and still got the same error.. so maybe the new nvidia drivers fixed it? I dunno

[[Support] Josh5 - Steam (Headless)]

On 1/11/2022 at 4:51 PM, Sqibble said:

Going over the logs I found some things referring to localhost.

 

in /mnt/user/appdata/steam-headless/.cache/xorg.err there's:

tcpserver: fatal: temporarily unable to figure out IP address for localhost: network unreachable

 

and in /mnt/user/appdata/steam-headless/.cache/x11vnc.err:

10/01/2022 17:41:06 x11vnc version: 0.9.16 lastmod: 2019-01-05  pid: 185
10/01/2022 17:41:06 XOpenDisplay(":0") failed.
10/01/2022 17:41:06 Trying again with XAUTHLOCALHOSTNAME=localhost ...

 

This led me to reconsider my network settings. I had the container set to use br0, changed it to host and changed the extra parameter --hostname='steam-headless' to my device's hostname. And now it boots. Not sure why it didn't work for me using br0 but I don't think the problem is with your container.

 

 So thanks for your time and sorry for wasting it 😅

HI there!
So I'm getting this same issue now.. I wasn't before and I don't know what changed.

When you say you changed hostname to device hostname, which do you mean? like if my unraid server was named bosh should i change it to --hostname='bosh'  ?

Thanks for any help!

[[Support] ich777 - Gameserver Dockers]

7 hours ago, ich777 said:

Container fixed, please force an update from the container and it should now work properly.

Awesome thank! that did it

[[Support] ich777 - Gameserver Dockers]

Hi there!

I'm getting a clean version of Neverwinter Nights server.. but it's giving me this error

 

--NWN:EE Dedicated Server not found, installing v8193.34!---
---NWN:EE Dedicated Server not found, installing v8193.34!---
---Something went wrong, can't download NWN:EE Dedicated Server, putting server in sleep mode---

 

is there something that needs to be updated? Thanks!

[[Plugin] Nvidia-Driver]

So far so good.. I haven't rebooted the server but things look good.

Using the miner's headless ghost plug I also turned on IOMMU.. which is different for all boards of course.

https://us.informatiweb.net/tutorials/it/bios/enable-iommu-or-vt-d-in-your-bios.html

Looks like it's been solid for two days.

[[Plugin] Nvidia-Driver]

I tried one of the headless ghosts that was made for miners. Took about 10 mins and the GPU disappeared..  Removed GPUstats AND I turned on IOMMU and now it seems... stable? Well it's lasted longer then 5 minutes.. it's going on a half hour now. So usually when it fails it fails in the first 5 minutes.  Fingers crossed I don't have to reboot for a while.

[[Plugin] Nvidia-Driver]

8 minutes ago, ich777 said:

I would recommend something like this: Click or Click

 

These two are actually emulating a Display and "certified" for mining, I think those should work with your card.

 

I think those LHR cards are causing problems on headless servers.

OK will try them.. It'll be here Sunday

[[Plugin] Nvidia-Driver]

1 hour ago, ich777 said:

What Dummy Device did you buy?

There are different models out there, some even transmit EDID and I think that's such a device that you actually need for your card to get it working or at least to keep it working.

These two

https://www.amazon.com/gp/product/B077CY48RB/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

[[Plugin] Nvidia-Driver]

On 11/23/2021 at 8:37 AM, HellraiserOSU said:

 

It is mining limited and after overnight leaving it plugged in with the monitor on, it's still working. I'll let you know on the ghost plug outcome.

I plugged in both an HDMI and DisplayPort headless ghost dongle.. both failed.. back to having the video card disappear .. 

[[Plugin] Nvidia-Driver]

7 hours ago, ich777 said:

Yes, maybe buy a dummy HDMI plug and please report back if this is working.

Really curious to see if this solves the issue.

Maybe you have a card with a mining limiter and something needs to be plugged in to a monitor output port and that causes the issue.

 

Thank you for the updates!

 

It is mining limited and after overnight leaving it plugged in with the monitor on, it's still working. I'll let you know on the ghost plug outcome.

[[Plugin] Nvidia-Driver]

OK, so this seems to be it.

As long as I have the monitor plugged in and on, it's fine.

After a minute or so when I turn off the monitor, those RmInitAdapter errolr happens.. and when I turn the monitor back on, nothing comes back on the screen.

So maybe it has something to do with how it goes to sleep and can't wake itself up? Maybe I will order that headless ghost plugin and try.

[[Plugin] Nvidia-Driver]

OK so it happened again and I think I know why. When the setup runs headless, this happens.
 

I just had my HDMI cable in my video card and it was working fine for a few days. Today I'm building a pfsense router and i took out the HDMI cable to plug it in to my pfsense box. That's when unraid starts giving the can't init adapter error and the nvidia card disappears.

 

I might just buy one of those HDMI ghost plugs to see if that works, but I think if there's nothing plugged into the RTX 3060 Ti,  after a little it'll just fail to be detected.

 

Nope... it's happening even with it plugged in.. i give up.

 

OK Maybe it's because I turned off the monitor.. I'm keeping the  monitor on to see if it stays working....  So far so good..

[ComiXed-Docker Support Thread]

On 11/20/2021 at 9:41 AM, poobahuk said:

I have.... Had to manually point it at the folder within the app for it to find the files, no automatic import. No files get moved until you hit 'consolidate', and then it drops all files into the library folder.

Ah yes that did it. When I did this I was able to import. Thanks!
 

[[Plugin] Nvidia-Driver]

On 7/21/2021 at 1:07 AM, ich777 said:

Put these lines in your /boot/config/go file on the bottom and reboot to enable it:

# Enable persistenced mode for Nvidia cards
nvidia-persistenced

 

That's really strange but eventually it's doing it over your iGPU (if you have one).

 

So I finally fixed my RTX 3060 Ti disappearing by just buying a damn new computer Went with an Asrock X570 and an AMD 5950X and now it all works.. Maybe it was just some hardware issue. but it's nice to be able to use this now without it disappearing

[ComiXed-Docker Support Thread]

Has anyone imported comics into this? I tried and can't seem to do it. I even put the files in the incoming directory and nothing shows up in the import screen. Thanks!

[[Support] selfhosters.net's Template Repository]

On 7/19/2021 at 1:33 AM, davidjmorin said:

 

You ever get this working?  I have the same issue

 

Oh God I did..

I can't remember what I did..

I know I changed to MS SQL Server as the database... I think that was part of it..  I can't remember and searching my one note docs, I didn't write anything down sorry. If I remember I'll let you know

 

[[Plugin] Nvidia-Driver]

On 7/19/2021 at 2:57 AM, Caennanu said:

@HellraiserOSU i seem to be having the exact same issue. multi GPU system however. and i have it on one of my GT710's i use to passthrough to VM's (i have 2x GT710 and 1x GTX1050ti, the 1050 is used for transcoding in dockers. And then we have AST onboard graphics to boot up unraid).

 

Have you found anything usefull? 

i'm only getting the error when trying to open up the nvidia driver plugin and the assigned VM is not started.

When i start the specific VM, i get the following 'statement': vfio-pci 0000:42:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x3f00, but the VM will boot without issues and is able to use the card.

I have not sorry. I'm not AS worried about it now since we don't go out as much so I only use Plex when we are out of the house and use Kodi for when we are inside and just do direct play.  All my TVs have NVIDIA Shields so they can play pretty much anything as is.

 

I only have a single GPU in my setup not counting the intel GPU. I can try to put in a GTX 980. I'll have to see if I can find the extra power cable and try that.. or the RTX 3080.. but I'm guessing i'll run into the same thing

[[Plugin] Nvidia-Driver]

On 7/13/2021 at 7:20 AM, ich777 said:

Sorry I really can't help with this since I think there is somewhere a setting that prevents the card from working correctly.

Have you already tried to enable persistenced mode?

 

Are you now booted with Legacy or UEFI mode?

 

Have you tried if hardware transcoding is working or not? Was it working?

 

Isn't this the wrong smiley?

 

Persistence mode? What is that?

I am booting in Legacy.

Hardware transcode... it say in Plex it's using hardware transcoding even if it's not finding the NVIDIA card..

I'm a developer and I do hardware.. I'm used to things not working at times when they do so I just smile and move on

[[Plugin] Nvidia-Driver]

4 hours ago, ich777 said:

Just a guess but could it be that you have one of the newer cards that have a mining limiter and you actually have to plugin in a monitor since otherwise it believes it's used for mining?

This is really just a wild guess but the only thing that comes in my mind.

 

Does it work until now?

 

I didn't touch the UI until this morning.
Went through the logs and saw nothing out of the ordinary.
As soon as I clicked on NVIDIA Driver in the plugins

No devices found.

RmInitAdapter failed!  appears in the logs.

I'm about ready to give up

[[Plugin] Nvidia-Driver]

11 hours ago, ich777 said:

Can you try to attach a monitor to the Nvidia card, is the iGPU set to the primary graphics card?

OK right now i have the monitor attached to the NVIDIA card.. iGPU is set as primary in the graphics card..

I rebooted and so far it's OK.. i have a feeling it isn't because of plugging into the HDMI but I could be wrong,
I also removed gpu statistics plugin.
It seemed after I booted up if I go to the Dashboard or NVIDIA plugin page it would do that init fail message.. so far so good but we'll see 

[[Plugin] Nvidia-Driver]

9 hours ago, ich777 said:

This is really strange...

Have you already tried to boot into Legacy mode?

 

How long did it work before?

What kind of power supply did you own?

 

Have you got a second PCIe socket where you can put the card in?

 

Seems like the card has fallen from the bus, is a monitor attached to the card?

 

It is booting in Legacy mode.

It worked i think for a day before.. I wasn't really monitoring it..

I own a 750W power supply.

Nothing in a second PCIe slot

No monitor attached.. it's headless. When I do plugin a monitor it's in the motherboard HDMI plug to use the intel GPU.

 

[[Plugin] Nvidia-Driver]

Well I thought it was fixed, but now it's back to this. Server hasn't been rebooted in 3 days.. Guess will keep digging 

 

 

Edit - did a server reboot and it appeared in the installed GPU for a second and then it goes with the RmInitAdapter failed errors.