Hi guys !!!

I am leading the LFSLapper for SFDT team. We have 4servers and when i connect LFSLapper to server #1 it goes on there. But when i connect it to server #2 #3 or #4 i get this error ''13.01.2011 20:19:35 -> Not a connexion packet! Close connection''

Now later night for Server 1 also :/ what to do ?

Pls help
-jsrk-

Can you post a copy of your LFSServers.cfg file as well as each servers /insim= and /port= lins from each servers setup.cfg file


That will let us see what the config is and if there is an issue;

Yo,

Sorry for late answer. Here are the information from server 1 and 2 at least. Server 3 and 4 ports i am not sure yet. But Servers 2-4 will go off soon anyway so we could at least fix the problem for server 1.

This is in my LFSLapper ''LFSServers.cfg'' :

# Configuration of LFSServer to be Managed with LFSLapper
# One line per server
# Remote port is the port used to manage LFSLapper remotely, future extension
# One remote port per LFSLapper on one machine, autoStart is optionnal
#Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork
timeOutScript=2000;
remotePort=3001;
DEF1|gr1|81.207.36.235|29999|./default|default_1.ini|autowork

insim port: 29999
normal port : 63392


For Server 2:

(Copy of LFSServers.cfg)

# Configuration of LFSServer to be Managed with LFSLapper
# One line per server
# Remote port is the port used to manage LFSLapper remotely, future extension
# One remote port per LFSLapper on one machine, autoStart is optionnal
#Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork
timeOutScript=2000;
remotePort=3001;
DEF1|gr1|85.17.183.199|29999|./default|default_1.ini|autowork

Insim port : 29999
normal port : 63392

3 and 4 not needed I can fix it for them same as for those 2 if needed

Hope we get the problem fixed

See you
-jsrk-

create copy of default folder in your LFS Lapper and rename it to
"default2" and put this to your lfsservers.cfg

I don't mean that. I mean the error. I get this to my LFSLapper.exe :

Lapper Instance abort, Go in StnadBy mode. Look at log file :./deafult/logs/85.17.183.199-ERR.log

-jsrk-

cmon. give a replay pls

Quote from jsrk :

I don't mean that. I mean the error. I get this to my LFSLapper.exe :

Lapper Instance abort, Go in StnadBy mode. Look at log file :./deafult/logs/85.17.183.199-ERR.log

-jsrk-

So whats in the log file?

I get nothing but 1 time i got this:

02.01.2011 20:50:05 -> Not a connexion packet! Close connection
02.01.2011 21:50:30 -> Not a connexion packet! Close connection


-jsrk-

Okay, can you please give us:

1. The ip address of each of your LFS servers.
2. Copy & paste the line that says somehting like "/insim=31993" from each of your LFS servers setup.cfg files

Are you running 2 instances of Lapper or only 1 that connects to both servers? If running 1 instance, paste your LFSServers.cfg file and a screenshot of an expanded explorer tree view of your Lapper directory so we can see that everything is in the right place.

Hi,

Answer 1: Ip adress for each server:

Server 1: 81.207.36.235 (not online atm)
Server 2: 85.17.183.199
Server 3: 85.17.183.199
Server 4: 85.17.183.199

Answer 2 :

For Server 1:
DEF1|gr1|81.207.36.235|29999|./default|default_1.ini|autowork

For Server 2 :
DEF1|gr1|85.17.183.199|29999|./default|default_1.ini|autowork

For Server 3 :
DEF1|gr1|85.17.183.199|30000|./default|default_1.ini|autowork

For Server 4 :
DEF1|gr1|85.17.183.199|30001|./default|default_1.ini|autowork

Answer 3 :

I have only run 1 lapper for 1 server at the same time, but if its possible to run it to many servers from the same lapper i will do that If i get example

Answer 4 : An Attachments+LFSServers.cfg

The LFSServers.cfg:

# Configuration of LFSServer to be Managed with LFSLapper
# One line per server
# Remote port is the port used to manage LFSLapper remotely, future extension
# One remote port per LFSLapper on one machine, autoStart is optionnal
#Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork
timeOutScript=2000;
remotePort=3001;
DEF1|gr1|85.17.183.199|29999|./default|default_1.ini|autowork

Hope that info is enough and that 1 screenshot

See you
-jsrk-

cmoooon no response:guilty:

Quote from jsrk :

Hi,

Answer 1: Ip adress for each server:

Server 1: 81.207.36.235 (not online atm)
Server 2: 85.17.183.199
Server 3: 85.17.183.199
Server 4: 85.17.183.199

Answer 2 :

For Server 1:
DEF1|gr1|81.207.36.235|29999|./default|default_1.ini|autowork

For Server 2 :
DEF1|gr1|85.17.183.199|29999|./default|default_1.ini|autowork

For Server 3 :
DEF1|gr1|85.17.183.199|30000|./default|default_1.ini|autowork

For Server 4 :
DEF1|gr1|85.17.183.199|30001|./default|default_1.ini|autowork

Answer 3 :

I have only run 1 lapper for 1 server at the same time, but if its possible to run it to many servers from the same lapper i will do that If i get example

Answer 4 : An Attachments+LFSServers.cfg

The LFSServers.cfg:

# Configuration of LFSServer to be Managed with LFSLapper
# One line per server
# Remote port is the port used to manage LFSLapper remotely, future extension
# One remote port per LFSLapper on one machine, autoStart is optionnal
#Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork
timeOutScript=2000;
remotePort=3001;
DEF1|gr1|85.17.183.199|29999|./default|default_1.ini|autowork

Hope that info is enough and that 1 screenshot

See you
-jsrk-

Okay,

Basically the issue is that you are trying to run Lapper clients connecting to multiple servers from the same directory etc. The way that Lapper works when setting up a new instance is that it will see if the directory exists and if not it makes a copy of the defaultfiles directory with the new name. Then you only need to change the server password in the .ini file.

Change the LFSServers.cfg to this:
(Change names to be more descriptive if you want to)

Run Lapper once and it should create the directories srv1,srv2,srv3 & srv4. Most likely it won't connect to all the servers as the passwords will be wrong, so kill Lapper, then edit the password entries in the default_1.ini files in each driectory to match the server passwords. Start Lapper again and see if it connects to the servers.