You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to #1191, the reason why unstable is failing to build, is because starting the app crashes passenger at some point and leaves a "core" file.
Since our binaries don't have debugging symbols, GDB is unable to give us much more information, it says:
icarito@tycho:/srv/mapknitter_unstable/mapknitter$ sudo gdb --core=core
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
[New LWP 8970]
Core was generated by `Passenger AppPreloader: /app (forking...)
'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fef54010fff in ?? ()
Although the app seems to be able to run fine afterwards, the created dump file is unreadable by the Docker daemon so therefore next time we build the unstable staging instance, it fails to build.
I will disable creation of dump files in docker-compose configuration, but we should keep an eye into exactly what is crashing and how we can fix it.
I found an issue suggesting this is likely a problem with our version of Ruby so we may want to try to either upgrade or downgrade it and see if it goes away - mastodon/mastodon#6734
The text was updated successfully, but these errors were encountered:
This is related to #1191, the reason why unstable is failing to build, is because starting the app crashes passenger at some point and leaves a "core" file.
Since our binaries don't have debugging symbols, GDB is unable to give us much more information, it says:
Although the app seems to be able to run fine afterwards, the created dump file is unreadable by the Docker daemon so therefore next time we build the unstable staging instance, it fails to build.
I will disable creation of dump files in docker-compose configuration, but we should keep an eye into exactly what is crashing and how we can fix it.
I found an issue suggesting this is likely a problem with our version of Ruby so we may want to try to either upgrade or downgrade it and see if it goes away - mastodon/mastodon#6734
The text was updated successfully, but these errors were encountered: