your-land/bugtracker
your-land
/
bugtracker
44
20
Code Issues 2.4k Projects 2 Wiki

Autocrafter Segfault #2816

New Issue
Closed
opened 2022-10-05 14:37:42 +00:00 by AliasAlreadyTaken · 28 comments
AliasAlreadyTaken commented 2022-10-05 14:37:42 +00:00
Owner
Copy Link

found by rabenkind.

When I take the result out of an autocrafter which is placed in an area, the server segfaults. Without the area, it works.

[38007.336689] Server[110138]: segfault at 7f6c662760ce ip 000055e2bf43277b sp 00007f6ba380ad30 error 4 in minetestserver[55e2bf0d8000+456000]
[38007.336703] Code: 85 a0 f7 ff ff 00 00 00 00 c7 85 94 f7 ff ff 00 00 00 00 44 0f bf 43 58 4d 8b 2e 4c 89 c0 48 c1 e0 05 4c 29 c0 4d 8d 6c c5 00 <41> 0f b7 55 20 66 44 39 ca 0f 83 11 19 00 00 66 89 93 b2 00 00 00

Repro:

  1. Place autocrafter in area
  2. Add 4 default stone in a 2x2 to make stonebrick
  3. Add default:stone to the autocrafter inv
  4. Switch the autocrafter on
  5. Let it produce some
  6. Eventually drag the result from the center slot (above the on-switch)
    => Server crash
found by rabenkind. When I take the result out of an autocrafter which is placed in an area, the server segfaults. Without the area, it works. [38007.336689] Server[110138]: segfault at 7f6c662760ce ip 000055e2bf43277b sp 00007f6ba380ad30 error 4 in minetestserver[55e2bf0d8000+456000] [38007.336703] Code: 85 a0 f7 ff ff 00 00 00 00 c7 85 94 f7 ff ff 00 00 00 00 44 0f bf 43 58 4d 8b 2e 4c 89 c0 48 c1 e0 05 4c 29 c0 4d 8d 6c c5 00 <41> 0f b7 55 20 66 44 39 ca 0f 83 11 19 00 00 66 89 93 b2 00 00 00 Repro: 1. Place autocrafter in area 2. Add 4 default stone in a 2x2 to make stonebrick 3. Add default:stone to the autocrafter inv 4. Switch the autocrafter on 5. Let it produce some 6. Eventually drag the result from the center slot (above the on-switch) => Server crash
AliasAlreadyTaken added the
1. kind/bug
2. prio/critical
 labels 2022-10-05 14:38:00 +00:00
AliasAlreadyTaken commented 2022-10-05 14:46:08 +00:00
Author
Owner
Copy Link

Tested pipeworks versions:

latest release from content db, release = 7488
yl 07e7e0e6e5 aka 20e81e67a0

areas latest release from content db, release = 5030

Tested pipeworks versions: latest release from content db, release = 7488 yl 07e7e0e6e5 aka 20e81e67a0 areas latest release from content db, release = 5030
flux commented 2022-10-05 14:53:18 +00:00
Member
Copy Link

my tests:

minetest areas pipeworks behavior
5.6.1 d46d72d 07e7e0e clears recipe
5.5.1 d46d72d 07e7e0e segfaults before the server finishes loading (unified_inventory getting all craft recipes)
my tests: | minetest | areas | pipeworks | behavior | | -------- | -------- | -------- | ------ | | 5.6.1 | d46d72d | 07e7e0e | clears recipe | | 5.5.1 | d46d72d | 07e7e0e | segfaults before the server finishes loading (unified_inventory getting all craft recipes) |
flux commented 2022-10-05 15:11:33 +00:00
Member
Copy Link

removed unified inventory, got 5.5.1 to crash:

(gdb) bt
#0  IMoveAction::apply (this=0x7fcd443f8810, mgr=0x556d19601120, player=0x7fcd443a6150, gamedef=0x7ffc035d8720)
    at /opt/minetest-vanilla/src/inventorymanager.cpp:439
#1  0x0000556d185af88f in Server::handleCommand_InventoryAction (this=0x7ffc035d8710, pkt=0x7fcd493a6270)
    at /opt/minetest-vanilla/src/network/serverpackethandler.cpp:747
