sudo systemctl status influxdb
* influxdb.service - InfluxDB is an open-source, distributed, time series database
Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-12-01 19:24:27 EST; 1h 22min ago
Main PID: 14600 (influxd)
`-14600 /usr/bin/influxd -config /etc/influxdb/influxdb.conf
Dec 01 20:15:43 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:15:43 -0500] "POST /query?chunked=true&db=ruuvi&q=select+distinct%2 widen terminal
Dec 01 20:15:58 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:15:58 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+DISTINCT%2 window
Dec 01 20:16:15 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:16:15 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+DISTINCT%2 to see all
Dec 01 20:16:21 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:16:21 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+DISTINCT%2 of the
Dec 01 20:16:59 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:16:59 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+minium%28b log message
Dec 01 20:17:31 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:17:31 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+min%28batt
Dec 01 20:17:48 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:17:48 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+min%28batt
Dec 01 20:18:04 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:17:55 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+min%28batt
Dec 01 20:18:43 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:18:30 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+mac%2C+min
Dec 01 20:22:28 pi93graf influxd: [httpd] ::1 - - [01/Dec/2018:20:22:10 -0500] "POST /query?chunked=true&db=ruuvi&q=SELECT+mac%2C+min
Warning: influxdb.service changed on disk. Run 'systemctl daemon-reload' to reload units.
with status, number of journal lines to show, counting from the most recent ones. Default 10.
with status, formatting journal entries. see journalctl. Default |
--output=short| short-full| short-iso| short-precise| short-monotonic| short-unix| verbose| export|
json| json-pretty| json-sse| cat
show [jjj…|job…]] output only the value
Show properties of one or more units, jobs, or the manager itself. |
If no argument is specified, properties of the manager will be shown.
If a unit name is specified, properties of the unit are shown, and
if a job ID is specified, properties of the job are shown.
By default, empty properties are suppressed. Use
--all to show those too.
To select specific properties to show, use
used when parsable output is required. Use status for formatted human-readable output.
Features=+PAM +AUDIT +SELINUX +IMA +APPARMOR
+SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT
+GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +
UNKN = Wed 1969-12-31 19:00:00 EST
FinishTimestamp=Mon 2018-11-05 12:23:01 EST
GeneratorsStartTimestamp=Thu 2016-11-03 13:16:42 EDT
GeneratorsFinishTimestamp=Thu 2016-11-03 13:16:42 EDT
UnitsLoadStartTimestamp=Thu 2016-11-03 13:16:42 EDT
UnitsLoadFinishTimestamp=Thu 2016-11-03 13:16:43 EDT
i.e. FFFFFFFF FFFFFFFF
-p p[,p …
--property= p[,p …
show unit/job/manager properties with, limit display to properties specified, such as "MainPID". .
Shell completion is implemented for property names.
For the manager itself, systemctl show will show all available properties. See
Properties for units vary by unit type, so showing any unit lists properties pertaining to this type.
Showing any job will list properties pertaining to all jobs.
Properties are documented in
systemd.unit(5), and individual unit types systemd.service(5), systemd.socket
| Show backing files of one or more units. |
Prints the "fragment" and "drop-ins" (source files) of units.
Each file is preceded by a comment which includes the file name.
Shows the contents of the backing files on disk,
which may not match the system manager's understanding of these units if any unit files were updated on disk and the
daemon-reload command wasn't issued since.
| Set unit properties at runtime, changing configuration parameter
properties such as resource control settings at runtime. |
Not all properties may be changed at runtime, settings in systemd.resource-control(5)) may.
The changes are applied immediately and stored on disk . With
--runtime the settings only apply until the next boot.
The syntax of the property assignment follows the syntax of assignments in unit files.
systemctl set-property foobar.service CPUShares=777
If the unit appears to be inactive, the changes will be stored on disk and will be effective when the unit will be started.
Allows changing multiple properties at the same time, which is preferable over setting them individually.
Assigning the empty list to list parameters will reset the list.
| Show manual pages.
When a unit fails (example: exiting with non-zero error code, terminating abnormally or timing out), it
enters the "failed" state and its exit code and status is recorded until the service is restarted or reset with this command.
List unit files installed on the system, in combination with their enablement state (as reported by |
UNIT FILE STATE
290 unit files listed.
enable name…, path…
Creates a set of symlinks, as per the |
[Install] sections of the unit files.
--force overwrite any existing conflicting symlinks.
System manager configuration is reloaded to ensure the changes effected immediately unless
Does not start units being enabled (unless
--now or invoke start with appropriate arguments later.)
In case of unit instance enablement (i.e. enablement of units of the form firstname.lastname@example.org), symlinks named the same as instances are
created in the unit configuration directory, which point to the single template unit file they are instantiated from.
Expects unit names (in which case various unit file directories are automatically searched
for unit files with appropriate names), or absolute paths to unit files (in which case these files are read directly).
If a specified unit file is located outside of the usual unit file directories, an additional symlink is
created, linking it into the unit configuration path, thus ensuring it is found when requested by commands such as start.
Outputs file system operations executed, suppress with
Creates only the symlinks suggested in the
[Install] section of the unit files.
Changes can be made by placing or removing symlinks below this directory. Useful to
create configurations that deviate from the suggested default installation.
reload daemon to effect the changes
Depending on whether
--system, --user, --runtime, or --global is specified, this enables the unit for the system,
for the calling user only, for only this boot of the system, or for all future logins of all users, or only this boot.
in the last case, no systemd daemon configuration is reloaded.
masked units cannot be enabled.
--now units will be started if enabled.
reenable name …
Combination of |
enable and is
useful to reset the symlinks a unit file is enabled with to the defaults configured in its "[Install]" section.
Expects a unit name only, it does not accept paths to unit files.
Removes symlinks to the unit files backing the specified units from the unit
configuration directory, and undoes any changes made by |
Removes all symlinks to matching unit files, including manually created ones
Also= units are disable as well.
Not symmetric with
enable, as disable may remove
more symlinks than a prior enable invocation of the same unit created.
Does not implicitly stop the units that are being disable unless
--now or invoke the
outputs information about the file system operations (symlink removals) executed. may be suppressed with
--system, --user, --runtime and --global in a similar way as enable.
Reloads system manager configuration after completing the operation unless
--now the units disabled will be stopped
mask name …
Link these unit files to |
/dev/null, making it impossible to start them.
disable, since it prohibits all kinds of activation of the
unit, including enablement and manual activation. Use this option with care.
--now the units masked are stopped.
--runtime to only mask temporarily until the next reboot of the system.
Expects valid unit names only, it does not accept unit file paths.
unmask name …
| Unmask unit files. unit names only, not unit file paths.
preset name …
Reset the enable/disable status unit files, to the defaults configured
in the preset policy files. |
disable or enable depending how the unit is listed in the preset files.
If the unit ihas no install information, it will be silently ignored .
name must be the real unit name, alias names are ignored .
with the |
full (the default),
controls whether units shall be disabled and enabled according to the preset rules, or only enabled, or only disabled.
| Resets all installed unit files to the defaults configured in the |
preset policy file (see above).
| Made available through one or more symlinks to the unit file
/etc…or transiently in
/run…), even though the unit file might reside outside of the unit file search path.
Link a unit file that is not in the unit file search paths into the unit file search path. expects an
absolute path to a unit file. |
May be undone with
Makes a unit file available for commands such as
start even though it is not installed directly in the unit search path.
revert name …
Revert unit files to their vendor versions. Removes drop-in configuration files that modify
units, as well as any user-configured unit file that overrides a matching vendor supplied unit file.|
For a unit
foo.service the matching directories
foo.service.d/ with all their contained files are
removed, both below the persistent and runtime configuration directories (i.e. below
/run/systemd/system); if the unit file has a vendor-supplied version (i.e. a unit file located below /usr) any
matching persistent or runtime unit file that overrides it is removed.
If a unit file has no vendor-supplied version (i.e. is only defined below /etc/systemd/system or /run/systemd/system, but not in a unit
file stored below /usr), it is not removed. Masked units are unmasked.
Used to undo all changes made with
systemctl edit, systemctl set-property and
systemctl mask and puts the original unit file with its settings back in effect.
add-wants target name …
add-requires target name…
| Adds dependencies, |
sudo systemctl add-requires ruuvicollector.service influxdb.service
Created symlink /etc/systemd/system/ruuvicollector.service.requires/influxdb.service ->
edit name …
Edit a drop-in snippet or a whole replacement file |
--full is specified, to extend or override the specified unit.
Depending on whether
--system (the default),
--global is specified,
creates a drop-in file
for each unit either for the system, for the calling user, or for all futures logins of all users.
Then, the editor (see the "Environment" section below) is invoked on temporary files which will be written to the real location if the
editor exits successfully.
--full copy the original units instead of creating drop-in files.
--force unit files will be created for editing if they don't exist.
--runtime changes will be made temporarily in
/run and they will be lost on the next reboot.
If the temporary file is empty upon exit, the modification of the related unit is canceled.
After the units have been edited, systemd configuration is reloaded (
Cannot be used to remotely edit units and cannot temporarily edit units which are in
/etc, since they take precedence over
| Return the default target to boot into. target unit name |
default.target is aliased (symlinked) to.
| Set the default target to boot into. This sets (symlinks) the default.target alias to the given target unit.
Allowed only on units where |
AllowIsolate= is enabled.
grep AllowIsolate /etc/systemd/system
name and its dependencies and stop all others.
If no extension is given,
.target is used is used
Similar to changing the runlevel in a traditional
Immediately stops processes not enabled in the new unit, possibly including the graphical environment or terminal you are currently using.!,
Units not active and are not in a failed state usually are not in memory, and will not be matched by any pattern. |
In case of instantiated units, systemd is often unaware of the instance name until the instance has been started.
using glob patterns with
start has limited usefulness, secondary alias names of units are not considered.
| deactivate (issues |
| if the units are running.
Reload units if they support |
reload. If not,
restart them ( most do not include reload) small>.
| If not running , they will be started.
| Asks units to reload their configuration. ( most do not include reload)|
Reloads the service-specific configuration, not the unit configuration file of systemd.
To reload the configuration file of a unit, use the
Example: Apache: Apache's
httpd.conf in the web server, not the apache.service systemd unit file.
sudo systemctl reload influxdb
Failed to reload influxdb.service: Job type reload is not applicable for unit influxdb.service.
See system logs and 'systemctl status influxdb.service' for details.
reload if they support it. If not,
If the units are not running they will be started.
| Send a signal to one or more processes of the unit.
with kill, |
SIGTERM, SIGINT or SIGSTOP. default:
| with kill, which processes to send a signal to. |
Must be one of
all to select
whether to kill only the main process, the control process or all processes of the unit.
The main process of the unit is the one that defines the life-time of it.
A control process of a unit is one that is invoked by the manager to induce state changes of it.
For example, all processes started due to the
ExecStartPre=, ExecStop= or ExecReload=
settings of service units are control processes.
there is only one control process per unit at a time, as only one state change is executed at a time.
For services of type
Type=forking, the initial process started by the
ExecStart= is a control process, while the process ultimately forked off by that one is then considered
the main process of the unit (if it can be determined). This is different for service units of other types, where the
process forked off by the manager for ExecStart= is always the main process itself. A service unit consists of zero
or one main process, zero or one control process plus any number of additional processes. Not all unit types manage
processes of these types however. For example, for mount units, control processes are defined (which are the
invocations of /bin/mount and /bin/umount), but no main process is defined. If omitted, defaults to all.
| with the kill command, if no units were killed, results in an error.