A fatal error was encountered booting this container

While starting the server it comes up with this error [Pterodactyl Daemon] A fatal error was encountered while starting this server. [Pterodactyl Daemon] A fatal error was encountered booting this container. Any reason why?

markd

markd

plox.host

Supreme

Reputation
56
Posts
647
Reactions
394
Resources
3

  • Hymart April fools


  • #2

Can you grab logs??

cd /srv/daemon/ && npm run diagnostics

when you run that add me on discord markd#2702

Poggers

Poggers

Suspended

Reputation
14
Posts
1,455
Reactions
115
Resources
4


  • #4

While starting the server it comes up with this error

[Pterodactyl Daemon] A fatal error was encountered while starting this server.
[Pterodactyl Daemon] A fatal error was encountered booting this container.

Any reason why?

https://discord.gg/UcQYjF9 Our fairly priced team could help! We are a small based classic team!

Dragson

Dragson

Supreme

Reputation
5
Posts
110
Reactions
23
Resources
0


  • #5

https://discord.gg/UcQYjF9 Our fairly priced team could help! We are a small based classic team!

The link is expired can you can give me another one?

Poggers

Poggers

Suspended

Reputation
14
Posts
1,455
Reactions
115
Resources
4


  • #6

The link is expired can you can give me another one?

Sure[DOUBLEPOST=1561473154][/DOUBLEPOST]

While starting the server it comes up with this error

[Pterodactyl Daemon] A fatal error was encountered while starting this server.
[Pterodactyl Daemon] A fatal error was encountered booting this container.

Any reason why?

https://discord.gg/4YSBXWz

Last edited: Jun 25, 2019

Eric

Eric

Software Engineer

Supreme

Reputation
14
Posts
1,762
Reactions
1,648
Resources
2

  • Hymart April fools


  • #7

https://discord.gg/UcQYjF9 Our fairly priced team could help! We are a small based classic team!

Can you stop spamming your services discord link everywhere?

Dragson

Dragson

Supreme

Reputation
5
Posts
110
Reactions
23
Resources
0


Poggers

Poggers

Suspended

Reputation
14
Posts
1,455
Reactions
115
Resources
4


  • #9

Can you stop spamming your services discord link everywhere?

Only people who need help not everyone

Reyn

Supreme

Reputation
2
Posts
76
Reactions
28
Resources
0


  • #11

Hello, please send me a DM over Discord: Reyn#9999
I should be able to get this sorted for you in a few hours for cheap.

Источник

So none of the above answers worked for me, but I finally found the problem, it was something in the .csproj file of the API, and it was causing the docker container hosting the API not to start with the message in the thread title.

This was the line that had been added in PropertyGroup node, presumably when someone had published the file for windows, and then checked in the updated .csproj

<RuntimeIdentifier>win-x64</RuntimeIdentifier>

As it turns out this is a publish option. Removing this sets the project to a default value of portable (in the UI) which is «any» in the file if it were explicitly specified. Removing the line above fixed the problem for me.

Edit

As a side note, I was able to leave the RuntimeIdentifier in the API .csproj file alone (kept win-x64 value) by changing my Dockerfile dotnet publish args to:

RUN dotnet publish ./src/API.csproj --self-contained --runtime linux-musl-x64 --configuration Release --output /app/publish

The important parts being the addition of --self-contained and --runtime linux-musl-x64 for alpine-linux … this image: mcr.microsoft.com/dotnet/aspnet:3.1-alpine

The build image for this is mcr.microsoft.com/dotnet/sdk:3.1

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account


Open

ufoscout opened this issue

Jul 20, 2017

· 40 comments


Open

Fatal error on startup

#126

ufoscout opened this issue

Jul 20, 2017

· 40 comments

Comments

@ufoscout

We are not able to start RC1 on our docker hosts.
In one host it crashes at start up:

