Skip to main content

Operations Overview

What Are You Trying to Do​

TaskRead
Turn on/off · RestartStartup · Shutdown · Restart
Check status · MonitorMonitoring
Backup · RecoveryBackup
Change password · keyCredentials
Diagnose when it doesn't workDiagnostics
Handling by situationOperational Scenarios
Manage containers directlyContainer Operations
Tables · SchemaDatabase Model
High AvailabilityHA
Upgrade versionUpgrade
Disk cleanupCleanup

This is a collection of operational scripts executed by the administrator (root) who accesses the gateway server via SSH. For general users, the web UI is sufficient, but operational tasks such as start / stop / backup / upgrade / fault diagnosis are performed using these scripts.

Container Mode (2026.05+) is a Separate Guide

If systemctl is-active plantpulse-edge.service is active, it's container mode. Instead of the native scripts on this page (bin/start.sh, etc.), use the Container Mode Operations page's /opt/kopens/install/bin/*.sh commands. This page is for native deployment boxes only.

Installation path (native):

PE_HOME=/opt/kopens/plantpulse-edge
cd $PE_HOME/bin
ls *.sh # 어떤 스크립트가 있는지 확인

At a Glance​

CategoryScriptBrief DescriptionDuration
Startstart.shBoots the gateway full stack~90–120 sec
start-daemon.shstart.sh as nohup backgroundImmediate
Stopstop.shGraceful stop per module (max 20 sec per component, incl. Cassandra drain)~60–90 sec
Restartrestart.shstop.sh + start.sh as a single process — full stack~150–210 sec
restart-app.shRestart Tomcat (app) only — the "App Restart" button is this30–90 sec
reboot.shOS reboot—
Backupbackup.shBack up settings + DB snapshot + tool data all at onceMinutes
Upgradeupgrade.shBackup → download/install new version5–15 min
firmware.shOS package update (dnf update)Minutes
Diagnosticslog-viewer.shIntegrated tail -f of 7 component logsIndefinite
ps.shLive plantpulse processesImmediate
node-info.shnodetool info (Cassandra status)Immediate
node-cql.shCassandra cqlsh interactive—
network-speed-test.shExternal network speed testMinutes
Cleanupclean.shBulk deletion of logs / temp filesImmediate
node-cleanup.shCassandra disk reclamationMinutes
Scenarios—New version deployment / fault diagnosis / disk full / regular backup / disaster recovery runbook—
Most frequently used commands

In the development/deployment cycle, the one used nearly every time is restart-app.sh (app only, 30–90 sec). start.sh is used once after an OS reboot, and stop.sh is used only right before an inspection or backup.


Sub-Component's Own start.sh / stop.sh​

The overall scripts (start.sh, stop.sh) only coordinate the sequence, and the internal implementation is handled by component-specific scripts. Call these directly when you want to restart just one:

ComponentStartStop
Redis (cache)$PE_HOME/cache/bin/start.sh$PE_HOME/cache/bin/stop.sh
Cassandra (DB)$PE_HOME/db/bin/start.sh$PE_HOME/db/bin/stop.sh
HiveMQ (MQTT)$PE_HOME/mqtt/bin/start.sh$PE_HOME/mqtt/bin/stop.sh
timeseries-engine$PE_HOME/timeseries/engine/bin/start.sh$PE_HOME/timeseries/engine/bin/stop.sh
timeseries-dashboard$PE_HOME/timeseries/dashboard/bin/start.sh$PE_HOME/timeseries/dashboard/bin/stop.sh
Tomcat (server)$PE_HOME/server/bin/start.sh$PE_HOME/server/bin/stop.sh
Node-RED$PE_HOME/node/bin/start.sh$PE_HOME/node/bin/stop.sh

Example — restart Node-RED only:

$PE_HOME/node/bin/stop.sh
$PE_HOME/node/bin/start.sh

Permissions / Location Reference​

  • All scripts require root privileges (port 80/443 binding, systemctl, /opt/ writes).
  • Directories:
PurposePath
Gateway code / artifacts/opt/kopens/plantpulse-edge/
User data (sparkplug bdSeq, grafana, node-red, hivemq, apm)/data1/pp-data/
Backup artifacts/data1/pp-backup/
Tomcat logs$PE_HOME/server/logs/catalina.out
Cassandra logs$PE_HOME/db/logs/system.log
HiveMQ logs$PE_HOME/mqtt/log/hivemq.log
Node-RED logs$PE_HOME/node/log/node-red.log
  • Note: It is recommended to place /opt/kopens/ and /data1/pp-data/ on separate disks. Separating code updates and data preservation reduces the risk of data loss during upgrade.

Learn More​

  • For detailed procedures in each category, see the Start / Stop / Restart / Backup / Upgrade / Diagnostics / Cleanup / Scenarios pages in the left menu.
  • For usage of each script, refer to --help or the comments at the top of the script.