>citserver is not crashing, but it loses or forgets its port number, (I noted >that you had this same thing happen, but I can reproduce it almost every time >citserver is restarted) and it does not remember the setting about not
>denying self service registration. I have rooms which are unable to be >deleted and messages showing up in the wrong rooms ( saying they are being >delivered to a user) It's weird, I really really did fix that port 504 issue. It was happening on my own system every single time, and it doesn't happen anymore. I agree that whatever is going on with your system, has something to do with the configuration being migrated to the new format. Hmm ... check this please. Let me know if the "citadel.config" and/or "citadel.control" files still exist. Those are supposed to get deleted after they're converted, and if they're not, it will import your old configuration every single time you restart the server. Worse, if the control record keeps getting imported, it'll start re-using message/room/user sequence numbers, which would explain messages appearing in the wrong rooms. Also look for the message "Existing database version on disk is" in your syslog; that's the telltale sign that it's trying to upgrade from an old data format on disk; obviously it shouldn't be doing that on every server run, only on the first run after you've upgraded. Now that I'm looking at the code, though, it seems I did put a lot of safety checks in there, to make the server exit if it can't delete the old-format configuration, or if it finds both old and new format configurations on disk. So maybe that's not it. Still seems like a permission problem of some sort, like it can't write the new config to disk or something.,
