pappaq
-
Posts
210 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by pappaq
-
-
And I am having the "File not found." error again after rebooting my server. Attached is the last diagnostics from yesterday. I don't want to set up my server again from scratch this time. Does anybody got a clue?
-
I've never had this error. BUT today the electricity was gone for five hours and my server was cut from electricity abruptly. Could you guys please take a look at the diagnostics?
Thanks
-
I've deleted the docker img and VM image and set up everything from scratch. The server ist running now witout a problem for nearly 4 days straight. Looks solved. If it occures again, I will report here.
-
I suspect more and more that it has something to do with the shares. Every time I start working on the shares in the main tab, the error comes up. I will try to reproduce the behavior...
-
15 hours ago, trurl said:
From your diagnostics, I see you are using 27G of 40G docker.img. Have you had problems filling docker.img? I run 15-20 containers and only use about half of 20G docker.img
Also, your system share has files on the array.
I have not had any problems with this so far. It was pretty full about two years ago and I enlarged it. No problems with that since.
I am going to reboot again and going to fix the shares.
-
15 hours ago, trurl said:
What I was specifically after was rootfs, the very first thing in the list from that command. Those results are also in diagnostics, but since you couldn't get them I asked for the results of the command.
Since you rebooted before getting the command results, we don't know what the results of that command would be if you did it while you were having the problem.
fortunately, the error occured again yesterday, some time after the reboot. There does not seem to be smth. wrong.
-
18 hours ago, trurl said:
In that case, I suspect you are filling rootfs (the RAM the OS lives in) and so the OS can't work reliably anymore. One common way to fill rootfs would be a container host path that isn't actual storage. Or anything else (such as a script) writing to a path that isn't actual storage.
What do you get from the command line with this?
df -h
I've rebooted the server before I read your comment...I've taken diagnostics and df -h shows no particular partition filling up over the course of the last 10 minutes.
The diagnostics are after the fresh reboot. I don't know if they help. And it seems like the only full drives are the data drives inside the pool, so no problem there?
I will have a look at it for the next hours and watch the partitions closely.
Thanks.
-
24 minutes ago, trurl said:
Some of the last entries in syslog are about plugins and scripts, including a script you have apparently setup with the User Scripts plugin.
Boot in SAFE mode, disable Docker and VM Manager in Settings, and see if it works like that for a few days.
The scripts are super basic move scripts which are triggered by cron every few minutes. Worked for month.
-
25 minutes ago, trurl said:
You should have taken diagnostics when you could get them instead of waiting until you couldn't.
Does it work again for a while if you reboot?
How should I have known that the command will vanish when the error occures? It normally returns to normal operation after the reboot.
Currently I've got no time to test. Furthermore my heating is automated via home assistant running on the server, making downtimes and disabling Dockers and VMs to my last resort.
I will try restarting and posting diagnostics then. Maybe you can review it then and tell if there is anything that indicates this kind of behavior.
-
Ok, everytime I try to load the GUI in any browser the following error occures in the syslog:
Feb 25 10:39:04 dringenet-MS nginx: 2022/02/25 10:39:04 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net" Feb 25 10:39:05 dringenet-MS nginx: 2022/02/25 10:39:05 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net" Feb 25 10:39:06 dringenet-MS nginx: 2022/02/25 10:39:06 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net" Feb 25 10:39:07 dringenet-MS nginx: 2022/02/25 10:39:07 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net" Feb 25 10:39:07 dringenet-MS nginx: 2022/02/25 10:39:07 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net" Feb 25 10:39:08 dringenet-MS nginx: 2022/02/25 10:39:08 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"
Does anybody got a clue?
-
And we are back to square one. The bug is back. And strangely enough the diagnostics command is gone as soon as the bug occures.
I can provide the syslog.txt only...If nobody got a clue I will try to investigate next weekend.
After disabling netdata docker the "FastCGI sent in stderr: "Primary script unknown"" is gone and does not spam the logs. But now I see that nothing really indicates smth. strange in the logs that indicates the bug. Soooo I am going to try safemode etc. when I find the time and will report back here.
This fucking sucks and will cost so much time...
-
Ok, I've reinstalled the flash drive and copied my config to it. Server back up and running. diagnostics is a command now...
I think I have never had a clean installation since I've started using unraid. And I changed the hardware and setups multiple times.
If the error occures again I will post the diagnostics. Thank you so much trurl for your support!
-
I thought I had installed a plugin which was configured to make frequent backups...didn't check it for a long time though.
Checked the flash drive and found no errors. Made a backup. Trying it again now.
Could you guide me to a tutorial to reinstall the flash drive?
-
Is there a way to bring the "diagnostics" command back to life?
-
14 minutes ago, trurl said:
Have you tried booting in SAFE mode? With no dockers or VMs?
Do you have a flash backup?
I have not tried that. Everything works except the GUI. Restarting nginx via etc/rc.d/rc.nginx restart didn't help either...
I've got a flash backup from march last year...that would be my last resort.
I opened this thread before that, so I guess it does not guarantee to solve the issue, because the current behavior occured before march last year.
Is there another way maybe? The server run 120 days after the last reboot without any issues...
-
All dockers are available and I am able to login to the server via SSH. I can't access the GUI and get:
Even when I try to enter just the ip after https://...
Also I get this one back in putty:
The last time this occured I was able to solve it by simply rebooting. I've done so 3 times now. It comes back...
-
Actually it does not work. I'm getting "command not found" back, when I'm logged in via SSH.
-
I've got the problem coming up again after rebooting and installing a SSD.
Rebooting helps for around half an hour until it occures again.
-
Does really nobody got a clue? I've searched many sites but can't figure out a good and safe way to do it.
Bump
-
Hey there,
I hope I am at the right place for this question.
My question is:
I need a script that compares two folders and deletes the duplicates in the second folder. This only needs to happen at folder level.
/mnt/user/temp/folder1/...
/mnt/user/temp/folder2/... <-- delete duplicate folders and files in the folders
I don't trust myself to do it, since it involves deleting possibly thousands of folders.
Could anybody help me, please?
cheers
-
Hey there, I can't right click on the nodes via VNC viewer in this instance of deconz. Does anybody got a clue how this could work?
Here a screenshot how it is in the docker and how it is in the normal deconz installation on my PC. I need the right click menu to add some sensors.
I need the possibility to right click nodes and get the options shown there.
Thanks in advance!
-
4 minutes ago, binhex said:
you are in the wrong support thread, this is for sabnzbd not the vpn variant (left click docker icon and select 'support'), as for your issue, see Q17 here:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
please reply in the correct support thread.
Thanks for your quick reply!
-
Hello all,
I have the following problem with my SABnzbd docker. Unfortunately, it no longer starts properly and the web frontend is no longer displayed to me. I just can't figure it out from the following logs.
Can someone help me to find a clue?
Hello all,
I have the following problem with my SABnzbd docker. Unfortunately, it no longer starts properly and the web frontend is no longer displayed to me. I just can't figure it out from the following logs.
Can someone help me to find a clue?
Thank you in advance!
-
5 hours ago, ChatNoir said:
Whoops, my bad you are right, I got confused with the startup temp issue.
If memory serve*, the issue with telegraph is that some components are either not up-to-date or missing.
I think It can be fixed with post arguments in the docker template.
* recent experience show that my memory is not always to be trusted.
I've disabled the plugin "HDDTemps" in the telegraf config. It would be awesome to get the functionality back up to monitor the HDD temps via grafana. But unti that I am happy that the HDDs stay spun down.
I am tackling the issue in the next few days, if I find the time for it.
Maybe you could explain the "post agrument" idea a little further?
Thanks!
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted
Same problem here. "linuxserver/nextcloud:140" downgrades too far.