Jump to content

pkoasne

Members
 View Profile  See their activity

  • Posts

    38

  • Joined

 Content Type 

Posts posted by pkoasne

    Error 522 intermittently

    in General Support

    Posted

    5 hours ago, FrostyBrew said:

    Did you ever get anywhere with this? In just the last handful of days I’m starting to see some of my externally-accessible services spitting a 522 error out.

     

    I'm also running NginxProxyManager, which logs did you see this in? I’ll dig into mine.

    It vanished as mysteriously as it had appeared.

    Error 522 intermittently

    in General Support

    Posted · Edited by pkoasne

    Hello, I'm experiencing a recurring problem where all of my services display a 522 error every few minutes, and then they resume normal operation. The service does not have an issue if the IP is used instead of domain name. The only information I can find in the ngnixproxymanager logs is: "An upstream response is buffered to a temporary file." This configuration has been functioning without issues for years prior to this.

     

    castle-diagnostics-20231120-0629.zip

    Run script when specific docker starts

    in General Support

    Posted · Edited by pkoasne
    added script

    19 hours ago, JonathanM said:

    Not that I can think of, but you can certainly start a container from a script. Disable the auto start for that container on the docker page and script the startup separately.

    schedule at array start

    sleep however long you want to wait

    docker start containername

    run the rest of your commands.

    Thanks, that is basically what I ended up doing. Running this on a cron every few minutes to check if the docker is running and if not it starts it up and executes the commands I need. Sharing the script in case anyone else ever needs this.

      

    #!/bin/bash

# Replace CONTAINER_NAME with the actual name of your running Docker container
CONTAINER_NAME="CHANGEME"

# Specify the log file path
LOG_FILE="docker_exec_log.txt"

# Check if the container is already running
if docker inspect -f '{{.State.Running}}' $CONTAINER_NAME > /dev/null 2>&1; then
    echo "Container $CONTAINER_NAME is already running."
    exit 0
fi

# Start the container if it's not running
docker start $CONTAINER_NAME

# Wait for the container to start
echo "Waiting for container $CONTAINER_NAME to start..."
while ! docker inspect -f '{{.State.Running}}' $CONTAINER_NAME > /dev/null 2>&1; do
    sleep 1
done

echo "Container $CONTAINER_NAME is now running."

# Run commands inside the Docker container and log errors/output
docker exec $CONTAINER_NAME bash -c '
 REPLACE_THIS_WITH_THE_COMMANDS_YOU_WANT_TO_RUN
' 2>&1 > $LOG_FILE

# Display the log file contents
cat $LOG_FILE

     

    • Thanks 1

    [Support] d8sychain - Elasticsearch

    in Docker Containers

    Posted

    https://github.com/jemalloc/jemalloc/issues/1328 

    # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

     

    where is sysctl.conf ? I couldn't find it in the container.

    issue creating new cache pool

    in General Support

    Posted

    I've formatted both nvme drives to btrfs yet unraid only detects 1 fs and it thinks its xfs:

      

    parted /dev/nvme0n1 print
