I would like to know what is the purpose of bin\standalone.log at windows server 2008 R2.
When I compare standalone.log whit log\server.log I see the same content.
Tks
If you're running as a service it might just be the piped stdout. If you're not running from a console you could remove the console handler which would limit the output.
Assuming the default configuration you could use the following CLI command to remove the handler.
/subsystem=logging/logging=root-logger:remove-handler(name=CONSOLE)
Related
PowerShell hangs - no response to keyboard actions.
Do CD - ok
Do httpd.exe - Apache service starts OK,
but then Powershell just hangs.
Can only close window, but then Apache service stops.
Same on all versions of PowerShell
From the documentation:
Running Apache as a Console Application
Running Apache as a service is usually the recommended way to use it,
but it is sometimes easier to work from the command line, especially
during initial configuration and testing.
To run Apache from the command line as a console application, use the
following command:
httpd.exe
Apache will execute, and will remain running until it is stopped by pressing Control-C.
Run the program asynchronously as follows:
Start-Process -Filepath .\httpd.exe
Another option: Running Apache as a Service…
I have setup Nagios 4 core on ubuntu machine and I have installed NSClient++ on windows 7 machine. For the out-of-box monitoring like CPU, memory , etc. everything works.
I also have written an EXE in .Net that gathers some metrics on the windows machine and the hope is that NSClient on the windows machine would execute this EXE and marshal these output back to the server. The problem is that I don't know how to install the plug in. Do you install it on the server? On the client? Both? If so where? Needless to say that ubuntu (where the nagios server is) shouldn't try to execute the .net EXE.
When I look at the configuration files on the server, I see that the nagios server uses Check_NT for communicating with the NSclient. We have a syntax like Check_nt!blah. Will I need to use the same syntax when executing my .Net EXE which is not part of the core?
I hardly found any detailed documentation as how to install a windows plugin and have the server and client talk to each other. So either it is extremely easy or extremely complicated. I also looked at some YouTube videos ...there is nothing there for the problem that I"m facing.
Any help is appreciated. Thanks all!
You'll want to define it as an NRPE check on your monitor, then define the check using the same name # NSClient++ on Windows. The NSClient++ configuration has a section for NRPE handlers, just for this (source: op5 kb):
[NRPE Handlers]
The nrpe handlers provide a way to execute any custom plugin/check command on the monitored Windows server. In this section you configure all the commands that should be available.
Adding a custom NRPE command to NSClient++ follow this syntax:
command[my_custom]=c:\mycustomdir\my_prog.exe
To test the check from your monitoring system you can use NRPE from the CLI to call my_custom:
./check_nrpe -H 10.0.0.1 -c my_custom
And then define the service in your Nagios config like so:
define service{
use generic-service
host_name windowshost
service_description CPU Load
check_command check_nrpe!my_custom
}
You may need to do some extra work to format the output correctly. In BASH, exit 1 and exit 0 are commonly used to indicate state, IE: OK/Critical (source), and you may find it easier to augment your EXE's output with some simple scripting like that.
I need to run remote powershell commands on a 2008 R2 server, so i enabled WinRM using the group policy
but then when i go into windows services to view the running services, the Windows Remote Management (WS-Management) is not on the list
so then when i try to run powershell commands that would setup WinRM
It says that the service is not running, thus i cant register the configuration; which is what i really need since i need to run powershell commands as PS version 2 and not version 3
has anyone encountered this before? does anyone have any idea of where to start looking?
thanks
First, you don't need WinRM or PowerShell remoting to run version 2.0. You just invoke powershell with that version:
powershell.exe -Version 2.0
As to your problem, I am not sure why the service is missing. Since you installed WMF 3/Powershell 3 yourself (I'm assuming, because it's 2008 R2), maybe you can try reinstalling or repairing it? Are there any messages in the event log? I admit I have never seen this before.
Have you used an installer for 2008 R2 that was customized or cut down, like the person who asked this question?
I was using Rapid7's Nexpose to scan one of our web servers (windows server 2008), and got a vulnerability for timestamp response.
According to Rapid7, timestamp response shall be disabled:
http://www.rapid7.com/db/vulnerabilities/generic-tcp-timestamp
So far I have tried several things:
Edit the registry, add a "Tcp1323Opts" key to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, and set it to 0. http://technet.microsoft.com/en-us/library/cc938205.aspx
Use this command: netsh int tcp set global timestamps=disabled
Tried powershell command: Set-netTCPsetting -SettingName InternetCustom -Timestamps disabled
(got error: Set-netTCPsetting : The term 'Set-netTCPsetting' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.)
None of above attempts was successful, after re-scan we still got the same alert.
Rapid7 suggested using a firewall that's capable of blocking it, but we want to know if there is a setting on windows to achieve it.
Thanks.
I will just try to explain why you are having the problem in PowerShell. Cannot speak to Nexpose part...
PowerShell is complaining because you do not have the modules required. Unfortunately, even though you might have the latest PowerShell version, you cannot have them on Windows Server 2008, because Microsoft ties them newer OSes. In other words, to be able to use that command, you would need to be on Windows Server 2012/R2/Windows8/8.1 etc... whichever OS the module that includes that CMDlet was released on.
I am deploying project with developer-targeted setup using Inno Setup. I've wrote some code to make some actions that are a bit too custom for the original Inno Setup.
One of such actions was connecting to and running SQL files, thanks to StackOverflow users I've found some code for doing so. The problem is that whenever I try deploying the project on a new Windows Server 2008 machine (x86), I'm getting such cryptic error on every sql command apart from the first one:
"Not enough storage space is available to complete this operation ProgID: ADODB.Connection"
So. The first command fires and works, next stop with error. If I'd run the code again, some of the commands might work, but at some point, the installer would hung. The problem does not exists on windows XP I am writing it on.
I use the code linked above for every SQL command I run (new ole object ADODB.Connection, new command, execute... end) - I don't make the second query for results of insert (as it's there just for showing purpose).
Any thoughts what can be happening here or how can I make a workaround?