#2  0x0000556d188420a7 in Server::handleCommand (this=0x7ffc035d8710, pkt=0x7fcd493a6270) at /opt/minetest-vanilla/src/server.cpp:1131
#3  0x0000556d1882ceed in Server::ProcessData (this=0x7ffc035d8710, pkt=0x7fcd493a6270) at /opt/minetest-vanilla/src/server.cpp:1208
#4  0x0000556d1882bfb9 in Server::Receive (this=0x7ffc035d8710) at /opt/minetest-vanilla/src/server.cpp:1028
#5  0x0000556d1882510e in ServerThread::run (this=0x556d1956c040) at /opt/minetest-vanilla/src/server.cpp:122
#6  0x0000556d1867305e in Thread::threadProc (thr=0x556d1956c040) at /opt/minetest-vanilla/src/threading/thread.cpp:188
#7  0x0000556d18673c86 in std::__invoke_impl<void, void (*)(Thread*), Thread*> (__f=@0x556d21eeb330: 0x556d18672fec <Thread::threadProc(Thread*)>)
    at /usr/include/c++/12.2.0/bits/invoke.h:61
#8  0x0000556d18673c09 in std::__invoke<void (*)(Thread*), Thread*> (__fn=@0x556d21eeb330: 0x556d18672fec <Thread::threadProc(Thread*)>)
    at /usr/include/c++/12.2.0/bits/invoke.h:96
#9  0x0000556d18673b79 in std::thread::_Invoker<std::tuple<void (*)(Thread*), Thread*> >::_M_invoke<0ul, 1ul> (this=0x556d21eeb328)
    at /usr/include/c++/12.2.0/bits/std_thread.h:252
#10 0x0000556d18673b32 in std::thread::_Invoker<std::tuple<void (*)(Thread*), Thread*> >::operator() (this=0x556d21eeb328)
    at /usr/include/c++/12.2.0/bits/std_thread.h:259
#11 0x0000556d18673b16 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (*)(Thread*), Thread*> > >::_M_run (this=0x556d21eeb320)
    at /usr/include/c++/12.2.0/bits/std_thread.h:210
#12 0x00007fcd6711f2f3 in std::execute_native_thread_routine (__p=0x556d21eeb320) at /usr/src/debug/gcc/libstdc++-v3/src/c++11/thread.cc:82
#13 0x00007fcd66de078d in ?? () from /usr/lib/libc.so.6
#14 0x00007fcd66e618e4 in clone () from /usr/lib/libc.so.6
removed unified inventory, got 5.5.1 to crash: ``` (gdb) bt #0 IMoveAction::apply (this=0x7fcd443f8810, mgr=0x556d19601120, player=0x7fcd443a6150, gamedef=0x7ffc035d8720) at /opt/minetest-vanilla/src/inventorymanager.cpp:439 #1 0x0000556d185af88f in Server::handleCommand_InventoryAction (this=0x7ffc035d8710, pkt=0x7fcd493a6270) at /opt/minetest-vanilla/src/network/serverpackethandler.cpp:747 #2 0x0000556d188420a7 in Server::handleCommand (this=0x7ffc035d8710, pkt=0x7fcd493a6270) at /opt/minetest-vanilla/src/server.cpp:1131 #3 0x0000556d1882ceed in Server::ProcessData (this=0x7ffc035d8710, pkt=0x7fcd493a6270) at /opt/minetest-vanilla/src/server.cpp:1208 #4 0x0000556d1882bfb9 in Server::Receive (this=0x7ffc035d8710) at /opt/minetest-vanilla/src/server.cpp:1028 #5 0x0000556d1882510e in ServerThread::run (this=0x556d1956c040) at /opt/minetest-vanilla/src/server.cpp:122 #6 0x0000556d1867305e in Thread::threadProc (thr=0x556d1956c040) at /opt/minetest-vanilla/src/threading/thread.cpp:188 #7 0x0000556d18673c86 in std::__invoke_impl<void, void (*)(Thread*), Thread*> (__f=@0x556d21eeb330: 0x556d18672fec <Thread::threadProc(Thread*)>) at /usr/include/c++/12.2.0/bits/invoke.h:61 #8 0x0000556d18673c09 in std::__invoke<void (*)(Thread*), Thread*> (__fn=@0x556d21eeb330: 0x556d18672fec <Thread::threadProc(Thread*)>) at /usr/include/c++/12.2.0/bits/invoke.h:96 #9 0x0000556d18673b79 in std::thread::_Invoker<std::tuple<void (*)(Thread*), Thread*> >::_M_invoke<0ul, 1ul> (this=0x556d21eeb328) at /usr/include/c++/12.2.0/bits/std_thread.h:252 #10 0x0000556d18673b32 in std::thread::_Invoker<std::tuple<void (*)(Thread*), Thread*> >::operator() (this=0x556d21eeb328) at /usr/include/c++/12.2.0/bits/std_thread.h:259 #11 0x0000556d18673b16 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (*)(Thread*), Thread*> > >::_M_run (this=0x556d21eeb320) at /usr/include/c++/12.2.0/bits/std_thread.h:210 #12 0x00007fcd6711f2f3 in std::execute_native_thread_routine (__p=0x556d21eeb320) at /usr/src/debug/gcc/libstdc++-v3/src/c++11/thread.cc:82 #13 0x00007fcd66de078d in ?? () from /usr/lib/libc.so.6 #14 0x00007fcd66e618e4 in clone () from /usr/lib/libc.so.6 ```
flux commented 2022-10-05 15:16:33 +00:00
Member
Copy Link