Unable to find image 'microsoft/mssql-server-linux:rc1' locally                                                                                                                                           
rc1: Pulling from microsoft/mssql-server-linux                                                                                                                                                            
aed15891ba52: Pull complete 
773ae8583d14: Pull complete 
d1d48771f782: Pull complete 
cd3d6cd6c0cf: Pull complete 
8ff6f8a9120c: Pull complete 
1fd7e8b10447: Pull complete 
bd485157db89: Pull complete 
273a1970ce9c: Pull complete 
fe20b2602177: Pull complete 
086b69c4d68d: Pull complete 
Digest: sha256:459a50fa650583d3e4b0502b486ae200cd46d256e771d175a8bcdc99bdb159a3
Status: Downloaded newer image for microsoft/mssql-server-linux:rc1
This is an evaluation version.  There are [173] days left in the evaluation period.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000003
      Message: result == 0
   Stacktrace: 0000562ab924f1f8 0000562ab924edb0 0000562ab922c20c 
               0000562ab922c96e 0000562ab92488b4 0000562ab922412b 
               00007fd1ff21d830 0000562ab9221cf9 
      Process: 9 - sqlservr
       Thread: 9
  Instance Id: 694bf992-bc8a-439e-bb42-0270b5c35587
     Crash Id: d2323697-cdf7-4bb0-a859-33e306b52708
  Build stamp: e83d0295c4b8a8055fc3842cb84be4f864e57a4bf7c38359c4427ace56a27dbf

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper
WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log for details
Attempting to capture a dump with gdb
WARNING: Unable to capture crash dump with GDB. You may need to
allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or
run as root.

On another host it hangs and it is not possible to connect to it and to stop the container.

@twright-msft

What is your docker run command? Are you mounting using -v?
What host OS are you running on? If RHEL flavor, is SELinux enabled?

@ufoscout

hi @twright-msft,

We are not mounting using -v.
The docker run command is:
docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Pass12345!' -p 34203:1433 microsoft/mssql-server-linux:rc1

Our OS is Ubuntu Server 16.04.2 LTS with docker 17.03.2-ee-4

@twright-msft

Can you please docker run with —cap_add=CAP_SYS_PTRACE and -v mount the /var/opt/mssql dir to your host? That should generate a dump at /log.

@andrewnicols

I’m experiencing the same issue with 126 on a newly installed Ubuntu 16.04 box running and Docker 17.06.0-ce.

Here are the generated logs: 126.zip

This is the command I’ve just used:

docker run -e ACCEPT_EULA=Y -e SA_PASSWORD=Passw0rd! -v /tmp/126:/var/opt/mssql --cap-add=SYS_PTRACE microsoft/mssql-server-linux:rc1

For anyone else trying to generate logs, please note it’s --cap-add=SYS_PTRACE (not --cap_add=CAP_SYS_PTRACE).

Containers: 10
 Running: 5
 Paused: 0
 Stopped: 5
Images: 10
Server Version: 17.06.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 214
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-21-generic
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.34GiB
Name: banana
ID: LHSX:VYJH:M3PA:JLVT:V2VQ:LPHC:ZD6Y:YVXA:B2WE:UZ7L:FKSA:FBGW
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: No swap limit support

@twright-msft

@kwerle

@twright-msft I’m suddenly seeing this on Ubuntu 14.04. I am NOT seeing this on my OSX box.
I tried
docker run -v $PWD/log:/var/opt/mssql --cap-add SYS_PTRACE -it private-repo.microsoft.com/mssql-private-preview/mssql-server:latest
but the log directory was empty. I can archive up it’s peers (data & secret) if those are of interest. But as you can see, I was just trying to start the container without any data at all.

p.s. Quite possible the image on my OSX box is cached back to a good version.

@twright-msft

Do you see exactly the same output on Ubuntu 14.04?
Note: Ubuntu 14.04 is not a supported version of Ubuntu. Its possible that there is an issue with that version of the kernel.

@andrewnicols

@twright-msft I assume your message is intended for @kwerle, but I have a 14.04.5 LTS (3.13.0-91-generic) box which can run the rc1 image, but it can only sometimes run the latest:

jenkins@nightly:/tmp/126$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty
Linux nightly 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
jenkins@nightly:/tmp/tmp.kUl9UiCVqi$ docker run -e ACCEPT_EULA=Y -e SA_PASSWORD=Passw0rd! -v /tmp/126:/var/opt/mssql --cap-add=SYS_PTRACE microsoft/mssql-server-linux:latest
This is an evaluation version.  There are [101] days left in the evaluation period.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000002
       Status: 0xc00002e3
   Parameters: 0x280c9fbc0
               [0] 0x280c9fbb0
               [1] 0xffffffffc0000058
   Stacktrace: 000000006a4ed558 000000006a43f1cd 000000006a50edd5
               000000006a50ee04 0000000281241533
      Process: 9 - sqlservr
       Thread: 99 (application thread 0x1158)
  Instance Id: 4a3afbae-d356-4ba1-8864-7f90ef464f65
     Crash Id: 304de20f-e130-4b02-b7e4-b788b25c1563
  Build stamp: 0a7fe2a13669acfb48c31a17e752ad495ef645f7e730a69404f903f749c677d0

