This section describes only the intital configuration step for the sat-nms EDB service.
The system ships a default configuration which is "ready-to-run" but you can modify some configuration to adapt the system to your environment. For a all-in-one MNC System no additional configuration is required.
Several other options require your attention if you run the EventDB on the central server or for complex setups which includes server redundancy.
A detailed description of all options from is available in the Administration Section of this Manual.
To ensure the EventDB service will automatically start on reboot, login as root and enable this service. Remember that the EventDB service is included in the common MNC service. So the following steps are identically to the installation of MNC service.
rootNow you can start the MNC service as user satnms and check if its running.
satnmssatnms-watch┌──────────────────────┤ sat-nms state ├─────────────────────────┐
│ │
│ hostname / MNC name : satnms7-dev / MNC │
│ satnms OS version : debian-satnms-7.01 2023-10-05 │
│ ____________________________________________________________ │
│ │
│ MNC service : STOPPED │
│ MNC service version : not installed │
│ │
...
│ │
│ last updated : 2025-14-02 16:48:48 UTC │
│ ____________________________________________________________ │
│ │
│ refresh refresh service states │
│ satnms-start start MNC Service │
│ backend-stop stop Backend Service │
│ nginx-start start Nginx Webserver │
│ │
│ <Select service> <Exit> │
└────────────────────────────────────────────────────────────────┘The output depends on the installed services. In the example above, only the sat-nms MNC service is installed and running, and as said this includes the EventDB service as well.
You can also control the EventDB service directly with the follwing commands:
sudo systemctl start satnmssudo systemctl stop satnmsCheck if the Event service start successfully:
systemctl status satnmssatnms@satnms7-dev:$ systemctl status satnms
● satnms.service - sat-nms MNC service
Loaded: loaded (/etc/systemd/system/satnms.service; enabled; preset: enabled)
Active: active (running) since Thu 2026-04-23 13:57:55 UTC; 3 days ago
Main PID: 461 (satnms-start)
Tasks: 34 (limit: 2298)
Memory: 118.2M
CPU: 41min 43.795s
CGroup: /system.slice/satnms.service
├─461 /bin/bash /home/satnms/satnms-start
├─491 /bin/bash /home/satnms/satnms-start
└─532 java -cp "satnms.jar:/home/satnms/jars/*" -mx512m -Djava.security.egd=file:/dev/./urandom -Dhostname=EDB-BCKP satnms3.vl>
Apr 23 13:58:00 satnms7-dev sudo[771]: satnms : PWD=/home/satnms ; USER=root ; COMMAND=/usr/sbin/dmidecode -t baseboard
Apr 23 13:58:00 satnms7-dev sudo[771]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Apr 23 13:58:00 satnms7-dev sudo[771]: pam_unix(sudo:session): session closed for user root
You can test if the EventDB started successfully by checking the output of the log file /home/satnms/debug.log. The first line shows an early stage of start process and is an indication that the MNC service begins to start. The second line shows that all sub processes are now initialized and the MNC service is ready to serve client requests. Starting from this the MNC service or clients are able to connect to the MNC service. Once the MNC service is running, you can also check if the EventDB comes up correctly. One indication is the file /home/satnms/edb/ID with a recent timestamp and at least two actual files starting with X and T followed by the number of the days since January 1, 1970 (the "Unix" epoch). For example the event files for the 27. April 2026 will be named X20570 and TX20570.
satnms@satnms7-dev:~$ tail /home/satnms/debug.log
...
000000 2025-03-05 12:32:18 2025-03-05 12:32:18 I SYSTEM Loading setup data (sat-nms MNC default config)
...
000000 2025-03-05 12:32:18 2025-03-05 12:32:18 I SYSTEM VLC 3.68.9 2025-03-05 07:22:02 is up
...satnms@edb-bckp:~/edb$ ls -l /home/satnms/edb/
...
-rw-r--r-- 1 satnms satnms 4 Apr 27 07:49 ID
...
-rw-r--r-- 1 satnms satnms 556 Apr 27 07:49 /home/satnms/edb/T20570
-rw-r--r-- 1 satnms satnms 384 Apr 27 07:49 /home/satnms/edb/X20570
...Some more details and extended error messages if something failed are available in /home/satnms/.panic.log
for the first run on a fresh EventDB installation you will see the following message which can be safely ignored. It just tells you that the ID was missing and was now created for the first time.
satnms@satnms:~$ cat .panic.log
...
java.io.FileNotFoundException: ./edb/ID (No such file or directory)
at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(FileInputStream.java:216)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:111)
at satnms3.edb.EventDbFeed.createID(EventDbFeed.java:447)
at satnms3.edb.EventDbFeed.run(EventDbFeed.java:138)
...A detailed description how to run the sat-nms MNC service is available in the administration manual.
Troubleshooting
If you have trouble to bring up the EventDB service check first if the MNC service is still running with:
systemctl status satnms or/home/satnms/satnms-statAdditionally you can lookup the process ID (PID) of the MNC service process:
satnms@satnms7-dev:~$ ps aux |grep satnms.jar
satnms 8204 ? Sl 25:18 java -cp satnms.jar:/home/satnms/jars/* -mx512m -Djava.security.egd=file:/dev/./urandom -Dhostname=MNC satnms3.vlc.Server -eNow check if the MNC process with this PID (here 8204 from the second column) was able to start the EventDB service. In this case the process should listening on TCP ports 2006.
satnms@satnms7-dev:~$ ss -tanp |grep 2006
LISTEN 0 50 *:2006 *:* users:(("java",pid=8204,fd=12))
...Port 2006 is using standard HTTP for request. Therefore you can fetch events with any web browser or on the command line with curl. Try the URL http://[ip-address]:2006/csvx? and you will see a list with actual events. Below an example with events on a new system just started:
21557 2026-04-27 13:26:55 2026-04-27 13:26:56 1 MNC SYSTEM Loading setup data (sat-nms MNC default config)
21558 2026-04-27 13:26:55 2026-04-27 13:26:56 1 MNC SYSTEM VLC 3.80.4 2025-11-12 15:50:23 is upRemark:
On all-in-one installation where Backend and EventDB service running on the same host, you can restrict the EventDB port to localhost. Please refer to the chapter vlc.properties in the sat-nms administration manual