mirror of
https://github.com/SystemRage/py-kms.git
synced 2024-12-01 20:54:14 +01:00
c979f42da9
* Merged docker/README.md into docs * Minor reformulations Added references * Moved docker section one up, because they are not really start parameters * Fix links * Moved the supported products section into documentation, as it does not fit the usage topic
227 lines
12 KiB
Markdown
227 lines
12 KiB
Markdown
# Getting Started
|
|
What follows are some guides how to start the `pykms_Server.py` script, which provides the emulated server.
|
|
|
|
## Running as a service
|
|
***
|
|
You can simply manage a daemon that runs as a background process. This can be achieved by using any of the notes below or by writing your own solution.
|
|
|
|
### Docker
|
|
![docker-auto](https://img.shields.io/docker/cloud/automated/pykmsorg/py-kms)
|
|
![docker-status](https://img.shields.io/docker/cloud/build/pykmsorg/py-kms)
|
|
![docker-pulls](https://img.shields.io/docker/pulls/pykmsorg/py-kms)
|
|
![docker-size](https://img.shields.io/docker/image-size/pykmsorg/py-kms)
|
|
|
|
If you wish to get _py-kms_ just up and running without installing any dependencies or writing own scripts: Just use Docker !
|
|
Docker also solves problems regarding the explicit IPv4 and IPv6 usage (it just supports both). The following
|
|
command will download, "install" and start _py-kms_ and also keep it alive after any service disruption.
|
|
```bash
|
|
docker run -d --name py-kms --restart always -p 1688:1688 pykmsorg/py-kms
|
|
```
|
|
If you just want to use the image and don't want to build them yourself, you can always use the official image at the [Docker Hub](https://hub.docker.com/r/pykmsorg/py-kms) (`pykmsorg/py-kms`). To ensure that you are using always the
|
|
latest version you should check something like [watchtower](https://github.com/containrrr/watchtower) out !
|
|
|
|
#### Tags
|
|
There are currently three tags of the image available (select one just by appending `:<tag>` to the image from above):
|
|
* `latest`, currently the same like `minimal`.
|
|
* `minimal`, which is based on the python3 minimal configuration of py-kms. _This tag does NOT include `sqlite` support !_
|
|
* `python3`, which is fully configurable and equipped with `sqlite` support and a web interface (make sure to expose port 8080) for management.
|
|
|
|
#### Architectures
|
|
There are currently the following architectures available (if you need an other, feel free to open an issue):
|
|
* `amd64`
|
|
* `arm32v6` Raspberry PI 1 (A, A+, B, B+, Zero)
|
|
* `arm32v7` Raspberry PI 2 (B)
|
|
* `arm64v8` Raspberry PI 2 (B v1.2), Raspberry PI 3 (A+, B, B+), Raspberry PI 4 (B)
|
|
|
|
_Please note that any architecture other than the classic `amd64` is slightly bigger (~4 MB), caused by the use of qemu during building._
|
|
|
|
#### Docker Compose
|
|
You can use `docker-compose` instead of building and running the Dockerfile, so you do not need to respecify your settings again and again. The following Docker Compose file will deploy the `latest` image with the log into your local directory.
|
|
```yaml
|
|
version: '3'
|
|
|
|
services:
|
|
kms:
|
|
image: pykmsorg/py-kms:latest
|
|
ports:
|
|
- 1688:1688
|
|
environment:
|
|
- IP=0.0.0.0
|
|
- SQLITE=true
|
|
- HWID=RANDOM
|
|
- LOGLEVEL=INFO
|
|
- LOGSIZE=2
|
|
- LOGFILE=/var/log/pykms_logserver.log
|
|
restart: always
|
|
volumes:
|
|
- /etc/localtime:/etc/localtime:ro
|
|
- ./:/var/log:rw
|
|
```
|
|
|
|
#### Parameters
|
|
Below is a fully expanded run command, detailing all the different supported environment variables to set. For further reference see the [start parameters](Usage.html#docker-environment) for the docker environment.
|
|
```bash
|
|
docker run -it -d --name py3-kms \
|
|
-p 8080:8080 \
|
|
-p 1688:1688 \
|
|
-e IP=0.0.0.0 \
|
|
-e PORT=1688 \
|
|
-e SQLITE=true \
|
|
-e HWID=RANDOM \
|
|
-e LOGLEVEL=INFO \
|
|
-e LOGSIZE=2 \
|
|
-e LOGFILE=/var/log/pykms_logserver.log \
|
|
-v /etc/localtime:/etc/localtime:ro \
|
|
-v /var/log:/var/log:rw \
|
|
--restart unless-stopped pykmsorg/py-kms:[TAG]
|
|
```
|
|
You can omit the `-e SQLITE=...` and `-p 8080:8080` option if you plan to use the `minimal` or `latest` image, which does not include the respective module support.
|
|
|
|
### Systemd
|
|
If you are running a Linux distro using `systemd`, create the file: `sudo nano /etc/systemd/system/py3-kms.service`, then add the following (change it where needed) and save:
|
|
```systemd
|
|
[Unit]
|
|
Description=py3-kms
|
|
After=network.target
|
|
StartLimitIntervalSec=0
|
|
|
|
[Service]
|
|
Type=simple
|
|
Restart=always
|
|
RestartSec=1
|
|
KillMode=process
|
|
User=root
|
|
ExecStart=/usr/bin/python3 </path/to/your/pykms/files/folder>/py-kms/pykms_Server.py 0.0.0.0 1688 -V DEBUG -F </path/to/your/log/files/folder>/pykms_logserver.log
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|
|
```
|
|
Check syntax with `sudo systemd-analyze verify py3-kms.service`, correct file permission (if needed) `sudo chmod 644 /etc/systemd/system/py3-kms.service`, then reload systemd manager configuration `sudo systemctl daemon-reload`,
|
|
start the daemon `sudo systemctl start py3-kms.service` and view its status `sudo systemctl status py3-kms.service`. Check if daemon is correctly running with `cat </path/to/your/log/files/folder>/pykms_logserver.log`. Finally a
|
|
few generic commands useful for interact with your daemon [here](https://linoxide.com/linux-how-to/enable-disable-services-ubuntu-systemd-upstart/).
|
|
|
|
### Etrigan
|
|
You can run py-kms daemonized (via [Etrigan](https://github.com/SystemRage/Etrigan)) using a command like `python3 pykms_Server.py etrigan start` and stop it with `python3 pykms_Server.py etrigan stop`. With Etrigan you have another
|
|
way to launch py-kms GUI (specially suitable if you're using a virtualenv), so `python3 pykms_Server.py etrigan start -g` and stop the GUI with `python3 pykms_Server.py etrigan stop` (or interact with the `EXIT` button).
|
|
|
|
### Upstart (deprecated)
|
|
If you are running a Linux distro using `upstart` (deprecated), create the file: `sudo nano /etc/init/py3-kms.conf`, then add the following (change it where needed) and save:
|
|
```
|
|
description "py3-kms"
|
|
author "SystemRage"
|
|
env PYTHONPATH=/usr/bin
|
|
env PYKMSPATH=</path/to/your/pykms/files/folder>/py-kms
|
|
env LOGPATH=</path/to/your/log/files/folder>/pykms_logserver.log
|
|
start on runlevel [2345]
|
|
stop on runlevel [016]
|
|
exec $PYTHONPATH/python3 $PYKMSPATH/pykms_Server.py 0.0.0.0 1688 -V DEBUG -F $LOGPATH
|
|
respawn
|
|
```
|
|
Check syntax with `sudo init-checkconf -d /etc/init/py3-kms.conf`, then reload upstart to recognise this process `sudo initctl reload-configuration`. Now start the service `sudo start py3-kms`, and you can see the logfile
|
|
stating that your daemon is running: `cat </path/to/your/log/files/folder>/pykms_logserver.log`. Finally a few generic commands useful for interact with your daemon [here](https://eopio.com/linux-upstart-process-manager/).
|
|
|
|
### Windows
|
|
If you are using Windows, to run `pykms_Server.py` as service you need to install [pywin32](https://sourceforge.net/projects/pywin32/), then you can create a file for example named `kms-winservice.py` and put into it this code:
|
|
```python
|
|
import win32serviceutil
|
|
import win32service
|
|
import win32event
|
|
import servicemanager
|
|
import socket
|
|
import subprocess
|
|
|
|
class AppServerSvc (win32serviceutil.ServiceFramework):
|
|
_svc_name_ = "py-kms"
|
|
_svc_display_name_ = "py-kms"
|
|
_proc = None
|
|
_cmd = ["C:\Windows\Python27\python.exe", "C:\Windows\Python27\py-kms\pykms_Server.py"]
|
|
|
|
def __init__(self,args):
|
|
win32serviceutil.ServiceFramework.__init__(self,args)
|
|
self.hWaitStop = win32event.CreateEvent(None,0,0,None)
|
|
socket.setdefaulttimeout(60)
|
|
|
|
def SvcStop(self):
|
|
self.killproc()
|
|
self.ReportServiceStatus(win32service.SERVICE_STOP_PENDING)
|
|
win32event.SetEvent(self.hWaitStop)
|
|
|
|
def SvcDoRun(self):
|
|
servicemanager.LogMsg(servicemanager.EVENTLOG_INFORMATION_TYPE,
|
|
servicemanager.PYS_SERVICE_STARTED,
|
|
(self._svc_name_,''))
|
|
self.main()
|
|
|
|
def main(self):
|
|
self._proc = subprocess.Popen(self._cmd)
|
|
self._proc.wait()
|
|
|
|
def killproc(self):
|
|
self._proc.kill()
|
|
|
|
if __name__ == '__main__':
|
|
win32serviceutil.HandleCommandLine(AppServerSvc)
|
|
```
|
|
Now in a command prompt type `C:\Windows\Python27\python.exe kms-winservice.py install` to install the service. Display all the services with `services.msc` and find the service associated with _py-kms_, change the startup type
|
|
from `manual` to `auto`. Finally `Start` the service. If this approach fails, you can try to use [Non-Sucking Service Manager](https://nssm.cc/) or Task Scheduler as described [here](https://blogs.esri.com/esri/arcgis/2013/07/30/scheduling-a-scrip/).
|
|
|
|
### Other Platforms
|
|
They might be useful to you:
|
|
- [FreeNAS](https://github.com/SystemRage/py-kms/issues/56)
|
|
- [FreeBSD](https://github.com/SystemRage/py-kms/issues/89)
|
|
|
|
## Manual Execution
|
|
***
|
|
|
|
### Dependencies
|
|
- Python 3.x.
|
|
- Tkinter module (for the GUI).
|
|
- If the `tzlocal` module is installed, the "Request Time" in the verbose output will be converted into local time. Otherwise, it will be in UTC.
|
|
- It can use the `sqlite3` module, storing activation data in a database so it can be recalled again.
|
|
- Installation example on Ubuntu / Mint:
|
|
- `sudo apt-get update`
|
|
- `sudo apt-get install python3-tk python3-pip`
|
|
- `sudo pip3 install tzlocal pysqlite3`
|
|
|
|
### Startup
|
|
A Linux user with `ip addr` command can get his KMS IP (Windows users can try `ipconfig /all`).
|
|
```bash
|
|
user@host ~ $ ip addr
|
|
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
|
|
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
|
|
inet 127.0.0.1/8 scope host lo
|
|
valid_lft forever preferred_lft forever
|
|
inet6 ::1/128 scope host
|
|
valid_lft forever preferred_lft forever
|
|
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
|
|
link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
|
|
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic noprefixroute enp6s0
|
|
valid_lft 860084sec preferred_lft 860084sec
|
|
inet6 ****:****:****:****:****:****:****:****/64 scope global dynamic noprefixroute
|
|
valid_lft 6653sec preferred_lft 3052sec
|
|
inet6 ****::****:****:****:****/64 scope link noprefixroute
|
|
valid_lft forever preferred_lft forever
|
|
```
|
|
In the example above is `192.168.1.102` the ip we want to listen on, so it is this command (**note you can omit the ip AND port specification if you just wish to listen on all interfaces with port 1688**):
|
|
|
|
```
|
|
user@host ~/path/to/folder/py-kms $ python3 pykms_Server.py 192.168.1.102 1688
|
|
```
|
|
|
|
To stop `pykms_Server.py`, in the same bash window where code running, simply press `CTRL+C`.
|
|
Alternatively, in a new bash window, use `kill <pid>` command (you can type `ps aux` first and have the process <pid>) or `killall <name_of_server>`.
|
|
|
|
### Quick Guide
|
|
The following are just some brief notes about parameters handling. For a more detailed description see [here](Usage.md).
|
|
|
|
- To generate a random HWID use `-w` option: `python3 pykms_Server.py -w RANDOM`.
|
|
- To get the HWID from any server use the client, for example type: `python3 pykms_Client.py :: 1688 -m Windows8.1 -V INFO`.
|
|
- To change your logfile path use `-F` option, for example: `python3 pykms_Server.py -F /path/to/your/logfile.log -V DEBUG`.
|
|
- To view a minimal set of logging information use `-V MININFO` option, for example: `python3 pykms_Server.py -F /path/to/your/logfile.log -V MININFO`.
|
|
- To redirect logging on stdout use `-F STDOUT` option, for example: `python3 pykms_Server.py -F STDOUT -V DEBUG`.
|
|
- You can create logfile and view logging information on stdout at the same time with `-F FILESTDOUT` option, for example: `python3 pykms_Server.py -F FILESTDOUT /path/to/your/logfile.log -V DEBUG`.
|
|
- With `-F STDOUTOFF` you disable all stdout messages (but a logfile will be created), for example: `python3 pykms_Server.py -F STDOUTOFF /path/to/your/logfile.log -V DEBUG`.
|
|
- With `-F FILEOFF` you disable logfile creation.
|
|
- Select timeout (seconds) for py-kms with `-t0` option, for example `python3 pykms_Server.py -t0 10`.
|
|
- Option `-y` enables printing asynchronously of messages (pretty / logging).
|