pteromyini

The log error mentions that the nginx binding address is in use. I checked Docker and the virtual machine but did not find any usage of port 80/443. I checked the port usage, and did not find any unusual ports. (Additionally, when I was exporting the logs, the GUI could not export them correctly and smoothly, remaining in the downloading stage for a long time. Therefore, I manually downloaded the recent logs using scp. I am not sure if the exported log data is complete.) root@howienas:~# netstat -tulpen | grep :443 tcp 0 0 100.66.66.66:443 0.0.0.0:* LISTEN 0 330865 662/nginx: master p tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 0 330863 662/nginx: master p tcp 0 0 192.168.66.66:443 0.0.0.0:* LISTEN 0 330864 662/nginx: master p tcp6 0 0 fd7a:115c:a1e0::ca0:443 :::* LISTEN 0 330871 662/nginx: master p tcp6 0 0 ::1:443 :::* LISTEN 0 330869 662/nginx: master p root@howienas:~# netstat -tulpen | grep :80 tcp 0 0 100.66.66.66:80 0.0.0.0:* LISTEN 0 330862 662/nginx: master p tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 0 330860 662/nginx: master p tcp 0 0 192.168.66.66:80 0.0.0.0:* LISTEN 0 330861 662/nginx: master p tcp6 0 0 fd7a:115c:a1e0::ca01:80 :::* LISTEN 0 330868 662/nginx: master p tcp6 0 0 ::1:80 :::* LISTEN 0 330866 662/nginx: master p howienas-diagnostics-20241021-1554.zip

Is there any way to modify it? As a person with obsessive-compulsive disorder, it is very uncomfortable to see it

After deploying docker-compose using the plugin, when a container has an update, when I update the container using the compose plugin, there is still a constant update reminder in the webui docker interface. The only solution I currently feel is to down from the plugin interface, then delete the container, and then open the prompt to update the project. Automatically start and restart NAS

There is a certain probability that the docker container br0 cannot access each other after running for a break or after the network is reconnected. Log prompt: no route to host, which can be repaired after restarting the docker setting. No recurrence pattern was found.

After I use Compose to create a container, it always prompts an update in the docker container interface, but the image is the latest version. I also encountered another problem, when Compose creates a container, there is a certain probability that the system docker will repeatedly create containers after starting docker, which leads to the containers created by Compose can not be used normally.

Thank you very much for your help, everything is back to normal, the data is normal, have a good day

This is my new diagnostic file. howienas-diagnostics-20231214-1731.zip

ok, I have added it and reboot my nas

I did the following: offline disk array, export pool, online disk array, I still can't function properly, and the pool device still prompts: Unable to mount: unsupported file system or no file system

These are my diags howienas-diagnostics-20231214-1650.zip

I accidentally chose the new configuration, so I lost my zfs pool. When I used the zpool import command and reconfigured the pool, my share could operate normally, but the disk array operation still showed that there were disks that could not be mounted.

I tried this method without success, please communicate in github issus next

I don't know what happened, but after installing tailscale my ssh is not available howienas-diagnostics-20230617-0936.zip

I reinstalled and tried again. Yesterday by chance, I found that my ssh service did not start, and the restart still failed. After I uninstalled the plugin, ssh returned to normal. I will reinstall tailscale today to try to reproduce this problem

I don’t know if someone is like me. Using this plugin in unraid 6.12 will cause the SSH service to be closed after booting and cannot be opened

I tried to open the system log server again and enter it again. It looks like the CPU is fully occupied. After confirming with the restart button, I am unable to enter the homepage

This is my diagnostic log howienas-diagnostics-20230605-0947.zip

I try to stop the Array, but It will not shut down, only leaving me the message "Array Stopping Retry unmounting user share(s)..." I installed this, to see what files are active: https://lime-technology.com/forums/topic/41196-open-files-plugin-can-help-with-troubleshooting-why-server-wont-shut-down/，But nothing about/mnt/user is displayed. I use the fuser -km /mnt/user command and it still doesn't work Also, my logs tip: umount: /mnt/user/system: target is busy.

This is indeed correct, but the usage of cache in the current version of unraid is not the well-known "cache" as many people think, which can cause confusion for new users.

In Unraid, the cache was originally used to provide write acceleration for the array. However, with the development of Unraid, the cache pool is no longer just a caching function, but also serves as a storage array. With the introduction of ZFS support in the cache pool in version 6.12, I believe it is necessary to make some changes to the naming of the cache. Cache is a very clear and unambiguous term in the fields of computer science, architecture, and software development, and it refers to providing high-performance IO or temporary storage space for storage systems. I think it is more reasonable to use hot data and cold data to distinguish between the cache pool and the array. Hot data is used to store active or high-performance data, while cold data is used to store read-only, infrequently accessed, or low-performance data. Additionally, using high-performance space and low-performance space to differentiate is also reasonable. This is a naming issue.

This is my log, I don't quite understand which parts of it are useful, can you help me? howienas-diagnostics-20230327-1651.zip

我的UNRAID每次启动都会重新奇偶校验，日志没有任何错误的提示，请问我如何定位问题

我通过联系更换密钥解决了，可能是因为这个密钥被滥用了...我的u盘是新买的

有时，我的 webgui 上的某些按钮没有响应，例如删除、关机、重新启动等。

我在试用屏幕上购买了新的 UNRAID Pro 订阅，但被告知激活黑名单上可能有一个或多个密钥。我该如何解决这个问题