I am trying to start Solr Cloud as windows service using Procrun but I can not find working solution how it can be done. Maybe there is some solution how to do this?
I have tried to setup Solr Cloud using this article - https://opensourceconnections.com/blog/2013/08/27/solrcloud-as-a-windows-service/ but it is not working.
Please try to use the NSSM tool (Non-Sucking-service-manager) that fits your requirement to setup Solr cloud on Windows as a service.
The detailed steps for implemetation are listed in the below link
How to Run Solr as a Service on Windows
For powershell with solrcloud and using zookeeper ensemble, please run
&"$nssm" install solr $ScriptPath start -cloud -p 8984 -z """""""$solrSvrArrayCsv""""""" -f
$nssm is the path to your nssm exe
$scriptPath is the path to your solr.cmd file
$solrSvrArrayCsv is a comma seperated array of zookeeper ensemble nodes ie) "zookeeper1:2181,zookeeper2:2181,zookeeper3:2181"
It must be wrapped in double quotes
This works for me launching solr cloud with ssl
Related
I configure logstash service following the instructions in the link https://www.elastic.co/guide/en/logstash/current/running-logstash-windows.html (logstash as a service using nssm) but I noted that the service does actually not running when I am disconnected from the remote server I installed it.
Is there a way to fix this problem?
thanks,
g
The same thing happens also running logstash manually (I mean , running the appropriate bat file in command prompt).
I have a PowerShell script that I want to run on some Azure AKS nodes (running Windows) to deploy a security tool. There is no daemon set for this by the software vendor. How would I get it done?
Thanks a million
Abdel
Similar question has been asked here. User philipwelz has written:
Hey,
although there could be ways to do this, i would recommend that you dont. The reason is that your AKS setup should not allow execute scripts inside container directly on AKS nodes. This would imply a huge security issue IMO.
I suggest to find a way the execute your script directly on your nodes, for example with PowerShell remoting or any way that suits you.
BR,
Philip
This user is right. You should avoid executing scripts on your AKS nodes. In your situation if you want to deploy Prisma cloud you need to go with the following doc. You are right that install scripts work only on Linux:
Install scripts work on Linux hosts only.
But, for the Windows and Mac software you have specific yaml files:
For macOS and Windows hosts, use twistcli to generate Defender DaemonSet YAML configuration files, and then deploy it with kubectl, as described in the following procedure.
The entire procedure is described in detail in the document I have quoted. Pay attention to step 3 and step 4. As you can see, there is no need to run any powershell script:
STEP 3:
Generate a defender.yaml file, where:
The following command connects to Console (specified in [--address](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/install/install_kubernetes.html#)) as user <ADMIN> (specified in [--user](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/install/install_kubernetes.html#)), and generates a Defender DaemonSet YAML config file according to the configuration options passed to [twistcli](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/install/install_kubernetes.html#). The [--cluster-address](https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/install/install_kubernetes.html#) option specifies the address Defender uses to connect to Console.
$ <PLATFORM>/twistcli defender export kubernetes \
--user <ADMIN_USER> \
--address <PRISMA_CLOUD_COMPUTE_CONSOLE_URL> \
--cluster-address <PRISMA_CLOUD_COMPUTE_HOSTNAME>
- <PLATFORM> can be linux, osx, or windows.
- <ADMIN_USER> is the name of a Prisma Cloud user with the System Admin role.
and then STEP 4:
kubectl create -f ./defender.yaml
I think that the above answer is not completely correct.
The twistcli command, does not export daemonset for Windows Nodes. The "PLATFORM" option, is for choosing the OS of the computer that the command will run.
After testing, I have made the conclusion that there is no Docker Image for Prisma Cloud for Windows Kubernetes Nodes, as it is deployed as a service at Windows OS, and not Container (as in Linux). Wrapping up, the Daemonset is not working at the Windows Hosts
I believe the only solution is this -> Windows
This is the Powershell script that Wytrzymały Wiktor has mentioned.
Unfortunately this cannot be automated easily, as you have to deploy an Azure VM per AKS Cluster (at the same network), and RDP to the AKS Windows Node and run the script.
If anyone has another suggestion or solution, feel free to share.
I wanted to use confluent in AWS EC2 environment. How can I install it. I have tried the confluent cli in my local and want to replicate this feature of connecting sql to kafka. Is there any documentation on this?
You can find how to install Confluent Platform from DEB or YUM sources in Confluent docs. Otherwise, extract the same package you would have done locally.
There's AWS quickstart templates or Ansible setups on Confluent Github for setting up a full cluster. Or you could use EKS to run it in Kubernetes, if that's something you're comfortable with. I'm sure there's some third party Terraform repos out there as well...
For non-container, production use cases, you'd use systemctl to start services on independently running servers, not all Confluent services on just one system like with confluent start
Sounds like you just want to run KSQL, but it's not clear if/where you have a running Kafka cluster
you just need to download confluent zip from here
https://www.confluent.io/download/
unzip in your desired folder
for start confluent services
go to confluent bin /path to extract folder/confluent/bin
for start all confluent service
confluent start
for check service status
confluent status
for stop service
confluent stop
Logged into Windows Server 2016 as Administrator, I can run Solr from the command line: bin\solr.cmd start -p 8983 -f
I have configured a Solr to run as a Windows Service - running as the same user, with the same command, same startup directory, etc. - however under load, the following error comes back from the upstream application (Sitecore xConnect, though this shouldn't make a difference)
{metadata={error-class=org.apache.solr.common.SolrException,root-error-class=org.apache.solr.common.SolrException},msg=SolrCore is loading,code=503}
To reiterate, everything works fine when Solr is started from the command line, only when it's run as a Windows Service does it error.
Solr version: 6.6.3
Windows version: Server 2016
Environment: AWS (m5.large EC2 instance)
Sitecore compatibility table says to use Solr 6.6.1 with Sitecore, You should still use 6.6.2 as it fixes a bug in Solr 6.6.1 that can affect the installation of SIF. Read here
I recommend you try again with Solr 6.6.2
It turns out that the service was configured to run without the -f flag. So the process would continually stop and re-spawn.
How can I run Selenium Server Standalone 2 as a windows service in Windows XP?
Or if you want it start at startup, you can do this:
Create file 01_start_hub.bat which will contain this command:
java -jar selenium-server-standalone-2.20.0.jar -role hub
Create file 02_start_node.bat which will contain this command:
java -jar selenium-server-standalone-2.20.0.jar -role node -hub http://localhost:4444/grid/register
Place both bat files into Startup folder C:\Documents and Settings\UserName\Start Menu\Programs\Startup
Yes you will have two "ugly" dos prompts after startup, but this is quickwin solutin
http://brantleytec.blogspot.com/2012/11/selenium-hub-and-node-as-windows-service.html
That link describes the process I used to set up and use Selenium hub and node as a service using native Microsoft programs. I was able to get this running locally on my work PC as well as on a remote server which runs my tests after every build.
If this is for your local PC though, I might suggest using the ChromeDriver instead of the RemoteWebDriver. It's less setup and allows new hires to start using your tests without any extra setup.
I've had a lot of luck with the Non-Sucking Service Manager. It's a standalone executable that creates and a windows service and works much better than any alternatives I've ever used (I'm thinking about srvany.exe). The usage instructions are pretty straightforward.
Here's how I used it:
Download and extract nssm.exe
I wanted to run a single instance that acted as both the hub and a node, so I didn't specify a role. I also just wanted the default settings, so I didn't pass in any parameters. Here's what I did from the command line: nssm install Selenium-Server "C:\Program Files\Java\jre6\bin\java.exe" "-jar C:\Selenium\selenium-server-standalone-2.21.0.jar"
If you want to run as just a hub or a node, then add in the -role hub or -role node to the last parameter in step #2, e.g. "-jar C:\Selenium\selenium-server-standalone-2.21.0.jar -role hub". You can specify any other parameters for Selenium here as well.
If you need to adjust the parameters later, you can do this through Regedit under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\\Parameters. Specifically, the AppParameters Key contains the parameters you pass to Selenium.
Checkout the following project...
I've used it to setup my Minecraft Server (java project) as a windows service.
http://yajsw.sourceforge.net/
Good Luck
And here is link to more durable solution - first create the BAT files as in my other answer. Second read this article - Its about creating the service. I would reccomend pointing out to the BAT files in the options.
I never created a service, so that help page is as much as I can offer