Strange Behavior after 5-10 Minutes after Reboot Driver and MudLib

[Eric]

We have a problem with our MudLib or Driver and would be very happy if someone has ideas on how to solve it. Maybe it is because of some Driver setting. So I hope, I am not in the wrong Group here. :-)

We use LDMud 3.2.17 in NATIVE mode, because the last version is still compatible with Amylaar's driver and our MudLib (a former SilberLand MudLib which based on an early MorgenGrauen MudLib) is most compatible with it.

We have imported an old backup of our mudlib, because we want to revive our old mud back from 2006. It last ran smoothly in 2006 under LDMud 3.2.13 on another server.

The problem:

We have a property P_TEMPERATURE_RANGE, which contains the temperature range for NPCs but also for player shells. After rebooting the driver with our MudLib, everything works fine, but then, after 5-10 minutes, P_TEMPERATURE_RANGE is set to 0 and accordingly all NPCs and players slowly die from heat.

In this context, we also noticed that the seer gates initially work normally, but then also no longer work properly after 5-10 minutes after a reboot.

So I think there is a connection here that has nothing to do with the seer gates or P_TEMPERATURE_RANGE directly, but somehow causes a change after 5-10 minutes.

Has anyone ever had a similar effect and therefore has an idea what that could be? We think it's not the reset because the 5-10 minutes are too short. A reset always takes place around every 45 minutes.

Thank you
Eric

[Zesstra]

Hello Eric,

I believe, without knowing your mudlib, one can only give wild and
unsubstantiated guesses. One might be, that the range in the property (is it
an array?) is shared between all livings and some object changes it.

Upgrading that old lib will likely be much work. There may be another
alternative you might think of: you could take the current driver und MG
public lib (which runs with 3.6.4) and port the needed features from the old
SL mudlib to it. While that is also some work, depending on the amount of
specific SL features you need, it might be less.

Zesstra

> --
> You received this message because you are subscribed to the Google Groups
> "LDMud Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ldmud-talk+...@googlegroups.com
> <mailto:ldmud-talk+...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ldmud-talk/5b930ac0-db7a-4d16-91e1-68d76c16c248n%40googlegroups.com
> <https://groups.google.com/d/msgid/ldmud-talk/5b930ac0-db7a-4d16-91e1-68d76c16c248n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
MorgenGrauen -
1 Welt, mehr als 200 Programmierer , mehr als 16000 Raeume,
viel mehr als 7000 unterschiedliche Figuren, 90 Quests, 13 Gilden,
ueber 5000 Waffen und Ruestungen, keine Umlaute und ein Haufen Verrueckter.
Existenz: mehr als 25 Jahre
http://mg.mud.de/

[Eric]

Thank you Zesstra, :-)

You are right. Unfortunatelly it could be anything. I stoped the time, and it is exactly 11 Minutes, so 660 seconds after reboot until this strange behavior occurs. This exact time also irritates me, but could be an indication of the problem.

We also get always:  "Caught error: Bad argument 1 to getuid()" in the mudlib.log when old wizard shells relogin. This is a error we did not get back in 2006 on the other server.

If I check P_TEMPERATURE_RANGE with the MG-Tool via xcall [...], after 11 Minutes, the result/array is set to 0. However withe the Lupe-Tool P_TEMPERATURE_RANGE will portrait the correct numbers of that array in P_TEMPERATURE_RANGE. Another Member of us pointed out, that their might be a problem with getuid() while geteuid() works fine. So this could be related to the Bad argument 1 to getuid (). from above.

So I also thought, maybe it has to do with the ./configure settings I did with the driver. Maybe here is the problem allready. enable_strict_euids?

#!/bin/sh
#
# Settings for the NordLand mudlib.
#
# configure will strip this part from the script.

exec ./configure --prefix=/home/nordland --libdir=/home/nordland/mudlib --libexec=/home/nordland/erq --with-setting=nordland $*
exit 1

with_malloc=sysmalloc
with_optimize=no

enable_erq=xerq

enable_access_control=no

with_time_to_clean_up=21600
with_time_to_swap=5400
with_time_to_swap_variables=10800
with_time_to_reset=3600

with_max_bits=1200

with_portno=4711
with_maxnumports=3

with_max_local=25

with_swap_file=/home/nordland/swapfiles/SwapFile

with_max_array_size=5000
with_max_players=100

with_htable_size=16384

enable_compat_mode=no
enable_strict_euids=yes

enable_supply_parse_command=no
enable_initialization_by___init=yes

with_max_malloced=0x1f000000



Thank you for any reply. :-)
Eric

[Zesstra]

Without knowing your code, nobody can help you here.

But I doubt that something is defective with getuid(), my assumption is that
you pass 0 or a destructed object to getuid(). That you will have to check in
your stacktrace.

Zesstra

On 09.06.21 13:31, Eric wrote:
> Thank you Zesstra, :-)
>
> You are right. Unfortunatelly it could be anything. I stoped the time, and it
> is exactly 11 Minutes, so 660 seconds after reboot until this strange behavior
> occurs. This exact time also irritates me, but could be an indication of the
> problem.
>
> We also get always:  "Caught error: Bad argument 1 to getuid()" in the

> mudlib.logwhen old wizard shells relogin. This is a error we did not get back

> in 2006 on the other server.
>

> <https://groups.google.com/d/msgid/ldmud-talk/5b930ac0-db7a-4d16-91e1-68d76c16c248n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/ldmud-talk/5b930ac0-db7a-4d16-91e1-68d76c16c248n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
>
> --
> MorgenGrauen -
> 1 Welt, mehr als 200 Programmierer , mehr als 16000 Raeume,
> viel mehr als 7000 unterschiedliche Figuren, 90 Quests, 13 Gilden,
> ueber 5000 Waffen und Ruestungen, keine Umlaute und ein Haufen Verrueckter.
> Existenz: mehr als 25 Jahre

> http://mg.mud.de/ <http://mg.mud.de/>

>
> --
> You received this message because you are subscribed to the Google Groups
> "LDMud Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ldmud-talk+...@googlegroups.com
> <mailto:ldmud-talk+...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/ldmud-talk/46e67b12-0855-4b57-a4c0-c21e17dddf88n%40googlegroups.com
> <https://groups.google.com/d/msgid/ldmud-talk/46e67b12-0855-4b57-a4c0-c21e17dddf88n%40googlegroups.com?utm_medium=email&utm_source=footer>.