Linux Experimental 18.1

slitterell · October 26, 2019

I see other servers running 18.1. Our clients (the people on my server) are on experimental 18.1. Linux server will not update to 18.1.

Local build id: 4263685 (installed on 2019-10-08 05:34:30)

Available build id: 4263685 (from 2019-10-07 11:17:20)

Invisan · October 26, 2019

Yeah i got the same Problem.

Server Version for me is Alpha 18 (b155)

Code i use to update is ./bin/steamcmd.sh +login anonymous +force_install_dir "7days" app_update 294420 -beta latest_experimental-unstable +quit

Unfortunately this does not update anything. My Client is already on Alpha 18.1 (b2) so i am not able to connect.

jodaco · October 27, 2019

It's latest_experimental not latest_experimental-unstable

Seraphin · October 27, 2019

./bin/steamcmd.sh +login anonymous +force_install_dir "7days" app_update 294420 -beta latest_experimental-unstable +quit

It's only latest_experimental ... there's no -unstable in it. Also you can try to add: -validate

slitterell · October 29, 2019

Mine was latest_experimental but there seems to be a delay on the linux server distro vs windows client releases

ShockValue · October 31, 2019

[ec2-user@ip-172-31-30-121 Steam]$ ./steamcmd.sh +login anonymous +app_update 294420 -beta latest_experimental +quit

Redirecting stderr to '/home/ec2-user/Steam/logs/stderr.txt'

[ 0%] Checking for available updates...

[----] Verifying installation...

Steam Console Client © Valve Corporation

-- type 'quit' to exit --

Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK

Waiting for user info...OK

Success! App '294420' already up to date.

Says I'm up to date but when I try to log in it says the server is running 18 and won't let me play with my 18.1 client.

Adding the -validate to the command checks a bunch, says it's all good, but ends up with the same problem.\

Any thoughts on what I'm missing here?

**meganoth** · November 1, 2019

Says I'm up to date but when I try to log in it says the server is running 18 and won't let me play with my 18.1 client.
Adding the -validate to the command checks a bunch, says it's all good, but ends up with the same problem.\
Any thoughts on what I'm missing here?

You really should check the log of 7D2D to see what is happening.

Ideas:

You downloaded the new version to a different directory and always start the old version at the old place.

Or the 18.0 server never stopped running and the 18.1 server never starts because there is already a running instance.

You misspelled lastest_experimental

slitterell · November 13, 2019

I am still having this issue. I am unable to upgrade to 18.1

local: 4263685, remote: 4263685

fallonjeff · November 13, 2019

Is it time to "opt out" of beta, I believe they only updated stable version?

**SylenThunder** · November 13, 2019

Is it time to "opt out" of beta, I believe they only updated stable version?

Correct. If you're still using -latest_experimental then you're going to be stuck on b6

slitterell · November 13, 2019

but 18.1 isn't experimental. It is stable release. It isn't available for Linux server as stable or experimental. They are behind on their Linux server releases

**SylenThunder** · November 13, 2019

but 18.1 isn't experimental. It is stable release. It isn't available for Linux server as stable or experimental. They are behind on their Linux server releases

If you update to stable, your Linux server will update. I know because I updated all of my Linux servers 6 hours ago.

slitterell · November 13, 2019

Available branches:

Branch | Build ID | Build set on

-----------------------+----------+--------------------

latest_experimental | 4263685 | 2019-10-07 11:17:20

public | 3848769 | 2019-05-30 23:47:19

alpha17.4 | 3848769 | 2019-06-24 11:21:12

alpha17.3 | 3799132 | 2019-05-21 09:11:10

alpha17.2 | 3579269 | 2019-02-27 17:08:24

alpha17.1 | 3472022 | 2019-01-18 16:26:16

alpha17.0 | 3421646 | 2019-01-05 09:31:14

alpha16.4 | 2222523 | 2017-10-27 03:02:48

alpha15.2 | 1642899 | 2017-02-22 04:34:55

alpha14.7 | 1189196 | 2016-06-20 11:45:46

alpha13.8 | 963565 | 2016-03-22 05:56:25

alpha12.5 | 745252 | ?

alpha11.6 | 658147 | ?

alpha10.4 | 480993 | ?

alpha9.3 | 385244 | ?

alpha8.8 | 334790 | ?

**SylenThunder** · November 13, 2019

Also note, experimental 18.1 is on build 6. Stable 18.1 is on build 7. They are different versions.

- - - Updated - - -

Use "app_update 294420 -verify +quit" to update to the stable branch.

slitterell · November 13, 2019

Also note, experimental 18.1 is on build 6. Stable 18.1 is on build 7. They are different versions.

- - - Updated - - -

Use "app_update 294420 -verify +quit" to update to the stable branch.

I tried that, no go

slitterell · November 13, 2019

build is the same/ not updated

slitterell · November 13, 2019

####:~$sudo 7dtd.sh updateengine

Engine is already at the newest build on the selected branch "latest_experimenta l" (local: 4263685, remote: 4263685).

Run with the --force parameter to update/validate the engine files anyway.

Run with --experimental, --stable or --branch to switch to a different branch.

####:~$ sudo 7dtd.sh updateengine --check

Installed:

Build ID: 4263685

Installed on: 2019-10-08 05:34:30

From branch: latest_experimental

Available branches:

Branch | Build ID | Build set on

-----------------------+----------+--------------------

latest_experimental | 4263685 | 2019-10-07 11:17:20

public | 3848769 | 2019-05-30 23:47:19

alpha17.4 | 3848769 | 2019-06-24 11:21:12

