Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
So to confirm, during a lag spike, you'd like me to SSH in as the user that controls RustDedicated (the one I installed LGSM with) and simply run "vmstat"?
Just want to make sure I have the process right, because the issue only happens once a day or so, so if I don't nail it the first time I won't have another chance for a while.
edit: running vmstat during a time of normal operation (right now, no lag spike) returns this:
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
1 0 0 12983608 6492 180800 0 0 33 10 987 734 8 1 92 0 0
Start up `vmstat -n 1 | tee /tmp/vmstat.out` when you start Rust. Then when the system freezes up, you can correlate the system resources with the vmstat output at the same time.
If you want more detailed time integrated into the log, then try something like:
Then when your system freezes, note the time and correlate it with the vmstat output in /tmp/system-status.out.
The ressource manager shows that rust stops using any ressources at all.
Any help?
We are using an Ubuntu v-server