possibly related upstream:

possibly related upstream: * https://github.com/minetest/minetest/issues/8405 * https://github.com/minetest/minetest/issues/11805
flux commented 2022-10-05 15:46:53 +00:00
Member
Copy Link

can't reproduce when pipeworks and areas are the only 2 mods installed...

can't reproduce when pipeworks and areas are the only 2 mods installed...
flux commented 2022-10-05 16:04:38 +00:00
Member
Copy Link

figured out how to reproduce it w/ minimal mods, and in 5.6.1 as well (so it's not fixed)

figured out how to reproduce it w/ minimal mods, and in 5.6.1 as well (so it's not fixed)
AliasAlreadyTaken commented 2022-10-05 16:08:08 +00:00
Author
Owner
Copy Link

https://your-land.de/res/2022-10-05%2018-04-14.mkv

https://your-land.de/res/2022-10-05%2018-04-14.mkv
flux commented 2022-10-05 16:22:19 +00:00
Member
Copy Link

i've updated https://github.com/minetest/minetest/issues/11805 w/ the info i've been able to dig up. might take a peek at fixing it, but i'm not sure i'll be able to do that effectively

i've updated https://github.com/minetest/minetest/issues/11805 w/ the info i've been able to dig up. might take a peek at fixing it, but i'm not sure i'll be able to do that effectively
👍 1
flux added the
3. source/engine
 label 2022-10-05 16:22:30 +00:00
flux commented 2022-10-06 01:00:06 +00:00
Member
Copy Link

it appears that exist upstream PR https://github.com/minetest/minetest/pull/11882 fixes the issue; guessing it'll make it into 5.7, or we can patch it in if it's urgent.

it appears that exist upstream PR https://github.com/minetest/minetest/pull/11882 fixes the issue; guessing it'll make it into 5.7, or we can patch it in if it's urgent.
flux commented 2022-10-06 01:05:34 +00:00
Member
Copy Link

was not able to replicate the issue on tunnelers' abyss

was not able to replicate the issue on tunnelers' abyss
flux commented 2022-10-06 01:09:24 +00:00
Member
Copy Link

can't replicate on pandorabox

can't replicate on pandorabox
flux commented 2022-10-06 03:14:20 +00:00
Member
Copy Link

if anyone could explain to me what Code: 85 a0 f7 ff ff 00 00 00 00 c7 85 94 f7 ff ff 00 00 00 00 44 0f bf 43 58 4d 8b 2e 4c 89 c0 48 c1 e0 05 4c 29 c0 4d 8d 6c c5 00 <41> 0f b7 55 20 66 44 39 ca 0f 83 11 19 00 00 66 89 93 b2 00 00 00 means, i'd give you a dollar, if i had any money to give. i hate being fed machine code in an error, when i'm not a machine.

maybe it's saying i need to use these numbers to buy a lottery ticket?

if anyone could explain to me what ```Code: 85 a0 f7 ff ff 00 00 00 00 c7 85 94 f7 ff ff 00 00 00 00 44 0f bf 43 58 4d 8b 2e 4c 89 c0 48 c1 e0 05 4c 29 c0 4d 8d 6c c5 00 <41> 0f b7 55 20 66 44 39 ca 0f 83 11 19 00 00 66 89 93 b2 00 00 00``` means, i'd give you a dollar, if i had any money to give. i hate being fed machine code in an error, when i'm not a machine. maybe it's saying i need to use these numbers to buy a lottery ticket?
AliasAlreadyTaken commented 2022-10-06 14:09:23 +00:00
Author
Owner
Copy Link

Maybe we should build at least the testserver not as Release, but as full debug build?

Maybe we should build at least the testserver not as Release, but as full debug build?
flux commented 2022-10-06 17:56:39 +00:00
Member
Copy Link

Maybe we should build at least the testserver not as Release, but as full debug build?

that's actually probably a good idea.

> Maybe we should build at least the testserver not as Release, but as full debug build? that's actually probably a good idea.
Diaeresis commented 2022-10-06 17:57:43 +00:00
Copy Link

if anyone could explain to me what Code: 85 a0 f7 ff ff 00 00 00 00 c7 85 94 f7 ff ff 00 00 00 00 44 0f bf 43 58 4d 8b 2e 4c 89 c0 48 c1 e0 05 4c 29 c0 4d 8d 6c c5 00 <41> 0f b7 55 20 66 44 39 ca 0f 83 11 19 00 00 66 89 93 b2 00 00 00 means, i'd give you a dollar, if i had any money to give. i hate being fed machine code in an error, when i'm not a machine.

I doubt it's of much use, but here you go:

   0:	85 a0 f7 ff ff 00    	test   %esp,0xfffff7(%rax)
   6:	00 00                	add    %al,(%rax)
   8:	00 c7                	add    %al,%bh
   a:	85 94 f7 ff ff 00 00 	test   %edx,0xffff(%rdi,%rsi,8)
  11:	00 00                	add    %al,(%rax)
  13:	44 0f bf 43 58       	movswl 0x58(%rbx),%r8d
  18:	4d 8b 2e             	mov    (%r14),%r13
  1b:	4c 89 c0             	mov    %r8,%rax
  1e:	48 c1 e0 05          	shl    $0x5,%rax
  22:	4c 29 c0             	sub    %r8,%rax
  25:	4d 8d 6c c5 00       	lea    0x0(%r13,%rax,8),%r13
  2a:	41 0f b7 55 20       	movzwl 0x20(%r13),%edx
  2f:	66 44 39 ca          	cmp    %r9w,%dx
  33:	0f 83 11 19 00 00    	jae    0x194a
  39:	66 89 93 b2 00 00 00 	mov    %dx,0xb2(%rbx)
> if anyone could explain to me what ```Code: 85 a0 f7 ff ff 00 00 00 00 c7 85 94 f7 ff ff 00 00 00 00 44 0f bf 43 58 4d 8b 2e 4c 89 c0 48 c1 e0 05 4c 29 c0 4d 8d 6c c5 00 <41> 0f b7 55 20 66 44 39 ca 0f 83 11 19 00 00 66 89 93 b2 00 00 00``` means, i'd give you a dollar, if i had any money to give. i hate being fed machine code in an error, when i'm not a machine. I doubt it's of much use, but here you go: ``` 0: 85 a0 f7 ff ff 00 test %esp,0xfffff7(%rax) 6: 00 00 add %al,(%rax) 8: 00 c7 add %al,%bh a: 85 94 f7 ff ff 00 00 test %edx,0xffff(%rdi,%rsi,8) 11: 00 00 add %al,(%rax) 13: 44 0f bf 43 58 movswl 0x58(%rbx),%r8d 18: 4d 8b 2e mov (%r14),%r13 1b: 4c 89 c0 mov %r8,%rax 1e: 48 c1 e0 05 shl $0x5,%rax 22: 4c 29 c0 sub %r8,%rax 25: 4d 8d 6c c5 00 lea 0x0(%r13,%rax,8),%r13 2a: 41 0f b7 55 20 movzwl 0x20(%r13),%edx 2f: 66 44 39 ca cmp %r9w,%dx 33: 0f 83 11 19 00 00 jae 0x194a 39: 66 89 93 b2 00 00 00 mov %dx,0xb2(%rbx) ```
flux commented 2022-10-07 21:35:47 +00:00
Member
Copy Link

i triggered this again, by accident, just now.

i triggered this again, by accident, just now.
AliasAlreadyTaken commented 2022-10-10 10:00:16 +00:00
Author
Owner
Copy Link

The testserver is now on DCMAKE_BUILD_TYPE=Debug and - by accident - 5.7.0, but now I can't reproduce it!

The testserver is now on DCMAKE_BUILD_TYPE=Debug and - by accident - 5.7.0, but now I can't reproduce it!
AliasAlreadyTaken commented 2022-12-25 15:41:30 +00:00
Author
Owner
Copy Link

There we are again

[ 256.455538] Server[3167]: segfault at 7fd5fc2c8 ip 000055ccf4cd517e sp 00007fd6196c1db0 error 4 in minetestserver[55ccf4982000+44d000]
[ 256.455862] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00

There we are again [ 256.455538] Server[3167]: segfault at 7fd5fc2c8 ip 000055ccf4cd517e sp 00007fd6196c1db0 error 4 in minetestserver[55ccf4982000+44d000] [ 256.455862] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00
Murmel commented 2022-12-27 16:19:23 +00:00
Copy Link

It also happens when the autocrafter is off.
But I still have no idea, how to reproduce this

It also happens when the autocrafter is off. But I still have no idea, how to reproduce this
flux commented 2022-12-28 00:16:24 +00:00
Member
Copy Link

@Murmel did you look at https://github.com/minetest/minetest/issues/11805?

@Murmel did you look at https://github.com/minetest/minetest/issues/11805?
Murmel commented 2022-12-28 15:17:05 +00:00
Copy Link

@Murmel did you look at https://github.com/minetest/minetest/issues/11805?

No I didn't until you mention. But as far is i understand, in the reported issue the autocrafter is turned on, when the error occurs. So I tried to be sure it is turned off, when I move items but still the server crashes.
Maybe this happens when it's laggy so the autocrafter only seems to be turned off but the server first gets the moving action and after the the signal to turn the autocrafter off?
Today i always waited a while after tuning it off, maybe this helps to avoid further crashes?

edit:
Mhhh, it does not.
I turned the autocrafter off and waited a while as I did more than one time before today.
Then I tried to clean the recipe, first by clearing the result-box which had no effect.

I closed the autocrafter after that, opened it after a moment and tried clearing the recipe by moving items from the left which resulted in a crash.
I think I will empty that autocrafter at a time not too many players are online and stop using it until we have an idea how to stop this behaviour.
Funny thing is: I have this one for a while now and crashes happen to occur just in the last few (probably three) days.

2nd edit: when the server was online i had a view in this autocrafter and it was turned on. So it seems my Idea, that the server did not get the turning off seems to be true.

> @Murmel did you look at https://github.com/minetest/minetest/issues/11805? No I didn't until you mention. But as far is i understand, in the reported issue the autocrafter is turned on, when the error occurs. So I tried to be sure it is turned off, when I move items but still the server crashes. Maybe this happens when it's laggy so the autocrafter only seems to be turned off but the server first gets the moving action and after the the signal to turn the autocrafter off? Today i always waited a while after tuning it off, maybe this helps to avoid further crashes? edit: Mhhh, it does not. I turned the autocrafter off and waited a while as I did more than one time before today. Then I tried to clean the recipe, first by clearing the result-box which had no effect. I closed the autocrafter after that, opened it after a moment and tried clearing the recipe by moving items from the left which resulted in a crash. I think I will empty that autocrafter at a time not too many players are online and stop using it until we have an idea how to stop this behaviour. Funny thing is: I have this one for a while now and crashes happen to occur just in the last few (probably three) days. 2nd edit: when the server was online i had a view in this autocrafter and it was turned on. So it seems my Idea, that the server did not get the turning off seems to be true.
AliasAlreadyTaken commented 2022-12-28 16:37:43 +00:00
Author
Owner
Copy Link

For whatever reason this happened during the last couple of days a lot more than in the past couple of month. Those are only the recorded segfaults after a server restart:

[  256.455538] Server[3167]: segfault at 7fd5fc2c8 ip 000055ccf4cd517e sp 00007fd6196c1db0 error 4 in minetestserver[55ccf4982000+44d000]
[  256.455862] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00
[75019.886971] Server[65148]: segfault at 7f8911a89010 ip 00007f892cf7165d sp 00007f89191d70e8 error 6 in libc.so.6[7f892ce45000+155000]
[75019.887134] Code: 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 83 fa 20 72 27 c5 fe 6f 06 48 83 fa 40 0f 87 a9 00 00 00 c5 fe 6f 4c 16 e0 <c5> fe 7f 07 c5 fe 7f 4c 17 e0 c5 f8 77 c3 0f 1f 44 00 00 83 fa 10
[75150.835246] Server[65312]: segfault at 7f74982b0000 ip 00007f74d0551661 sp 00007f74b3ffb0e8 error 7 in libc.so.6[7f74d0425000+155000]
[75150.835409] Code: 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 83 fa 20 72 27 c5 fe 6f 06 48 83 fa 40 0f 87 a9 00 00 00 c5 fe 6f 4c 16 e0 c5 fe 7f 07 <c5> fe 7f 4c 17 e0 c5 f8 77 c3 0f 1f 44 00 00 83 fa 10 73 2d 83 fa
[175503.449323] Server[87053]: segfault at 7f49918c4 ip 0000556c7cfd417e sp 00007f4a33dcbdb0 error 4 in minetestserver[556c7cc81000+44d000]
[175503.449563] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00
[194805.063604] Server[140997]: segfault at 7fa665750ee4 ip 0000557ea33c017e sp 00007fa3df6eedb0 error 4 in minetestserver[557ea306d000+44d000]
[194805.063794] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00
[259256.606443] Server[152685]: segfault at 7f78efc36 ip 0000556cbca6217e sp 00007f79f0481db0 error 4 in minetestserver[556cbc70f000+44d000]
[259256.606632] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00
[262953.609834] Server[188921]: segfault at 7f65a55f4 ip 0000559e99dea17e sp 00007f65f58d5db0 error 4 in minetestserver[559e99a97000+44d000]
[262953.610022] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00
For whatever reason this happened during the last couple of days a lot more than in the past couple of month. Those are only the recorded segfaults after a server restart: ``` [ 256.455538] Server[3167]: segfault at 7fd5fc2c8 ip 000055ccf4cd517e sp 00007fd6196c1db0 error 4 in minetestserver[55ccf4982000+44d000] [ 256.455862] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00 [75019.886971] Server[65148]: segfault at 7f8911a89010 ip 00007f892cf7165d sp 00007f89191d70e8 error 6 in libc.so.6[7f892ce45000+155000] [75019.887134] Code: 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 83 fa 20 72 27 c5 fe 6f 06 48 83 fa 40 0f 87 a9 00 00 00 c5 fe 6f 4c 16 e0 <c5> fe 7f 07 c5 fe 7f 4c 17 e0 c5 f8 77 c3 0f 1f 44 00 00 83 fa 10 [75150.835246] Server[65312]: segfault at 7f74982b0000 ip 00007f74d0551661 sp 00007f74b3ffb0e8 error 7 in libc.so.6[7f74d0425000+155000] [75150.835409] Code: 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 83 fa 20 72 27 c5 fe 6f 06 48 83 fa 40 0f 87 a9 00 00 00 c5 fe 6f 4c 16 e0 c5 fe 7f 07 <c5> fe 7f 4c 17 e0 c5 f8 77 c3 0f 1f 44 00 00 83 fa 10 73 2d 83 fa [175503.449323] Server[87053]: segfault at 7f49918c4 ip 0000556c7cfd417e sp 00007f4a33dcbdb0 error 4 in minetestserver[556c7cc81000+44d000] [175503.449563] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00 [194805.063604] Server[140997]: segfault at 7fa665750ee4 ip 0000557ea33c017e sp 00007fa3df6eedb0 error 4 in minetestserver[557ea306d000+44d000] [194805.063794] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00 [259256.606443] Server[152685]: segfault at 7f78efc36 ip 0000556cbca6217e sp 00007f79f0481db0 error 4 in minetestserver[556cbc70f000+44d000] [259256.606632] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00 [262953.609834] Server[188921]: segfault at 7f65a55f4 ip 0000559e99dea17e sp 00007f65f58d5db0 error 4 in minetestserver[559e99a97000+44d000] [262953.610022] Code: 66 44 89 93 b2 00 00 00 83 bd 9c f7 ff ff ff 0f 85 8c 12 00 00 0f bf 7b 58 4d 8b 0e 48 89 f8 48 c1 e0 05 48 29 f8 4d 8d 2c c1 <45> 0f b7 55 20 66 44 3b 95 a8 f7 ff ff 73 10 66 44 89 93 b2 00 00 ```
flux commented 2023-01-15 22:47:57 +00:00
Member
Copy Link

temporarily disabled clearing the crafting recipes via the output slot of the autocrafter, until the engine fix goes live: 3af3478bd7

temporarily disabled clearing the crafting recipes via the output slot of the autocrafter, until the engine fix goes live: https://gitea.your-land.de/your-land/yl_commons/commit/3af3478bd72e51473f54736a90308ac6e601b914
👍 1
flux added the
4. step/ready to QA test
4. step/partially fixed
 labels 2023-01-15 22:48:11 +00:00
AliasAlreadyTaken added this to the 1.1.117 milestone 2023-01-16 03:46:35 +00:00
AliasAlreadyTaken commented 2023-01-16 09:04:58 +00:00
Author
Owner
Copy Link

2023-01-16 09:04:25: ACTION[Main]: Server: Shutting down
2023-01-16 09:04:27: ERROR[Main]: ModError: Failed to load and run script from /home/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:
2023-01-16 09:04:27: ERROR[Main]: ...mods/yl_commons/bugfixes/autocrafter_inventory_crash.lua:11: attempt to call field 'override_node' (a nil value)
2023-01-16 09:04:27: ERROR[Main]: stack traceback:
2023-01-16 09:04:27: ERROR[Main]: ...mods/yl_commons/bugfixes/autocrafter_inventory_crash.lua:11: in main chunk
2023-01-16 09:04:27: ERROR[Main]: [C]: in function 'dofile'
2023-01-16 09:04:27: ERROR[Main]: ...e/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:179: in function 'dofile'
2023-01-16 09:04:27: ERROR[Main]: ...1/Minetest_test/bin/../mods/yl_commons/bugfixes/init.lua:8: in main chunk
2023-01-16 09:04:27: ERROR[Main]: [C]: in function 'dofile'
2023-01-16 09:04:27: ERROR[Main]: ...e/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:179: in function 'dofile'
2023-01-16 09:04:27: ERROR[Main]: ...e/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:188: in main chunk

2023-01-16 09:04:25: ACTION[Main]: Server: Shutting down 2023-01-16 09:04:27: ERROR[Main]: ModError: Failed to load and run script from /home/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua: 2023-01-16 09:04:27: ERROR[Main]: ...mods/yl_commons/bugfixes/autocrafter_inventory_crash.lua:11: attempt to call field 'override_node' (a nil value) 2023-01-16 09:04:27: ERROR[Main]: stack traceback: 2023-01-16 09:04:27: ERROR[Main]: ...mods/yl_commons/bugfixes/autocrafter_inventory_crash.lua:11: in main chunk 2023-01-16 09:04:27: ERROR[Main]: [C]: in function 'dofile' 2023-01-16 09:04:27: ERROR[Main]: ...e/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:179: in function 'dofile' 2023-01-16 09:04:27: ERROR[Main]: ...1/Minetest_test/bin/../mods/yl_commons/bugfixes/init.lua:8: in main chunk 2023-01-16 09:04:27: ERROR[Main]: [C]: in function 'dofile' 2023-01-16 09:04:27: ERROR[Main]: ...e/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:179: in function 'dofile' 2023-01-16 09:04:27: ERROR[Main]: ...e/mt/5.6.1/Minetest_test/bin/../mods/yl_commons/init.lua:188: in main chunk
AliasAlreadyTaken commented 2023-01-16 09:10:50 +00:00
Author
Owner
Copy Link

Fixed 294a6e39ef

Fixed https://gitea.your-land.de/your-land/yl_commons/commit/294a6e39ef9c74dc3bed59d034b9d0144ef783ce
AliasAlreadyTaken added the
ugh/QA main
 label 2023-01-18 11:53:32 +00:00
flux added
5. result/fixed
 and removed
4. step/ready to QA test
4. step/partially fixed
 labels 2023-01-25 22:20:31 +00:00
flux commented 2023-01-25 22:21:09 +00:00
Member
Copy Link

the patch is in place, considering this fixed, even though the engine issue isn't resolved yet.

the patch is in place, considering this fixed, even though the engine issue isn't resolved yet.
flux closed this issue 2023-01-25 22:21:10 +00:00
AliasAlreadyTaken commented 2023-02-13 14:18:09 +00:00
Author
Owner
Copy Link

https://github.com/joe7575/techage/issues/117

https://github.com/joe7575/techage/issues/117
flux commented 2023-05-27 17:19:23 +00:00
Member
Copy Link

upstream PR has been closed as abandoned :(

upstream PR has been closed as abandoned :(
😕 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

  
ugh/petz

yet another petz bugz.

  
ugh/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
ugh/QA NOK

Fix didn't yield the expected results

  
ugh/QA OK

tested

No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
Milestone
Clear milestone
No items
No Milestone
1.1.117
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#2816
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?