Hello Varga, could you please let me know what steps should be done to reproduce: "whenn one unregistered participant is logged in with nickname."
Thanks in advance! On Sun, Feb 16, 2014 at 2:57 PM, Varga Balázs <[email protected]> wrote: > Hello! > > I try update OM to latest build and unsucces this. > > /opt/red5# ./admin.sh -i -v /opt/3.0.0/720/red5/backup_ > 2014_02_16_08_26_41.zip > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [jar:file:/opt/3.0.0/737/red5/ > red5-server.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [jar:file:/opt/3.0.0/737/red5/ > lib/logback-classic-1.0.13.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.red5.logging.LoggingContextSelector] > User login was not provided, or too short, should be at least 4 character > long. > > I check usernames in db, and have many short username. > The short usernbames generated OM automaticali, whenn one unregistered > participant is logged in with nickname. > eg.: 1_zz, 1_, 1_dd, 1_cs...etc. > > The OM insert into om_users all participant as contact, and not correctly > set login length. eg: 1_ > > Balazs > -- WBR Maxim aka solomax
