Bad API Password... ???

[Knutselmaaster]

Well, update to the latest release of manialive and the freezone plugin then.
How can you say that you won't update because you don't want problems, and at the same time say that you have problems?
Always update everything to the latest version, that is your side of the things you can try to fix it.
And it really is weird to have the same problem on different physical machines, as there are not many people with this problem, so it really is a strange coincidence.
Are all server logins made by the same login?
And as W1lla stated, there is no support for manialive/xaseco compatibility problems.
But i must add that there are also cases of freezone servers that only run manialive and still have the api password problem.
Please give me the login(s) that made the serveraccounts so that i can check them.

[Stardust8888]

People are forced to use Manialive. So you wanna tell me all the years of development and time people invested to make xaseco are gone not possible because of FreeZone?

Users!!! and this are the people who pay for the game, love it. So you wanna tell me, well yes thanks for buying Nadeo Game but pls i dont care about your work?

Willa your comment sounds like no sense.

But to shorten up this. Maybe, when you accept that im not a beginner user, i would like to get in direct contact to Knutselmaaster. So we can stop this post wich will not lead to anything.

You told before im would not like to help with fixing it, thats just not true. Ofcourse it is in my interest to fix it.
But there is no sense in asking me same noob questions as all.

So @ Knutselmaaster, i would like to get in contact with you. Im able to deliver all things you need.
So pls let me know if you agree with that. This post will only end in misunderstandings.

[reaby]

If you wanna have reports and things, just setup a test system wich can run until it crashes, just take care it is running enough servers and have enough visitors and im sure it will.

Problem is, that a testing system at localhost doesn't have the same playertraffic going on as real server.
I have tested manialive for many days running on localhost. When there is no players it runs fine.

Thanks goes to Nouseforname for his 40 slot mlepp testing server, which is propably the most active testing system for running native manialive.

The findings are, like you noted: manialive at high traffic live usage runs about a day.
During the time, the memory consumption grows from initial of 50megs to way over 300mb.
IF the memoryconsumption doesn't get hight enough for php limits, it will crash on managedwindow line 516 at some point.
Earlier the testing server faced this same problem as you - every time player did a connect or disconnect from server <freezone> bad server api - messages was send to all admins. On a 40 player server this was irritating, since people leave and join all the time.

SO the bad api password message:
It has to be serverside problem at nadeo... since the configs are right and it starts after some time, my 10 points goes to:

* your freezone session at nadeo server timeouts -> this will trigger 401 --> which will say bad api password.

if this is the thing, then freezone plugin should try to login every now and then back to master server.

I dont wanna play with my custormers and i dont have money to setup a root server just for getting your bugs.

Point noted.

[aseco]

Okay, I think there is more than one problem being discussed here.

a) You feel tricked because you have to run ManiaLive for the FreeZone.
Of course aseco is a great tool (oh yeah), but somewhen you reach a point where you need to start something new to make advantage of improved technology/architecture/etc.
Supporting the development of ManiaLive will be of use for everyone. I have put so much work in aseco myself, but in the end you have to face the borders of each technology and think about the way to go. In this case it was time for a "revolution" - you might not see it if you are not working with the code directly - there were reasons to not rely on the aseco base anymore (event management, window handling, threading ...). This all works with a little community developing on it, but the more players working on plugins and the more windows etc are being used the more we need a new server tool which supports this kind of stuff. Clearly we all want to stick with the stuff we like, but change can be for good ... ManiaLive shall take the tough work from the community, give a common base for dedicated server development. The more futures are being added, the harder it will be to have a reliable and up to date code base managed by the community.

Don't get me wrong, I am not trying to push people into ManiaLive, it is just that complaining about it does not make it anything better. There is so much missing, especially plugins and community content!
Of course this can't be the end of aseco and I wouldn't want it.
There's still people driving petrol cars today while there are electric ones, too.

b) ManiaLive is buggy and has memory issues.
The ManiaLive core should be very stable and does not leak a noticable amount of memory. Even the core plugins have been tested and have performed really good. As stated before the internal FreeZone servers are restarted once a week and the memory delta is quite low. I think the problem are third party plugins that are using the windowing system. (no offence, glad there are people working to improve the situation!)
Background information: When a window is being opened for a player it will create everything (all controls, data) just for him. The problem starts when a player leaves and ManiaLive tries to release the memory for all the windows that have been created for him. Now if you write your own windows it is essential to remove/clear all references to and from other objects. Otherwise php won't let the memory free up and will keep these windows though the player has left the server hours and hours ago!
I will write some debugging switch that you can use to show information about deleted windows/controls in the near future to make the development process easier!

Phew, lots of text, whoever managed to read until here: thanks.
Hopefully some of it made sense for you and you won't be that sceptic of ManiaLive anymore ...
Keep it going

