I think everyone gets those CAsyncIOManager errors which appear to be as harmless ass that S_API_FAIL, continuing with current anyway thing on server consoles. I guess it was just a borked hlds client update for servers that introduced something new which they did not tell us.
-ics 4.6.2010 23:56, David A. Parker kirjoitti: > Hello everyone, > > I went to download the latest L4D2 update, and the steam binary behaved > strangely. I shut down the server, and then I ran a normal update > command from the srcds directory: > > $ ./steam -command "update" -game "left4dead2" -dir . -verify_all > Checking bootstrapper version ... > Getting version 36 of Steam HLDS Update Tool > > ... And it just sat there for several minutes. So I killed it and tried > the good old "delete ClientRegistry.blob" trick, and then I got some odd > results: > > $ rm ~/.steam/ClientRegistry.blob > $ ./steam -command "update" -game "left4dead2" -dir . -verify_all > Checking bootstrapper version ... > removing stale semaphore last operated on by process 6540 with name > 0eBlobRegistryMutex_9B5FB06AEFB0559E72F8B8DB387A9278 > removing stale semaphore last operated on by process 6540 with name > 0eBlobRegistrySignal_9B5FB06AEFB0559E72F8B8DB387A9278 > Getting version 36 of Steam HLDS Update Tool > Downloading. . . . . . . . . . . .Steam Linux Client updated, please > retry the command > CAsyncIOManager: 0 threads terminating. 0 reads, 0 writes, 0 deferrals. > CAsyncIOManager: 19 single object sleeps, 0 multi object sleeps > CAsyncIOManager: 0 single object alertable sleeps, 0 multi object > alertable sleeps > > ... And then it returned. So I tried the update again, and got even > more odd output: > > $ ./steam -command "update" -game "left4dead2" -dir . -verify_all > Checking bootstrapper version ... > Updating Installation > Updating 'left 4 dead 2 common' from version 30 to version 31 > > 1.22% downloading ./left4dead2/bin/gameui.dll > 5.79% downloading ./left4dead2/left4dead2/bin/server.dll > 5.80% downloading ./left4dead2/left4dead2/modelsounds.cache > 5.80% downloading ./left4dead2/left4dead2/steam.inf > 5.80% downloading ./left4dead2/left4dead2_dlc1/pak01_004.vpk > 5.87% downloading ./left4dead2/left4dead2_dlc1/pak01_dir.vpk > 5.87% downloading ./left4dead2/update/pak01_013.vpk > 6.10% downloading ./left4dead2/update/pak01_014.vpk > 6.21% downloading ./left4dead2/update/pak01_dir.vpk > > Updating 'left 4 dead 2 linux dedicated server' from version 24 to > version 25 > > 12.42% downloading ./left4dead2/left4dead2/bin/server.so > > Checking/Installing 'Left 4 Dead 2 Add-on Support' version 6 > > > HLDS installation up to date > CAsyncIOManager: 0 threads terminating. 0 reads, 0 writes, 0 deferrals. > CAsyncIOManager: 90 single object sleeps, 0 multi object sleeps > CAsyncIOManager: 0 single object alertable sleeps, 0 multi object > alertable sleeps > > ... I have no idea where those CAsyncIOManager messages are coming from > or why I'm seeing them, and I have no idea why the update got to 12.42% > and then said it was finished. A second update said that the server was > up-to-date. Does anyone know what these messages mean, or why they are > showing up? They look pretty harmless but I've never seen them before. > Also, did everyone else only get to 12% in the update? > > Thanks, > Dave > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
