Jump to content

exico

Members
  • Posts

    47
  • Joined

  • Last visited

About exico

  • Birthday August 4

Converted

  • Gender
    Male
  • URL
    www.gmservices.pro
  • Location
    North East Italy

Recent Profile Visitors

1,322 profile views

exico's Achievements

Rookie

Rookie (2/14)

5

Reputation

1

Community Answers

  1. I checked, Im starting to understand how the snapshots works. From what I got the snapshots folders are created only when i delete a file/folder from the source that corresponds to that date. For example if I deleted today a file created Jan 13 2024 I will find it in the folder 20240113somethingsomething. With that forget what i said about missing snapshots. With that said it would be nice to have a timestamp in the LastCronLog and maybe an option to cycle the logs
  2. Hello, Im using Lucky Backup and my jobs include snapshots. The problem is: If i run the tasks manually LB creates the snapshots, I can see them in .luckybackup-snapshots and in the gui but if i set them on a schedule no snapshots are created, or at least I dont see them. No extra folders created in .luckybackup-snapshots and it isnt listed in manage snapshots in the gui. I know that the schedule works because i placed some files on the source and checked the destination after the scheduled time. There are some logs that I can provide?
  3. My 2 cents on the container swap. I dont fully support/understand the decision on why use two dockers but at least the instructions on how to set up the new containers should be more clear for Unraid. In my case the init script didnt want to work. I edited the variables on the mongo container but it didnt want to execute the script on the first boot. I had to enter the container console and: mongo < path_of_the_init_script_in_the_container.js At first i tought it was a problem with the connection between the two containers since i run unifi in its own IP and mongo in bridge. tried to install ping to troubleshoot in the unifi container but apt has broken dependencies and doesnt let me do anything. So, please, expand the instructions on the github for Unraid. [insert instruction not clear joke here]
  4. Well I did update the system roughly 1 week after 6.12.4 came out. Thats why its strange. Anyway I can report that no more crashes occured. At least for now.
  5. Will do and report back. If it is that its strange. Didnt change it or added containers in a while and happened out of the blue.
  6. I've been dealing with this for 2 weeks... I have a very strange random freeze that only a reset or forced shutdown can clear. I had problem with setting up the syslog but now it works. What i did so far: - Remove HBA (LSI 9211) working for 5 years or so - Remove NIC (HP branded Broadcom 10G ethernet) - Remove video card (1050 ti) - Swap PSU - Memtest the RAM - Swap the Motherboard with a Gigabyte X79 UP4 with a 4930K and some ddr3 ram At the moment I have just my motherboard with a NVME adapter and 8 Sata drives and im using the integrated 1G nic (e1000) and sata ports The motherboard is a Supermicro X9SRL-F with a E5-2697 v2 CPU and 64 GB of RAM I attached diagnostics and the last syslog. The last freeze occured at "Nov 13 12:29:29" Checking the syslog I was a "tainted kernel" (you can see one at line 8284 "Nov 13 12:28:29 UNRAIDSRV kernel: CPU: 16 PID: 11248 Comm: kworker/16:1 Tainted: P W O 6.1.49-Unraid #1" After some digging i got this: root@UNRAIDSRV:~# cat /proc/sys/kernel/tainted 4609 root@UNRAIDSRV:~# ./kernel-chktaint Kernel is "tainted" for the following reasons: * proprietary module was loaded (#0) * kernel issued warning (#9) * externally-built ('out-of-tree') module was loaded (#12) For a more detailed explanation of the various taint flags see Documentation/admin-guide/tainted-kernels.rst in the Linux kernel sources or https://kernel.org/doc/html/latest/admin-guide/tainted-kernels.html Raw taint value as int/string: 4609/'P W O ' root@UNRAIDSRV:~# Im not a big linux person so I can go so far. Do you have any suggestion on what i can try before i go mad? syslog-127.0.0.1.zip unraidsrv-diagnostics-20231113-1317.zip
  7. Found the problem, I had two interfaces with the same IP but I do not understand why the rc script bind the same ip twice on one interface. I think that a check should be in place for that. Bear in mind that I had one interface disabled I removed the IP from both interfaces and the upgrade has gone smooth
  8. I searched but i did not see this problem in another "no webgui" thread. I upgraded from the RC6 to 6.12.0 stable and also tried 6.12.1 but i had to revert on both occasions. I attached the diagnostics but from what i see: Tried to: /etc/rc.d/rc.nginx check Checking configuration for correct syntax and then trying to open files referenced in configuration... nginx: [emerg] a duplicate default server for 192.168.80.105:80 in /etc/nginx/conf.d/servers.conf:43 nginx: configuration file /etc/nginx/nginx.conf test failed I then checked servers.conf and indeed there are various entries duplicated on my eth3. I tried to comment them and check again, some warnings but no [emerg]. Tried to start and these entries reappear and stop nginx. For example: server { listen 192.168.80.105:80 default_server; # eth3 return 302 https://192-168-80-105.c8100b769f7ebe9a046d3c97b75b083b26c4ca45.myunraid.net:443$request_uri; } server { listen 192.168.80.105:80 default_server; # eth3 return 302 https://192-168-80-105.c8100b769f7ebe9a046d3c97b75b083b26c4ca45.myunraid.net:443$request_uri; } somethingsomething server { somethingsomething listen 192.168.80.105:443 ssl http2 default_server; # eth3 listen 192.168.80.105:443 ssl http2 default_server; # eth3 somethingsomething } (somethingsomething is just a placeholder for the other config text, just wanted to highligh the duplicated entries) And there are more. For now i reverted to the RC Since the eth3 is integrated in the MB i cannot even remove it to try if it fix itself, also there is no option in the BIOS to disable it MB is a supermicro X9SRL-F unraidsrv-diagnostics-20230623-2116.zip
  9. I understand that they are working on it for another release but there is a fix or configuration that i can set to make it work in the mean time? Maybe in the Samba Extra configuration? I use Wireguard to connect two servers in different locations and this will break things
  10. I have the same problem with the new version My docker was already set to 911:911 as permissions and when i updated it did not work. I tried to set PUID and PGID to 99 and 100, obviously it did not work because it is different from the file permissions. I chown 'ed the folder to 99 100 and still it did not work. I set the version to 2.9.22 as suggested by Tweak91 and it started. Files user:group now is the same as variables on the docker. (99:100, before was 911:911) Mind that I'm still at version 6.11.5 of UNRAID
  11. Just a question, would be possible to add curl to LuckyBackup docker? For now I console'd in and apt installed it into the container but it's not ideal since it will vanish with the next update. I'm asking this because I'm using curl in the Also Execute section in the tasks to power on a machine, wait and then start the backup.
  12. I just updated UNRAID from 6.10.1 to 6.10.3 and now steam headless wont work. On the log console i get a spam of this: 2022-06-22 20:56:06,396 INFO spawned: 'x11vnc' with pid 566 2022-06-22 20:56:07,408 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-06-22 20:56:07,409 INFO exited: x11vnc (exit status 1; not expected) 2022-06-22 20:56:08,412 INFO spawned: 'x11vnc' with pid 567 2022-06-22 20:56:09,425 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-06-22 20:56:09,426 INFO exited: x11vnc (exit status 1; not expected) 2022-06-22 20:56:10,429 INFO spawned: 'x11vnc' with pid 568 etc... What should i check? Attached, my config
  13. Tried again today and now it finds the 6.10 release and I upgraded with no issues Thank you!
  14. Unfortunately I can't seem to update from rc8 to stable. When i try from Tools -> update OS it doesnt find any new release in Next or Stable. If i try to install it manually like told in the first post in Plugins -> Install Plugin i get this: plugin: installing: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer.plg plugin: downloading https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer.plg plugin: downloading: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer.plg ... done plugin: not installing older version
×
×
  • Create New...