Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Due to spam on this forum, all posts now need moderator approval.

 Entire forum ➜ SMAUG ➜ Running the server ➜ SmaugFuss 1.8 Lua weird behavior.
SmaugFuss 1.8 Lua weird behavior.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Pages: 1 2  

Posted by Corey   (54 posts)  Bio
Date Thu 20 Dec 2007 08:19 PM (UTC)
Message
I noticed a wierd behavior with smaugfuss 1.8 lua today.
I messed up my IMC config so it couldn't connect to the server, and then noticed when this happens the mud will answer telnet with a blank screen and won't let anyone logon. any ideas?
Top
Posted by David Haley   USA  (3,881 posts)  Bio
Date Reply #1 on Thu 20 Dec 2007 10:19 PM (UTC)
Message
Chances are that if IMC fails to initialize correctly, something else doesn't get initialized correctly either -- and that something else is responsible for setting up the Lua states (or something like that). I'd look in the code for where IMC gets set up and see what happens when it fails. (Can't help more, am not at home at the moment and don't have a speedy connection to download the code.)
David Haley aka Ksilyan
Head Programmer,
Legends of the Darkstone

http://david.the-haleys.org
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #2 on Fri 21 Dec 2007 02:23 AM (UTC)
Message
I think if it "answers with a blank screen" it has accepted the connection but not triggered the "nanny" processing. From memory this can happen if it gets confused about the descriptor list. I would fix the IMC problem first if possible.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Corey   (54 posts)  Bio
Date Reply #3 on Sat 08 Mar 2008 07:40 PM (UTC)
Message
and 1.9 still has this problem.
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #4 on Sat 08 Mar 2008 08:25 PM (UTC)
Message
Is this Cygwin or Linux?

I would make version 1.9 into a new directory, and try there. That way you get the default IMC and other configurations. I haven't had any problems with 1.9 myself.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Corey   (54 posts)  Bio
Date Reply #5 on Sat 08 Mar 2008 11:22 PM (UTC)
Message
Cygwin on win32
copied all the new stuff over the old stuff.
still get it.
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #6 on Sat 08 Mar 2008 11:43 PM (UTC)
Message
That isn't exactly what I suggested. Make a totally new directory, unzip the SmaugFuss files into that, do a make, and then test. That way any strange files in the old installation won't affect you.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Corey   (54 posts)  Bio
Date Reply #7 on Sun 09 Mar 2008 04:45 AM (UTC)
Message
ok, did it. all new setup in new dir. still same problem.

Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #8 on Sun 09 Mar 2008 05:25 AM (UTC)
Message
Are you sure it is actually running? Like, when you connect does the Smaug log window show anything?
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Corey   (54 posts)  Bio
Date Reply #9 on Sun 09 Mar 2008 03:56 PM (UTC)
Message
shows nothing, like it's waiting for something.
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #10 on Sun 09 Mar 2008 08:50 PM (UTC)

Amended on Sun 09 Mar 2008 08:53 PM (UTC) by Nick Gammon

Message
Hmmm, I think we need to go back to basics here. After you compiled Smaug (by typing "make"), you should be able to run it by typing:


cd ../area
../src/smaug


1. Did you do that?



After doing that you should see a heap of messages, like this:


$ cd ../area
$ ../src/smaug
Mon Mar 10 07:41:47 2008 :: Booting Database
 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mon Mar 10 07:41:47 2008 :: [*****] BOOT: ---------------------[ Boot Log ]--------------------
Mon Mar 10 07:41:47 2008 :: Initializing libdl support...
Mon Mar 10 07:41:47 2008 :: Loading commands...
Mon Mar 10 07:41:48 2008 :: Loading spec_funs...
Mon Mar 10 07:41:48 2008 :: Loading sysdata configuration...
Mon Mar 10 07:41:48 2008 :: Loading socials
Mon Mar 10 07:41:48 2008 :: Loading skill table
Mon Mar 10 07:41:48 2008 :: Sorting skill table...

(more messages here)

