LFS Dedicated Linux server [Archive]

windsurf

11th September 2005, 10:09

no, but it does run very well with wine, see here for a small howto http://www.powie.de/part/artikel.php?id=41

(but i'd like to see a native linux version too :)

Thank You for the help! It worked.
Only the howto had some small mistakes :-)
The path is not longer:
http://www.liveforspeed.net/file_rsc.php?name=LFS_S1H_DEDI.zip (http://www.liveforspeed.net/file_rsc.php?name=LFS_S1H_DEDI.zip)

But:
http://www.liveforspeed.net/file_lfs.php?name=LFS_S2_DEDI_P2.zip

and not:
# nohup wine LFS.exe /cfg=setup.cfg >/dev/null & echo $! > lfs.pid
but
# nohup wine LFS.exe /cfg=setup.cfg >/dev/null & echo $! >lfs.pid

But thnx anyway :-)
(I'm a noob on Linux, but i managed to set it up ...Weeeeee)
Thnx again for the help!

Windsurf

windsurf

14th September 2005, 08:32

Need some more help here :-)

I now have a server up running on the linux machine. But server does not report our racing results to the LFSworld server. Is there any ports on the router I have to forward/open to get the server to report to LFSworld??

I have open port 63392 for both UDP and TCP
Must both UDP and TCP be open??

the_angry_angel

14th September 2005, 13:25

You need to open the following:
29339 TCP
63392 TCP and UDP

Yes, both TCP and UDP need to be used on the final port. LFS uses UDP to transfer car position, as its quicker.

Sheepy1977

17th April 2006, 08:58

Dopez,ur link was failure.pls correct it .thx.

avellis

25th April 2006, 11:05

It seems there was a change in the host powie.de. I just managed to find the correct link, which is:

http://www.powie.de/cms/artikel/artikel.php?id=41

avellis

25th April 2006, 11:25

I find that according to:

http://www.winehq.com/site/docs/wineusr-guide/config-wine-main

there is no more '.wine/config' configuration file and the winecfg program needs to be used to configure things:

In the past, Wine used a special configuration file that could be found in ~/.wine/config. If you are still using a version of Wine that references this file (older than June, 2005) you should upgrade before doing anything else. All settings are now stored directly in the registry and accessed by Wine when it starts.

The bad thing for a dedicated linux host is that winecfg works only with a graphic user interface.

Now, I can think of two solutions:

1) Downgrade to an older wine version

2) Install wine to an identical machine with X-Windows enabled, and then copy over the registries files.

However, before I embark on actually doing all this exciting stuff (! :) ) I thought I would try and ask if anyone else can think of some other, cleaner workaround or solution for console-only wine.

Any ideas?

StuntCarRacer

26th April 2006, 01:22

Now, I can think of two solutions:

1) Downgrade to an older wine version
2) Install wine to an identical machine with X-Windows enabled, and then copy over the registries files.

3) Run it on Xvnc

dawesdust_12

26th April 2006, 02:45

I wish there was a LFS server liveCD/liveUSB (USB most wise because of CFG files and updated) where you could just go, pop the thing in, and have a linux server with wine and all no sweat.

avellis

26th April 2006, 08:58

3) Run it on Xvnc

Hmm yes, of course, or even X11. I just skipped this automagically, because of stupid router ACLs between the server and my desktop machine. (And the fact that I would have to restart my X to allow TCP connections :razz: )

Will try, though.

I wish there was a LFS server liveCD/liveUSB (USB most wise because of CFG files and updated) where you could just go, pop the thing in, and have a linux server with wine and all no sweat.

Nah, I would want the macine to do other stuff as well and not just LFS Dedi.

Since I have experience with Debian packages, I might try to put together a .deb or two that sets up some stuff right away. I don't make any promises, though. :)

spikee

10th June 2006, 13:07

I wish there was a LFS server liveCD/liveUSB (USB most wise because of CFG files and updated) where you could just go, pop the thing in, and have a linux server with wine and all no sweat.
hi dawesdust_12

I have built such a thingy...its called "cdedix" :D. Made it some months ago, so it still runs patch_Q, but would be no prob to update to newer versions. Also an installation to usb-stick is possible , but not needed because it can update changes to a webserver.

Its based on slax: http://www.slax.org and is modular, that means, a running system can load modules at runtime. I just created the needed modules for a dedi-server with LFSLapper support.

Unfortunately i encountered the same probs as some other linux-wine-dedi installations: after a while ppl cant see each other...but chat...only a restart of the dedi helps then :shrug: Solution in sight: regular restarts via cronjob, but not already included in the last version of "cdedix". I must downgrade to an older wine version, lets see if that works...

Newer versions will also support the racemanager, includes an insim-gateway, so other insim tools like the LFSLapper and the LFSSpectator can connect simultaneous :thumb:

