Sorry if format is poor. I am very new to Webmin and this forum.
The Symptom is that Webmin is listening on port 10000. The server is nginx.
In all cases, if I access the server on port 10000 I get a Webmin login prompt. That seems fine regardless of the browser type. If I log in with Firefox browser version 153.0.1 (64 bit) everything seems to work and the display is as expected. The Dashboard is nominal and all is well.
If I log in using the DuckDuckGo (beta) browser the system seems to hang. There are a lot of errors posted on the console but the system is occupied so extensively that I cannot even perform console commands. I have experienced this twice now and in both cases had to reboot the server to regain control.
The first time I used DuckDuckGo because that is my normal browser. After that I used Firefox successfully several times. However I forgot today and accidently used DuckDuckGo and thus had it occur again.
It is not critical to my usage since I can simply use Firefox. But it seems like the crashy part probably is not good. I can try to get more debugging information if anyone is interested but it is expensive in time since it takes about 20 minutes and a server restart to learn anything.
Thanks! I really appreciate your having spent time to investigate this.
I took your suggestion and ran “top” on an ssh terminal. That immediately showed the difference between the two browsers.
The ddg (DuckDuckGo) browser resulted in the kswapd0 demon consuming a constant 35% CPU. The VPS I am running on only has 1Gig of real memory. So some serious thrashing go on. I noticed a huge spike in the number of processes called /usr/libexec/we. This continues until the system can’t maintain the web connection. After that no further connection is possible. As before I couldn’t even shutdown the system and had to cut the power (not sure what the VPS provider actually does to effect that but it is treated the same).
After rebooting I tried the same with the Firefox browser and there was no swap activity at all. Also no /usr/libexec/we processes. Just nice and quiet.
So I figure that the ddg browser is making some (look ahead maybe?) demands on the server. Not sure how much memory would have satisfied the demand (I noted that your server shows 3.56G so maybe thats enough?)
In anycase I will write this one off to a ddg being a hog and not enough server memory to feed it.
1 Gig I would create just used for testing, I don’t think its enough for permanent server unless its running very few domains. BTW have you allocated swap? Do you see virtual memory..
Logging onto virtualmin can cause a pick in memory use for a shot period.Weird DuckDuckGo is any different then say Firefox or chrome as its just a browser.
The fact that Firefox works while DuckDuckGo Browser crashes the server makes me think the problem is probably browser specific rather than Webmin itself. I’d compare the request headers from both browsers and check the Webmin logs at the exact time the crash happens. It would also be useful to know whether the same behavior happens on another machine or with a fresh Webmin installation.
Thanks again for the support responses!
As Stefan guessed I have, in fact, no swap configured! (I never checked!)
So before I go much further I need to configure a couple Gigs for that.
I suspect that that will clear the problem up. I think that the ddg browser probably does a lot more pre-fetching than the Firefox so I probably don’t exceed the real memory limit when using Firefox (based upon no actual knowledge).
I will let you know after I set the swap to something greater than zero.