Mon Mar 10 07:41:50 2008 :: Reading in area files...
(help.are)
limbo.are     : Rooms:     2 - 99    Objs:     2 - 99    Mobs:     1 - 99
gods.are      : Rooms:  1200 - 1201  Objs:  1200 - 1200  Mobs:  1200 - 1200
newacad.are   : Rooms: 10300 - 10499 Objs: 10300 - 10499 Mobs: 10300 - 10499
newgate.are   : Rooms:   100 - 199   Objs:   100 - 199   Mobs:   100 - 199
newdark.are   : Rooms: 21000 - 21499 Objs: 21000 - 21435 Mobs: 21000 - 21499
plains.are    : Rooms:   300 - 345   Objs:   300 - 313   Mobs:   300 - 350
haon.are      : Rooms:  6000 - 6156  Objs:  6000 - 6155  Mobs:  6000 - 6117
midennir.are  : Rooms:  3500 - 3590  Objs:  3500 - 3550  Mobs:  3500 - 3550
sewer.are     : Rooms:  7001 - 7445  Objs:  7190 - 7310  Mobs:  7000 - 7206
redferne.are  : Rooms:  7900 - 7918  Objs:  7909 - 7911  Mobs:  7900 - 7900
grove.are     : Rooms:  8901 - 8999  Objs:  8900 - 8919  Mobs:  8900 - 8911
dwarven.are   : Rooms:  6500 - 6554  Objs:  6502 - 6519  Mobs:  6500 - 6517
daycare.are   : Rooms:  6601 - 6651  Objs:  6600 - 6647  Mobs:  6600 - 6610
grave.are     : Rooms:  3600 - 3651  Objs:  3600 - 3613  Mobs:  3600 - 3605
chapel.are    : Rooms:  3405 - 3475  Objs:  3400 - 3430  Mobs:  3400 - 3416
astral.are    : Rooms:   800 - 899   Objs:   800 - 899   Mobs:   800 - 899
Build.are     : Rooms:  9500 - 9589  Objs:     0 - 0     Mobs:     0 - 0
pixie.are     : Rooms:  2070 - 2099  Objs:  2070 - 2077  Mobs:  2070 - 2073
export.are    : Rooms:  9810 - 9899  Objs:  9810 - 9899  Mobs:  9800 - 9899
srefuge.are   : Rooms:  1500 - 1599  Objs:  1500 - 1599  Mobs:  1500 - 1599
manor.are     : Rooms:  2400 - 2499  Objs:  2400 - 2499  Mobs:  2405 - 2484
unholy.are    : Rooms:  2101 - 2172  Objs:  2101 - 2150  Mobs:  2101 - 2120
gallery.are   : Rooms: 24800 - 24899 Objs: 24800 - 24899 Mobs: 24800 - 24899
Mon Mar 10 07:41:51 2008 :: Fixing exits
Mon Mar 10 07:41:51 2008 :: Initializing economy
Mon Mar 10 07:41:51 2008 :: Resetting areas

(more messages here)

Mon Mar 10 07:41:52 2008 :: Initializing socket
Mon Mar 10 07:42:03 2008 :: IMC: Loading IMC2 command table...
Mon Mar 10 07:42:03 2008 :: IMC: Loading IMC2 network data...
Mon Mar 10 07:42:03 2008 :: IMC: Loading IMC2 help file...
Mon Mar 10 07:42:03 2008 :: IMC: Loading IMC2 color table...
Mon Mar 10 07:42:03 2008 :: IMC: Loading IMC2 who template...
Mon Mar 10 07:42:03 2008 :: IMC: imcfread_word: EOF encountered on read.
Mon Mar 10 07:42:03 2008 :: IMC: IMC2 network data loaded. Autoconnect not set.
IMC2 will need to be connected manually.
Mon Mar 10 07:42:03 2008 :: (Name Not Set) ready on port 4000.


This tells you the MUD is ready to run and is awaiting connections on port 4000 (the last line).

2. Did you see this stuff?



If you saw those messages you should be able to connect to the MUD by connecting, on the same PC as the server is running to IP address "localhost", and the same port number as in the line above (4000 in my case).

3. Did you connect (using MUSHclient or telnet, or some other client) in this way?



