Author Topic: Trouble running/compiling  (Read 8323 times)

Offline syphon

  • Acquaintance
  • *
  • Posts: 0
    • View Profile
Trouble running/compiling
« Reply #15 on: November 16, 2006, 10:03:00 PM »

I can telnet in but when I ./startmud it keeps repeating this

socket_connect: requested on: 149.152.218.102 23

socket_connect: socket already bound to address/port: 24.0.0.0/0

socket_connect: requested on: 149.152.218.102 23

socket_connect: socket already bound to address/port: 24.0.0.0/0



when I run ./startmud I get this



DeadSoulsNew (MudOS v22.2b14) starting up on Linux - Thu Nov 16 23:54:19 2006





Connection to address server (localhost 9999) refused.



Loading preloaded files ...

]Preloading: /lib/sentient...](0.0)

]Preloading: /lib/std/table...](0.0)

]Preloading: /lib/std/room...](0.0)

]Preloading: /daemon/soul...](0.0)

]Preloading: /lib/player...](0.0)

]Preloading: /secure/daemon/localpost...](0.0)

]Preloading: /secure/daemon/letters...](0.0)

]Preloading: /secure/daemon/folders...](0.0)

]Preloading: /secure/daemon/events...](0.0)

]Preloading: /daemon/seasons...](0.0)

]Preloading: /daemon/intermud...](0.0)

]Preloading: /secure/daemon/economy...](0.0)

]Preloading: /secure/daemon/chat...](0.0)

]Preloading: /daemon/verbs...](0.0)

]Preloading: /daemon/command...](0.0)

]Preloading: /daemon/preload_check...](0.0)

]Preloading: /daemon/decay...](0.0)

]Preloading: /daemon/reaper...](0.0)

]Preloading: /secure/daemon/ping...](0.0)

]Preloading: /secure/daemon/update...](0.0)

]Preloading: /secure/room/arch...](0.0)

]Preloading: /secure/daemon/snoop...](0.0)

]Preloading: /secure/daemon/log...](0.0)

Initializations complete.



Accepting connections on port 5000.

socket_connect: socket already bound to address/port: 24.0.0.0/0

socket_connect: requested on: 149.152.218.102 23





[1]+ Stopped ./startmud



Then When I point addr_server to 9999 and ./startmud I get this



DeadSoulsNew (MudOS v22.2b14) starting up on Linux - Fri Nov 17 00:02:07 2006





Connected to address server on localhost port 9999



Loading preloaded files ...

]Preloading: /lib/sentient...](0.0)

]Preloading: /lib/std/table...](0.0)

]Preloading: /lib/std/room...](0.0)

]Preloading: /daemon/soul...](0.0)

]Preloading: /lib/player...](0.0)

]Preloading: /secure/daemon/localpost...](0.0)

]Preloading: /secure/daemon/letters...](0.0)

]Preloading: /secure/daemon/folders...](0.0)

]Preloading: /secure/daemon/events...](0.0)

]Preloading: /daemon/seasons...](0.0)

]Preloading: /daemon/intermud...](0.0)

]Preloading: /secure/daemon/economy...](0.0)

]Preloading: /secure/daemon/chat...](0.0)

]Preloading: /daemon/verbs...](0.0)

]Preloading: /daemon/command...](0.0)

]Preloading: /daemon/preload_check...](0.0)

]Preloading: /daemon/decay...](0.0)

]Preloading: /daemon/reaper...](0.0)

]Preloading: /secure/daemon/ping...](0.0)

]Preloading: /secure/daemon/update...](0.0)

]Preloading: /secure/room/arch...](0.0)

]Preloading: /secure/daemon/snoop...](0.0)

]Preloading: /secure/daemon/log...](0.0)

Initializations complete.



Accepting connections on port 5555.

socket_connect: socket already bound to address/port: 24.0.0.0/0

socket_connect: requested on: 149.152.218.102 23





[2]+ Stopped ./startmud



When I telnet in all I get is





snoop@presidium:~/ds/ds2.1.1/bin$ telnet presidium.org 5555

Trying 199.232.228.66...

Connected to presidium.org.

Escape character is '^]'.



-Syphon


-Syphon

Offline cratylus

  • Your favorite and best
  • Administrator
  • ***
  • Posts: 1020
  • Cratylus@Dead Souls <ds> np
    • View Profile
    • About Cratylus
Trouble running/compiling
« Reply #16 on: November 16, 2006, 10:09:20 PM »

Looks like you're running multiple instances of the mud.

Probablt a problem with the startmud script.



Type: killall -9 startmud

Then: killall -9 driver

Then: cd /wherever/the/mud/is/bin/

Then: nohup ./driver ./mudos.cfg 1>/dev/null 2>/dev/null &



This should start a backgrounded single instance of the mud, with

no pesky messages.



You won't see any output.



Just telnet to the port you specified in mudos.cfg.





Also: Please post your mudos.cfg and startmud scripts. It's

hard to troubleshoot scripting problems without seeing the scripts.



Also: never mind the address server for now. Just concentrate

on the external_port_1 line and make sure it has the mud

port you want to be able to connect on.


Offline syphon

  • Acquaintance
  • *
  • Posts: 0
    • View Profile
Trouble running/compiling
« Reply #17 on: November 16, 2006, 10:17:43 PM »

Thank you very much, Good thing I didn't waste all that time reading abouting coding LPmuds. It's good to know there are people out there that are willing to help others out.



I can login and everything but when I logout from my shell account It shutsdown.



What did you mean by 1>/dev/null 2>/dev/null & ? Those directories don't exisit.



This is startmud

#!/bin/sh



# Specify your mud dir here.

MUDHOME=""



# It has been reported that non-US users have problems

# with some .o files because their systems default to

# commas for decimal notation and not periods. The

