1UPSD(8)                           NUT Manual                           UPSD(8)
2
3
4

NAME

6       upsd - UPS information server
7

SYNOPSIS

9       upsd -h
10
11       upsd [OPTIONS]
12

DESCRIPTION

14       upsd is responsible for serving the data from the drivers to the
15       clients. It connects to each driver and maintains a local cache of the
16       current state. Queries from the clients are served from this cache, so
17       delays are minimal.
18
19       It also conveys administrative messages from the clients back to the
20       drivers, such as starting tests, or setting values.
21
22       Communication between upsd and clients is handled on a TCP port.
23       Configuration details for this port are described in upsd.conf(8).
24
25       This program is essential, and must be running at all times to actually
26       make any use out of the drivers and clients.
27
28       Controls in the configuration files allow you to limit access to the
29       server, but you should also use a firewall for extra protection. Client
30       processes such as upsmon(8) trust upsd for status information about the
31       UPS hardware, so keep it secure.
32

OPTIONS

34       -c command
35           Send command to the background process as a signal. Valid commands
36           are:
37
38           reload
39               reread configuration files
40
41           stop
42               stop process and exit
43
44       -P pid
45           Send the command signal above using specified PID number, rather
46           than consulting the PID file. This can help define service units
47           which start upsd as a foreground process so it does not create a
48           PID file. See also -FF option as an alternative.
49
50       -D
51           Raise the debugging level. upsd will run in the foreground by
52           default, and will print information on stdout about the monitoring
53           process. Use this option multiple times for more details.
54
55       -F
56           upsd will run in the foreground, regardless of debugging settings.
57           Specify twice (-FF or -F -F) to save the PID file even in this
58           mode.
59
60       -B
61           upsd will run in the background, regardless of debugging settings.
62
63       -h
64           Display the help text.
65
66       -r directory
67           upsd will chroot(2) to directory shortly after startup and before
68           parsing any configuration files with this option set. You can use
69           this to create a "jail" for greater security.
70
71           You must coordinate this with your drivers, as upsd must be able to
72           find the state path within directory. See upsdrvctl(8) and
73           nutupsdrv(8).
74
75       -u user
76           Switch to user user after startup if started as root. This
77           overrides whatever you may have compiled in with configure
78           --with-user.
79
80       -V
81           Display the version of the program.
82

RELOADING

84       upsd can reload its configuration files without shutting down the
85       process if you send it a SIGHUP or start it again with -c reload. This
86       only works if the background process is able to read those files.
87
88       If you think that upsd can’t reload, check your syslog for error
89       messages. If it’s complaining about not being able to read the files,
90       then you need to adjust your system to make it possible. Either change
91       the permissions on the files, or run upsd as another user that will be
92       able to read them.
93
94       DO NOT make your upsd.conf or upsd.users world-readable, as those files
95       hold important authentication information. In the wrong hands, it could
96       be used by some evil person to spoof your primary-mode upsmon and
97       command your systems to shut down.
98

DIAGNOSTICS

100       upsd expects the drivers to either update their status regularly or at
101       least answer periodic queries, called pings. If a driver doesn’t
102       answer, upsd will declare it "stale" and no more information will be
103       provided to the clients.
104
105       If upsd complains about staleness when you start it, then either your
106       driver or configuration files are probably broken. Be sure that the
107       driver is actually running, and that the UPS definition in ups.conf(5)
108       is correct. Also make sure that you start your driver(s) before
109       starting upsd.
110
111       Data can also be marked stale if the driver can no longer communicate
112       with the UPS. In this case, the driver should also provide diagnostic
113       information in the syslog. If this happens, check the serial or USB
114       cabling, or inspect the network path in the case of a SNMP UPS.
115

ACCESS CONTROL

117       If the server is build with tcp-wrappers support enabled, it will check
118       if the NUT username is allowed to connect from the client address
119       through the /etc/hosts.allow and /etc/hosts.deny files. Note that this
120       will only be done for commands that require to be logged into the
121       server. Further details are described in hosts_access(5).
122

FILES

124       The general upsd configuration file is upsd.conf(5). The administrative
125       functions like SET and INSTCMD for users are defined and controlled in
126       upsd.users(5). UPS definitions are found in ups.conf(5).
127

ENVIRONMENT VARIABLES

129       NUT_CONFPATH is the path name of the directory that contains upsd.conf
130       and other configuration files. If this variable is not set, upsd uses a
131       built-in default, which is often /usr/local/ups/etc.
132
133       NUT_STATEPATH is the path name of the directory in which upsd keeps
134       state information. If this variable is not set, upsd uses a built-in
135       default, which is often /var/state/ups. The STATEPATH directive in
136       upsd.conf(5) overrides this variable.
137
138       NUT_ALTPIDPATH is the path name of the directory in which upsd and
139       drivers store .pid files. If this variable is not set, upsd and drivers
140       use either NUT_STATEPATH if set, or ALTPIDPATH if set, or otherwise the
141       built-in default STATEPATH.
142

SEE ALSO

144   Clients:
145upsc(8)
146
147upscmd(8)
148
149upsrw(8)
150
151upslog(8)
152
153upsmon(8)
154
155   CGI programs:
156upsset.cgi(8)
157
158upsstats.cgi(8)
159
160upsimage.cgi(8)
161
162   Driver control:
163nut-driver-enumerator(8)
164
165upsdrvctl(8)
166
167upsdrvsvcctl(8)
168
169   Drivers:
170nutupsdrv(8)
171
172adelsystem_cbi(8)
173
174al175(8)
175
176apcsmart-old(8)
177
178apcsmart(8)
179
180apcupsd-ups(8)
181
182asem(8)
183
184bcmxcp(8)
185
186bcmxcp_usb(8)
187
188belkin(8)
189
190belkinunv(8)
191
192bestfcom(8)
193
194bestfortress(8)
195
196bestuferrups(8)
197
198bestups(8)
199
200       •   blazer-common(8)
201
202blazer_ser(8)
203
204blazer_usb(8)
205
206clone(8)
207
208dummy-ups(8)
209
210etapro(8)
211
212everups(8)
213
214gamatronic(8)
215
216generic_modbus(8)
217
218genericups(8)
219
220huawei-ups2000(8)
221
222isbmex(8)
223
224ivtscd(8)
225
226liebert-esp2(8)
227
228liebert(8)
229
230       •   macosx-ups(8)
231
232masterguard(8)
233
234metasys(8)
235
236mge-shut(8)
237
238mge-utalk(8)
239
240microdowell(8)
241
242microsol-apc(8)
243
244netxml-ups(8)
245
246nut-ipmipsu(8)
247
248nutdrv_atcl_usb(8)
249
250nutdrv_qx(8)
251
252nutdrv_siemens_sitop(8)
253
254oneac(8)
255
256optiups(8)
257
258phoenixcontact_modbus(8)
259
260pijuice(8)
261
262powercom(8)
263
264       •   powerman-pdu(8)
265
266powerpanel(8)
267
268rhino(8)
269
270richcomm_usb(8)
271
272riello_ser(8)
273
274riello_usb(8)
275
276safenet(8)
277
278snmp-ups(8)
279
280socomec_jbus(8)
281
282solis(8)
283
284tripplite(8)
285
286tripplite_usb(8)
287
288tripplitesu(8)
289
290upscode2(8)
291
292usbhid-ups(8)
293
294victronups(8)
295
296   Internet resources:
297       The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
298
299
300
301Network UPS Tools 2.8.0           04/26/2022                           UPSD(8)
Impressum