Apparently it was a permission problem.

My user home folder was being created manually with *mkdir*, which made its
owner *root:root*. Creating it with *useradd -m tf2* apparently fixed the
issue. I could've also chown the dir, but the *useradd -m* seems like the
proper way to go.

So, yeah, permissions. ¯\_(ツ)_/¯

Many thanks to all those who took the time to answer.

Hope this helps some other fool in the future.


_pilger

On 15 October 2017 at 18:00, pilger <[email protected]> wrote:

> @Svensk
>
> Can't really do that right now, since I'm rebuilding the whole thing. I
> don't think it's anyhow related to resources, since the proper output for
> an up-to-date server would be
>
>>
>>
>> *Updating server using Steam.*
>> *----------------------------*
>> *Redirecting stderr to '/home/tf2/.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.**login anonymous*
>>
>> *Connecting anonymously to Steam Public...Logged in OK*
>> *Waiting for user info...OK*
>> *force_install_dir /home/tf2/srcds*
>> *app_update 232250*
>> *Success! App '232250' already up to date.*
>> *quit**CWorkThreadPool::~CWorkThreadPool: work processing queue not
>> empty: 2 items discarded.*
>
>
> I believe it isn't supposed to validate the whole thing without me
> explicitly saying so. Even if the validation was fast.
>
> If my new session of tinkering doesn't solve it, I'll do a top and send
> the results. Many thanks!
>
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> @Jeff
>
> The docker image is local, built "from 32bit/ubuntu:16.04".
>
> It shouldn't be outdated since I created it a couple of days ago and there
> wasn't any updates for a while now.
>
> I don't believe the "docker run" behavior is the cause, because the server
> validate the files even when I quit just the server and not the container.
> When I rcon it with "quit", it restarts internally (srcds_run) and do the
> 10 minute validation.
>
> I'm attempting to build an image that gets SteamCMD from the package
> repository instead of downloading it manually with wget. Let's see if that
> does the trick. If it doesn't I'll post some more details.
>
>
> Many thanks for the answers, guys.
>
>
> _pilger
>
> On 15 October 2017 at 17:32, Jeff Nelson <[email protected]> wrote:
>
>> Since you are using docker...
>> Where is this docker image located? Are you pulling this from someone's
>> docker hub? Or was this built from a dockerfile you created?
>>
>> If you don't have the +validate in the script, then it sounds like the
>> docker image you are using is out of date with the current version of TF2.
>> Therefore, when you are running the script, it's updating to latest. I do
>> believe a validate is done after an update - could be wrong on that one
>> though.
>>
>> Another thing to make sure is when you are starting the docker container
>> correctly.
>>
>> Running "docker run ...... <tf2-image>" will create a new container.
>> If you stop this container and perform another "docker run" will will
>> create a NEW container. So any work needed to get running again, including
>> updating, will be done.
>> "docker start container-name" will start up previously run containers that
>> were stopped and not need to be updated. Since you are using docker, maybe
>> look into the --name option. It will make these tasks easier if running
>> many containers as not providing one will randomize these names at
>> startup.
>>
>> If you still have issues, please send the dockerfile along with your
>> startup "docker run" command.
>> Likewise, if you are publishing your image to docker hub, include that as
>> well. Maybe I can pull from your uploaded image and test for myself if
>> problem persists.
>>
>>
>>
>> On Sun, Oct 15, 2017 at 1:52 PM, pilger <[email protected]> wrote:
>>
>> > Apparently I can't send images here because of a size limit.
>> >
>> > I'll resend the previous email without the image. I'm sorry if you got
>> the
>> > first one and this is a duplication.
>> >
>> > ------------------------------------------------------------
>> > ------------------------------------------------------------
>> > --------------------------------------------------
>> > ------------------------------------------------------------
>> > ------------------------------------------------------------
>> > --------------------------------------------------
>> > @Svensk
>> >
>> >
>> > Thanks for your answer Svensk!
>> >
>> > *First - don't run as root, create a user and run as that, I think some
>> > > problems get solved by that.*
>> >
>> >
>> > If I'd run the whole thing as root, it would actually solve the error
>> I'm
>> > getting. But I only ran as root as a test. My intention is, precisely,
>> not
>> > run as root.
>> >
>> >
>> > *Second - your launch line would be good to see. We are using this line
>> on
>> > > all our servers.*
>> >
>> >
>> > tf2/srcds_run -game tf -autoupdate -steam_dir ~/hlserver/steamcmd
>> > -steamcmd_script ~/hlserver/tf2_ds.txt -port 28015 -nohltv +sv_pure 1
>> +exec
>> > autoexec -replay +maxplayers 24 +map pl_badwater
>> >
>> > But it doesn't appear to be related, since the validation also happens
>> when
>> > I run "steamcmd.sh +runscript ../tf2_ds.txt" directly.
>> >
>> >
>> > *What distro are you using?*
>> >
>> >
>> >  Ubuntu:16.04 32bit
>> >
>> >
>> > *Im not familiar with "docker", what kind of drive does it have and
>> > > read/write speed?*
>> >
>> >
>> > It's a virtualization system that compartimentalize apps into containers
>> > without the need of for each virtual machine to run its own OS. I
>> wouldn't
>> > know about what kind of drivers it uses.
>> > This image might explain it better:
>> > http://blog.zenifer.com/wp-content/uploads/2015/04/
>> > docker-containers-vms.png
>> >
>> > Visit http://blog.zenifer.com/docker-explained-in-laymans-terms/ for
>> more
>> > info if you're interested. That person on the blog explains it better
>> than
>> > me, for sure.
>> >
>> >
>> > *But after a reboot its taking some time before its up and running, but
>> our
>> > > servers don't take more then a minute before they are ready.*
>> >
>> >
>> > After the whole validation (roughly 10 minutes), the server appears to
>> run
>> > properly. A 10 minute downtime every time the server restarts is kind
>> of a
>> > pain. Specially when I'm setting up the damn thing and have to restart a
>> > lot. But I strongly suspect it won't be able to autoupdate when
>> required.
>> > And that is a major issue.
>> >
>> >
>> > *How long time does the first errors take before the validation is
>> > > starting?*
>> >
>> >
>> > It starts validating almost right after the errors are thrown. Maybe 1~2
>> > seconds.
>> >
>> > ------------------------------------------------------------
>> > ------------------------------------------------------------
>> > --------------------------------------------------
>> > ------------------------------------------------------------
>> > ------------------------------------------------------------
>> > --------------------------------------------------
>> > @Sean
>> >
>> > Thanks for the answer Sean.
>> >
>> > There is no +validation on the script.
>> >
>> >
>> > > *login anonymous*
>> > > *force_install_dir ../tf2*
>> > > *app_update 232250**quit*
>> >
>> >
>> >
>> >
>> > Again, thanks for the help!
>> >
>> >
>> > _pilger
>> > _______________________________________________
>> > To unsubscribe, edit your list preferences, or view the list archives,
>> > please visit:
>> > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
>> >
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
>>
>
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux

Reply via email to