In your client program you should then see on your screen the following:



         /     _      _            _      _    _____
        /      |\    /|     /\     |      |   /     \     ***************
       /       | \  / |    /  \    |      |  |            *   \._.//   *
      /        |  \/  |   /    \   |      |  |            *   (0...0)   *
     /_______  |      |  |______|  |      |  |            *    ).:.(    *
            /  |      |  |      |  |      |  |            *    {o o}    *
           /   |      |  |      |  |      |  |     __     *   / ' ' \   *
          /    |      |  |      |  |      |  |       |    *-'^.VxvxV.^'-*
         /     |      |  |      |   \____/    \_____/     ***************
        / 

SMAUG 1.8 FUSS changes by Samson. Other bugfixes and changes provided by
various members of the SMAUG community. Their contributions are greatly
appreciated.
SMAUG 1.4 written by Thoric (Derek Snider) with Altrag, Blodkai, Haus, Narn,
Scryn, Swordbearer, Tricops, Gorog, Rennard, Grishnakh, Fireblade and Nivek.
Original MERC 2.1 code by Hatchet, Furey, and Kahn.
Original DikuMUD code by:
Hans Staerfeldt, Katja Nyboe, Tom Madsen, Michael Seifert & Sebastian Hammer

Enter your character's name, or type new:


4. Did you see that?



In the server output window (the one I showed above) there should be 3 more lines, like this:


Mon Mar 10 07:46:19 2008 :: Preloading player data for: Admin (9K)
Mon Mar 10 07:46:20 2008 :: Loading player data for: Admin (9K)
Mon Mar 10 07:46:20 2008 :: Admin (127.0.0.1) has connected.


5. Did those lines appear?



Please answer all 5 of my questions.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #11 on Sun 09 Mar 2008 09:05 PM (UTC)

Amended on Sun 09 Mar 2008 09:08 PM (UTC) by Nick Gammon

Message
It might help to add a couple of lines to comm.c in the source - this shows when a connection is actually established.

In the file comm.c, around line 1005, inside function new_descriptor, look for the lines below and add the extra ones in bold:


   if( check_bad_desc( new_desc ) )
   {
      set_alarm( 0 );
      return;
   }
#if !defined(FNDELAY)
#define FNDELAY O_NDELAY
#endif

// ---> add new lines here

   printf ("Accepted connection from %s, port %d\n", inet_ntoa( sock.sin_addr ), ntohs( sock.sin_port ));
   fflush (stdout);



Once you have added that, type "make" to recompile, change back to the area directory and try again. This time, in the MUD server window, as soon as I connect I see this extra line:


Accepted connection from 127.0.0.1, port 1084


This shows that someone has connected, even before it attempts to display any messages to them.

If you do that, can you tell me whether or not you see the line "Accepted connection from 127.0.0.1" in your MUD window?
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Corey   (54 posts)  Bio
Date Reply #12 on Mon 10 Mar 2008 06:12 AM (UTC)
Message
ok, added your code and recompiled. no connection info.
here is as much of the log as the board will let me post:

Sun Mar 9 23:06:00 2008 :: Initializing socket
Sun Mar 9 23:06:01 2008 :: IMC: Loading IMC2 command table...
Sun Mar 9 23:06:01 2008 :: IMC: Loading IMC2 network data...
Sun Mar 9 23:06:01 2008 :: IMC: Loading IMC2 help file...
Sun Mar 9 23:06:01 2008 :: IMC: Loading IMC2 color table...
Sun Mar 9 23:06:01 2008 :: IMC: Loading IMC2 who template...
Sun Mar 9 23:06:01 2008 :: IMC: imcfread_word: EOF encountered on read.
Sun Mar 9 23:06:01 2008 :: IMC: IMC2 network data loaded.
Sun Mar 9 23:06:01 2008 :: IMC: IMC2 Network Initializing...
Sun Mar 9 23:06:01 2008 :: IMC: Connecting to server.
Sun Mar 9 23:06:01 2008 :: IMC: Loading channels...
Sun Mar 9 23:06:01 2008 :: IMC: configured Server01:ichat as ichat
Sun Mar 9 23:06:01 2008 :: IMC: configured Server01:pchat as pchat
Sun Mar 9 23:06:01 2008 :: IMC: configured Server01:ibuild as ibuild
Sun Mar 9 23:06:01 2008 :: IMC: configured Server02:icode as icode
Sun Mar 9 23:06:01 2008 :: IMC: configured Server02:igame as game
Sun Mar 9 23:06:01 2008 :: IMC: configured Server02:i3chat as i3
Sun Mar 9 23:06:01 2008 :: IMC: configured Server02:i2chat as i2
Sun Mar 9 23:06:01 2008 :: IMC: configured Server02:irc as irc
Sun Mar 9 23:06:01 2008 :: IMC: configured Server02:inews as inews
Sun Mar 9 23:06:01 2008 :: IMC: Loading ban list...
Sun Mar 9 23:06:01 2008 :: IMC: Loading ucache data...
Sun Mar 9 23:06:01 2008 :: MudPlace ready on port 4000.
Top
Posted by Corey   (54 posts)  Bio
Date Reply #13 on Mon 10 Mar 2008 06:15 AM (UTC)
Message
and here is the log tail when it connects to the IMC system:

Sun Mar 9 23:11:19 2008 :: MudPlace ready on port 4000.
Sun Mar 9 23:11:20 2008 :: IMC: SHA-256 Authentication completed.
Sun Mar 9 23:11:20 2008 :: IMC: Connected to Server01. Network ID: MudBytes
Accepted connection from 192.168.2.2, port 1345
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #14 on Tue 11 Mar 2008 12:15 AM (UTC)
Message
Judging by this stuff:


Sun Mar 9 23:06:01 2008 :: IMC: configured Server01:ichat as ichat
Sun Mar 9 23:06:01 2008 :: IMC: configured Server01:pchat as pchat


... you are not following my suggestion of running a "vanilla" installation.

You initially said "I messed up my IMC config so it couldn't connect to the server, and then noticed when this happens the mud will answer telnet with a blank screen and won't let anyone logon." - so my first approach would be to try a separate vanilla installation without any IMC config, and see if the problem goes away.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

49,182 views.

This is page 1, subject is 2 pages long: 1 2  [Next page]

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum

[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.

Home