# Set up a production environment
Use the following information to set up and manage your production-level full Paloma node.
For information about running a validator node, visit the validator guide.
# Create a dedicated user
palomad does not require a super user account, during the
setup process you'll need super user permission to create and modify
some files. It is strongly recommended to use a normal user when
# Increase the maximum files
palomad can open
palomad is set to open 1024 files by default. It is recommended
that you increase this amount.
/etc/security/limits.conf* (opens new window)
to increase the amount, where
nofile is the number of files
palomad can open.
# If you have never changed this system config or your system is fresh, most of this file will be commented # ... * soft nofile 65535 # Uncomment the following two lines at the bottom * hard nofile 65535 # Change the default values to ~65535 # ...
# Run the server as a daemon
palomad must be running at all times. It is recommended that you
palomad as a
systemd service so that it will be started
automatically when the system reboots.
palomad as a service
Create a service definition file in
[Unit] Description=Paloma Daemon After=network.target [Service] Type=simple User=<Paloma_USER> ExecStart=<PATH_TO_PalomaD>/palomad start Restart=on-abort [Install] WantedBy=multi-user.target [Service] LimitNOFILE=65535
Service section according to your environment:
- Enter the user (likely your username, unless you created a user
- Enter the path to the
/usr/go/bin. Confirm this with
- Make sure you made the correct edits to /etc/security/limits.conf
systemctl daemon-reload followed by
systemctl enable palomad.
This will register
palomad as a system service and turn it on upon startup.
Now start the serivce with
systemctl start palomad.
# Controlling the service
systemd to start, stop, and restart the service:
# Check health systemctl status palomad # Start systemctl start palomad # Stop systemctl stop palomad # Restart systemctl restart palomad
# Access logs
journalctl -t to access entire logs, entire logs in reverse,
and the latest and continuous log.
# Entire log reversed journalctl -t palomad -r # Entire log journalctl -t palomad # Latest and continuous journalctl -t palomad -f