[Bug]: lgsm don't update node_modules only by remove the folder it redownload it lol
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 35/100
調査の方向性
The failure surfaces when the monitor command installs and invokes gamedig under lgsm/node_modules; start by reading the gamedig install/download path used by the monitor command and by update-lgsm, then compare how each decides whether the module tree is current. The report shows a stale nested dependency (fast-xml-builder expecting xml-naming) that only a full reinstall fixed, so the likely gap is a version/integrity check rather than a re-download. Done means a documented rule for when node_modules is refreshed and a manual path to reproduce the stale tree on a test box.
索引モデルが issue の本文から書いたものです。
説明
Severity
severity: critical
Reproducibility
reproducible: unable
Regression
regression: unknown
Affects latest release
latest-release: yes
User story
update-lgsm need to check if node_modules are up to date lol
Script name
ns2server
Game
Natural Selection 2
Linux distro
Ubuntu 26.04
Command
command: monitor
Expected behavior
i used monitor over crontab and it should restart the server when it's dead or hang xD
Actual behavior
i used monitor over crontab and server keep restarting all 5 mins and no error what the Problem is :(
Further information
found that in the logs:
Nov 13 11:17:51.184 ns2server: START: INFO: LinuxGSM version: v26.6.0
Nov 13 11:17:51.210 ns2server: START: PASS: core_exit.sh exiting with code: 0
Nov 13 11:20:01.881 ns2server: CORE: PASS: Using cached IP as public IP address
Nov 13 11:20:02.692 ns2server: MONITOR: PASS: Using cached IP as public IP address
Nov 13 11:20:04.977 ns2server: MONITOR: PASS: Using cached IP as public IP address
Nov 13 11:20:06.608 ns2server: MONITOR: INFO: Checking session: CHECKING
Nov 13 11:20:06.844 ns2server: MONITOR: PASS: Checking session: OK
Nov 13 11:20:08.457 ns2server: MONITOR: INFO: Querying port: gamedig: 192.168.178.20:27051 : 1 : QUERYING
Nov 13 11:20:08.806 ns2server: MONITOR: WARN: Querying port: gamedig: 192.168.178.20:27051 : 1 : FAIL
Nov 13 11:20:10.418 ns2server: MONITOR: INFO: Querying port: gamedig: 178.201.208.119:27051 : 1 : QUERYING
Nov 13 11:20:10.770 ns2server: MONITOR: WARN: Querying port: gamedig: 178.201.208.119:27051 : 1 : FAIL
Nov 13 11:20:30.499 ns2server: MONITOR: INFO: Querying port: gamedig: 192.168.178.20:27051 : 2 : QUERYING
Nov 13 11:20:30.853 ns2server: MONITOR: WARN: Querying port: gamedig: 192.168.178.20:27051 : 2 : FAIL
Nov 13 11:20:32.465 ns2server: MONITOR: INFO: Querying port: gamedig: 178.201.208.119:27051 : 2 : QUERYING
Nov 13 11:20:32.809 ns2server: MONITOR: WARN: Querying port: gamedig: 178.201.208.119:27051 : 2 : FAIL
Nov 13 11:20:52.550 ns2server: MONITOR: INFO: Querying port: gamedig: 192.168.178.20:27051 : 3 : QUERYING
Nov 13 11:20:52.891 ns2server: MONITOR: WARN: Querying port: gamedig: 192.168.178.20:27051 : 3 : FAIL
Nov 13 11:20:54.502 ns2server: MONITOR: INFO: Querying port: gamedig: 178.201.208.119:27051 : 3 : QUERYING
Nov 13 11:20:54.848 ns2server: MONITOR: WARN: Querying port: gamedig: 178.201.208.119:27051 : 3 : FAIL
Nov 13 11:21:14.581 ns2server: MONITOR: INFO: Querying port: gamedig: 192.168.178.20:27051 : 4 : QUERYING
Nov 13 11:21:14.934 ns2server: MONITOR: WARN: Querying port: gamedig: 192.168.178.20:27051 : 4 : FAIL
Nov 13 11:21:16.547 ns2server: MONITOR: INFO: Querying port: gamedig: 178.201.208.119:27051 : 4 : QUERYING
Nov 13 11:21:16.889 ns2server: MONITOR: WARN: Querying port: gamedig: 178.201.208.119:27051 : 4 : FAIL
Nov 13 11:21:36.630 ns2server: MONITOR: INFO: Querying port: gamedig: 192.168.178.20:27051 : 5 : QUERYING
Nov 13 11:21:36.971 ns2server: MONITOR: WARN: Querying port: gamedig: 192.168.178.20:27051 : 5 : FAIL
Nov 13 11:21:37.181 ns2server: MONITOR: WARN: Querying port: gamedig: 192.168.178.20:27051 : 5 : FAIL
Nov 13 11:21:37.412 ns2server: MONITOR: WARN: Query port: Port 27051/udp is open by the game server (server_linux) but it did not answer; the server may be hung, or the query port or type may not match
Nov 13 11:21:37.692 ns2server: MONITOR: PASS: Using cached IP as public IP address
Nov 13 11:21:37.707 ns2server: MONITOR: INFO: Sending alert: Unable to query ns2server. Game server has been restarted
Nov 13 11:21:39.559 ns2server: MONITOR: PASS: Sending Discord alert
Nov 13 11:21:40.427 ns2server: RESTART: PASS: Using cached IP as public IP address
Nov 13 11:21:41.249 ns2server: RESTART: PASS: Using cached IP as public IP address
Nov 13 11:21:42.136 ns2server: STOP: PASS: Using cached IP as public IP address
Nov 13 11:21:42.570 ns2server: STOP: PASS: Using cached IP as public IP address
Nov 13 11:21:43.805 ns2server: STOP: INFO: Graceful: CTRL+c
Nov 13 11:21:44.230 ns2server: STOP: PASS: Graceful: CTRL+c: OK: 1 seconds
Nov 13 11:21:45.463 ns2server: START: PASS: Using cached IP as public IP address
Nov 13 11:21:46.298 ns2server: START: PASS: Using cached IP as public IP address
Nov 13 11:21:46.932 ns2server: START: INFO: Rotating log files
because i don't saw any errors i disabled monitor in crontab -e, then i checked today manually the monitor command and get this error
ns2server@homeserver:~$ ./ns2server m
[ OK ] Monitoring ns2server: Checking session ... OK
[ .... ] Monitoring ns2server: Querying port: gamedig: 192.168.178.20:27051 : 0/1 ... QUERYINGnode:internal/modules/helpers:81
internalFsBinding.legacyMainResolve(pkgPath, main, base),
^
Error: Cannot find package '/home/ns2server/lgsm/node_modules/fast-xml-builder/node_modules/xml-naming/index.js' imported from /home/ns2server/lgsm/node_modules/fast-xml-builder/src/orderedJs2Xml.js
at legacyMainResolve (node:internal/modules/helpers:81:23)
at Object.loaderMethodWrapper [as legacyMainResolve] (node:internal/modules/helpers:123:12)
at legacyMainResolve (node:internal/modules/esm/resolve:171:40)
at packageResolve (node:internal/modules/esm/resolve:763:12)
at moduleResolve (node:internal/modules/esm/resolve:840:18)
at defaultResolve (node:internal/modules/esm/resolve:973:11)
at #cachedDefaultResolve (node:internal/modules/esm/loader:708:20)
at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:728:38)
at ModuleLoader.resolveSync (node:internal/modules/esm/loader:766:56)
at #resolve (node:internal/modules/esm/loader:690:17) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v26.13.1
[ .... ] Monitoring ns2server: Querying port: gamedig: 178.201.208.119:27051 : 0/1 ... QUERYINGnode:internal/modules/helpers:81
internalFsBinding.legacyMainResolve(pkgPath, main, base),
^
Error: Cannot find package '/home/ns2server/lgsm/node_modules/fast-xml-builder/node_modules/xml-naming/index.js' imported from /home/ns2server/lgsm/node_modules/fast-xml-builder/src/orderedJs2Xml.js
at legacyMainResolve (node:internal/modules/helpers:81:23)
at Object.loaderMethodWrapper [as legacyMainResolve] (node:internal/modules/helpers:123:12)
at legacyMainResolve (node:internal/modules/esm/resolve:171:40)
at packageResolve (node:internal/modules/esm/resolve:763:12)
at moduleResolve (node:internal/modules/esm/resolve:840:18)
at defaultResolve (node:internal/modules/esm/resolve:973:11)
at #cachedDefaultResolve (node:internal/modules/esm/loader:708:20)
at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:728:38)
at ModuleLoader.resolveSync (node:internal/modules/esm/loader:766:56)
at #resolve (node:internal/modules/esm/loader:690:17) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v26.13.1
[ FAIL ] Monitoring ns2server: Querying port: gamedig: 178.201.208.119:27051 : 3/1 ... WAIT^C
then i remove /home/ns2server/lgsm/node_modules over winscp and use the monitor command again and then everything worked again lol
ns2server@homeserver:~$ ./ns2server m
[ .... ] Monitoring ns2server:
Installing Gamedig
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 746 100 746 0 0 15822 0 0
npm warn deprecated [email protected]: Use promise-toolbox/fromEvent instead
npm warn deprecated [email protected]: See https://github.com/mvdan/sh/issues/1145
added 66 packages in 734ms
25 packages are looking for funding
run npm fund for details
[ OK ] Monitoring ns2server: Checking session ... OK
[ OK ] Monitoring ns2server: Querying port: gamedig: 192.168.178.20:27051 : 0/1 ... OK
update-lgsm should check that /lgsm/node_modules as well ?
Pre-checks
- I ran update and validate before reporting this issue.
Relevant log output
Steps to reproduce
idk how to reproduce it i just Updated from Ubuntu Server 24.04.5 LTS to Ubuntu Server 26.04.1 LTS, and first time no Problems just yesterday i got that Problem.
- 主要言語
- Shell
- スター
- 4.9k
- フォーク
- 866
- 平均マージ
- 17時間 58分
- マージ済み PR(30日)
- 100
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
GameServerManagers/LinuxGSM のほかの issue
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
GameServerManagers/LinuxGSM#5242 ·
メンテナーはふだん 1 日以内に返信
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
GameServerManagers/LinuxGSM#5241 ·
メンテナーはふだん 1 日以内に返信
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
GameServerManagers/LinuxGSM#5240 ·
メンテナーはふだん 1 日以内に返信
-
engine: null game: Teamspeak 3
難易度 3/5 半日 初心者へのやさしさ 66/100
GameServerManagers/LinuxGSM#5237 ·
メンテナーはふだん 1 日以内に返信
-
command: install command: monitor command: start priority: medium scope: all servers type: feature
難易度 3/5 1〜2日 初心者へのやさしさ 68/100
GameServerManagers/LinuxGSM#5204 ·
メンテナーはふだん 1 日以内に返信
GameServerManagers/LinuxGSM の issue をすべて見る
似ている issue
-
enhancement good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
varnish/helm-varnish#173 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
📦 Update Request
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
cdnjs/packages#2225 · コメント 1 件 ·
メンテナーはふだん 3 日以内に返信
-
good first issue help wanted testing
難易度 1/5 1時間未満 初心者へのやさしさ 78/100