FOLLOW-UP: apcupsd on e250/sol8 - tty error
From: tim guinn (guinn_at_mail.utexas.edu)
Date: 11/11/03
- Previous message: Loukinas, Jeremy: "Batch password reset help."
- In reply to: tim guinn: "apcupsd on e250/sol8 - tty error"
- Next in thread: Robert Milkowski: "kernel memory leak?"
- Reply: Robert Milkowski: "kernel memory leak?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 11 Nov 2003 12:02:07 -0600 To: sunmanagers@sunmanagers.org
thanks to those who have replied (andy and dave). i also benefitted from reading the post yesterday from marian re 'ups serial connect trouble'.
andy pointed out that indeed apcupsd 3.10.6 isn't working for sparc/solaris, so i'm at least happy that the version i'm trying to work with ~should~ work ... <g>
at this point, i know part of the trouble lies in the fact that port monitors are running on both ttya and ttyb. i have tried using sacadm and pmadm as follows, with output indicated
'bash-2.03$ sudo sacadm -l'
PMTAG PMTYPE FLGS RCNT STATUS COMMAND
zsmon ttymon - 0 NO_SAC /usr/lib/saf/ttymon #
bash-2.03$ sudo pmadm -l -p zsmon
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
zsmon ttymon ttya u root /dev/term/a I - /usr/bin/login - \
9600 ldterm,ttcompat ttya login: - tvi925 y #
zsmon ttymon ttyb u root /dev/term/b I - /usr/bin/login - \
9600 ldterm,ttcompat ttyb login: - tvi925 y #
so i tried doing
'bash-2.03$ sudo sacadm -k -p zsmon'
to stop the monitor and got "can not contact sac".
judging by the status msg 'no_sac' i'm wondering what's best way of terminating the monitor process? just kill it?
additionally, i've tried hunting down the method by which sac would be implemented, but without much luck. nothing in inittab or /etc/init.d that i can identify...
fwiw, a predecessor ran 'yassp' on this particular system and i have a feeling it might have moved stuff around so 'what should be isn't what is' ... following up on that, later, when i go to the site.
any insight wrt stuff above much appreciated!
ps it's worth mentioning that i tried contacting the apcupsd developer (twice) and neither msg has been answered; hence, my efforts in this forum.
thx
On 2003.11.10 16:00, tim guinn wrote:
greetings-
bash-2.03$ uname -a
SunOS fooz 5.8 Generic_108528-24 sun4u sparc SUNW,Ultra-250
trying to get apcupsd-3.8.6 working. could never get (latest) 3.10.6 to compile w/o errors, however, the older version 'seems' to have built okay. 'seems' because of the following error...
when doing 'sudo /etc/opt/apcupsd/sbin/apctest' i get:
2003-11-10 15:37:56 apctest 3.8.6 (5 February 2003) sun
Checking configuration ...
sharenet.type = DISABLE
cable.type = CUSTOM_SMART
You are using a SMART cable type, so I'm entering SMART test mode
mode.type = SMART
Setting up serial port ...
apctest FATAL ERROR in apcserial.c at line 173
PANIC! Cannot communicate with UPS via serial port.
apctest FATAL ERROR in apcserial.c at line 173
PANIC! Cannot communicate with UPS via serial port.
apctest error shutdown completed
the apcupsd.conf file is config'd so it should use /dev/ttya, and in fact, the smart cable is indeed plugged into that port.
wondering if anyone else here is familiar with this problem? any suggestions as to how i can better test/diagnose the problem? i will summarize for the list if anything useful rec'd in response.
-- tim guinn senior systems analyst you are not what you own _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Previous message: Loukinas, Jeremy: "Batch password reset help."
- In reply to: tim guinn: "apcupsd on e250/sol8 - tty error"
- Next in thread: Robert Milkowski: "kernel memory leak?"
- Reply: Robert Milkowski: "kernel memory leak?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