Capturing core dump and information...
/opt/mssql/bin/crash-support-functions.sh: line 337: hash: lsof: not found
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
Core dump and information are being compressed in the background. When complete,
they can be found in the following location:
  /var/opt/mssql/log/core.sqlservr.08_01_2017_01_46_41.9.tbz2

Strangely, that only happened the first time that I ran the image. Subsequent runs appear to run without issue.

I have a dump from that run too, but it’s 38MB and too big to upload here. Are there any particular files that you require from it?

@kwerle

Do you see exactly the same output on Ubuntu 14.04?

No — it simply exits.

Note: Ubuntu 14.04 is not a supported version of Ubuntu. Its possible that there is an issue with that version of the kernel.

Fair enough — but I’ve been using it flawlessly for a number of months as part of my CI process. When my build process mysteriously stopped working, this was the first thing I found — and the timing seems about right…

Finally got some output:
db_1 | This is an evaluation version. There are [175] days left in the evaluation period.
db_1 | This program has encountered a fatal error and cannot continue running.
db_1 | The following diagnostic information is available:
db_1 |
db_1 | Reason: 0x00000006
db_1 | Status: 0x40000015
db_1 | Message: Kernel bug check
db_1 | Address: 0x6a42b4b0
db_1 | Parameters: 0x6a62a250
Stacktrace: 000000006a4e8446 000000006a42b50b 000000006a41ecad
db_1 | 000000006a42aeab 000000006a4e69dd 000000006a4e5a1c
db_1 | 000000006a4e5890 000000006a4e57c5
Process: 9 — sqlservr
db_1 | Thread: 13 (application thread 0x1000)
db_1 | Instance Id: 5f7cce7a-c274-42cc-a85f-8033d5d3e210
db_1 | Crash Id: 5e84f144-7856-49fb-8b0b-d7dc8232feea
db_1 | Build stamp: 55510f72dd93234a74042039c0e0adc75f542b8b6493470445965c74d94e9385
db_1 |
db_1 | Capturing core dump and information…
db_1 | No journal files were found.
db_1 | No journal files were found.
db_1 | Attempting to capture a dump with paldumper

@kwerle

Falling back to microsoft/mssql-server-linux:ctp2-1 for now.

andrewnicols

added a commit
to andrewnicols/moodle-db-mssql
that referenced
this issue

Aug 11, 2017

@andrewnicols

@fcina

Same issue with RC2:

$ docker run --name sql-test-01 -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Admin12345!' -p 12433:1433 microsoft/mssql-server-linux:rc2
This is an evaluation version.  There are [152] days left in the evaluation period.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000003
      Message: result == 0
   Stacktrace: 000055e25bbb0e28 000055e25bbb09d0 000055e25bb8b309 
               000055e25bb8bafe 000055e25bbaa4d4 000055e25bb830eb 
               00007fad77f11830 000055e25bb80cb9 
      Process: 9 - sqlservr
       Thread: 9
  Instance Id: 71eaf808-c81a-46c8-9421-9df6836aabe7
     Crash Id: 2b4f5e54-34af-478c-9bef-d2ae55ed6ded
  Build stamp: a37664e45e4156e76a53fa282fd694cb49f70c2037515f5684e3ce6dfa7549bc

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper
WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log for details
Attempting to capture a dump with gdb
WARNING: Unable to capture crash dump with GDB. You may need to
allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or
run as root.

I cannot enable ptrace or run as a root because I have restricted access to that environment.

@ufoscout

FYI
I created a CentOS based SqlServer RC2 docker image based on the provided Dockerfile. I launched the image in the same machine where the defauld one (ubuntu based) fails and I got exactly the same issue:

> docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=oiw4ool9Qu' -e 'MSSQL_PID=Developer' docker-test/sql-server-linux:centos-rc2

