Replies: 3 comments 11 replies
-
|
restore your backup, then try the upgrade again |
Beta Was this translation helpful? Give feedback.
-
|
do you have this line in |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it is the very first line. |
Beta Was this translation helpful? Give feedback.
-
|
strange, that should take care of the "too many open files error" it has worked for people with way more agents than you. what OS are you on? and can you please paste the output of this command for i in $(ps aux | grep nginx | grep -v grep | awk '{print $2}'); do cat /proc/$i/limits; done |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your help with this. I am running Ubuntu 20.04.4 LTS administrator@trmm:~$ for i in $(ps aux | grep nginx | grep -v grep | awk '{print $2}'); do cat /proc/$i/limits; done |
Beta Was this translation helpful? Give feedback.
-
|
hmm so limit for each nginx worker process is still 1024, not 1000000 |
Beta Was this translation helpful? Give feedback.
-
2nd person with nginx not restarting? |
Beta Was this translation helpful? Give feedback.
-
|
this is the first i've heard of it. update script stops nginx before updating, and starts it at the end so unless update script was modified i am not sure why it didn't get restarted |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I didn't think there was any others, other than my miss guided attempt there in discord. I checked the update script just incase, but guess users may change it on their servers |
Beta Was this translation helpful? Give feedback.
-
|
thought bbrendon had nginx not sticking...but he was probably just messing with settings and didn't restart. ;) |
Beta Was this translation helpful? Give feedback.
-
|
no, bbrendon settings were correct. issue was not related to settings but something with his machine or network not freeing up used connections |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
I need to preface this with the "I know enough to be dangerous" with Linux so if there are any error logs that I can procure to help I just need a pointer as to the location of the logs. Also this is the first time I have posted anything to GitHub so please let me know if I am doing something incorrectly. It may be important to know that I have 607 agents reporting to RMM.
After upgrading to 0.14.2 using the official upgrade script I have been getting a massive amount of sporadic errors that seem to do with NGINX. If I refresh RMM I will get NGINX error 500 but if I refresh a few more times it will display RMM correctly. If I try to take control of a device sometimes I will get "Backend is offline" or "Unable to connect to websocket, click here to reconnect". If I click reconnect enough times it will allow me to connect through Mesh. Other times I will get a white screen when clicking on Take Control. Other times I will get an NGINX 500 internal server error when clicking on Take Control.
I am seeing a TON of the following error in NGINX error logs:
2022/07/19 15:42:04 [alert] 1040#1040: *41180 socket() failed (24: Too many open files) while connecting to upstream, client:
Also here are the results for ulimits:
-Hn 1048576
-Sn 1024
I know it is a lot of different occurring issues but I would appreciate any help with it.
Screenshots
Beta Was this translation helpful? Give feedback.
All reactions