Nonblocking Connect: Connection Refused with tinyfugue

Posted by Vacant on Sun 07 Jul 2002 12:02 AM — 5 posts, 19,178 views.

#0
Okay, okay so I run Slackware 8.1 =o)
This is just the best forum I have been to about PennMUSH. I have connected to my mush on localhost once before perfectly fine. Now I get the error:

Nonblocking Connect: Connection Refused

I don't run windows...I know this is the wrong place to ask, but I figured somone out there might have a solution. No firewall, ipchains, or anythinglike that. No special inetd.conf configuration. I do not see port 4996 open when i do an nmap though(if anyone knows what nmap is)
Thanks in advance
-Dan
Australia Forum Administrator #1
Are you connecting on the same PC again (ie. localhost?). If so, then probably the server is not up any more. Check the log file, and do a "ps" to check if the server is running. From memory it calls itself netmush, so you could do this:


ps -a | grep netmush

12547 p0 D+ 0:00.01 grep netmush (bash)
30401 C0- SN 18:42.15 ./netmush mush.cnf log/netmush.log (netmud)
#2
Alright I understanbd whats happening now...Its a DB issue. I removed my originial indb and cp minial to indb again and it wokrs fine...it crashes whenever someone tries to create a character though....then it refuses connection until I restore the old indb....any help?
#3
Okay, the MUSH runs fine and I can log in as One...however, it will not recognize any chnages I make...I can create all the rooms I want, and @pcreate all the players I want...I can change the name of One to Pancreator and set a new password and everything, but none of these changes /actually/ take place. They dont save even when I do a @dump...I really need help on this, if anyone knows what is wrong here. DB not saving? I dunno....Thanks in advance though...
-Dan
AIM name: clockscan
Australia Forum Administrator #4
It obviously isn't saving, you need to work out why. If I was in your shoes I would do this ...

  • Check you have write permissions to the data directory
  • Look inside log/game.log file to see if there were error messages after you typed @dump, and get some clues from that.
  • Have a look inside your mush.cnf file - possibly the compression you are using is not supported (ie. not installed). Here is the relevant bit ...
    
    # Database compression
    # When your databases are dumped, they can be dumped in a compressed
    # format to save disk space, or uncompressed for speed.
    # To use a compression program, you must know the name of the
    # program that compresses, the name of the program that uncompresses,
    # and the suffix that the compression program adds.
    #
    # Most people can just use one of the following:
    #
    # Use these 3 lines for no compression. Required on win32 and MacOS 7/8/9.
    #compress_program
    #uncompress_program
    #compress_suffix
    #
    # Use these 3 lines for gzip compression
    #compress_program gzip
    #uncompress_program gunzip
    #compress_suffix .gz
    #
    # Use these 3 lines for Unix compress compression
    #compress_program compress
    #uncompress_program uncompress
    #compress_suffix .Z
    #
    # Use these 3 lines for bzip2 compression
    #compress_program bzip2
    #uncompress_program bunzip2
    #compress_suffix .bz2
    #
    compress_program compress
    uncompress_program uncompress
    compress_suffix .Z
    


    For instance, if you are using bzip2 and bzip2 isn't installed, it won't be able to compress the database when it writes it, and thus it won't be saved.

    Try commenting out the 3 lines you currently have, and uncommenting one of the other ones, after checking that the one you choose is there. You can always use no compression (first example).