This is an evaluation version.  There are [145] days left in the evaluation period.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000003
      Message: result == 0
   Stacktrace: 0000555907473f18 0000555907473ac0 000055590744e409 
               000055590744ebfe 000055590746d5c4 00005559074461eb 
               00007fdd45cdab35 0000555907443dc5 
      Process: 8 - sqlservr
       Thread: 8
  Instance Id: 6fe1fc04-5e76-45a7-b565-ca3b228f2b17
     Crash Id: 758a5941-ce7e-4af5-a830-fb8f3384f6bf
  Build stamp: ff4c991962e5ff435939d15a8b81bdfaa2f354495851a34781907e95e2b94e88

Capturing core dump and information...
/opt/mssql/bin/crash-support-functions.sh: line 357: hash: lsof: not found
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper
WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.8.temp/log/paldumper-debug.log for details
Attempting to capture a dump with gdb

@HeikoH

Same issue here with RC2 (on Ubuntu 16.04 host), container runs fine until I start importing some data. I consistently fails halfway the import job with

2017-09-13 17:47:03.72 spid52      AppDomain 2 (master.sys[runtime].1) created.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000003
      Message: bufferPlaintextSize > 0
   Stacktrace: 0000005a6b01e228 0000005a6b010fa8 0000005a6b01072b
               0000005a6afe01a9 0000005a6afdfe59
      Process: 9 - sqlservr
       Thread: 168 (application thread 0x126c)
  Instance Id: dbccfea3-adaa-4c9e-8eb9-bee1337e05a8
     Crash Id: 9bb05926-db81-4fec-98af-909749d4d4e4
  Build stamp: a37664e45e4156e76a53fa282fd694cb49f70c2037515f5684e3ce6dfa7549bc

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper

CTP2-1 works fines (and the data import seems to go much much faster)

@zCarot

Same issue
Full logs are here

$ docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Pass12345!' --cap-add=SYS_PTRACE microsoft/mssql-server-linux:rc2

This is an evaluation version.  There are [130] days left in the evaluation period.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000003
      Message: result == 0
   Stacktrace: 0000006a0a9e5e28 0000006a0a9e59d0 0000006a0a9c0309
               0000006a0a9c0afe 0000006a0a9df4d4 0000006a0a9b80eb
               00007f395488e830 0000006a0a9b5cb9
      Process: 9 - sqlservr
       Thread: 9
  Instance Id: c8e8186e-0760-4a52-87be-85da66ae442e
     Crash Id: 51aae6d6-12c4-4474-bcf6-9e469c4f9926
  Build stamp: a37664e45e4156e76a53fa282fd694cb49f70c2037515f5684e3ce6dfa7549bc

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper

@ufoscout

Issue still present in 2017-GA:

$ docker run --name sql2017test -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=yourStrong(!)Password' -p 41453:1433 microsoft/mssql-server-linux:2017-GA
Unable to find image 'microsoft/mssql-server-linux:2017-GA' locally
2017-GA: Pulling from microsoft/mssql-server-linux
aed15891ba52: Pull complete 
773ae8583d14: Pull complete 
d1d48771f782: Pull complete 
cd3d6cd6c0cf: Pull complete 
8ff6f8a9120c: Pull complete 
1fd7e8b10447: Pull complete 
bd485157db89: Pull complete 
273a1970ce9c: Pull complete 
006581b3a024: Pull complete 
25c54ac351f0: Pull complete 
Digest: sha256:77ebcec549076994f93ab85c5ce194e85366d9bcd124c53e1347660edd315666
Status: Downloaded newer image for microsoft/mssql-server-linux:2017-GA
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

       Reason: 0x00000003
      Message: result == 0
   Stacktrace: 0000559d10829488 0000559d10829030 0000559d1086074c 
               0000559d10860eaf 0000559d10822b34 0000559d1080b1cb 
               00007fa65625c830 0000559d10808d99 
      Process: 9 - sqlservr
       Thread: 9
  Instance Id: 13cca678-2a1b-4b77-8bb3-4d784132bcca
     Crash Id: 74badf46-df3b-4421-9568-c6dbd22e9c92
  Build stamp: 07e6b1037a01f9cc32c071e751452f019056fdc3a8163dd8b5897e1ca436c02a

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper
WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log for details
Attempting to capture a dump with gdb
WARNING: Unable to capture crash dump with GDB. You may need to
allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or
run as root.

