[PennMUSH] Blasting my MUSH back to the stone age?

Jeff Ferrell jmferrell at mac.com
Thu Jul 24 07:00:32 PDT 2008


I *don't* know the max dbref, and that's the problem here, I think --  
I've got no way to find it out, at this point. I *do* know that the  
file I have here goes to !7963, and it seems to be expecting an end  
after object 7961.

Just for fun, I deleted objects !7963 and !7962 from the database file  
(what's a couple more objects lost, at this point?), but I still get a  
"No end of dump after object #7961" error on startup.

I'm wondering about this +V536865794 at the beginning of the file --  
is that some sort of checksum, or something? If so, can it be decoded/ 
adjusted?

Jeff.


On Jul 24, 2008, at 9:46 AM, Nick Burtner wrote:

> From the looks of it, there's a corrupted object in there.  Do you  
> know the max dbref of your game?  If this is a bad one, its not a  
> hard task to modify the DB by hand (well, it wasn't a few years  
> ago.  I've been out of the Penn loop for a little while) and remove  
> the offending object.  After that, it should startup fine.
>
> On Thu, Jul 24, 2008 at 7:39 AM, Jeff Ferrell <jmferrell at mac.com>  
> wrote:
> Hi, again!
>
> Please disregard everything from the previous exchange. I did
> something *very, VERY* stupid and catastrophic to my system, that is
> far too embarrassing to admit, and totally screwed up the startup
> execution. (Ok, I'll admit it, for anyone puzzling over the log in my
> last message: In a fit of total ignorance, I had *replaced* /bin/sh
> WITH my python script. How's that for stupid, huh?) This morning I
> woke up, and had the answer. So that's fixed -- the MUSH starts to
> start up properly.
>
> I've got a different problem, though... I've got a database from a
> couple of months back, at least, but it was kicking out some small
> errors on startup; just some little glitches. I've gone in and cleaned
> all those out, I think, and now my log is showing this:
>
> ERROR: No end of dump after object #7961
>
> The database file is showing !7963 and then ***END OF DUMP***
>
> I'm assuming the database "knows" when it should expect an end? Is
> there a way I can doctor it to include the last two objects in the
> count, or is there something more serious going on here?
>
> Thanks for all your input so far!
> Jeff.
>
> _______________________________________________
> PennMUSH mailing list
> PennMUSH at pennmush.org
> http://www.pennmush.org/mailman/listinfo/pennmush
> PennMUSH FAQ-o-matic! http://www.pennmush.org/cgi-penn/fom
>



More information about the PennMUSH mailing list