|
|
|||||||
I had to restore the lib to Feb 13th 2008 because of a crash of the driver. all those online at the time lost everything and had to restore. I am not sure why it crashed but will be looking into it. |
||||||||
|
|
|||||||
ok it was restored to the 12th of 2008. that was the last backup we had. the 13th was from another lib. that is why it was giving a locked up by admin message |
||||||||
|
|
|||||||
It looks like someone was doing combat right at 12:47:02 to 12:48:02 when the driver crashed. it was a hard crash, didn't even exit via the crash function that would do player saves and exits. ExperienceAward:Thu Feb 14 12:47:00 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:00 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:00 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:08 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:08 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:12 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:12 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:16 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:16 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:20 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:20 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:20 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:24 2008: /std/skills/inscribe_malsa_plasmar ExperienceAward:Thu Feb 14 12:47:24 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:24 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:24 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:28 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:28 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:32 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:32 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:33 2008: /std/skills/inscribe_xen_firas ExperienceAward:Thu Feb 14 12:47:36 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:36 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:40 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:44 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:48 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:48 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:52 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:47:52 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:52 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:47:53 2008: /std/skills/inscribe_xen_frosor ExperienceAward:Thu Feb 14 12:47:56 2008: /std/user myexp execute_attack() ExperienceAward:Thu Feb 14 12:48:00 2008: /std/user deal_critical() ExperienceAward:Thu Feb 14 12:48:00 2008: /std/user myexp execute_attack() driver/driver:Driver went down (exit code: 134): Thu Feb 14 12:48:02 PST 2008 |
||||||||
|
|
|||||||
Everyone noticed armour downgrade since Feb 12 backup restored. On laen it's about -25 protection. On iron, well, I am not sure, my guess is about -15. Would someone explain what's happened, please? Regards, -Guinness |
||||||||
|
|
|||||||
As far as I can tell, the weapons and armour bugs were caused because a directory was deleted or not restored when we reloaded from a backup. I've copied the directory and its information from test, and as far as I can tell it's fixed now. Still working to reproduce the crash, which I assume came as a result of the drinking object changes. All the bugs that were logged as a result of the change were expected, and I've been able to reproduce them on test without any crashes. I'll keep you posted. |
||||||||
|
|
|||||||
In case I hadn't announced it before hand... The Valentine's Day (Mud) Massacre happened as a result of me failing to copy over the changes to corpses that are now on live (special descriptions, decay rate display, etc). It's been resolved and I am now aware of where looping failures are logged, so this type of incident is unlikely to happen again. My full apologies to all who were inconvenienced. |