Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
https://oxidemod.org/threads/error-app-258550-state-is-0x202-after-update-job-out-of-space.25482/
I started over just as explained here: https://linuxgsm.com/lgsm/rustserver/
I still get the same errors as the post above.
The stderr file is as follows:
sh: 1: /home/rustserver/steamcmd/linux32/../ubuntu12_64/gldriverquery: not found
sh: 1: /home/rustserver/steamcmd/linux32/../ubuntu12_32/gldriverquery: not found
sh: 1: /home/rustserver/steamcmd/linux32/../ubuntu12_64/vulkandriverquery: not found
CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
CAppInfoCacheReadFromDiskThread took 35 milliseconds to initialize
Could you post the output of "df -h"?
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 7.0M 1.6G 1% /run
/dev/md1 4.0G 970M 3.0G 25% /
/dev/vg00/usr 4.8G 959M 3.6G 21% /usr
tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/mapper/vg00-home 4.8G 3.4G 1.2G 75% /home
/dev/mapper/vg00-var 4.8G 1.5G 3.2G 32% /var
tmpfs 1.6G 0 1.6G 0% /run/user/0
tmpfs 1.6G 0 1.6G 0% /run/user/1001
How do I ensure that my /home/rustserver/ directory is large enough? The file system is on RAID drives, I know that much if it makes a difference. I'm a system admin but I don't work with Linux much at all. I know I have the HDD space. It just doesn't seem like it may be available to steamcmd.
Here's the output of fdisk -l:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x13a4ea17
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 8390655 8388608 4G fd Linux raid autodetect
/dev/sda2 8390656 12584959 4194304 2G 82 Linux swap / Solaris
/dev/sda3 12584960 1953525167 1940940208 925.5G fd Linux raid autodetect
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd6eb235a
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 8390655 8388608 4G fd Linux raid autodetect
/dev/sdb2 8390656 12584959 4194304 2G 82 Linux swap / Solaris
/dev/sdb3 12584960 1953525167 1940940208 925.5G fd Linux raid autodetect
Disk /dev/md1: 4 GiB, 4294901760 bytes, 8388480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md3: 925.5 GiB, 993761296384 bytes, 1940940032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/vg00-usr: 5 GiB, 5368709120 bytes, 10485760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/vg00-var: 5 GiB, 5368709120 bytes, 10485760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/vg00-home: 5 GiB, 5368709120 bytes, 10485760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
You root is residing on md1 with 4 GB, while md3 with close to one TB seems to be unused.
Could you reinstall the system?
I figured it had to do with disk space from what I have read. Once I knew the permissions were good that's all that was left that others had experienced. I'll try that. Thanks.