Hi starlet_man, please try again - your host should be visible there again.
Right, so I finally figured out what's the cause and that means I was able to fix this now. Or should be at least (bit hard to fully test this one).
Can you please try to unlock an old version again? I think it's fixed.
Hi, the host is running now. Please give it a go.
Oof sorry. The relay crashed and I had switched off monitoring for it so I didn't notice 
Fixed now though.
Fixed now though.Thanks! That's updated.
That's actually in the Lapper.lpr file of the latest official release
See the uploaded LFSLapper archive in https://www.lfs.net/forum/thread/92832-Release%3A-LFSLapper-V7-0-6-3
I think it's working. So besides commenting the console event init stuff which uses a function not present in mono, I had to compile lapper with the symbol MONOSQLITE so it would use Mono.Data.SqliteClient instead of System.Data.SQLite .
Perhaps in the future you could make two releases? One for windows and one for linux (mono)
Additionally I installed libmono-i18n4.0-all which installed a whole lot more libs for mono which helped a bit too with some other problems. Not sure why I hadn't done that before...
I can provide a bit updated code tomorrow (it's late now and i might do some more tweaks), allowing you to easily create the two version if you want.
@alau07 could you try lapper again on your host?
EDIT - hmm found some more problems. Might take until tomorrow before they're fixed.
Perhaps in the future you could make two releases? One for windows and one for linux (mono)
Additionally I installed libmono-i18n4.0-all which installed a whole lot more libs for mono which helped a bit too with some other problems. Not sure why I hadn't done that before...
I can provide a bit updated code tomorrow (it's late now and i might do some more tweaks), allowing you to easily create the two version if you want.
@alau07 could you try lapper again on your host?
EDIT - hmm found some more problems. Might take until tomorrow before they're fixed.
Last edited by Victor, .
Turns out it was already installed 
Playing around with lapper now. Not initing the console events got me a bit further but now i run into another problem again ...
Will see how far i can get.
Playing around with lapper now. Not initing the console events got me a bit further but now i run into another problem again ...Will see how far i can get.
Got the same problem. However, I installed libmono-i18n4.0-all which added the missing code pages. Now I get another error though:
Doing a quick search led me to this thread: https://www.lfs.net/forum/post/1937853#post1937853
This might be a problem I cannot fix (easily).
Were these new kernel32 functions added in recent versions of lapper?
EDIT - I wonder if this could be avoided, maybe with a startup param or config variable that enables console events or not. In my case I'd disable them and this piece of code wouldn't have to run.
Maybe I should install VS again .. hmm.
Doing a quick search led me to this thread: https://www.lfs.net/forum/post/1937853#post1937853
This might be a problem I cannot fix (easily).
Were these new kernel32 functions added in recent versions of lapper?
EDIT - I wonder if this could be avoided, maybe with a startup param or config variable that enables console events or not. In my case I'd disable them and this piece of code wouldn't have to run.
Maybe I should install VS again .. hmm.
Last edited by Victor, .
Thanks! I'll give that a try soon.
True, but i currently don't have visual studio setup to compile it :/
pff ... have updated the os and mono and everything, but still the same issue. Seems mono doesn't know about 1251. But apparently it is supposed to know "windows-1251" (even though 1251 in the functions below should work according to docs).
I wonder if it's possible for you to create a test version with the following change? Would like to try.
CodePage.cs
I wonder if it's possible for you to create a test version with the following change? Would like to try.
CodePage.cs
private static readonly Dictionary<char, Encoding> EncodingMap = new Dictionary<char, Encoding> {
{ 'L', Encoding.GetEncoding("windows-1252", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'G', Encoding.GetEncoding("windows-1253", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'C', Encoding.GetEncoding("windows-1251", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'J', Encoding.GetEncoding("shift_jis", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'E', Encoding.GetEncoding("windows-1250", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'T', Encoding.GetEncoding("windows-1254", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'B', Encoding.GetEncoding("windows-1257", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'H', Encoding.GetEncoding("big5", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'S', Encoding.GetEncoding("gb2312", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
{ 'K', Encoding.GetEncoding("ks_c_5601-1987", EncoderExceptionFallback.ExceptionFallback, DecoderExceptionFallback.ReplacementFallback) },
};
Last edited by Victor, .
just some more food ...
I've dumped some Lapper traffic where you can see:
17:03:03.879720 - Lapper sends ISP_ISI with the correct admin password
17:03:03.881793 - LFS sends ISP_VER in reply (so everything should be ok, yet I don't see this in the LFS console
)
and then some more data is exchanged before Lapper hangs up right after sending ISP_TINY + TINY_NCN (17:03:04.015324).
So this is pretty weird. In which cases does Lapper report that the admin password is incorrect?
I've dumped some Lapper traffic where you can see:
17:03:03.879720 - Lapper sends ISP_ISI with the correct admin password
17:03:03.881793 - LFS sends ISP_VER in reply (so everything should be ok, yet I don't see this in the LFS console
)and then some more data is exchanged before Lapper hangs up right after sending ISP_TINY + TINY_NCN (17:03:04.015324).
So this is pretty weird. In which cases does Lapper report that the admin password is incorrect?
Last edited by Victor, .
and oh, no ERR files and I'm using a default configuration ... except the two extra lines with $configFile and $superUsersFile in default_1.ini, as pasted above.
Your console question got me a bit further. No, I don't have a console of Lapper, but i'm now piping the output to a file, to see this:
Are these two errors? Something admin password related and a codepage exception?
Re. the password, I have it configured:
Did something change regarding the password?
And no idea about the exception. Should I update mono maybe? It's quite an ancient version that I have there.
Are these two errors? Something admin password related and a codepage exception?
Re. the password, I have it configured:
Did something change regarding the password?
And no idea about the exception. Should I update mono maybe? It's quite an ancient version that I have there.
I tried remotePort=3002 but it didn't help unfortunately.
EDIT - so just checking ... remotePort is for remote management of Lapper, correct? So this port should always be randomised as Lapper will open a local socket on that port for each instance?
EDIT 2 - actually I don't see a listening socket on 3001 at all. Even though there should be one?
EDIT 3 - aha, when I start a new instance of Lapper, I can briefly see activity on 3001:
but then it goes away after Lapper exits, of course. At least this hints that remotePort (or at least, setting up the socket) is not the issue here.
EDIT - so just checking ... remotePort is for remote management of Lapper, correct? So this port should always be randomised as Lapper will open a local socket on that port for each instance?
EDIT 2 - actually I don't see a listening socket on 3001 at all. Even though there should be one?
EDIT 3 - aha, when I start a new instance of Lapper, I can briefly see activity on 3001:
but then it goes away after Lapper exits, of course. At least this hints that remotePort (or at least, setting up the socket) is not the issue here.
Last edited by Victor, .
The logs don't tell us much unfortunately.
Via the LFS console I'm seeing Lapper connect, and disconnect basically immediately:
/bin/default/logs/127.0.0.1-57497-MSS.log:
/bin/logs/LFSLapper-MSS.log:
and that's all
We're using the latest Lapper v7.0.6.3
I'll keep trying to find out what's going on. Though I wonder if there could be a bit more debug for the log files.
Another thing I noticed is that Lapper doesn't seem to send an init packet at all. Otherwise the console output would have shown "InSim : version 7 requested - using 7" after "InSim - TCP : LFSLapper", but there's no such line.
I assume the message "InSim guest closed : LFSLapper" means Lapper actively closed the connection.
Does that give you guys any hints?
Via the LFS console I'm seeing Lapper connect, and disconnect basically immediately:
/bin/default/logs/127.0.0.1-57497-MSS.log:
/bin/logs/LFSLapper-MSS.log:
and that's all
We're using the latest Lapper v7.0.6.3
I'll keep trying to find out what's going on. Though I wonder if there could be a bit more debug for the log files.
Another thing I noticed is that Lapper doesn't seem to send an init packet at all. Otherwise the console output would have shown "InSim : version 7 requested - using 7" after "InSim - TCP : LFSLapper", but there's no such line.
I assume the message "InSim guest closed : LFSLapper" means Lapper actively closed the connection.
Does that give you guys any hints?
Hmm no I'm afraid the above is the only hotlap log information we have.
You can get the hotlap log entries via the pub stat api.
For this to work you'll need to generate an ident key at lfsworld: https://www.lfsworld.net/?win=settings&whichTab=pubstat
With that key you can make an api call like this:
The maximum number of results it returns are 150. But you can do paging by setting a start time in the query, like so:
Then just take the last timestamp of each result set and make another call with that timestamp set as starttime to go to the next page.
For more information on pubstat, see: https://www.lfs.net/forum/thread/14480-How-to-retrieve-LFS-World-stats%3F
Hope that helps.
For this to work you'll need to generate an ident key at lfsworld: https://www.lfsworld.net/?win=settings&whichTab=pubstat
With that key you can make an api call like this:
https://www.lfsworld.net/pubstat/get_stat2.php?version=1.5&idk={identKey}&action=hl_log&s=1&lines=150The maximum number of results it returns are 150. But you can do paging by setting a start time in the query, like so:
https://www.lfsworld.net/pubstat/get_stat2.php?version=1.5&idk={identKey}&action=hl_log&s=1&lines=150&starttime=1543875060Then just take the last timestamp of each result set and make another call with that timestamp set as starttime to go to the next page.
For more information on pubstat, see: https://www.lfs.net/forum/thread/14480-How-to-retrieve-LFS-World-stats%3F
Hope that helps.
hm, I don't see any different numbers? Don't know what version you have .. 
Hi, sorry about that. It is fixed now.
It tries to load an image from imgur but imgur returns a 403 Forbidden. I guess they don't like the referrer (cdn.knightlab.com)? Try hosting the image on another website.
Sorry, 100% fixed now.
FGED GREDG RDFGDR GSFDG