# following language exports are for the benefit of

# people who run into this problem.



LANG=en_US

LANGUAGE=en_US

LC_ALL=en_US

export LANG LANGUAGE LC_ALL MUDHOME



umask 007



ulimit -n 120

while [ true ]; do



   if [ $MUDHOME ] && [ -f $MUDHOME/bin/driver ]  && [ -f $MUDHOME/bin/mudos$

        then

        $MUDHOME/bin/driver $MUDHOME/bin/mudos.cfg

        else

        if [ -f ./driver ]  && [ -f ./mudos.cfg ]

            then

            ./driver ./mudos.cfg

            else

            break

        fi

    fi



done





And here is mudos.cfg



# port number to accept users on

external_port_1 : telnet 5555



# the address server is an external program that lets the mud translate

# internet names to numbers (and vice versa).  select an unused port.

address server ip : localhost

address server port : 9999



# absolute pathname of mudlib

mudlib directory : /home/snoop/ds/ds2.1.1/lib



# absolute pathname of driver/config dir

binary directory : /home/snoop/ds/ds2.1.1/bin



# debug.log and author/domain stats are stored here

log directory : /log



# the directories which are searched by #include <...>

# for multiple dirs, separate each path with a ':'

-Syphon

Offline saquivor

  • BFF
  • ***
  • Posts: 110
    • View Profile
Trouble running/compiling
« Reply #18 on: November 16, 2006, 11:59:42 PM »
The startmud script should have



This is startmud

#!/bin/sh



# Specify your mud dir here.

MUDHOME="/home/snoop/ds/ds2.1.1/"

Offline syphon

  • Acquaintance
  • *
  • Posts: 0
    • View Profile
Trouble running/compiling
« Reply #19 on: November 17, 2006, 12:06:33 AM »
Even When I do that I get the same problems, So far Ive got it down to connect to the mud, but once I leave the shell account It goes down, This is begin to upset me, I spent alot of time reading on coding LPmuds. Im about to just try to find somebody to login and find out whats wrong.
-Syphon

Offline saquivor

  • BFF
  • ***
  • Posts: 110
    • View Profile
Trouble running/compiling
« Reply #20 on: November 17, 2006, 12:33:03 AM »

are you running ./startmud & to make it a background process ?



have you possible corrupted your startmud file ? If you have a backup copy of the orginal file, perhaps try and it up again from scratch.



I have compiled mudsos/ds2 on several versions of linux and not come accross that issue yet, so stick in there. I learned a lot from early mistakes/hackings of the various mudos/ds2 files :)



Given some of the problems you have had so far, you may consider re extracting source code, recompile and setup the mud again, to see if the problem repeats itself?



Saquivor


Offline syphon

  • Acquaintance
  • *
  • Posts: 0
    • View Profile
Trouble running/compiling
« Reply #21 on: November 17, 2006, 12:42:44 AM »

Im sorry I feel like an idiot, I was forgeting the &. I didn't get the server port to accept though, but the mud is staying up on presidium.org 5555.

When I type "addr_server 9999" That freezez at listening for open port, and I have to ctrl-z to get out, but then the port will accept.


-Syphon

Offline saquivor

  • BFF
  • ***
  • Posts: 110
    • View Profile
Trouble running/compiling
« Reply #22 on: November 17, 2006, 12:57:34 AM »
The address server issue is probably a red herring for you, it performs DNS lookups for commands such as mudlist (as far as I know) ignore the error messages it shows for now.



As long as you can access the mud via the telnet port you set then you have got the mud up and running so congrats.



There is no need to feel foolish, just hope you managed to get up and running :)



Saquivor



PS checked out your domain, I am also a cocker spaniel fan see http://lpmuds.net/forum/index.php?webtag=LPC&msg=82.2">here

Offline detah

  • BFF
  • ***
  • Posts: 190
  • Ruler of 2D
    • View Profile
Trouble running/compiling
« Reply #23 on: November 17, 2006, 05:44:20 AM »

I dont think this has anything to do with your current issue, but....

Your post #14 is timestamped 1:04 (and edited at 0:11).

your post #15 is timestamped 0:50.

Then your post #16 is timestamped 1:03.



I find the whole thing very suspcious. Have you been fiddling with the time on your computer or perhaps altered the time adjustment here at LPMuds multiple times?


Offline Aransus

  • Acquaintance
  • *
  • Posts: 2
    • View Profile
Trouble running/compiling
« Reply #24 on: November 17, 2006, 10:04:14 AM »

You probably know this already, but it's worth throwing in just in case...



If you forget the '&' and have to ctrl-z to get back to a command prompt, you can use the 'jobs' command to see which jobs are running and which are stopped. Then if you see:



[1]+  Stopped                 ./addr_server 9999



You can type 'bg %1' to toss the process into the background, which does what the forgotten '&' would have done. If you want to kill it instead, you could 'fg %1' and then ctrl-c, or just 'kill -9 %1'.



Sometimes it's easier to work with job ID's, since there's less of a risk of killing something you don't want to kill. In any case, hope you're up and running well now :).


Offline cratylus

  • Your favorite and best
  • Administrator
  • ***
  • Posts: 1020
  • Cratylus@Dead Souls <ds> np
    • View Profile
    • About Cratylus
Trouble running/compiling
« Reply #25 on: November 21, 2006, 08:58:52 PM »

For those curious about the resolution to this, the problem

seems to have been the mud host killing the mud process because

the user isn't logged in.



nohup apparently wasn't enough to solve the problem, so

Syphon is now using "screen" to run the mud in a virtual

console. This seems to have worked, and the looping

mud restarts have gone away.





EDIT:

Also, the previous problem was that he was missing some

standard unix libraries when trying to compile. Presumably

he took care of that issue with help from elsewhere.