email me, when u wanna test it: domagk45@gmail.com (domak45@gmail.com)

greetz from germany :D

eimer_

10th June 2006, 22:13

4) Forget about the config file and just use wineconsole instead of wine :nod:

spikee

11th June 2006, 10:34

4) Forget about the config file and just use wineconsole instead of wine :nod:
Great idea, i tried:

wineconsole --backend=curses LFS.exe /cfg=$CFG >/dev/null & echo $! > lfs.pid

in a script and it seems to work, thx for the tip :D

avellis

11th June 2006, 14:11

Thx all, I just had success with wineconsole and 'curses' backend.

Apparently, the other thing that I had to change to make it work was

/dedicated=invisible

in setup.cfg. /dedicated=nogfx would still complain about no X display being available.

avellis

11th June 2006, 16:43

Update -- I'm slowly finding out stuff. I ended up with a /tmp/wine.log.foo file with size of 4 GB, and the filesystem got full.

To avoid this, be sure to run wine with WINEDEBUG=-all.

for instance,

WINEDEBUG=-all wineconsole --backend=curses LFS.exe /cfg=setup.cfg >/dev/null & echo $! > lfs.pid

I haven't checked out powie.de's init scripts yet, to see if they take that into account. But for those of you who do this manually, be aware of the above thing.

eimer_

12th June 2006, 13:02

try the newest version of wine! u say u still have a setup.cfg file, what means your version is older than one year...

avellis

12th June 2006, 21:05

try the newest version of wine! u say u still have a setup.cfg file, what means your version is older than one year...

Sorry? setup.cfg is LFS' file, not wine's. Can you clarify?

