Jump to content

Danuel

Members
  • Posts

    253
  • Joined

  • Last visited

Posts posted by Danuel

  1. hi, guys, need some help, problem i have started in the last hour,  docker containers are taking to long time to start, this happen after trying to manually update a container then server got stuck, so i did a restart then the array did not want to come back or having problem to start, so i entered in safe mode and disabled docker then array started as normal, now i started docker and all docker containers taking forever to start , any help please, i am with almost 2 hours and still not all containers started

    Ulogs.txt

  2. On 7/16/2023 at 6:35 PM, robertmorison said:

    Did you ever find a solution to this? Dealing with the same issue.

    if your container does not have a variable where to add GPU ID, you have to created that VAraible

    then in extra parameters: add this line  -e NVIDIA_DRIVER_CAPABILITIES=all  -e NVIDIA_VISIBLE_DEVICES=all  --gpus all 

  3. hi, just updated to 27.0.0 

    i do get a message in nextcloud 

     

    `Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation ↗. (List of invalid files… / Rescan…)` pressing rescan does nothing, any fix for this ?

  4. 1 hour ago, JorgeB said:

    Unfortunately there's nothing relevant logged, assuming you already did the Ryzen tweaks this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

     can HDD temp influence a crash early my HDD were 46c and around 10 am server froze

  5. 28 minutes ago, ishtangli said:

    I downgraded the docker and tried to run an update. Getting an error

     

    PHP Warning:  fopen(/data/updater.log): Failed to open stream: Permission denied in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 1128
    Could not open updater.log

     

     

    use the File manager Plugin in uNRAid and edit permision from there

  6. this is a guide on how to upgrade from terminal you might find it more easy

     

    if you have problem This version of Nextcloud is not compatible with PHP>=8.2.<br/>You are currently running 8.2.6

     

    what i have did i revert back to 25.0.3

    then started the upgrade from terminal

     

     

    1. open terminal from nextcloud container

    2. Turn on maintenance mode
    cd /config/www/nextcloud/
    sudo -u abc php occ maintenance:mode --on

    3. Backup current nextcloud install
    cd /config/www/
    mv nextcloud nextcloud-backup

    if you get a error regarding backup delete `nextcloud-backup` and try again to backup

    4. Grab newest nextcloud release and unpack it

    wget https://download.nextcloud.com/server/releases/nextcloud-26.0.2.tar.bz2 or whatever version, "you can see latest version on https://download.nextcloud.com/server/releases"
    tar -xvf nextcloud-26.0.2.tar.bz2

    5. Copy across old config.php from backup
    cp nextcloud-backup/config/config.php nextcloud/config/config.php

     

    ##Now Restart docker container via Unraid WebGUI

    6. Open terminal in container

    7. Perform upgrade

    cd /config/www/nextcloud/
    sudo -u abc php occ upgrade  (if you get error you might have to enable permision)

    8.Turn off maintenance mode
    sudo -u abc php occ maintenance:mode --off

    9. Now Restart docker container via Unraid WebGUI   and upgrade your container to latest version 26.0.2 in my case

     

    ###fixes after installation###

     

     
    *if you get error "sudo: ./occ command not found" (run chmod 777 occ) then run the fix


    sudo -u abc ./occ db:add-missing-indices

    sudo -u abc ./occ db:convert-filecache-bigint

     

     

    **Other fixes

     

    you have to stop the nextcloud container and proxymanager

    go to  appdata\nextcloud\nginx\site-confs

    and edit the line

    add_header X-Robots-Tag "noindex, nofollow" always;

    add_header X-Frame-Options "SAMEORIGIN" always;

     

    also if you still have problem with apps after updating nextcloud, you have to change ownership to apps nextcloud\www\nextcloud\apps i use the plugin `file manager` from unraid to achieve that and i set owner to nobody


     

     

  7. 1 hour ago, binhex said:

    it looks to me like you aren't running the latest image, go to unraid/docker then toggle basic view to advanced view, then click on 'force update' for the container, this will then force download the latest image.

     i can confirm, that  foce update fix the problem

  8. is just me or the latest update broke the app ? because for me latest is not working

     

    downgrading to 2.16.1-3-01 is working

     

     

    `

    Traceback (most recent call last):
      File "/usr/sbin/websockify", line 33, in <module>
        sys.exit(load_entry_point('websockify==0.10.0', 'console_scripts', 'websockify')())
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      File "/usr/sbin/websockify", line 22, in importlib_load_entry_point
        for entry_point in distribution(dist_name).entry_points
                           ^^^^^^^^^^^^^^^^^^^^^^^
      File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 981, in distribution
        return Distribution.from_name(distribution_name)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 565, in from_name
        raise PackageNotFoundError(name)
    importlib.metadata.PackageNotFoundError: No package metadata was found for websockify

    2023-05-07 11:45:57,217 DEBG 'start' stderr output:
    _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

    2023-05-07 11:45:57,217 DEBG 'start' stderr output:

    Xvnc TigerVNC 1.13.1 - built Mar 10 2023 21:57:50
    Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
    See https://www.tigervnc.org for information on TigerVNC.
    Underlying X server release 12101006


    Sun May  7 11:45:57 2023
     vncext:      VNC extension running!

    2023-05-07 11:45:57,217 DEBG 'start' stderr output:
     vncext:      Listening for VNC connections on all interface(s), port 5900
     vncext:      created VNC server for screen 0

    2023-05-07 11:45:57,266 DEBG 'start' stderr output:
    [mi] mieq: warning: overriding existing handler (nil) with 0x563e1a18b920 for event 2
    [mi] mieq: warning: overriding existing handler (nil) with 0x563e1a18b920 for event 3

    2023-05-07 11:46:01,157 DEBG 'start' stdout output:
    [info] tint2 not running

    2023-05-07 11:46:01,167 DEBG 'start' stderr output:
    tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavi
    2023-05-07 11:46:01,167 DEBG 'start' stderr output:
    or or crashes

    2023-05-07 11:46:01,172 DEBG 'start' stderr output:
    t
    2023-05-07 11:46:01,173 DEBG 'start' stderr output:
    int2: xRandr: Found crtc's: 1
    tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96

    2023-05-07 11:46:01,199 DEBG 'start' stderr output:

    (hexchat:93): Gtk-WARNING **: 11:46:01.198: Unable to locate theme engine in module_path: "adwaita",

    2023-05-07 11:46:01,338 DEBG 'start' stderr output:

    (hexchat:93): Gtk-WARNING **: 11:46:01.338: Unable to locate theme engine in module_path: "murrine",

    2023-05-07 11:46:01,349 DEBG 'start' stderr output:

    (hexchat:93): Gtk-WARNING **: 11:46:01.349: Unable to locate theme engine in module_path: "adwaita",

    2023-05-07 11:46:16,178 DEBG 'start' stderr output:
    tint2: warning : WM doesn't respect NETWM specs. tint2 default to 1 desktop.

    2023-05-07 11:46:16,178 DEBG 'start' stderr output:
    tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
    tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc

    2023-05-07 11:46:16,181 DEBG 'start' stderr output:
    tint2: real transparency on... depth: 32

    2023-05-07 11:46:16,182 DEBG 'start' stderr output:
    tint2: panel items: TSC
    tint2: Systray composited rendering on

    2023-05-07 11:46:16,182 DEBG 'start' stderr output:
    tint2: nb monitors 1, nb monitors used 1, nb desktops 1
    tint2: panel 1 uses scale 1 

    2023-05-07 11:46:16,215 DEBG 'start' stderr output:
    tint2: Kernel uevent interface initialized...

    2023-05-07 11:46:16,215 DEBG 'start' stderr output:
    tint2: systray window 4194317
    tint2: systray started

    `

  9. Hi,

     

    i just got this error, i set the trim for weekly, how i can fix this ?

     

     

    Apr 16 10:31:54 Seven kernel: sd 10:0:2:0: [sdd] tag#58 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
    Apr 16 10:31:54 Seven kernel: sd 10:0:2:0: [sdd] tag#58 Sense Key : 0x5 [current] 
    Apr 16 10:31:54 Seven kernel: sd 10:0:2:0: [sdd] tag#58 ASC=0x21 ASCQ=0x0 
    Apr 16 10:31:54 Seven kernel: sd 10:0:2:0: [sdd] tag#58 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
    Apr 16 10:31:54 Seven kernel: critical target error, dev sdd, sector 975384536 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
    Apr 16 10:31:54 Seven kernel: BTRFS warning (device dm-5): failed to trim 1 device(s), last error -121
    Apr 16 10:42:10 Seven  emhttpd: spinning down /dev/sdi
    Apr 16 10:42:35 Seven  emhttpd: spinning down /dev/sdg
    Apr 16 10:47:11 Seven kernel: sd 10:0:3:0: [sde] tag#178 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
    Apr 16 10:47:11 Seven kernel: sd 10:0:3:0: [sde] tag#178 Sense Key : 0x5 [current] 
    Apr 16 10:47:11 Seven kernel: sd 10:0:3:0: [sde] tag#178 ASC=0x21 ASCQ=0x0 
    Apr 16 10:47:11 Seven kernel: sd 10:0:3:0: [sde] tag#178 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
    Apr 16 10:47:11 Seven kernel: critical target error, dev sde, sector 973287403 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 0
    Apr 16 10:47:11 Seven root: /var/lib/docker: 22.3 GiB (23920013312 bytes) trimmed on /dev/loop2
    Apr 16 10:47:11 Seven kernel: BTRFS warning (device dm-3): failed to trim 1 device(s), last error -121
    Apr 16 10:47:11 Seven  sSMTP[22654]: Creating SSL connection to host
    Apr 16 10:47:11 Seven  sSMTP[22654]: SSL connection using TLS_AES_256_GCM_SHA384
    Apr 16 10:47:13 Seven  sSMTP[22654]: Sent mail for [email protected] (221 2.0.0 closing connection f16-20020a05600c4e9000b003f0a6a1f969sm9098870wmq.46 - gsmtp) uid=0 username=root outbytes=542
     

  10. @JorgeB just made a bios update and set the Power Supply Idle Control to  typical current idle, now i will wait and see and XMP was disabled

     

    can be something from PSU ? meaning that is not enough W ? 

  11. Hi, i just change my motherboard+ram+cpu from my windows machine

     

    problem that i have is that my server freezes and i don't know why

    i am not able to find any logs

     

    MOtherBoard:  MSI B350 PC MATE

    CPU: AMD Ryzen 5 1500X

    RAM : 16GB

     

     

     

    any solution much appreciated

  12. does anyone else have problem sending files of 160MB using the send tool ?

     i does say that support 500 MB but i get aeeror on 160MB files 

     

    An Error has occured 
    Failed to fetch

     

    [2023-03-03 19:35:17.181][request][INFO] POST /api/sends/file/v2
    03/03/2023 19:35:17
    [2023-03-03 19:35:17.184][response][INFO] (post_send_file_v2) POST /api/sends/file/v2 => 200 OK
    03/03/2023 19:39:30
    [2023-03-03 19:39:30.769][request][INFO] DELETE /api/sends/93df4fdc-3df8-4311-a31a-d07347d4ded7
    03/03/2023 19:39:30
    [2023-03-03 19:39:30.770][request][INFO] DELETE /api/sends/563c642d-0fb7-4dd8-8be7-9f152a645ba7
    03/03/2023 19:39:30
    [2023-03-03 19:39:30.781][response][INFO] (delete_send) DELETE /api/sends/<id> => 200 OK
    03/03/2023 19:39:30
    [2023-03-03 19:39:30.783][response][INFO] (delete_send) DELETE /api/sends/<id> => 200 OK

     

    this is using the app

    Version 2023.2.0 Shell 21.3.1 Renderer 106.0.5249.181 Node 16.16.0 Architecture x64

     

    also using the plugin same error, either on opera or brave

×
×
  • Create New...