• [I was directed here] Console.log not opening
    5 replies, posted
Hello, once again I have stumbled upon an issue. As of lately I have ran into a serverside problem that I would love to access the console.log for. Obviously (Because ya' know, I'm clunky) I wasn't able to read the console.log in my FTP, so like any normal human being I went to move it to my desktop to view and... it didnt move Here is some code my FTP is spitting out. [code] Command: CWD /garrysmod Response: 250 CWD command successful. Command: TYPE I Response: 200 Type set to I. Command: PASV Response: 227 Entering Passive Mode (dont look at my IP nerd). Command: RETR console.log Error: Transfer connection interrupted: ECONNABORTED - Connection aborted Response: 550 The process cannot access the file because it is being used by another process. Error: Critical file transfer error[/code] I've been at this for around 2 days now and haven't been able to figure out the reason why (yes I even did a google search or two!) So hopefully one of you people will be able to help.
The server, where you got this issue, is under Windows or Linux? While I see that you're trying to retrieve the "console.log" in "/garrysmod", is the server from a hosting company or other places?
Another process has a lock on the file. Is this on Windows? That would probably be the reason. I don't waste much time on Windows when it comes to hosting services, for good reason, but I think you might be able to create a copy of the file, even though it's locked, and then grab the copy.
[QUOTE=nikomo;51279482]Another process has a lock on the file. Is this on Windows? That would probably be the reason. I don't waste much time on Windows when it comes to hosting services, for good reason, but I think you might be able to create a copy of the file, even though it's locked, and then grab the copy.[/QUOTE] 1. Yes, this is running on windows 2. How would I create a copy? [editline]29th October 2016[/editline] It appears to me someone has marked this as dumb, could that person please send a solution?
Not sure if I am misunderstanding your problem, but is your server running? If so, stop the server and open the console.log
Okay that deserves a face palm and a half. Thank you for that obvious answer :v:
Sorry, you need to Log In to post a reply to this thread.