On Wednesday 29 Oct 2003 5:46 pm, James Sparenberg wrote: > On Wed, 2003-10-29 at 07:48, Anne Wilson wrote: > > On Wednesday 29 Oct 2003 12:57 pm, Brian V Bonini wrote: > > > On Wed, 2003-10-29 at 05:34, Anne Wilson wrote: > > > > My ups is working well, but I would like to use the > > > > monitoring software. Unfortunately I seem to have a config > > > > problem, which I don't understand. These are the error > > > > messages: > > > > > > > > Wed Oct 29 09:53:14 GMT 2003 Cannot create > > > > /var/lock/subsys/apcupsd/LCK..ttyS0 serial port lock file: > > > > ERR=No such file or directory > > > > Wed Oct 29 09:53:14 GMT 2003 apcupsd FATAL ERROR in > > > > apcdevice.c at line 87 > > > > Unable to create UPS lock file. > > > > Wed Oct 29 09:53:14 GMT 2003 apcupsd error shutdown > > > > completed > > > > > > > > The directory /var/lock/subsys/apcupsd exists. Why can't it > > > > create the lock file? > > > > > > > > Anne > > > > > > I guess the first obvious question is does the dir have the > > > correct permissions for whatever apcupsd is running as? On my > > > system it runs as root. And, are you sure there is a > > > /var/lock/subsys/apcupsd directory? I have a apcupsd file in > > > /var/lock/subsys/ but no apcupsd directory... > > > > I think you pointed me at the solution <g>. I created the > > /var/lock/subsys/apcupsd directory, because it seemed to want to > > use that to create the lock file. However, I now think I was > > wrong. I have deleted that directory. There is a file > > /var/lock/subsys/apcupsd, which must be used in the lock file > > creation. We'll see what happens at the next reboot, but I think > > that is right. > > > > Anne > > Note that they are files in this dir not directories. From my > experience (as useless as it may be.) these are just 0 byte files > that get touched by a product to signal that it is running. I've > seen the create error a number of times when a process dies > incorrectly and this file is left behind. The next time it starts > it can't touch the file and fails to start because the program > doesn't know how to recover from this condition. If you remove it > from this dir is the program then able to start correctly? > > James
Hi, James. I had ended up with a directory and a file with the same name. Unfortunately, even after deleting the directory, all is not well. The upsmon program is not as well documented as apcupsd, imo, so I accept that my config file is faulty, but I don't know how to correct it. Do the errors in the attached file tell you what I need to do? Anne -- Registered Linux User No.293302 Have you visited http://twiki.mdklinuxfaq.org yet?
Oct 29 19:05:57 anne-linux apcupsd[1434]: apcupsd FATAL ERROR in apcdevice.c at line 87 Unable to create UPS lock file. Oct 29 19:05:57 anne-linux apcupsd[1434]: apcupsd error shutdown completed Oct 29 19:05:57 anne-linux apcupsd: failed Oct 29 19:05:58 anne-linux upsmon: Network UPS Tools upsmon 1.2.1 Oct 29 19:05:58 anne-linux upsmon: Oct 29 19:05:58 anne-linux upsmon: Fatal error: insufficient power configured! Oct 29 19:05:58 anne-linux upsmon: Oct 29 19:05:58 anne-linux upsmon: Sum of power values........: 0 Oct 29 19:05:58 anne-linux upsmon: Minimum value (MINSUPPLIES): 2 Oct 29 19:05:58 anne-linux upsmon: Oct 29 19:05:58 anne-linux upsmon: Edit your upsmon.conf and change the values. Oct 29 19:05:58 anne-linux upsmon: upsmon.conf: invalid directive MONITOR anne-linux Oct 29 19:05:58 anne-linux upsmon: Using power down flag file /etc/killpower Oct 29 19:05:58 anne-linux upsmon: Oct 29 19:05:58 anne-linux upsmon: upsmon.conf: invalid directive EXEC - Execute NOTIFYCMD (see above) with the message Oct 29 19:05:58 anne-linux upsmon: NUT Starting UPS monitor: failed
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