I have wine 0.9.15 or something like that, whatever is in Debian unstable. ( http://www.winehq.org )

felplacerad

13th June 2006, 00:58

I'm running a lfs server on wine and i am experiencing some problems.

some users tend to fail to connect, or loose connection.

it has never happened to me nor any of the "regulars" though, for those it does happen, it is happening all the time ...

im not sure what information you need from me but, im running:

Wine 20050310
LFS_S2_DEDI_U
Linux version 2.6.10 (gcc version 2.95.4 20011002 (Debian prerelease)) #14

It struck me that the wine version was quite outdated, im now running

Wine 0.9.15

let's see if that helps.

avellis

22nd June 2006, 10:20

FYI, in my setup, wineconsole did not like 'nohup'. It seemed to need that tty open or something. And if I simply closed the remote shell session, it would start consuming 100% CPU and writing a big log file. Again. With WINEDEBUG=-all. :pillepall

My hack to make my dedicated server work was to use screen and then detach the terminal.

So my command line now is:

cd <LFS_Directory>
screen -S "$NAME" wineconsole --backend=curses LFS.exe /cfg=$CFG

where
NAME = a meaningful name to display in 'screen -ls', in case a lot of servers are used.
CFG = the config file

Then I do CTRL-A, D to detach from the terminal. (one can also use screen switches: -d -m - Start screen in "detached" mode. This creates a new session but doesn't attach to it. This is useful for system startup scripts.)

I've been running the two [noobs] servers, 'cow' and 'meow' :), successfully for two weeks now, using the above workaround. No problems at all!

the_angry_angel

22nd June 2006, 11:52

I find theres a major problem with screen; I have a bad habit of opening them for compiles, lynx, etc. and then forgetting they're open. 2 weeks later I wonder where all the RAM has gone :doh: Rarely will I say a tool is too useful for its own good, but in this case screen is ;) It should be made less useful!!!11oneoneone

To stay on topic, to "reactivate" a screen, you can also use the pid instead of the name, as mentioned above. man screen Should help you work it out, if you're not already familiar :D

the_angry_angel

26th June 2006, 08:26

As far as I'm aware, Scawen hasn't said no. Although he has said that his *ix programing experience is rather limited (or was at the time).

TDSyco

28th June 2006, 12:33

I asked for it about a Year ago.
Scaven (Or was it Eric?) told me that they have not enough time to release a Linux Dedicated Host in near future.
But he didnt negotiate it :smileypul

Nathan D.

9th August 2009, 10:32

I'm trying to run LFS on Linux using wine. This is the error I get:

Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:wineconsole:WINECON_Fatal Couldn't find a decent font, aborting

Also, I have the following line in my config file:
/dedicated=invisible

Lastly, the command I am running is:
wineconsole LFS.exe /cfg=setup.cfg

I am using the above command temporarily so I can see the error that the server gives me. Please advise.

avellis

9th August 2009, 10:51

I am using the above command temporarily so I can see the error that the server gives me. Please advise.

Actually if you are in a remote machine, you won't be able to see the error this way.

Most probably, what happens is that something is wrong with LFS's configuration file and it wants to open a window to display the error.

Perhaps the easiest way to solve this is to forward the X display to your machine so that you can see the error message that is shown. You can also try substituting "wineconsole" command with simply "wine".

I have suggested a solution (http://www.lfsforum.net/showthread.php?t=36314) for this, in the past.

Nathan D.

9th August 2009, 10:58

How can I forward the X display to my machine? And, I've tried wineconsole and just wine, both do the same. Also, I am doing everything through SSH to my remote box.

I am a novice when it comes to Linux so I just need a little further explaining.

avellis

9th August 2009, 11:09

How can I forward the X display to my machine?

Well, you could google about it for more information about setting $DISPLAY etc... But a quick way to enable it is to just initiate an ssh with ' -X ' switch and it should work immediately (the ssh client will try to do all the stuff automagically). ;-)

This is only to determine what errors LFS emits. After you're done resolving any errors with the configuration file, then there should be no need for all this X forwarding.

(Edit: I am assuming that the client machine you are on also runs Linux or similar. If you are on windows, you would obviously need a Windows X Server to see the display.)

Nathan D.

9th August 2009, 11:20

Yes, I am on a Windows client.

I downloaded Xming X Server and am using Putty as my SSH client. Not sure what to do from here though.

I noticed that when using "wine LFS.exe /cfg=server.cfg" to run the LFS server, I get a different error:
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

bunder9999

10th August 2009, 08:13

Nathan D.

14th August 2009, 08:15

i run my servers in NX... it satisfies the need for an X server, and allows me to disconnect from the "screen" if and when i need to. :shrug:

nathan, the error you're getting is either because your alsa is messed up, or because wine is looking for a midi that might or might not be there... if you have a choice of compiling wine, you can remove midi support.

Could you provide some assistance with this? How can we confirm that wine is looking for a midi, and once confirmed, how can I recompile wine?

By the way, my OS is CentOS 5.2 64bit if that helps.

Nathan D.

17th August 2009, 00:47

Bump. I really want to get a server going but I don't know much about Wine. Please someone help.

bunder9999

17th August 2009, 10:14

http://winehq.org

you're welcome.

xfirestorm

16th February 2011, 18:58

For future reference, if you can't find a package of wine that works without X11 for your distribution, you can re-compile wine with --without-opengl and --without-x options passed to ./configure

More detailed:
download tar.gz or tar.bz2 file from http://winehq.org

Unpack it with:
tar xvf wine-*.tar.gz (replace the file with the file you've downloaded)
cd into the dir that you have unpacked that tarball and run configure with above options:
./configure --without-opengl --without-x
When configure finishes run make with, yes simple:
make
When build finishes(go grab a beer or two):
run:
make install AS ROOT!!!!

misiek08

26th February 2011, 09:29

Why not apt-get/aptitude install wine ?
Then wine LFS.exe /cfg=setup.cfg and done.

xfirestorm

26th February 2011, 10:02

Why not apt-get/aptitude install wine ?
Then wine LFS.exe /cfg=setup.cfg and done.

Not everyone is using Ubuntu/Debian(thank god) and I don't even know if it will install under Ubuntu that way. X11 might come up as dep. packet. And if you don't want X11 on your server(which you probably don't if you have everything in place "up there") then your best shot is to either find a precompiled package of wine that has been compiled with above options or you compile if your self. Which I personally prefer.

MadCatX

26th February 2011, 10:38

"dpkg --force-depends wine.deb" will ignore dependencies, so you don't have to install X11, PulseAudio and some other stuff you don't need on a server to run LFS Dedi.

Compiling and installing apps directly from source is usually a bad practice if you run a distro with extensive package management (pretty much every distro except LFS). Possible file conflicts and inability to actually uninstall such software without the risk of breaking something is usually not worth it. Most distros offer tools to build a proper package from source anyway, so I don't see any reason why would anyone want to use the "configure, make, make install" way.

xfirestorm

26th February 2011, 12:03

Compiling is bad? :really:
If you compile software on your own machine it is better than download a compiled package. File conflicts? I've never had those and I've been compiling software from source since like, forever.

And again, dpkg. Another distro specific software. make is cross-distro, so it will work anywhere, as long as you have the right libs and compilers installed.

I do agree that "make install" files are harder to hunt down, but like you said, you can have the source compiled and packaged in a distro specific package and install that. I just didn't want to include it in the above "guide", because it would again be distro specific.
But if you want it, you can use src2pkg on slackware. Maybe even on some others, but I cba to try out other distros.

MadCatX

26th February 2011, 12:53

Compiling is bad? :really:

Of course not, it's the subsequent installation outside the packaging system that can set you hell bound. It doesn't have to if you're careful and set a different install prefix than / or /usr and use your brain while doing it;)

Don't make me wrong, I agree with you that "configure, make, make install" works anywhere, anytime on anything, I just thought I'd mention some of the risks this approach has.

xfirestorm

26th February 2011, 19:35

If the source software package was made by a moron or the software it self was written by a moron, who will use a common name for his own libs i.e., it would be risky yes. Because if he named his one of his libs "libglib.so", you'd have a problem if you installed this and overwrite the original lib.
But AFAIK, wine is not developed by morons and their lib names are quite different from other software, so there is no danger in manually compiling and installing wine. :)

If you are still afraid you'll overwrite something or that you'll have to spend much time hunting down files to delete should you decide to remove the software, you could pass "--preffix=/opt/mysoftware" to install it in that dir. You would then need to alter your $PATH or pass "--bindir=/usr/bin --sbindir=/usr/sbin" to have the binaries installed in a place that is already included in $PATH.

E.Reiljans

26th February 2011, 19:41

You would then need to alter your $PATH or pass "--bindir=/usr/bin --sbindir=/usr/sbin" to have the binaries installed in a place that is already included in $PATH.Linux has this wonderful thing called 'symlinks'. :p

xfirestorm

26th February 2011, 20:05

Orly nao? Haven't noticed those in the past 10 years working with Linux. :tilt:

Or yes, you could make symlinks into /usr/(s)bin

StuntCarRacer

27th February 2011, 02:16

When build finishes(go grab a beer or two):
run:
make install AS ROOT!!!!

You can run Wine directly from the source tree, no need to install, and no need for root access.

xfirestorm

2nd March 2011, 11:38

Well I've ran into a problem now.
LFS server has been running fine, has shown up on server list and people could connect to it.
Now I've recompiled the kernel to the newest stable, 2.6.37.2, and the server doesn't show up on lfsworld.net server list anymore. Why is that? Inspecting the connection list it is connected to LFS:
tcp 0 0 my-IP:29999 lfs-IP:61506 ESTABLISHED 23372/wineserver
tcp 0 0 my-IP:47387 lfs-IP:29339 ESTABLISHED 23372/wineserver

So firewall is not blocking. The darn thing just doesn't show up there. I'm guessing it doesn't show up in the game either, and no I can not test it out right now. But if anyone would be so kind, server name is "GT3 Racing", without quotes.

It also shows that airio does connect to the server, so have no clue what's going on.

yankman

2nd March 2011, 15:56

It might not have directly to do with recomplining the kernel,
but my experience is, that stopping/starting a host running via wine makes it not showing up in server list.
When I put a delay between stopping and starting however non such problem occures.

One other thing, if you like to have full control of your binaries (=compile them from source) and squeeze the last bit out of your hardware try gentoo (http://www.gentoo.org/) distribution.

MadCatX

2nd March 2011, 16:27

If it's any help, I'm able to connect to your server by typing its name directly in the Join Specific Server screen. However, I can't see on lfsworld nor in the game.

xfirestorm

3rd March 2011, 06:52

One other thing, if you like to have full control of your binaries (=compile them from source) and squeeze the last bit out of your hardware try gentoo (http://www.gentoo.org/) distribution.

<-- Slackware maniac. :nod: Thanks for the tip tho. :)

I know, stopping and starting right after makes it act...strange...mostly, the insim port doesn't get bound, but that's not the problem here, as it is listening on both ports.
I know it might not be kernel-recompile-related, but that is the last thing that I have done on the system, so I'm kinda, sorta out of ideas.
And inspecting the whole thing on my side, it seems to be working good, but I have no clue why is it not showing up there. I have even enabled logging everything from my firewall to see if anything LFS related gets blocked, but all passes through just fine.

Thanks MadCatX for trying it out.

yankman

3rd March 2011, 10:46

I wasn't talking about binding port tho.

It is like I said, if I stopped a host (via kill) and then started it with no delay,
it did not appear on lfsworld.

But shame on me I just tested it 2 times and now it appears even with no delay.

Little OT: If you really going in gentoo, I could give you same valueable tipps.

xfirestorm

3rd March 2011, 13:29

I'm not going on Gentoo. I use Slackware for ages. Gentoo doesn't offer anything special to me that it would be worth for me to change the distro. :)
I compile everything from code anyway, by hand or by using slackbuilds. :)

I know what you meant, and I've also tried shutting down the server(LFS ofc, not the whole machine) and leaving it like that for 30 minutes and starting again, with no effect.

MadCatX

3rd March 2011, 14:43

You could try starting the server on Windows to see if it appears on the master server then. If it does, you can launch it on your Linux server again. If anything, it might help you diagnose where the problem is. Also downgrading to 2.6.37.1 might be worth a try just to eliminate an improbable possibility of a glitch in the kernel.