This has spanned multiple messages now for me, so I apologize if this has
already been suggested, but try to run an update on the server with
-verify_all. It's completely possible that in the time since you last ran
it a file has been corrupted on your drive. The -verify_all should root out
the problem if it's within the file structure.
-Richard Eid
On Thu, Feb 5, 2009 at 5:13 PM, <t...@cybergate02.com> wrote:
> Deleting the blob, then restarting the update did not change anything...
> I am sure I never ran the ship ded server since last update (october).
> I deleted everything about the ship yesterday then reinstall it.
> i don't understand why all other servers runs well.
> It seems to be a master server issue.
>
> >Try deleting or renaming clientregistry.blob from .steam. I've had to
> >remove that when my updates got hosed. That causes the steam app to
> >recreate it and then updates started running. I know this isn't an
> >update issue, but perhaps it will fix master server look up.
> >
> >Sent from my iPhone
> >
> >On Feb 5, 2009, at 9:38 AM, tech at cybergate02.com wrote:
> >
> >> Yes, I tried.
> >> I reboot the machine and tried to start it with default port 27015.
> >> It was the only thing that ran on the machine. Same issue...
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