alpha17.3 | 3799132 | 2019-05-21 09:11:10

alpha17.2 | 3579269 | 2019-02-27 17:08:24

alpha17.1 | 3472022 | 2019-01-18 16:26:16

alpha17.0 | 3421646 | 2019-01-05 09:31:14

alpha16.4 | 2222523 | 2017-10-27 03:02:48

alpha15.2 | 1642899 | 2017-02-22 04:34:55

alpha14.7 | 1189196 | 2016-06-20 11:45:46

alpha13.8 | 963565 | 2016-03-22 05:56:25

alpha12.5 | 745252 | ?

alpha11.6 | 658147 | ?

alpha10.4 | 480993 | ?

alpha9.3 | 385244 | ?

alpha8.8 | 334790 | ?

Engine on the latest build.

####:~$ sudo 7dtd.sh updateengine --experimental

Engine is already at the newest build on the selected branch "latest_experimenta l" (local: 4263685, remote: 4263685).

Run with the --force parameter to update/validate the engine files anyway.

Run with --experimental, --stable or --branch to switch to a different branch.

####:~$ sudo 7dtd.sh updateengine --stable

Engine is already at the newest build on the selected branch "public" (local: 4263685, remote: 3848769).

Run with the --force parameter to update/validate the engine files anyway.

Run with --experimental, --stable or --branch to switch to a different branch.

**SylenThunder** · November 14, 2019

Have you updated Alloc's scripts?

slitterell · November 14, 2019

all scripts and fixes up to date but that shouldn't affect the read out from steam saying it is up to date and saying there is no other build, right?

**SylenThunder** · November 14, 2019

Ok, for giggles I restored everything from an old update.

Here's what I get.

root@beta:~# 7dtd.sh updateengine --checkUpdating version information...
Installed:
 Build ID:     4317498 
 Installed on: 2019-10-23 22:07:30
 From branch:  public


Available branches:
Branch                 | Build ID | Build set on
-----------------------+----------+--------------------
public                 |  4385749 | 2019-11-13 15:22:43
alpha18.1              |  4377937 | 2019-11-13 06:22:37
alpha18.0              |  4317498 | 2019-10-29 06:28:57
alpha17.4              |  3848769 | 2019-06-24 12:21:12
alpha16.4              |  2222523 | 2017-10-27 04:02:48
alpha15.2              |  1642899 | 2017-02-22 05:34:55
alpha14.7              |  1189196 | 2016-06-20 12:45:46
alpha13.8              |   963565 | 2016-03-22 06:56:25
alpha12.5              |   745252 |  ?
alpha11.6              |   658147 |  ?
alpha10.4              |   480993 |  ?
alpha9.3               |   385244 |  ?
alpha8.8               |   334790 |  ?

So then I run the update command for stable

root@beta:~# 7dtd.sh updateengine --stable
A newer version of the engine is available.
Local build id:     4317498 (installed on 2019-10-23 22:07:30)
Available build id: 4385749 (from 2019-11-13 15:22:43)


Continue? (yn) y
Updating...
Redirecting stderr to '/root/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.


Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Update state (0x3) reconfiguring, progress: 0.00 (0 / 0)
Update state (0x11) preallocating, progress: 65.57 (7805379876 / 11904339347)
.....

And it's off downloading the latest update.

slitterell · November 14, 2019

so why would mine not show latest updates? how do I get it to update to update that list?

**SylenThunder** · November 14, 2019

so why would mine not show latest updates? how do I get it to update to update that list?

Dunno. The only time I recall that ever happening was when there was a change to Steamcmd, and Allocs scripts needed to be updated in the way it was checking.

slitterell · November 14, 2019

Well, fixed it. I did a force update even though it said it was up to date when it was on a18 and it said it updated to the same version, a18. It then updated to a18.1 ¯\_(ツ)_/¯

Engine is already at the newest build on the selected branch "latest_experimental" (local: 4263685, remote: 4263685).

Run with the --force parameter to update/validate the engine files anyway.

Run with --experimental, --stable or --branch to switch to a different branch.

slitterell@minecraft:~/Steam/appcache$ sudo 7dtd.sh updateengine --branch latest_experimental --force

A newer version of the engine is available.

Local build id: 4263685 (installed on 2019-10-08 05:34:30)

Available build id: 4263685 (from 2019-10-07 11:17:20)

Continue? (yn) y

Updating...

------------------------------------------------------------------

Updating version information...

rm: cannot remove '/root/Steam/appcache/appinfo.vdf': No such file or directory

Installed:

Build ID: 4385749

Installed on: 2019-11-14 02:03:58

From branch: public

Available branches:

Branch | Build ID | Build set on

-----------------------+----------+--------------------

public | 4385749 | 2019-11-13 14:22:43

alpha18.1 | 4377937 | 2019-11-13 05:22:37

alpha18.0 | 4317498 | 2019-10-29 05:28:57

alpha17.4 | 3848769 | 2019-06-24 11:21:12

alpha16.4 | 2222523 | 2017-10-27 03:02:48

alpha15.2 | 1642899 | 2017-02-22 04:34:55

alpha14.7 | 1189196 | 2016-06-20 11:45:46

alpha13.8 | 963565 | 2016-03-22 05:56:25

alpha12.5 | 745252 | ?

alpha11.6 | 658147 | ?

alpha10.4 | 480993 | ?

alpha9.3 | 385244 | ?

alpha8.8 | 334790 | ?

Engine on the latest build.

Sign In

Linux Experimental 18.1

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Archived