Is there any real investigation going on about this issue? Any update?

@ufoscout
ufoscout

changed the title
RC1 crashes or hangs at startup

Fatal error on startup

Oct 3, 2017

@tynor88

Same issue here:

This program has encountered a fatal error and cannot continue running.

The following diagnostic information is available:

Reason: 0x00000003
Message: result
Stacktrace: 0000561171279762 00005611712481c7
Thread: 13 (application thread 0x1000)
Instance Id: 647a44ee-dbb9-4c7c-b592-2f1ca4865fcf
Crash Id: 23bb9925-30b7-46b6-b959-6be8e524d5c7
Build stamp: 07e6b1037a01f9cc32c071e751452f019056fdc3a8163dd8b5897e1ca436c02a

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
/opt/mssql/bin/crash-support-functions.sh: line 185: 138 Aborted $program_dir/paldumper $dokill -p $pid -d $paldumper_dump_type_str -o $dump_filename.gdmp > $paldumper_debuglog_filename 2>&1
WARNING: Capture attempt failure detected

Attempting to capture a filtered dump with paldumper

Running with:

docker run -d —name=»mssql-server-linux» —net=»bridge» -e TZ=»Europe/Paris» -e HOST_OS=»unRAID» -e «SA_PASSWORD»=»yourStrong(!)Password» -e «ACCEPT_EULA»=»Y» -p 1433:1433/tcp -v «/mnt/user/appdata/mssql-server»:»/var/opt/mssql»:rw —cap-add sys_ptrace microsoft/mssql-server-linux:2017-latest

This was referenced

Oct 17, 2017

@slabber

Hi Everyone, I also had a crash that was resolved by explicitly setting -e «MSSQL_TCP_PORT»=»1433»

@zCarot

Thanks, @slabber, seems that it’s running now

@zCarot

@slabber now it start working on one host even without your additional env, but at the second host it still failing with the same issue, even with this env

@ufoscout

@slabber unlucky guy here, it doesn’t solve the issue for me.

@andrewnicols

I’m pretty sure it’s related to storage and not to do with port.

@sunnymoon

In our case, we still found the problem, until we finally understood it was related to our underlying filesystem on the host being ext3 instead of ext4. That’s how we solved it… Change to ext4 and mssql starts executing again.

@twright-msft

@fcina

@sunnymoon

@fcina can you send docker info output?

@twright-msft

@fcina — I noticed above that you said

I cannot enable ptrace or run as a root because I have restricted access to that environment.

Does that mean that the SQL Server container is not running as root? If so, that is likely the problem. For now, the SQL Server container must run as root.

@sunnymoon

@twright-msft We don’t actually run as root and it works perfectly… ;)

@twright-msft

@sunnymoon — Interesting. Do you run it on a container platform like k8s, OpenShift, etc. or on Docker Engine directly?

@sunnymoon

Docker engine (with docker-compose)…

Best
JP

…

@ufoscout

@twright-msft
here the docker info of 2 different hosts.
In host1 ( docker info 1 ) sqlserver always fails to start.
In host2 ( docker info 2 ) only one sqlserver container can be started a time. This means that if I try to execute for example three containers, only the first one succeed and all others fail, e.g.:

# Start the first one, it works
> docker run --name sql_server_test_1 -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Abc123!?'  -e 'MSSQL_PID=Developer' -d microsoft/mssql-server-linux:2017-CU1

# Start the second one, it fails
> docker run --name sql_server_test_2 -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Abc123!?'  -e 'MSSQL_PID=Developer' -d microsoft/mssql-server-linux:2017-CU1

# Start the third one, it fails... and so on...
> docker run --name sql_server_test_3 -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Abc123!?'  -e 'MSSQL_PID=Developer' -d microsoft/mssql-server-linux:2017-CU1

If I stop the first one, I can successfully start a new one but then the first one cannot restart as it fails.
It seems that those containers are not isolated at all.

@sunnymoon

@fcina Do not use aufs as a storage driver… change it to overlay2…

Regards

…

