This seems like simple question but I have yet to find a clear and recent answer. Here's why I'm looking for this information:
PROBLEM: We load balance 8 web servers and every server hosts the same sites. We sometimes run into situations where a specific user receives errors while doing something and in order to diagnose and correct the problem we need to determine what server the user last connected to. In some cases the issue is reproducible on all servers but in other cases it can only be reproduced on a specific server, which is why we need to find it. Currently, we do the following to find the bad server:
1) Remove all servers from the balancer except one
2) Have the user attempt to reproduce the problem
3) If the problem can't be reproduced, repeat the same process with the next server.
This is time consuming and frustrating to our customers and I'm trying to find a better/faster way of finding the affected server. I've done a lot of reading but so far I've only found one article from back in 2005 (IIS 6) that answers my question:
http://blogs.msdn.com/b/david.wang/archive/2005/10/08/howto-see-who-is-logged-into-iis.aspx
Is what's described in this article still true today, 10 years later?
Thank you for your help!
Related
I´m invoking https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.DesktopVirtualization/hostPools?api-version=2021-07-12 and randomly fails, returning a "500 Internal Server Error". Is there any way to troubleshoot this obscure error? Any log I can check?
Regards
EDIT: I do not provide the source code because this is not a code issue. This restapi call have been working in prod perfectly for months and, two days ago, suddenly it started to fail returning a 500 error in (more or less) 40% of calls. I would like to check some log or whatever in order to know what is happening on behind.
Azure Virtual Desktop troubleshooting steps are documented here:
https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-overview
Not really enough detail in the question to answer anything specific for your environment.
I am very new to development, so I apologize in advance if I am not being clear enough. I appreciate any feedback on the question and how to better pose it.
I'm currently working on an angular app hosted in WSL2. To get it to run locally, this is what I do:
Launch solution in VS Code
From terminal, run npm start
Then, I click on Run and Debug
Once I get the Now listening on: ..... message, I move on to Chrome to start debugging my app
Since this morning, I keep getting a ERR_CONNECTION_REFUSED in the browser, and I'm currently waiting on IT to step in as there could have been some security changes placed that are blocking the requests. Also, I'm not using the VPN.
In the meantime, is there a way to know for sure (or get as close as possible to) what is causing the connection to be refused in my particular scenario? I'm curious about it, but I don't know how to even search the topic properly due to lack of proper terms.
What should one do to at least obtain more details about the issue on their own (perhaps, to help expedite help by collecting important info upfront)? Where my apps are hosted in WSL2, I get very confused between the ip address originating the request and that of the server.
I appreciate any guidance anyone could provide.
It turned out there was a VPN software running where the firewall was ON, even though I was not in the VPN (it went on after I connected to the VPN the previous day). I guess there was nothing else I could have done anyway.
2.5 months ago, I was running a website on a Linux server to do a user study on 3 variations of a tool. All 3 variations ran on the same website. While I was conducting my user study, the website (i.e., process hosting the website) crashed. In my sleep-deprived state, I unfortunately did not record when the crash happened. However, I now need to know a) when the crash happened, and b) for how long the website was down until I brought it back up. I only have a rough timeframe for when the crash happened and for long it was down, but I need to pinpoint this information as precisely as possible to do some time-on-task analyses with my user study data.
The server runs Linux 16.04.4 LTS (GNU/Linux 4.4.0-165-generic x86_64) and has been minimally set up to run our website. As such, it is unlikely that any utilities aside from those that came with the OS have been installed. Similarly, no additional setup has likely been done. For example, I tried looking at a history of commands used in hopes that HISTTIMEFORMAT was previously set so that I could see timestamps. This ended up not being the case; while I can now see timestamps for commands, setting HISTTIMEFORMAT is not retroactive, meaning I can't get accurate timestamps for the commands I ran 2.5 months ago. That all being said, if you have an idea that you think might work, I'm willing to try (as long as it doesn't break our server)!
It is also worth mentioning that I currently do not know if it's possible to see a remote desktop or something of the like; I've been just ssh'ing in and use the terminal to interact with the server.
I've been bouncing ideas off with friends and colleagues, and we all feel that there must be SOMETHING we could use to pinpoint when the server went down (e.g., network activity logs showing spikes around the time that the user study began as well as when the website was revived, a log of previous/no longer running processes, etc.). Unfortunately, none of us know about Linux logs or commands to really dig deep into this very specific issue.
In summary:
I need a timestamp for either when the website crashed or when it was revived. It would be nice to have both (or otherwise determine for how long the website was down for), but this is not completely necessary
I'm guessing only a "native" Linux command will be useful since nothing new/special has been installed on our server. Otherwise, any additional command/tool/utility will have to be retroactive.
It may or may not be possible to get a remote desktop working with the server (e.g., to use some tool that has a GUI you interact with to help get some information)
Myself and my colleagues have that sense of "there must be SOMETHING we could use" between various logs or system information, such at network activity, process start times, etc., but none of us know enough about Linux to do deep digging without some help
Any ideas for what I can try to help figure out at least when the website crashed (if not also for how long it was down)?
A friend of mine pointed me to the journalctl command, which apparently maintains timestamps of past commands separately from HISTTIMEFORMAT and keeps logs that for me went as far back as October 7. It contained enough information for me to determine both when I revived my Node js server as well as when my Node js server initially went down
I'm getting worried. For one specific computer where I run win10 and chrome i maybe once every 30-60 days get a different web page compared to the url I manually type in.
I have tested kaspersky and avast, but none of them found anything on my computer.
I suspect that some service on my computer injects itself every now and then between chrome and the DNS server to give me the wrong ip address for the site that I'm looking for.
I have a ubiquity edge router and can not see any odd setting in it.
I have tried to run wireshark, but since it happens so rarely I have not managed to have wireshare running while this happens.
The pages that I get to instead of where I want to get is online gambling sites.
I have searched the web after instructions on how to trouble shoot this and tried many without any success.
What is the best working instruction to sort this out? Grateful for any help or direction.
to begin with, I have an internship with a trading company that has 15 points of sale. My mission is to manage its IT infrastructure with ITSM 9.1.6.
To discover its network, I use Fusioninventory 9.1+1.0.
I also have installed the latest Fusioninventory agent for Windows. My problem is that I only get response from only 10 points of sale. I didn't get my problem to solve it because the agent works well (for the 15 points of sale).
PS: it's not a problem of a firewall, I installed the netdiscovery, deploy, ESX and the other fusioninventory features
I don't have a good knowledge about ITSM neither about the Fusioninventory but I followed tutorials.
Soryy if I asked dummy questions but could any one help me please ?
You should check the logs to start debugging.
Enable logging by seting debug to 1 or 2. Open regedit and head to HKLM/Software/Fusioninventory/ find the debug key and edit it.
If you are running the agent as a service then restart it, otherwise just execute the fusioninventory-agent.bat script to launch a new inventory.
Check the logs. They are usually at %programfiles%\fusioninventory-agent\ although I think they are better at %programfiles%\fusioninventory-agent\var\. You can change where to store the log at the logfile key.
There you'll find what is stopping your inventory from reaching the server.