Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, Google, Majestic-12, Yandex

Members: 0
Guests: 4
Stats
Files
Topics
Posts
Members
Newest Member
481
3,734
19,366
618
Micheal64X
Today's Birthdays
Vintar (28)
Related Links
» SmaugMuds.org » General » General Discussions » "Failed" reboot?
Forum Rules | Mark all | Recent Posts

"Failed" reboot?
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Dec 18, 2005, 9:39 am
Go to the top of the page
Go to the bottom of the page

Zeno
Sorcerer
GroupMembers
Posts723
JoinedMar 5, 2005

Well this is odd. I've never seen the MUD not reboot.
It is 11 o'clock am.
Today is Wednesday the 17th of October.

The mud started up at:    Sat Dec 17 12:32:02 2005
The system time (PST):    Sun Dec 18 09:26:28 2005
Next Reboot is set for:   Sun Dec 18 06:00:00 2005
The MUD has been up:      20 hours, 54 minutes, 26 seconds.


It past the reboot time.
Syntax: setboot time {hour minute <day> <month> <year>}
        setboot manual {0/1}
        setboot default
Boot time is currently set to Sun Dec 18 06:00:00 2005
, manual bit is set to 0

And it's not manual... Any idea why it wouldn't have rebooted?
       
Post is unread #2 Dec 18, 2005, 1:19 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

You didn't happen to crash or something near the expected boot time did you? Keep an eye on it and see if it fails again at 06:00 on the 19th. I have no idea what elese might cause it except the code thinking it's too soon to reboot again.

Of course, I no longer have the autoboot code in AFKMud because the main reason for it ever being included was to deal with Smaug's numerous stock memory leaks and I don't have enough of those anymore to matter :)
       
Post is unread #3 Dec 18, 2005, 1:32 pm
Go to the top of the page
Go to the bottom of the page

Remcon
Geomancer
GroupAdministrators
Posts1,873
JoinedJul 26, 2005

Heh, I normaly always drop the autoboot's to like 1 a month or so, taking it out works too though.
       
Post is unread #4 Dec 18, 2005, 2:20 pm   Last edited Dec 18, 2005, 4:00 pm by Zeno
Go to the top of the page
Go to the bottom of the page

Zeno
Sorcerer
GroupMembers
Posts723
JoinedMar 5, 2005

Samson said:

You didn't happen to crash or something near the expected boot time did you? Keep an eye on it and see if it fails again at 06:00 on the 19th. I have no idea what elese might cause it except the code thinking it's too soon to reboot again.


Nope, like it says it's been up for 20 hours.

*shrug* I really haven't seen this happen before.
       
Post is unread #5 Dec 18, 2005, 2:37 pm
Go to the top of the page
Go to the bottom of the page

Remcon
Geomancer
GroupAdministrators
Posts1,873
JoinedJul 26, 2005

try setting the boot time for like 5 mins or something and see if it keeps failing through manual/non manual settings if it keeps failing id have to go with your missing a part that actually makes it do the reboot somewhere
       
Post is unread #6 Dec 21, 2005, 4:50 pm
Go to the top of the page
Go to the bottom of the page

Keberus
Conjurer
GroupFUSS Project Team
Posts341
JoinedJun 4, 2005

This may seem really simple, but its just a thought. Maybe you had done a clean make or something that deleted the bin/executable file ....so if it would have tried I think the code would have stopped it. Similar to doing a make clean in the code and trying to copyover/hotboot, it won't let you.

Later,
KeB
       
Pages:<< prev 1 next >>