On Wed, Nov 22, 2017 at 11:17 AM, Francesco ***@***.***> wrote:
@twright-msft <https://github.com/twright-msft>
here the docker info of 2 different hosts.
In host1 ( docker info 1
<https://github.com/Microsoft/mssql-docker/files/1495691/host1.txt> )
sqlserver always fails to start.
In host2 ( docker info 2
<https://github.com/Microsoft/mssql-docker/files/1495698/host2.txt> )
only one sqlserver container can be started a time. This means that if I
try to execute for example three containers, only the first one succeed and
all others fail, e.g.:

# Start the first one, it works
> docker run —name sql_server_test_1 -e ‘ACCEPT_EULA=Y’ -e ‘SA_PASSWORD=Abc123!?’ -e ‘MSSQL_PID=Developer’ -d microsoft/mssql-server-linux:2017-CU1

# Start the second one, it fails
> docker run —name sql_server_test_2 -e ‘ACCEPT_EULA=Y’ -e ‘SA_PASSWORD=Abc123!?’ -e ‘MSSQL_PID=Developer’ -d microsoft/mssql-server-linux:2017-CU1

# Start the third one, it fails… and so on…
> docker run —name sql_server_test_3 -e ‘ACCEPT_EULA=Y’ -e ‘SA_PASSWORD=Abc123!?’ -e ‘MSSQL_PID=Developer’ -d microsoft/mssql-server-linux:2017-CU1

If I stop the first one, I can successfully start a new one but then the
first one cannot restart as it fails.
It seems that those containers are not isolated at all.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#126 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEJ6KCgtHlBEFurSYt0iUOHEA9qDwYz4ks5s5ALhgaJpZM4OeHT->
.

—

@fcina

@sunnymoon Tested on 3 different hosts with overlay2 storage driver, it works in two of them but it still shows the same issue on the third one. In addition, I have another host with aufs in which it works fine.

@sunnymoon

@axelfontaine

FWIW upgrading the kernel from 4.13 to 4.14 did it for me.

@dleute

I am also experiencing this issue. Upgrading the kernel did not do it for me. Overlay2 is already in use. And the docker mount is ext4. Kernel 4.13 and 4.4 were also tried to the same result. I even tried Centos based container with the same issue.

Any other revelations on this?

@gabp

Any update on this issue? I have the same problem where I am not able to run more than 6 mssql containers at the same time. After that, I get the 0x00000003 error.

@gabp

@DooDleWilk

I ran into the same problem, but the solution was different from @gabp
I found this link
Once I set the soft stack limit from unlimited to 8192, it starts correctly.

@hernandanielg

@gabp solutions saved the day! 👍 😛

Thanks!

@lexfrei

Faced the same issue today.
I’m running rocky 9.
Switched to RHEL-image and all looks fine now.
For now, my manifest looks like this

Источник
};

            // If the server "crashed" with a normal exit code indicating that it was stopped successfully
            // don't force it to reboot. This can happen if a plugin stops the server for someone.
            if (!Config.get('internals.clean_exit_is_crash', true) && parseInt(props.ExitCode, 10) === 0 && !props.OOMKilled) {
                return;
            }

            // If crash detection is disabled for the server don't do anything.
            if (!_.get(this.json, 'container.crashDetection', true)) {
                this.log.warn(props, 'Server detected as entering a crashed state; crash handler is disabled; aborting reboot.');
                return;
            }

            this.emit('console', `${Ansi.style['bg-red']}${Ansi.style.white}[Pterodactyl Daemon] ---------- Detected server process in a crashed state! ----------`);
            this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Exit Code: ${Ansi.style.reset}${props.ExitCode}`);
            this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Out of Memory: ${Ansi.style.reset}${props.OOMKilled}`);
            this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Error Response: ${Ansi.style.reset}${props.Error}`);
            this.emit('crashed');

            if (moment.isMoment(this.lastCrash) && moment(this.lastCrash).add(60, 'seconds').isAfter(moment())) {
                this.setCrashTime();
                this.log.warn(props, 'Server detected as crashed but has crashed within the last 60 seconds; aborting reboot.');
                this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Aborting automatic reboot due to crash within the last 60 seconds.`);

                return;
            }

            this.log.warn(props, 'Server detected as crashed! Attempting server reboot.');
            this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Server process detected as entering a crashed state; rebooting.`);
            this.setCrashTime();
Источник

Best JavaScript code snippets using ansi-escape-sequences.red(Showing top 7 results out of 315)

diskUse(self) { 
    self.fs.size((err, size) => {
      if (err) return self.log.warn(err);

      self.currentDiskUsed = Math.round(size / (1000 * 1000)); 
      if (self.json.build.disk > 0 && size > (self.json.build.disk * 1000 * 1000) && self.status !== Status.OFF) {
        self.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Server is violating disk space limits. Stopping process.`);

        if (Config.get('actions.disk.kill', true)) {
          self.kill(killErr => {
            if (killErr) self.log.error(killErr);
          });
        } else {
          self.stop(stopErr => {
            if (stopErr) self.log.error(stopErr);
          });
        }
      }
    });
  }

