Jump to content

workermaster

Members
  • Posts

    241
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by workermaster

  1. Hi, 

     

    I have a problem with the Satisfactory container. I have been running multiple Satisfactory servers for a while but stopped playing the game early 2023. I have now started again with some friends since the new game update. 

     

    One of the containers is having trouble starting a lot of the time. I tried removing the container and installing it again. That does not work. Rebooting my Unraid server does seem to work most of the time, but that is not an option for me. 

     

    The logfile shows an error but closes when the container reboots. I managed to get this screenshot:
    image.thumb.png.da660014391eec7e9455bb747cae7fd2.png

     

    Trying to reinstall this container sometimes even gives me the error "can't find excecutable". My other Satisfactory container does start just fine, but this one keeps giving me trouble. 

     

    Any help would be greatly appreciated.

  2. Hi, 

     

    I am running a range of Docker containers. They have been running fine for a while but today, most of them won't start anymore. 

    Last week I upgraded to Unraid 6.12.5. I experienced some issues with a specific Docker container (not related to that update but I thought it was at first) and then decided to upgrade to 6.12.6 in hopes that my container would run again. Today almost all Docker containers broke without warning. 

     

    I am not able to start most of my containers. I can start only 3. The others get this error:

    image.png.49404e5f5eaff00489a6d848c8423c1e.png

     

    I can only start Plex, Pihole and Telegraf:
    image.thumb.png.1febfaf48da615dd2873bbf5650b0943.png

     

    I have tried to disable the Docker service and then enabling it again. It did not help. I also see a lot of errors in the system log, but don't know if these are related:

    image.thumb.png.d6b32408b78422c3c0c5937214d0f96c.png

     

    I will post the system logs and diagnostics here as well. 

     

    Any help would be greatly appreciated since I am very inexperienced with Docker errors and have no idea what to do. 

    milkyway-diagnostics-20231204-2244.zip milkyway-syslog-20231204-2145.zip

  3. 2 minutes ago, ich777 said:

    If it is still boot looping then the container isn‘t properly updated.

     

    Sorry, I‘m currently on the go and can‘t tell drom the top of my head which one you meed to change.

     

    You could also do this with a startup game parameter.

    Ah, now I see the option. I never looked at those settings in the container template. I will add the ports there. 

     

    I have also managed to connect to my server in update 8. Quite buggy but that is expected from the experimental branch. Thanks for your help!

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

    Please update the container itself.

    I pushed a update to the container yesterday to make it compatible with update 8

     

    I tested both the stable and experimental branch and both are working fine on my server.

     

    Did you also change them in the config?

    U have updated the containers and am trying to boot into the experimental one in a few minutes. My game is now updating on Steam. 

     

    What config file do I need to change? I am now scrolling through the Satisfactory folder in my appdata looking for config files. The only one that I have found now is the serverconfig. But if I open that with Notepad++, it only shows me weird data. 

     

    I don't remember chaning a config file before, but it could be that I just forgot what I did back then

  5. Hi, 

     

    I am running 2 Satisfactory servers. They both ran update 7 and different saves. Server 1 ran on the default ports, and server 2 ran on the default ports +1 (7778 instead of 7777). 

    With the release of update 8 I wanted to try and switch one over to the experimental branch. Unfortunately, the server kept bootlooping. I assumed that I did something wrong and switched it off with the intention of fixing that later and wanting to play the game. I tried booting the server that I didn't touch, but that one was also broken. I then figured out that while I had the servers running on different ports, they were using the same Satisfactory folder in my appdata. Anyway, to fix it, I decided to remove both servers and templates and then install them again. I now can't get the second server to run properly again even though nothing should be changed. 

     

    Server 1 is running just fine on the default ports;

    image.png.b73c50d6e9449128255dd0a571de25c8.png

    image.thumb.png.82c1033a2151c652bf0ec7874f1f3bdd.png

     

    I can connect to that server and play the game. 

     

    I then tried setting up the second server. 

    I installed the container. Before installing it, I changed the ports to these values;

    image.png.18790a2b884421ffc174a2eb26f4ea83.png

    image.thumb.png.82a34a98b6af068e2490e65fb6fc5945.png

    I did remove the old ports and then added these as instructed. The server seems to install correctly and boot. The logfile shows that it is tying to use the ports 7777 and 15000 even though I have changed those;

    image.thumb.png.15f41e71ff971fc1a11bc9f13527b517.png

     

    The server does not appear online in my game;

    image.png.7f742c0212b3bc2dd7e4df4eb896948c.png

     

    I checked the port forwarding, and found no issues. These ports have not changed and 2 days ago, both servers were running happily on these ports. I have been trying to get this to work again, but don't know what I can try. Everything seems to be as it was before. 

     

    Does anyone know how to fix this?

  6. Hi,

     

    I have a VM that I want to boot, and then shutdown on it's own. I got the boot part working, and got it to shutdown with the Windows task scheduler, but it doesn't always shutdown. So I want to shutdown the VM via userscripts. 

     

    Here is how I start the VM:

    image.png.2e18249e6b8d17219c64ba23ec7fd764.png

     

    Easy enough. 

    I found online that I could change it to this to get it to shutdown:

    image.png.61cea05fe4f1d873d4e5cb3b641c545c.png

     

    Now for the problem. The VM does not always shutdown on the first try. Sometimes I need to manually run the shutdown command again. 

    I would like to have the shutdown command run every 5 minutes until it notices that the VM is shutdown. Does anyone know how to do that?

     

    I am not familiar with these commands, so I don't know how to make it do that. 

  7. 45 minutes ago, Cornflake said:

    i dont think that this would make a difference. you could try creating a completly new bot and with a new token.

    I have tried making a new bot and new token a couple of times, but still get the same error. I've attached the unedited .env file here (and changed the bot token after sharing so nobody can abuse it) .env

     

    The new gameserver monitor that you made does work (at least a few days ago when I tried it), but I was missing a few options for adding text, that's why I wanted to try the classic version again. 

  8. 31 minutes ago, Cornflake said:

    i dont think so that this is the reason.

    the error message says that there is a format issue with (probably) your token. 

    Would it be possible for me to send you the .env file with full token so you can see if there is a problem in there? As long as I immediately change the actual token in the Discord development console, it should be safe right? That way you have the token I am trying now, but not the new one. 

  9. 1 minute ago, Cornflake said:

    i hope this is not your actually discord token. if so, change it immediately.

     

    i tested the classic versions. i think your discord bot id could be incorret. not sure

    It is part of the full bot token. The full token is much longer. I just removed the middle part for the screenshot. 

     

    I have created new tokens multiple times and copied them into the .env file. I still get the error. I have removed the bot, and all files from my Unraid server, then installed the classic container again, did all the installation steps again, and started the bot. No error, and it told me that it created the .enf and configuration files. I only added the bot token to the .env file, and started it again, but got the padding error again. 

     

    I don't know where to look, since the bot token is the same in the file and in the Discord development console. 

     

    Could this be because I updated my system to Unraid 6.11.2 a while back, and then downgraded back to 6.9?

  10. 18 minutes ago, Cornflake said:

    Could only be a misconfiguration in the config file

    I did take another look at the config files, but can't find any problem. I made sure to look at any comma's as well, and that the tokens were correct. 

    Here are screenshots of the config files (with sensitive information deleted from them)

    image.thumb.png.4055fe380fc9f43c10e00d5ee602dbe6.png

     

    image.thumb.png.c91930acbfe825da2a8e971b1534b08c.png

  11. On 11/29/2022 at 6:57 PM, Cornflake said:

    With the new version the way how you add servers has changed.

    You should read the documentation, it’s pretty simple.

    https://discordgsm.com/guide/commands
     

    You add server in discord directly via chat commands

     

    So I tried the new one, but didn't like it as much. I liked the classic one more because it was easier for me to manage everything. I removed the new one, and tried getting the classic monitor to work on my new Discord server. 

     

    I did all the steps needed, and the bot is connected to my server. But when I start the container in Unraid, I get this error:

    image.png.14f9c8a525c1ec7e5c9b8c84c3dc8434.png

     

    I do not know how to debug this. Could you help me figure this out?

  12. Hi, 

     

    I used the DiscordGSM in the past and needed to set it up again. I saw that there now is a new version. I used this version before: 

    image.png.7e05e4a7f66f770158c1fc991f2acdbe.png

     

    And now want to try the new version:

    image.thumb.png.d0caed0e131a7acedf86b23738c67172.png

     

    I installed the new bot, added the 2 requested Id's and got the bot connected to the Discord server. I then looked in the botfolder to see how I should add the gameservers. There were no files in there that I could edit. There was only a logfolder. I tried adding the ENV and CONFIG file from the classic bot but the new bot didn't seem to use them. 

     

    How do we setup the new bot? The SQL database file has a lot of "NULL" in it and I am not sure how to edit that one.

  13. 25 minutes ago, Kaizac said:

    It's something Google recently started doing for new accounts. I've told you about this possibility earlier. You can ask for more but they will probably demand you buy 3 accounts first and then still have to explain and ask for more storage with increases of 5TB only.

     

    Alternative is to use Dropbox unlimited which you need 3 accounts for as well but it's really unlimited with no daily upload limits. But it all depends on how much storage you need and your wallet.

    I just contacted support. They told me that I could add another account to double the storage, or contact sales to see what they can offer me. They did not have an answer for me as to why the enterprise account says unlimited storage, but is only 5TB. 

     

    I am now looking at dropbox. They are quite a bit more expensive, but taking power consumption, drive costs and capacity in mind, it might be worth it. I am going to be trying the trial of Dropbox to see if streaming works well. 

  14. I have started uploading and because I have an enterprise standard, I assumed that I have unlimited storage. 

    Google drive shows that I have a maximum of 5TB and I just got a mail telling me that if I exceed it, the files will become read only. Looking at the ways to increase the size, I see that I have to contact support and request more storage. 

     

    Does anyone else have to do this? Or is the 5TB limit not enforced?

    image.png.0058c92e5f7c2a55c75f49ee97610176.png

     

    image.png.30c2ab56303082f29452ea64fdcb8b7c.png

  15. 1 hour ago, Kaizac said:

    You're misunderstanding the way service accounts work. They function as regular accounts. So instead of using your mail account, you use a service account to create your mount. What I did is rename some of the service account files to the mount they represent. You can put them in a different folder. Like sa_gdrive_media.json for your media mount. So for this you will have to not put in the path to the folder with the service account, but to the exact folder. Which you did in your last post. By seperating this you will also not use these SA's for your upload script, seperating any potential API bans.

     

    The upload script will pick the first of the service accounts. Then when it finishes because it hits the 750gb api limit it will stop. That's why you put it on a cron job so it will start again with service account 2 until that one hits the api limit. And so on.

    Just so you understand, the script doesn't just keep running through all your service accounts. You will have to restart it through a cron job.

     

    About moving your current folder to your teamdrive. It depends whether the files are encrypted the same as your new team drive mount. So with the same password and salt. If that is the case you can just drag the whole folder from your gdrive to your team drive from the Google Drive website. Saves a lot of time waiting for rclone transfers to finish. You can even do this to transfer to another account. The encryption has to be identical though.

    I think that I might still not understand fully how to set it up then. I get how it works now (I think) but am not sure if I did set it up correctly now. 

     

    I think that I did use a service account to create the mount. I noticed that I didn't have to login to Google to verify myself when creating these mount points. Is this mount correct?;

    image.thumb.png.b57770aee3fe3798fd3b9360626908ff.png

    The service account file is the first file in the folder:

    image.png.33d976fc5ec47389d86117c77752f71e.png

     

    I assume that when the upload reaches 750gb, it shuts itself down, and like you said, the next time it starts from a cron job, it will use the second account? Or do I have something setup wrong and need to change things?

     

    Sorry for asking so many questions. I am trying but am not that good when it comes to new things like these. 

     

     

     

    EDIT:

    I realised that I didn't change any parameters in the upload script for the service accounts:

    image.thumb.png.25db8875f736116697548b24ad354b5e.png

    I guess that I need to change these as well. I will do that now:

    image.thumb.png.d5783981d1ac8ca0a95e5ebbdc123c95.png

  16. 6 minutes ago, DZMM said:


    Just add the service accounts directly to your rclone config file via the plugin editing window. When done your tdrive remote "pairs" should look like this:

     

    [tdrive]
    type = drive
    scope = drive
    service_account_file = /mnt/user/path_to_first_service_account/sa_tdrive_new.json
    team_drive = xxxxxxxxxxxxxxxxxxxx
    server_side_across_configs = true
    
    [tdrive_vfs]
    type = crypt
    remote = tdrive:crypt
    filename_encryption = standard
    directory_name_encryption = true
    password = xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    password2 = xxxxxxxxxxxxxxxxxxxxxxxxx


    The whole point of the service accounts is that the script automatically rotates the service account in use, so that you can upload 750GB on each run of the script - read the script notes and it will be clear e.g. If you say in the script to rotate 10 SAs and your SA branch starts with sa_tdrive_new, then the script will change the SA used on each run (that must all be in the same location) i.e.


    sa_tdrive_new1.json
    sa_tdrive_new2.json

    sa_tdrive_new3.json

    sa_tdrive_new4.json

    sa_tdrive_new5.json

    sa_tdrive_new6.json

    sa_tdrive_new7.json

    sa_tdrive_new8.json

    sa_tdrive_new9.json

    sa_tdrive_new10.json
     

    and on the 11th run, back to 1:

     

    sa_tdrive_new1.json

    sa_tdrive_new2.json

    etc etc

     

    You need 14-16 SAs to safely max out a gig line.

    I cant figure out how to add them and what window you mean. I assume this window:

    image.png.4a96f7ffe15e015e79bb92b10d279481.png

     

    What I did (for testing) is instead of pointing the SA location in the previous post to the folder containing all 20 SA accounts, I now went a level deeper and gave it the path to the first SA account in that folder. It now points to:

    image.thumb.png.018a1954ee819b54146b5fc1cecb8b67.png

     

    Then created new upload and mount scripts, and now it has been uploading for half an hour at full speed. I hope this works and that it will change over to a new service account when it reaches the 750gb mark. 

     

  17. 3 minutes ago, DZMM said:

    I hope they are in a recycling bin somewhere so you can restore.  given the difficulty you had creating them, you could have just put them in a folder for future use e.g. I'm using about 90 service accounts now across multiple mounts.

     


    as long you have server side transfers setup in your rclone config i.e.

     

    [tdrive]
    type = drive
    scope = drive
    service_account_file = /mnt/user/appdata/other/rclone/service_accounts/sa_tdrive_new.json
    team_drive = xxxxxxxxxxxxxxxxxxxxxx
    server_side_across_configs = true

     

    then it's as simple as running:

     

    rclone move source_mount: target_mount:

     

    you can add in other arguments if you want e.g. this is how I move files between from my main tdrive to one of my movies tdrives as an overnight job (again, this is all covered in this thread several times):
     

    rclone move --min-age 30d tdrive:crypt/encrypted_movies_folder_name tdrive_movies_adults:crypt/encrypted_movies_folder_name \
    --user-agent="transfer2" \
    -vv \
    --buffer-size 512M \
    --drive-chunk-size 512M \
    --tpslimit 8 \
    --checkers 8 \
    --transfers 4 \
    --order-by modtime,ascending \
    --exclude *fuse_hidden* \
    --exclude *_HIDDEN \
    --exclude .recycle** \
    --exclude .Recycle.Bin/** \
    --exclude *.backup~* \
    --exclude *.partial~* \
    --drive-stop-on-upload-limit \
    --delete-empty-src-dirs

     

    Thanks for the info. I still have a copy of all the accounts saved somewhere, so they are safe. 

     

    I tried creating a tdrive and got to the part where it asks me the location of the SA credentials:

    image.png.e323dd025539b1570ee4fa19a12113b2.png

     

    I assume that I need to put the path of the SA accounts there. That would be:

    image.thumb.png.0787fac2b86a964f5da0824f9b87c374.png

    I had to save them there according to the renaming instructions. 

     

    But when I enter that path, it doesn't work:

    image.png.36f0e043033fde2879235aeb85f3efac.png

    because it can't find the files in the next step where I say that it is a team drive:

    image.thumb.png.bb3bc83c6fc33e4d464f0722e39e6eb5.png

     

    I see that it is asking for a file, and not a path, but I thought it needed the path to all 20 accounts? What am I supposed to put there?

  18. So, I am almost there. Turns out that I created about 800 SA. Some with a new project and some not. I don't think that should matter. I have removed a lot of them and only kept 20. Of these 20, I have added 10 to the group and added that group to the teamdrive. 

     

    The accounts are saved in appdata and renamed according to the instructions. As far as I can tell, this only leaves the editing of the mount and upload script. I do need a little bit of help here because I can't figure out how to edit them so they point to a teamdrive and not just Google drive. 

     

    This is the upload script I have now:

    image.thumb.png.7c5d8715ecb99ff9938c4a3cc8f88a8e.png

     

    And this is the mount script:

    image.thumb.png.e1275922f7423e5a3b8f43c84f6e1e32.png

     

    They pointed to the drive at the top but now need to point to the teamdrive:

    image.png.02897c3b0295041d7cf01cd8694054c7.png

     

    And (hopefully my last question) how do I move the data that is already uploaded in the secure folder, to the teamdrive? Someone mentioned using the move command in Rclone, but I don't know how to use that. Can I just have 2 mount scripts running at the same time and copy the data already uploaded to my local sytem and then later have it moved to the teamdrive?

  19. 14 hours ago, Roudy said:

     

    You don't have to do the sample part of that website, just enable the API. You should be able to continue on.

    Thanks for the help. 

     

    I tried running this the command agian to create the service accounts (wanted to start a few steps back to make sure that I do everything correctly). I get an error telling me to authenticate again, but I don't know how to do that. 

    image.thumb.png.3fe199ed3d50a9cf863104619b0be2f4.png

     

    I also tried to continue with the accounts that I already have, but got an error telling me that the index is out of range:

    image.png.dc3ed074bd907adcde112f5acf70a8d1.png

     

    I realise that the last step is optional. You can also add the accounts manually to the group. Do you know how to do that? 

    I made some screenshots in this post asking how to do it: 

    Do I need to copy the emailadresses from the service accounts and paste them somewhere?

     

     

     

    EDIT: I think that I figured it out. I opened up 10 of the SA .json files and copied the email address inside. Then added that to the goup and then added the group to the teamdrive:

    image.thumb.png.0e7c376501ebcf4982c54ffaa4acee19.png

     

    I have only done 10 for now, but 7.5TB per day is plenty for me. So now I have to figure out how to rename the service accounts, where to save them and how to edit the mount and upload script so they both know to use the teamdrive. 

  20. 14 minutes ago, DZMM said:

    The rclone drive is a team drive i.e. shared.

    If you created the Group and added the service accounts as per Step 3, and then added the Group address to the team drive as per Step 4, you have finished setting up your SAs.

    All that's left is to remane the SAs to whatever you want, store them in a folder somewhere, and then use them in the script where it tells you want to do. 

     

    If you're unsure, please search this thread for service accounts where I ran through how to use them - find the first instance and go from there.  Everything you need is in here several times.

     

     

    Thanks! Good to know that the shared drive I have already created is a team drive. That clears up some confusion for me. 

     

    While I have created the group, I have trouble adding the service accounts to the group. I hope that this is the last of the problems I encounter, so I can start the upload process. As I mentioned, I need to enable a SDK API, and then run a command to open the quickstart.py and give permission to something. But I get an error when I do that. 

    image.thumb.png.dc7b5649f9661ae6f86e3852460c433a.png

     

    I hope @Kaizac or someone else can help with that error. I get the feeling that his is the last of the problems still in my way. Then again, I am a professional idiot and tend to find all the problems that you can find, so who knows. 

  21. 12 minutes ago, DZMM said:

    I'm not an expert here and I think I got lucky doing this at the first attempt, but it looks like you've got your service accounts right there - they just need renaming!

    I think that I managed to create 100 of them, but according to the manual, I now need to enable a SDK API and I am stuck there. I get the error's mentioned in the posts above. I can skip those steps and manually add these service accounts to the group I created, but I don't know how to do that. 

     

    What do you mean renaming? None of the steps mention that. Do you know how I should rename them and how to add them to my project? I am trying these steps (Step 2 is complete, a group is made, but step 1 gives me trouble): image.thumb.png.d9fe2f699009e3ab08ae1d601d828e48.png

     

    In the meantime, I was reading up on the next steps. I see that I need to have a teamdrive. When I login to Google drive, I only have 2 options:

    image.png.ba8d9c78702f63c4c89e9e70880996f5.png

     

    The top one is where I am currently uploading data. The bottom one is a shared drive. Is a shared drive the same thing as a team drive? 

    image.png

  22. Right, so I kept trying things and thought that maybe I should try to run:

    python3 gen_sa_accounts.py --quick-setup 1

    and have Python create a new project with accounts. There were no errors during this step. 

     

    Then I went ahead to step 3 and tried the steps again to enable the API:

    image.thumb.png.9ff727377a2a7c1516ff597b6272d9ce.pnghttps://developers.google.com/admin-sdk/directory/v1/quickstart/python

     

    I can do all the steps on that page, except the last one where I have to run:

    python quickstart.py

     

    I now get a different error when I run that command:

    image.png.76c3a9c155d6f6f95cfd651868bad6e9.png

     

    I also did not see a second project:

     

     

    So I am not entirely sure that a new project was created in the previous step. Maybe that is the reason why I keep getting errors in this step?

     

    I am not touching anything for now in fear of making an even bigger mess. 

    image.png

     

     

     

    EDIT: how do I manually add the service accounts? I have this screen:

    image.thumb.png.27f7fc3b5c095b9697102db4999bbfa2.png

     

    And these accounts:

    image.png.67588e90d6819befdd12b3b9ba432aee.png

     

    What do I need to copy into what field?

×
×
  • Create New...