Maniaplanet Forum

Tavernicole wrote: ↑16 May 2017, 22:33 Command not working

We can't use the "/admin remove" command. Even if we use a "/list" command before to display the list of maps, entering "/admin remove 1" for instance, the controler responds that we must use /list before.

Fixed for the next release (fix is available at github).

Tavernicole wrote: ↑16 May 2017, 22:33 Missing antislash check

Added to the todo list.

Tavernicole wrote: ↑16 May 2017, 22:33 Memory load

uaseco v0.9.1 occupies 3.5MB of memory, while uaseco v0.9.2 needs 36.8MB (uaseco.php + webrequest.php). As before, this issue is not critical as a game server has sufficient memory to handle this, but I'm sure that with this one I will definitely ruin your next sunday, lol!

Does both dedicated server have the same amount of maps and players while you compared this? The RAM requirements of UASECO depends very much on this. You can turn on debug (in UASECO.xml -> <developer_options>) to let UASECO print more details into the logfile.

EDIT: I guess the smallest php process is webrequest.php, because the others are nearly the same size, which lets me thing that are the UASECO processes. Because webrequest.php can't really need that much RAM...

undef.de wrote: ↑16 May 2017, 22:53

Tavernicole wrote: ↑16 May 2017, 22:33 Memory load

uaseco v0.9.1 occupies 3.5MB of memory, while uaseco v0.9.2 needs 36.8MB (uaseco.php + webrequest.php). As before, this issue is not critical as a game server has sufficient memory to handle this, but I'm sure that with this one I will definitely ruin your next sunday, lol!

Does both dedicated server have the same amount of maps and players while you compared this? The RAM requirements of UASECO depends very much on this. You can turn on debug (in UASECO.xml -> <developer_options>) to let UASECO print more details into the logfile.

EDIT: I guess the smallest php process is webrequest.php, because the others are nearly the same size, which lets me thing that are the UASECO processes. Because webrequest.php can't really need that much RAM...

My mistake. I killed the 3.5MB process and saw the uaseco v0.9.1 was down, that's why I reported the issue. But now, as I upgraded the second server, I can see that I have two 18MB processes and two 3.5MB process. So you're right, me and my picture were wrong, the small one may be the WebRequest and the biggest ones are uaseco, AND more interestingly, their sizes are similar between v0.9.1 and v0.9.2. The issue is fixed: the report IS the bug.

I use the actually version,...

This worker kills himself on UASECO shutdown, so there is no need to kill him manually.

this don't work for me,.... I have to kill him manually,... (ubuntu system)

ramires wrote: ↑17 May 2017, 08:43 I use the actually version,...

This worker kills himself on UASECO shutdown, so there is no need to kill him manually.

this don't work for me,.... I have to kill him manually,... (ubuntu system)

That was a bug which is fixed for the next release (or available at github).

great,.. thx,.. will check the github,...

On every server with music server enabled I get on every start of the map the debug screen of mp4 other people are not affected by it seems would like to make an screeny but f10 does not work on debug screen

copy of the debug screen =

endbase wrote: ↑17 May 2017, 11:19 On every server with music server enabled I get on every start of the map the debug screen of mp4 other people are not affected by it seems would like to make an screeny but f10 does not work on debug screen

Try then ALT+Print, that will copy a screenshot into clipboard. Then start XnView (or similar tool) and press CTRL+SHIFT+V to paste that.

endbase wrote: ↑17 May 2017, 11:19

Code: Select all

	declare persistent Boolean RecordsEyepieceMusicWidgetVisible = True;

ERR [30, 69] Persistent storage limit reached.
	MusicWidget ()::Main() [30, 69]

Thanks for report, will be fixed in the next release.

[Plugin] » Can not register chat command "/elist" because callback Method "chat_elist()" of class "PluginRecordsEyepiece" is not callable, ignoring!

Getting this error in log file with actual github version,... Working anyway,...

Ahhaa... yes... fail: Just rename line 1367 from
to
I'll do that too.

thx,.. working fine,...