SteamCMD can sometimes output errors when something goes wrong. Sadly Valve has never released an official list of what the error messages mean. Because of this, a lot of guess work has been needed to figure it out. This page will highlight what we already know and info on researching what the error might mean in the hope that you can contribute to understanding SteamCMD errors.
SteamCMD uses hexadecimal numbers to give its current "state". Every time SteamCMD does something it changes its state. When SteamCMD fails it will output its has hexadecimal state, for example 0x202
.
Not enough disk space.
Error! App '<appid_number>' state is 0x202 after update job.
​ | ​ |
Reason | Not enough disk quota |
Hex | 0x202 |
Decimal/StateFlags | 514 |
Unknown error, if you have any details please let us know
Error! App '<appid_number>' state is 0x206 after update job.
​ | ​ |
Reason | ​ |
Hex | 0x206 |
Decimal/StateFlags | 518 |
Missing content_log.txt if you have experienced this error and have a log it please let us know.
Connection issue with steam, you will need to wait for the steam servers to recover.
Error! State is 0x402 after update job.
​ | ​ |
Reason | ​ |
Hex | 0x402 |
Decimal/StateFlags | 1026 |
Missing content_log.txt if you have experienced this error and have a log it please let us know.
Unknown error, if you have any details please let us know
Error! State is 0x602 after update job.
​ | ​ |
Reason | ​ |
Hex | 0x602 |
Decimal/StateFlags | 1538 |
Missing content_log.txt if you have experienced this error and have a log it please let us know.
Unknown error, if you have any details please let us know
Error! App '<appid_number>' state is 0x606 after update job.
​ | ​ |
Reason | ​ |
Hex | 0x606 |
Decimal/StateFlags | 1542 |
Missing content_log.txt if you have experienced this error and have a log it please let us know.
Error! App '<appid_number>' state is is 0x2 after update job.
​ | ​ |
Reason | ​ |
Hex | 0x2 |
Decimal/StateFlags | 2 |
Missing content_log.txt if you have it please let us know.
Error! App '<appid_number>' state is 0x6 after update job.
​ | ​ |
Reason | No connection to content servers |
Hex | 0x6 |
Decimal/StateFlags | 6 |
Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Update state (0x5) validating, progress: 13.48 (1554089956 / 11530459441)
Update state (0x11) preallocating, progress: 8.53 (983870089 / 11530459441)
Update state (0x61) downloading, progress: 1.11 (127644881 / 11530459441)
Update state (0x101) committing, progress: 3.43 (395043827 / 11530459441)
To get more info and output see the SteamCMD logs in ~/.steam/logs
. The most useful log is content_log.txt
that will provide more information of errors.
If you have experienced an error we don't have logs for please can you provide them to us to assist in diagnosing the issue.
SteamCMD uses hex error codes such as 0x202
which can be converted in to decimal 514
. Using the table below you can work out that the status messages. By doing a calculation. Find the highest number below the state 512
which if the first error. Then take the number away from the total 514-512=2
which gives you the last error. This can be done for any error
514-512-2=0
512 StateUpdateRunning
, 2 StateUpdateRequired
​ | ​ |
StateInvalid | 0 |
StateUninstalled | 1 |
StateUpdateRequired | 2 |
StateFullyInstalled | 4 |
StateEncrypted | 8 |
StateLocked | 16 |
StateFilesMissing | 32 |
StateAppRunning | 64 |
StateFilesCorrupt | 128 |
StateUpdateRunning | 256 |
StateUpdateRunning | 512 |
StateUpdateStarted | 1024 |
StateUninstalling | 2048 |
StateBackupRunning | 4096 |
StateReconfiguring | 65536 |
StateValidating | 131072 |
StateAddingFiles | 262144 |
StatePreallocating | 524288 |
StateDownloading | 1048576 |
StateStaging | 2097152 |
StateCommitting | 4194304 |
StateUpdateStopping | 8388608 |
This table is from 2015 and is probably out dated now but its the best we currently have.
./steamcmd.sh: line 17: ulimit: open files: cannot modify limit: Operation not permitted
Some users may get a ulimit error (no permission/cannot open file) while script is starting up. This error caused by a low setting of the -n parameter (number of file descriptors) of ulimit. Some servers forbid increasing ulimit values after startup (or beyond a limit set by root). This can be fixed by changing the file descriptor number ulimit:
ulimit -n 2048
The Steam account being used does not have a license for the required game.
The password for the branch is incorrect.
Ignore the error, do not do anything to attempt to fix it. It is a known error that has been happening ever since SteamPipe was introduced (this includes on Source1 games). It does not cause any issue and can be ignored.
Ignore the error, do not do anything to attempt to fix it. It does not cause any issue and can be ignored.
Ignore the error, do not do anything to attempt to fix it. It does not cause any issue and can be ignored.
Ignore the error, do not do anything to attempt to fix it. It does not cause any issue and can be ignored.