I am having trouble with this error when attempting to connect to perforce client
Fatal client error; disconnecting! write: ...: No space left on device
I have tried looking into the contents of this "..." folder but there is not much there.
The machine which runs your Perforce server is probably out of disk space.
Do you have an administrator who runs your server? Contact them, and ask them to have a look at the server machine to see if disk space can be freed up.
Related
When a process is stuck in downloading a remote file(I can see from jstack that is is being blocked in socket read), is there any Linux command to tell what's the actual URL of the remote file that the process is downloading?
Tools like lsof seem only giving the remote host, instead of the path of particular remote files.
Considering that the client has already sent the HTTP request to the server and is now waiting for the response the exact URL requested is no longer available on the network. Nor is the URL available somewhere in sockets states because these deal only with network and transport layer information and not with application level information (i.e. HTTP). If you are lucky than you can find the original URL somewhere inside the memory of the application but since it is actually not needed any longer by the application (request has been sent) it might be, that it is not even known to the application any longer.
I'm trying to set up a remote desktop session for monitoring specific systems at my place of work. I only have access to a Linux machine and I need to connect via a terminal server gateway. I am using FreeRDP to do this and i am using the following command to create the connection:
xfreerdp /d:** /u:***** /p:******* /g:******.************.***
/v:****.*********.***** /port:3389 /size:1920x1080
I have hidden all connection details per my supervisors request however both he and I verified the correct information is entered into the fields.
When I send the connection through I get the following error:
Connected to ******.************.***:443
Connected to ******.************.***:443
TS Gateway Connection Success
Got stub length 4 with flags 3 and called 7
Got stub length 4 with flags 3 and called 6
SSL_read: I/O error: connection reset by peer (104)
Rpc_client_frag_read: error reading header
Would anyone have any idea of what I might be missing? I have even tried adding
/sec:rdp
to the script and even that produced the same error
Try rdp from a Windows system (or have someone else try from their system, since you don't have direct access to Windows). I know it won't solve your problem, but it may give you better information. I'm in a similar situation and got the same error message. I tried remmina instead of xfreerdp and got even less information than xfreerdp spits out.
From a Windows VM, at least I could tell when I got my domain\username & password right -- it told me my account was not allowed rdp access to that server. I'm figuring that means that there are accounts that can rdp in, but mine is not among them. Along the way, though, I found that the remote was using a certificate from an untrusted authority, which was useful information for my case.
If your Linux is old or hasn't been updated, do so. Your certificate store may be out of date. But it may also be that your company's Windows domain has certificates that Linux doesn't know about. It could be a simple matter that you're lacking the company-supplied cert (because they push it to all Windows machines on the domain, but your Linux machine doesn't get that "benefit").
I have a small Web API app that runs fine under Visual Studio. When I try to deploy it under IIS, however, I get this:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: SQL
Network Interfaces, error: 50 - Local Database Runtime error occurred.
The specified LocalDB instance does not exist. )
The app is using a sqllocaldb server, and the server is started and queries (via sqllocaldb info) as being alive and running. I have tried setting the app pool Identity to my userid vs using "ApplicationPoolIdentity", and have tried setting up and using a shared version of the server. Changing the userid produced a different but equally unhelpful message; using a shared server changed nothing.
I've also determined that I can provoke the same message running directly in VS if I use a bogus server instance name in the connection string.
It would be ever so slightly helpful if the error message positively identified which server instance it cannot find, but nowhere in the message (either in the browser or when examined by an attached Visual Studio session) does it name the missing server.
How can one identify the "does not exist" server?
Update:
A coworker solved my problem (without actually answering the above question). The solution was to open my applicationHost.config file (In Windows\System32\inetsrv\config) and edit the <system.applicationHost> <applicationPools> <add> item for the application pool containing my app and add (within the <processModel> element) loadUserProfile="true" setProfileEnvironment="true". Exactly what that hocus pocus does I don't know, but he found it here.
I am trying to connect to website in win azure using filezilla. It connected fine for few minutes and I was able to upload the files. But then it stopped working. I am getting this message:
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Response: 227 Entering Passive Mode (137,117,88,16,40,32).
Command: LIST
Response: 150 Opening BINARY mode data connection.
Response: 550 The network connection was aborted by the local system.
Error: Failed to retrieve directory listing
I have tried setting transfer mode to ACTIVE and few other suggestions, but nothing seems to work. What could be the problem?
There might be a time-out issue on the server. You will need to tell your FTP client to keep the connection alive so that it doesn't start a second connection while the first connection is still alive.
To set this in FileZilla client, go to Edit, Settings, Connection, FTP, and check "Send FTP keep-alive commands" checkbox.
For more detailed explanation of the problem, visit: http://blogs.msdn.com/b/wats/archive/2013/12/13/setting-up-a-passive-ftp-server-in-windows-azure-vm.aspx Scroll towards the bottom and read the "Points to consider from Azure SLB perspective" section.
I had the same problem with my FTP on Azure (getting 550 errors) and checking the "Send FTP keep-alive commands" checkbox above solved my problem.
Hope this helps!
The error message:
Response: 550 The network connection was aborted by the local system
Suggests that there is an error in your local network.
This error is not within Windows Azure, but within your local network (and appears to only be triggered by FileZilla). Contact your system administrator or Internet Service Provider. Also, please try first solving the problem yourself using something like this.
So I have an issue where I am remotely connecting to a Mongodb on my linode box, and I am not longer able to access this DB. I can from my local machine, but when I am on this remote server (where the website runs) it is not working. I am not seeing the connection come into the Mongo logs, so this leads me to believe that maybe it is being intercepted by a firewall?
How can I watch traffic and see if this connection is at least making it to my linode box? I am connecting with Mongoid, so if there is a way to prove no connection there too.
Right now the only error I get is a erb view timeout execution error - not much to go on.
Thanks,
Daniel