Model: Samsung SSD 980 1TB (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  1000GB  1000GB  btrfs

      

    parted /dev/nvme1n1 print
Model: SPCC M.2 PCIe SSD (nvme)
Disk /dev/nvme1n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  1024GB  1024GB  btrfs


    image.thumb.png.93236a838a0d89cd2387119c815188ec.png

    [REQUEST] Mastodon

    in Docker Engine

    Posted

    On 11/30/2022 at 3:44 AM, pkoasne said:

    Max_toot_length is not configurable with official mastodon. Changing max_toot_length manually isn't great because every time the docker updates, your configuration will be wiped. To get around this I created a userscript which I manually run after I update the docker. replace 5000 with whatever length you want to use.

      

    #!/bin/bash
docker exec mastodon sed -i 's/500/5000/g' /app/www/app/javascript/mastodon/features/compose/components/compose_form.js
docker exec mastodon sed -i 's/500/5000/g' /app/www/app/validators/status_length_validator.rb
docker exec mastodon sed -i 's/:registrations/:registrations, :max_toot_chars /g' /app/www/app/serializers/rest/instance_serializer.rb
docker exec mastodon sed -i 's/private/def max_toot_chars\n    5000\n  end\n\n  private/g' /app/www/app/serializers/rest/instance_serializer.rb
docker exec -w /app/www/app mastodon bundle exec rails assets:precompile && echo "pass" || echo "fail"
docker container restart mastodon

     

    At some point I'll get tired of manually running the script and will add a precheck to determine if the script should be run or not.

     

    Got around to updating the script:

      

    #!/bin/bash

if docker exec mastodon grep -q 5000 /app/www/app/javascript/mastodon/features/compose/components/compose_form.js &&
   docker exec mastodon grep -q 5000 /app/www/app/validators/status_length_validator.rb; then
  echo "No changes needed, 5000 already present in both files."
else
  docker exec mastodon sed -i 's/500/5000/g' /app/www/app/javascript/mastodon/features/compose/components/compose_form.js
  docker exec mastodon sed -i 's/500/5000/g' /app/www/app/validators/status_length_validator.rb
  docker exec mastodon sed -i 's/:registrations/:registrations, :max_toot_chars /g' /app/www/app/serializers/rest/instance_serializer.rb
  docker exec mastodon sed -i 's/private/def max_toot_chars\n    5000\n  end\n\n  private/g' /app/www/app/serializers/rest/instance_serializer.rb
  docker exec -w /app/www/app mastodon bundle exec rails assets:precompile && echo "Assets precompiled successfully." || echo "Assets precompilation failed."
  docker container restart mastodon
fi

     

    [Support] Gitea

    in Docker Containers

    Posted

    has anyone been able to get this working again? I'm stuck with this:

      

    Server listening on :: port 22.
Server listening on 0.0.0.0 port 22.
2023/01/12 05:43:34 cmd/web.go:106:runWeb() [I] Starting Gitea on PID: 18
2023/01/12 05:43:34 ...s/setting/setting.go:613:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.19.0
2023/01/12 05:43:34 cmd/web.go:160:runWeb() [I] Global init
2023/01/12 05:43:34 ...s/setting/setting.go:613:deprecatedSetting() [E] Deprecated fallback `[server]` `LFS_CONTENT_PATH` present. Use `[lfs]` `PATH` instead. This fallback will be removed in v1.19.0
2023/01/12 05:43:34 routers/init.go:116:GlobalInitInstalled() [I] Git Version: 2.36.3, Wire Protocol Version 2 Enabled (home: /data/gitea/home)
2023/01/12 05:43:34 routers/init.go:117:GlobalInitInstalled() [I] AppPath: /usr/local/bin/gitea
2023/01/12 05:43:34 routers/init.go:118:GlobalInitInstalled() [I] AppWorkPath: /app/gitea
2023/01/12 05:43:34 routers/init.go:119:GlobalInitInstalled() [I] Custom path: /data/gitea
2023/01/12 05:43:34 routers/init.go:120:GlobalInitInstalled() [I] Log path: /data/gitea/log
2023/01/12 05:43:34 routers/init.go:121:GlobalInitInstalled() [I] Configuration file: /data/gitea/conf/app.ini
2023/01/12 05:43:34 routers/init.go:122:GlobalInitInstalled() [I] Run Mode: Prod
Received signal 15; terminating.

     

    [REQUEST] Mastodon

    in Docker Engine

    Posted · Edited by pkoasne

    Max_toot_length is not configurable with official mastodon. Changing max_toot_length manually isn't great because every time the docker updates, your configuration will be wiped. To get around this I created a userscript which I manually run after I update the docker. replace 5000 with whatever length you want to use.

      

    #!/bin/bash
docker exec mastodon sed -i 's/500/5000/g' /app/www/app/javascript/mastodon/features/compose/components/compose_form.js
docker exec mastodon sed -i 's/500/5000/g' /app/www/app/validators/status_length_validator.rb
docker exec mastodon sed -i 's/:registrations/:registrations, :max_toot_chars /g' /app/www/app/serializers/rest/instance_serializer.rb
docker exec mastodon sed -i 's/private/def max_toot_chars\n    5000\n  end\n\n  private/g' /app/www/app/serializers/rest/instance_serializer.rb
docker exec -w /app/www/app mastodon bundle exec rails assets:precompile && echo "pass" || echo "fail"
docker container restart mastodon

     

    At some point I'll get tired of manually running the script and will add a precheck to determine if the script should be run or not.

    • Thanks 1

    Fix common problem error - Invalid folder cache contained within /mnt

    in General Support

    Posted

    FCP doesn't say anything more than:

    • Invalid folder users contained within /mnt
      • Generally speaking, most times when other folders get created within /mnt it is a result of an improperly configured application. This error may or may not cause issues for you  More Information

    Output of 

    ls -la /mnt

      

    
# ls -la /mnt
total 0
drwxr-xr-x 17 root   root  340 Nov 25 06:46 ./
drwxr-xr-x 21 root   root  440 Nov 25 07:05 ../
drwxrwxrwx  5 nobody users  52 Nov 25 04:40 cache/
drwxrwxrwx  5 nobody users  51 Nov 25 04:40 disk1/
drwxrwxrwx  6 nobody users  85 Nov 25 04:40 disk2/
drwxrwxrwx  8 nobody users 127 Nov 25 04:40 disk3/
drwxrwxrwx  6 nobody users  87 Nov 25 04:40 disk4/
drwxrwxrwx  4 nobody users  45 Nov 25 04:40 disk5/
drwxrwxrwx  5 nobody users  67 Nov 25 04:40 disk6/
drwxrwxrwx  5 nobody users  67 Nov 25 04:40 disk7/
drwxrwxrwx  8 nobody users 127 Nov 25 04:40 disk8/
drwxrwxrwx  9 nobody users 146 Nov 25 04:40 disk9/
drwxrwxrwt  4 nobody users  80 Nov 25 06:49 disks/
drwxrwxrwt  2 nobody users  40 Nov 21 06:33 remotes/
drwxrwxrwt  2 nobody users  40 Nov 21 06:33 rootshare/
drwxrwxrwx  1 nobody users  51 Nov 25 04:40 user/
drwxrwxrwx  1 nobody users  51 Nov 25 04:40 user0/

     

    [Support] A75G Repo

    in Docker Containers

    Posted

    On 11/20/2022 at 2:11 PM, eaglephantom said:

    When I use the terminal to view /mnt/user/appdata/matrix, there's nothing in the folder. Before attempting to install the Matrix container I did what the above guide said (set my network type to my proxynet, which works with other reverse-proxied containers of mine, and set my server name to my chat domain). I also double-checked my SWAG conf file for Matrix and everything looks correct. My CNAME is added in Cloudflare and points to my DuckDNS domain for my home network, and proxy is not enabled, just "DNS only".

     

    Any ideas on why this permission error is happening?

     

    Unraid with Matrix install: version 6.10.3

    2nd Unraid with SWAG install: version 6.11.4

     

    I had to add write permissions to the /appdata/matrix folder to get it to write the config files.

×
×
  • Create New...