BennyD

Members
  • Posts

    52
  • Joined

  • Last visited

Posts posted by BennyD

  1. On 6/16/2023 at 7:40 PM, Johnny T said:

    Thanks. My only reservation (that I read) was that you needed to use SM motherboards etc inside their cases? Not 100% sure if this is true or not but that is a potential reservation I have. Thanks again for all your help and advice 🙂

    Sorry, haven't logged in and didn't see a notification, you can use almost any motherboard in these chassis'. EATX, ATX, MATX, I think even DTX and ITX, you can put MB standoffs in a ton of places.

  2. Hey guys! I left unRAID a while back to play with some other systems, I have came back as of 6.12.1 and thought I had properly set things up, however it seems that even though I have my main share set to 30% minimum free space, it is still filling all of my drives to full. I will attach some screenshots.

     

    Anyone able to give me a hand to point out what I've done wrong and what I need/can do to fix my issue?

    share.png

    disks.png

  3. Yes, a 24 bay IMO is better than the 36's because you can fit a full sized GPU in them. If you get a 36 bay, 12 of the drive bays are in the back of the chassis and that puts the motherboard tray above those 12 drives therefor making the motherboard "compartment" only a 2U section. So you won't be fitting a full sized GPU in there, and you will only have a handful of options that would be worth even having in there.... 


    I am telling you from experience, I bought a SuperMicro 36 bay 4U chassis and wish I would have only gotten a 24, simply because I would like to be able to fit a full sized GPU in it.

    Other than that, I would highly recommend one of the SuperMicro's... I got mine from The Server Store for around $600 shipped. It has 36 hot swap bays. You can buy a barebones chassis, just the chassis with PSU's... Check em out, if you have any other questions, feel free to shoot me a private message.

  4. 2 minutes ago, ich777 said:

    This is really strange, it should perform „better“ throught the direct path than the FUSE path.

    Anyways, glad it is now working!

     

    Make sure that you forwrd the right port in your router with the right protocol (UDP).

     

    Then it should show up.

     

    All good now... Just need to customize everything to our liking! Thanks for your time! Keep up the great working on these game servers... It's great to have access to these containers! 

    • Like 1
  5. 9 minutes ago, ich777 said:

    Yes, I asked on the Discord and nobody really knows...

    Even a users stated that it works fine on his Unraid server (i9-9900k).

    Nobody really wants to help because I run it through WINE but from what I saw on their GitHub Linux servers should be also available soon.

     

    Well I've gotten it working... I just changed it from /mnt/cache/appdata/vrising/ to /mnt/user/appdata/vrising/... I have my appdata folder set to use my nvme drive, so it doesn't need to be linked to /mnt/cache/ it needed to be linked to /mnt/user/appdata/ for me to have it working.

     

    Now if only I could get it to show up in the list of servers lol I can connect direct through WAN IP but it doesn't show up in the list of games

  6. 3 minutes ago, ich777 said:

    This is really strange...

    I can only assume that there is a CPU issue but I'm not too sure, on my i5-10600 the dedicated server runs just fine.

    You are having the exact same issue as @f.lim.

     

    Do you have a cache drive installed, can you send a screenshot from your Docker template?

     

    Sure thing! 

    I use a couple of your other containers with no issues, maybe it's a WINE thing.

    disks.png

    vrising.png

  7. Thanks for the response, I’ve not noticed my ram usage above 30%, ever, that’s why I’m kind of confused as to what’s happening. I’ll have to attach a new diagnostics tomorrow, apparently it didn’t like me using my iPhone to save and upload them. I won’t be back to the pc until tomorrow morning.

  8. I think actually I was, I just changed it. Will see if that fixes the issue, but it's been setup the same exact way for I don't know how many months. 64GB of ram, figured that was plenty. I will see if the issue remains, thanks a lot!

  9. I know some of these have been posted, FCP says to make a post and upload a diagnostics.

     

    This just started happening 2 days ago, I haven't made any changes other than updating docker containers in months, been running for quite a few months with no issues until a couple of days ago.  Any help would be much appreciated. I rebooted hoping it would just fix itself but I knew better and it's happening again, so I am here to post my diags. 

     

    Thanks in advance!

     

    biohazard-diagnostics-20220401-0032.zip

  10. On 1/3/2022 at 1:25 PM, ich777 said:

    Wait, you are trying to connect over the internet from what I see, is NAT reflection working or did you try this from your local network?

     

    Have you yet tried to connect through your LAN? I would also recommend that you double check the port forwarding and the protocols.

     

    After removing the Steamcmd and re-installing, it works fine, and you can't change the IP in the config file from 0.0.0.0 to your LAN IP or it breaks. It's working though, thanks for your time.

  11. 2 hours ago, ich777 said:

    Can you send over a screenshot from the message?

     

    I've now tried it on a fresh copy pulled from the CA App and it works flawlessly:

    screenshot3.png.79bdc6f4c0d43eec04a659185e1cd81e.png

    screenshot.thumb.png.815125d28e0892a1d200a81d0cf44104.png

    screenshot2.thumb.png.3ed28dbbfea7e66bf3f950b0c30bb2a9.png

     

    Have you also created and fille in the 'serverSteamAccount' like described in the GAME_PARAMS variable?

    grafik.thumb.png.71c8e36964f3de8403122224af28894b.png

     

    I will also push an update to the container itself shortly to update the base. DONE

     

    This is what a full startup looks on my server: theforest.log

     

     

    Here ya go, screens of everything and a log.txt

     

    game listed.png

    join game.png

    not setup correctly.png

    docker.png

     

    log.txt

  12. I seem to be having issues with The Forest... I don't what's goin on, the logs end with the following, the game is showing up but when you try to connect it says the server isn't setup correctly.
     

    Quote

    DS configurations tests: Host fail network configurations tests. Please check error log and your configuration.

    Unloading 14 unused Assets to reduce memory usage. Loaded Objects now: 62400.
    Total: 17.987501 ms (FindLiveObjects: 1.616500 ms CreateObjectMapping: 4.000500 ms MarkObjects: 12.224600 ms DeleteObjects: 0.145000 ms)

    Steam Manager Started.
    0009:fixme:ntdll:EtwEventRegister ({f72b578f-cae9-556a-01dc-b94f14b3cbd9}, 0x13f001100, 0x13f05b018, 0x13f05b038) stub.
    0009:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x13f0504be, 13) stub
    0009:fixme:ntdll:EtwEventRegister ({66f0a0b9-f747-5080-bdb9-4974c990ecd2}, 0x13f001100, 0x13f05b050, 0x13f05b070) stub.
    0009:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x13f0504dc, 19) stub
    006b:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
    006b:fixme:wbemprox:client_security_SetBlanket 000000006775DD00, 0000000011144840, 10, 0, (null), 3, 3, 0000000000000000, 0x00000000
    006b:fixme:wbemprox:client_security_Release 000000006775DD00
    0028:fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
    0028:fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
    006b:fixme:wbemprox:enum_class_object_Next timeout not supported
    0028:fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
    0028:fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
    GameServer init success. Port: 27015
    Set a LogOnAnonymous
    0067:fixme:iphlpapi:NotifyAddrChange (Handle 0x22320410, overlapped 0x22320418): stub
    Connected to Steam successfully
    The Forest Server is not VAC Secure!
    Game server SteamID:90154686102121472
    CoopSteamManager Initialize
    CoopLobby.LeaveActive instance=
    0009:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
    CoopPlayerCallbacks::BoltStartBegin CoopVoice.VoiceChannel:[UdpChannelName Voice:1]
    006f:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0540.
    InvalidCastException: Cannot cast from source type to destination type.
    at (wrapper managed-to-native) object:__icall_wrapper_mono_object_castclass (object,intptr)
    at UdpKit.UdpEvent.As[UdpEventStartDone] () [0x00000] in <filename unknown>:0
    at BoltCore.PollNetwork () [0x00000] in <filename unknown>:0
    at BoltCore.Poll () [0x00000] in <filename unknown>:0
    at BoltPoll.FixedUpdate () [0x00000] in <filename unknown>:0

    (Filename: Line: -1)

     

  13. Hey all, over the last couple of days my docker containers randomly stop responding, say's they're running, but can't access them. Also some of my shares seem to be randomly not accessible as well.

     

    Attached are my Diagnostic Logs and my Enhanced System Logs.

     

    Anyone give me a hand please? The stuff works for a period after a reboot, but it will stop working eventually.

     

    Squid had pointed me me to this

    However I'm not sure this is actually the problem, this server has been running perfectly fine for over a year until 2 days ago.

    biohazard-syslog-20211002-1652.zip biohazard-diagnostics-20211002-0353.zip

  14. 1 minute ago, itimpi said:

    It is better if you provide your system’s diagnostics zip file (obtained via Tools->Diagnostics) as this contains more information.

     

    handling of disabled disks is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the UnRaid GUI.

     

    Thanks, I had just found that.

  15. I've have done some googling, however all of the articles that I am pulling up are from around 2016 and the documents that they have linked for fixes no longer exist.

     

    I will attach my disk log info and sys logs and also the diagnostics logs

    If I need something else, please let me know. I'm terrible with this...

     

    I removed the sys logs cause Im not sure if there is info there that shouldn't be shared, I noticed an anonymous option for the diag.

     

    SMART test completed without errors it says.

     

    disk log info.txt

    biohazard-diagnostics-20210601-1737.zip