View Full Version : Trouble figuring out the path for SSH logfile windows server
UnDead
01-12-2004, 01:03 AM
Hey,
I am currently trying to get to my log file with ServerWatch. Its for call of duty... The windows path is C:\program files\cod3\data\main\games_mp3.log. Getting this error in SSH DEBUG
[1/11/2004 11:58:13 PM] Child process could not be created: The system cannot find the file specified.
I have tried
tail -f /program files/cod3/data/main/games_mp3.log
tail -f \program files\cod3\data\main\games_mp3.log
I am getting debug error saying could not find file specified? Is there an easy way to find the path. I am remoting into our server which is located out of state. I have full admin rights to our windows 2k CoD server. Any ideas? help appreciated.
On our CoD server we are running winSSHD and I left the intial path blank in WinSSHD.
UnDead
ShadowBee
01-13-2004, 03:20 AM
tail -f /program files/cod3/data/main/games_mp3.log isn't correct.
tail -f is linux specific.
and if you were using linux ssh server then your file path would either have to be:
tail -f Program/Files\cod3\data\main\games_mp3.logNote: Case sensitive and "/" is a place holder for the space between Program and Files.
or
tail -f "Program Files/cod3/data/games_mp3.log"
For windows you'll need to check and see what the root access directory of your ssh program is set to. This may be a root directory for either the program or a user account. Either way you'll need to find out what that is and then adjust the file path from there.
Example:
You posted that your file is located in
C:\program files\cod3\data\main\games_mp3.log
If the root SSH directory is C:\ then your file path should be \program files\cod3\data\main\games_mp3.log
Hopefully this helps. I may be wrong since I haven't messed with SSH too much but that should be right. Please let me know if this helped you solve your problem. I'll have to investigate this issue further and adjust my setup guide.[/code]
UnDead
01-13-2004, 01:01 PM
Thanks ShadowBee,
It did help I am getting closer to getting this to work... Now I am getting this error in the SSH DEBUG LOG.
[1/13/2004 12:00:46 PM] Child process could not be created: The process cannot access the file because it is being used by another process.
[1/13/2004 12:01:26 PM] Child process could not be created: The process cannot access the file because it is being used by another process.
So it sees the files now but cannot use it because it thinks its in use. This is what haunted me with FTP access. I am looking for settings on the windows SSH server software, any ideas on this one?
Thanks for any help.
ShadowBee
01-13-2004, 02:15 PM
I'm not sure on that one. Still sounds like its trying to edit the file rather than just open it. Also. Why are you using games_mp3.log rather than just games_mp.log. That may have something to do with it. By default CoD writes to the games_mp.log file automatically anytime there is an event on the server.
UnDead
01-13-2004, 05:32 PM
Thanks again for your reply....
Yeah, we have it named that way because we have 3 CoD servers. We have the config file setup to log the info correctly into the games_mp3.log file for this server and I have tested that to make sure it was updating and it was. BTW we have 3 seperate CoD folders, a seperate folder for each gametype server we run. And we have a BAT file that runs and graps the individual logs and then compiles stats every morning around 5am. So as far as the logfile itself its working like its supposed to and it seems SW is asking windows 2k to do something and win 2k is stupid and doesn't understand :)
So I guess the question is now, is there a way to get windows 2k to allow reading the logfile via command line or Putty and not trying to cut the file or open it with notepad or whatever its trying to do?
Hmm... Maybe if I remove the association of .log from using notepad then windows 2k will allow Putty to open it? I will try that tonight.
ShadowBee
01-13-2004, 09:23 PM
yeah the next thing i was gonna ask is for you to check the file sharing permisions. And check the options on the ssh software.
Also. Heres a question for either Cobra or Enforcer or both.
Does ServerWatch support SSH2 or just SSH1 or both?
SSH2 being the latest of course.
If SW doesn't support SSH2 then your WinSSHD server may be incompatible. But it sounds like its working so far so I'm guessing that SW does support SSH2.
Anyhow you're just gonna have to tweak your settings to find something that works. Sounds like you are almost there. Just the same issue with the file itself. In which case if you solved that issue you would probabaly be able to use either SSH or FTP.
imported_Enforcer
01-13-2004, 10:10 PM
Here we go. For the ssh connection it use the plink.exe in the data dir.
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
That support ssh2 for sure but if you have problems a update should help.
UnDead
01-15-2004, 03:30 AM
Thanks for the link enforcer. New Plink works fine too, just still getting same thing and error message as last post.
I am pretty sure now though the problem is with windows 2000 locking down the file and not letting other programs have access to it... Could it be "Opportunistic Locking" that is causing this problem?
Here’s the Easy explanation for Opportunistic Locking:
Workstation #1 opens the database and receives exclusive locks on the files from the server.
When workstation #2 opens the same database, it asks for and receives a release of workstation 1’s exclusive lock on the server.
In the meantime workstation #1, assuming it still has the exclusive lock, tries to write to the file. Everything gets totally confused and the ACT! database index files are corrupted.
In other words, Opportunistic Locking is a big bully that needs to be shut down so that it will stop making life so difficult for everyone.
More info here as well.
http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html
Any ideas?
imported_Enforcer
01-15-2004, 08:51 AM
Normaly not. If you can open the file on the machine itself it should also be possible with the command.
But something else came into my mind.
Did you ever logged in with something like putty and tested the command manually ?
I think you will get an error like command not found. Because windows dont know the tail command and ssh is only providing a shell to a system and if you use cygwin its a basic linux running on windows. On your ssh server i think its just a normal dos command promt.
I dont know any windows console program that behaves like tail. If all is goind bad i can write one.
Hey I found something http://wintail.hofle.com/ only one problem its not for console :-/
Well I searched some minutes nothing found maybe you find something that is for console. Only GUI apps available it looks like for me.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.