Async.waterfall([
          callback => {
            this.buildInProgress = true;
            callback();
          },
          callback => {
            this.emit('console', `${Ansi.style.cyan}[Pterodactyl Daemon] Your server container needs to be rebuilt. This should only take a few seconds, but could take a few minutes. You do not need to do anything else while this occurs. Your server will automatically continue with startup once this process is completed.`);
            this.setStatus(Status.STOPPING);
            this.setStatus(Status.OFF);
            this.rebuild(callback);
          },
          callback => {
            this.log.info('Completed rebuild process for server container.');
            this.emit('console', `${Ansi.style.green}[Pterodactyl Daemon] Completed rebuild process for server. Server is now booting.`);
            this.start(callback);
          },
        ], err => {
          if (err) {
            this.setStatus(Status.OFF);
            this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] A fatal error was encountered booting this container.`);
            this.buildInProgress = false;
            this.log.error(err);
          }
        });

this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] No stop configuration is defined for this egg.`);
return next();

this.server.output(`${Ansi.style.red}[Pterodactyl Daemon] Your server is sending too much data, process is being killed.`);
this.server.log.warn('Server has triggered automatic kill due to excessive data output. Potential DoS attack.');
this.server.kill(() => {}); 

this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] A fatal error was encountered while starting this server.`);
this.log.error(err);
return next(err);

this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Exit Code: ${Ansi.style.reset}${props.ExitCode}`);
this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Out of Memory: ${Ansi.style.reset}${props.OOMKilled}`);
this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Error Response: ${Ansi.style.reset}${props.Error}`);
this.emit('crashed');
  this.setCrashTime();
  this.log.warn(props, 'Server detected as crashed but has crashed within the last 60 seconds; aborting reboot.');
  this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Aborting automatic reboot due to crash within the last 60 seconds.`);
this.emit('console', `${Ansi.style.red}[Pterodactyl Daemon] Server process detected as entering a crashed state; rebooting.`);
this.setCrashTime();

}).catch(readError => {
  activeSocket.emit('console', {
    line: `${Ansi.style.red}[Pterodactyl Daemon] An error was encountered while attempting to read the log file!`,
  });

Источник

Guest User

Untitled

a guest

Jul 25th, 2019

183

0

Never

Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!

  1. [Pterodactyl Daemon] Server marked as STARTING

  2. [Pterodactyl Daemon] Your server container needs to be rebuilt. This should only take a few seconds, but could take a few minutes. You do not need to do anything else while this occurs. Your server will automatically continue with startup once this process is completed.

  3. [Pterodactyl Daemon] Server marked as STOPPING

  4. [Pterodactyl Daemon] Server marked as OFF

  5. [Pterodactyl Daemon] Rebuilding server container…

  6. [Pterodactyl Daemon] New container built, rotating hamsters…

  7. [Pterodactyl Daemon] Container is being initialized…

  8. [Pterodactyl Daemon] Completed rebuild process for server. Server is now booting.

  9. [Pterodactyl Daemon] Server marked as STARTING

  10. [Pterodactyl Daemon] Checking size of server data directory…

  11. [Pterodactyl Daemon] Not enough disk space! 33396M / 10240M

  12. [Pterodactyl Daemon] Server marked as OFF

  13. [Pterodactyl Daemon] A fatal error was encountered while starting this server.

  14. [Pterodactyl Daemon] A fatal error was encountered booting this container.

Источник

Понравилась статья? Поделить с друзьями:
  • A fatal error occurred when attempting to access the ssl server credential private key
  • A fatal error occurred timed out waiting for packet content esp32
  • A fatal error occurred this chip is esp8266 not esp32 wrong chip argument
  • A disk read error occurred ноутбук asus
  • A disk read error occurred как исправить через биос