I found the problem in my previous post, but it just uncovered another
problem. It seems that the script expects a upsd.pid file. I get a
upsmon.pid file but no upsd.pid file.I looked through the code and it
seems that upsd.c should create the file. My script works if I create
the upsd.pid
I loaded Ubuntu 6.06 which has kernel 2.6.15-28-386 and upsdrvcntrl stop
works as it should. See the attached output. I was running Ubuntu 6.10
which has kernel 2.6.17-generic. I could not find a way to switch to a
different kernel. I think I still have a problem with the script that
stops
Hi Gary,
I am no good at reading kernel logs; these are Greek to me.
The normal sequence is that upsd, upsmon, and the driver are all
stopped. Then 'upsdrvctl shutdown' is called as a standalone program
at the very end to turn off the power. (Neither a daemon nor a monitor
are required at that
I have attached a section of my syslog. It seems to say that newhidups
had a problem on the shutdown part of a restart. But before that upsd is
still running after newhidups has exited.
That is bad. It looks a lot like neither upsd, nor the driver have been
properly stopped before receiving
When I run upsdrvctl stop I get an error. I have attached the output
from stopping upsmon, upsd upsdrvctl. This is similar to what I get in
syslog for a normal shutdown now -r
Peter Selinger wrote:
Hi Gary,
I am no good at reading kernel logs; these are Greek to me.
The normal sequence
On 2/19/07, Gary Redden [EMAIL PROTECTED] wrote:
Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784748] BUG: unable to handle
kernel paging request at virtual address 76697264
Feb 18 14:57:57 ubuntu-desk-610 kernel: [ 1504.784767] printing eip:
Feb 18 14:57:57 ubuntu-desk-610 kernel: [
I do not have enough knowledge of Linux to answer those questions. I am
running Ubuntu desktop the GUI version so I must be running some nVidia
driver. I run the GUI version so I can poke around faster. I have spent
most of three weeks getting this far. I will continue to work on this
but need
I have attached a section of my syslog. It seems to say that newhidups
had a problem on the shutdown part of a restart. But before that upsd is
still running after newhidups has exited. This might be causing the
paging error. My script tries to shut down upsd before it runs upsdrvctl
stop. Am
I see. Sorry for that; my halt script looks very different. However, I
don't think it's a no-op; at least not if it's called with parameter
stop.
To test the shutdown script, you should of course not wait for the
battery to run down. You should use upsmon -c fsd.
-- Peter
Gary Redden wrote:
On 2/7/07, Gary Redden [EMAIL PROTECTED] wrote:
I am still not able to get the UPS to shutdown. Here is a list of rc0.d
and the file I created to shutdown the UPS after umountroot mounts the
filesystem read-only and before halt (halt seems to be a no op here. No
code under the start case).
Gary Redden wrote:
Nut will monitor the ups and shutdown Linux when the ups goes to low
battery as it should. But the UPS is not shut down so the system will
restart when the power is restored. If I switch the UPS off , restore
power and switch the UPS on the system will restart. I have not
On 2/6/07, Gary Redden [EMAIL PROTECTED] wrote:
See the poweroff section of the script. My question is:
Since I do not have much knowledge on how the Linux system boots and
shutdown I have spent the last several days searching for how the scrips
/etc/init.d are supposed to work but every thing
12 matches
Mail list logo
