Pol095 shard.
If I take a backup of the shard running in d:\pol and transfer it to another PC into c:\pol, I get a strange problem.

(servers.cfg and pol.cfg adjusted)

To save ftp time I removed the bak files from the data directory before transferring.

The new shard runs, and even does a world save after 2 hours successfully. Not sure if there are bak and txt files, the log just says a wordsave is successful - implies bak and txt files are there.

After another 2 hours elapses it tries to save but fails. It has even done an exception and crashed at this point but not always.
It writes out the ndt files just fine but seems unable to either delete or rename the bak or txt files.

Even when I delete all files except txt files it won't save so I have no choice but to stop the shard and manually rename and delete the savegame files.

I've done this twice.


Anybody know of a problem transferring a shard from d:\pol to c:\pol?

I haven't ruled out virus scanners or internal firewalls etc, but this is just strange.

Any thoughts?
OldnGrey.

Does the shard run on Linux or Windows?
If you use Linux, there may be permission-problems:
Try to start your pol-server as "root" for testing.

If you use Windows, I have no idear.

c:\pol

I guess he is on windows... there's no c:, d:, e: on linux...

maybe no space on hdd ?:)

Did you drag and drop the files with Windows XP?

If so it might have set permissions on the files as read only or something. That would cause the save errors you are seeing.

No, it was done by ftp to the new server.
* Diskspace not an issue.
* Can't verify what permissions were before the error, but they are fine now and it's happily saving games now like clockwork.

Unless you have migrated a live shard from one place to another you might not ever see this error.

I guess it's not repeatable.
I tried it again and it ran flawlessly.
/me hopes it never happens again

I have migrated a shard between 2 or 3 different machines before. Each time the shard was taken down and after the move I had to reset the file permissions on the new machine to get things working just right again.