[w1lla]

For windows etc.

This is a quite good function to use for developers or did it read the api wrong...

Code: Select all

/**
    * Frees the memory that has been allocated
    * for the player's window(s).
    * If it is currently displayed it will also be
    * closed.
    * @param string $login
    */
   static function Erase($login)
   {
      $class_name = get_called_class();
      
      if (isset(self::$instances[$login][$class_name]))
      {
         $window = self::$instances[$login][$class_name];
         $window->hide();
         $window->setCloseCallback(array($window, 'destroy'));
      }
      
      if (isset(self::$instancesNonSingleton[$login]))
      {
         foreach (self::$instancesNonSingleton[$login] as $window)
         {
            if (is_subclass_of($window, $class_name))
            {
               $window->hide();
               $window->setCloseCallback(array($window, 'destroy'));
            }
         }
      }
   }

Edit:


In file:

ManiaLive\libraries\ManiaLive\Gui\Windowing\Window.php

[Knutselmaaster]

Thanks goes to Nouseforname for his 40 slot mlepp testing server, which is propably the most active testing system for running native manialive.

The findings are, like you noted: manialive at high traffic live usage runs about a day.
During the time, the memory consumption grows from initial of 50megs to way over 300mb.

I thought Nouses memory problem was already solved a long time ago?
I don't have it on any of my 7 manialive servers, although they aren't as well visited as Nouse's is, they run a long time (since i stopped using the dedi plugin) get hundreds of visitors and have no high memory count.
And i don't remember seeing the window problem neither (but i can be wrong about that)

[nouseforname]

I thought Nouses memory problem was already solved a long time ago?

nope, its not. i just allow to have unlimited memory. as i wrote before. the default mem_limit in php.ini is -1 which i interpret as unlimited anyway.
Also i know the information of the "Profiler" and Konsole command

Code: Select all

MEM=`cat /proc/$(cat $PIDFILE)/status | grep VmSize`

show different values. but both are much higher than 20-50mb.
The Highest Konsole value afaik was 700mb.

i stopped observing the mem since its not crashing caause of memory anymore. thats why i didnt follow up here.

i am quite sure it must be something with 3rd party plugins (MLEPP), and i am quite sure its related to the amount of players.

the daily crash comes from window handling as well, but since i used the fix, i cant see any crash.... will observe.


ps. i also make a weekly auto res for all my servers.

[farfa]

This problem is dependent of the plugin developer, it's his responsibility to check if an object instance has been entirely destroyed. ManiaLive itself has no way to do this.

[Stardust8888]

Well alot comments, thanks for it.

First i would like to say that im only realy angry with Nadeo, because they created this weird situation with this nonsense Freezone crap. But im not going to start a discussion about this here.
I always have great respekt for all the devolopers who spend alot of time in building this amazing scripts players realy love and make game interesting.

You say the basic core of Manialive is running stable. I can accept this, but i think the sense of it is to run plugins .
I hear problem comes from third party plugins, i accept this also.

But i think it is also a fact that Manialive, at this point of developement cant replace xaseco.
Im not a developer i just have to work with this things. So what is the solution?

I think i read some good ideas, like giving some developer tools so they can check if third party plugins are running ok.
I think alot more communication between developers is needed, just to find errors faster.

It is hard to find out wich plugins are still developed and wich not. So maybe a list with something like "certyfied" Plugins would be helpful. This should contain plugins wich are known for running or known for still beeing developed.
And maybe a list with plugins wich are known for causing problems.

One more idea would be to check every plugin before it is getting released, or accepted officialy. I know this sound weird because it would need somebody, or more people to have a look into plugins. But maybe this would avoid alot probs wich normaly comes later. And maybe this will be in the end less work, because you can tell developer direct what is missing, like closing all windows.

But whats the solution for now with the memory problem? We have to live with workarounds like restarting Manialive every day?


PS: Im hosting alot of servers. Over 20 Freezone and even more "normal" servers. So maybe i see problems wich will not be seen by somebody with a single server. I do not know how exactly but i would like to help. But i think this is something for a personal talk. I cannot allways upload error logs manualy, but maybe if i get a FTP account i can write scripts to do such things automatically.

[nouseforname]

PS: Im hosting alot of servers. Over 20 Freezone and even more "normal" servers. So maybe i see problems wich will not be seen by somebody with a single server. I do not know how exactly but i would like to help. But i think this is something for a personal talk. I cannot allways upload error logs manualy, but maybe if i get a FTP account i can write scripts to do such things automatically.

the memory problem only exist if you are using manialive with all plugins incl MLEPP.
in case you are using simple manialive with freezone plugin, there is no prob with memory.