|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
pcnet not working?Hi guys,
I'm fairly new to apcupsd but have trawled through the mailing list and manual with no joy. I'm using a APC Smart-UPS 3000 with a AP9619 management card. I'm looking to have apcupsd communicate with the management card and shutdown itself, and eventually about half a dozen other servers. I also have 2x APC Smart-UPS 1500s which I'll connect up via serial or usb once I have the pcnet integration working - but this is separate for the moment. I've tried the debian package (3.12.4-2) and I've tested 3.14.3 and 3.14.4 from the source (./configure --enable-pcnet). I've set the powerchute shutdown auth phrase to 'fred' for testing (yes, I've added the client ip to the powerchute client list) and my apcupsd.conf file contains the following: ## apcupsd.conf v1.1 ## UPSCABLE ether UPSTYPE pcnet DEVICE 192.168.0.26:admin:fred LOCKFILE /var/lock UPSCLASS standalone #UPSCLASS netmaster UPSMODE disable #UPSMODE sharenet NETSERVER on NISPORT 3551 I've tried various options including running: apcupsd -d1000 -T Within the trace file I keep getting: 42.004 apcupsd: pcnet.c:426 process_packet: line='SH=5154E6DD55549B789AA9AB67F34DA431' 42.004 apcupsd: pcnet.c:434 process_packet: key='SH' value='5154E6DD55549B789AA9AB67F34DA431' 42.004 apcupsd: pcnet.c:426 process_packet: line='MD=b2e9d6cd90359a732f20412e41cb305a' 42.004 apcupsd: pcnet.c:434 process_packet: key='MD' value='b2e9d6cd90359a732f20412e41cb305a' 42.004 apcupsd: pcnet.c:426 process_packet: line='</BODY>' 42.004 apcupsd: pcnet.c:444 process_packet: calculated=912be3b4e49581e6ac9b0552ec47c4d6 42.004 apcupsd: pcnet.c:447 process_packet: message hash failed And I'm also receiving alerts for: Broadcast Message from root@dns2 (somewhere) at 14:50 ... Warning communications lost with UPS dns2 I can perform apcaccess status: # apcaccess status APC : 001,019,0464 DATE : Fri Jun 06 14:48:49 BST 2008 HOSTNAME : dns2 RELEASE : 3.14.4 VERSION : 3.14.4 (18 May 2008) debian UPSNAME : dns2 CABLE : Ethernet Link MODEL : PCNET UPS Driver UPSMODE : Stand Alone STARTTIME: Fri Jun 06 14:48:41 BST 2008 STATUS : MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds NUMXFERS : 0 TONBATT : 0 seconds CUMONBATT: 0 seconds XOFFBATT : N/A STATFLAG : 0x07000000 Status Flag END APC : Fri Jun 06 14:48:49 BST 2008 Is there anything really obvious that I'm missing? Any ideas? SG ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Apcupsd-users mailing list Apcupsd-users@... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
|
|
Re: pcnet not working?Simon Gray wrote:
> Hi guys, > > I'm fairly new to apcupsd but have trawled through the mailing list > and manual with no joy. I'm using a APC Smart-UPS 3000 with a AP9619 > management card. I'm looking to have apcupsd communicate with the > management card and shutdown itself, and eventually about half a dozen > other servers. I also have 2x APC Smart-UPS 1500s which I'll connect > up via serial or usb once I have the pcnet integration working - but > this is separate for the moment. What firmware version does your AP9619 have? > I've tried the debian package (3.12.4-2) and I've tested 3.14.3 and > 3.14.4 from the source (./configure --enable-pcnet). I've set the > powerchute shutdown auth phrase to 'fred' for testing (yes, I've added > the client ip to the powerchute client list) and my apcupsd.conf file > contains the following: > > ## apcupsd.conf v1.1 ## > UPSCABLE ether > UPSTYPE pcnet > DEVICE 192.168.0.26:admin:fred > LOCKFILE /var/lock > UPSCLASS standalone > #UPSCLASS netmaster > UPSMODE disable > #UPSMODE sharenet > NETSERVER on > NISPORT 3551 That all looks good. The IP address of the UPS in the DEVICE line is critical, so be sure to double-check that. > I've tried various options including running: apcupsd -d1000 -T > > Within the trace file I keep getting: > > 42.004 apcupsd: pcnet.c:426 process_packet: > line='SH=5154E6DD55549B789AA9AB67F34DA431' > 42.004 apcupsd: pcnet.c:434 process_packet: key='SH' > value='5154E6DD55549B789AA9AB67F34DA431' > 42.004 apcupsd: pcnet.c:426 process_packet: > line='MD=b2e9d6cd90359a732f20412e41cb305a' > 42.004 apcupsd: pcnet.c:434 process_packet: key='MD' > value='b2e9d6cd90359a732f20412e41cb305a' > 42.004 apcupsd: pcnet.c:426 process_packet: line='</BODY>' > 42.004 apcupsd: pcnet.c:444 process_packet: > calculated=912be3b4e49581e6ac9b0552ec47c4d6 > 42.004 apcupsd: pcnet.c:447 process_packet: message hash failed Ok, clearly an authentication failure. Could you send me (privately) a full trace log? > And I'm also receiving alerts for: > > Broadcast Message from root@dns2 > (somewhere) at 14:50 ... > > Warning communications lost with UPS dns2 Expected because all the data from the UPS is being tossed on the floor due to the authentication failure. --Adam ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Apcupsd-users mailing list Apcupsd-users@... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
|
|
A problem...I am running SuSE 10.3 and trying to get it to connect with Smart-UPS
1400 using a AP9618 Network Management Card. The AP9618 lists this information about itself: Description : Smart-UPS & Matrix-UPS APP ----------------------------------------------------------------------- Name : sumx Type : StatApp Version : 331 Sector : 16 Date : 01/05/2007 Time : 15:59:40 CRC16 : 410D Description : Network Management Card AOS ----------------------------------------------------------------------- Name : aos Type : APC OS Version : 334 Sector : 47 Date : 01/05/2007 Time : 14:23:44 CRC16 : 2D13 I downloaded apcupsd version 3.14.4 at tried to compile and install it. The ./configure and make went fine. However, when I su'd to root and did the 'make install' it failed. It was fine until it got to the SuSE specific section. Then I downloaded the latest version on 06-Jun-2008 using cvs. I did ./configure and make having no problems. When I tried the 'make install' I received the same errors: ------------------------------------------------------------ SuSE distribution installation ------------------------------------------------------------ apcupsd: unknown service make[3]: *** [install-suse] Error 1 make[2]: *** [install] Error 2 make[1]: *** [suse_DIR] Error 2 make: *** [platforms_DIR] Error 2 Ted ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Apcupsd-users mailing list Apcupsd-users@... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
|
|
Re: pcnet not working?Thanks for the reply.
Adam Kropelin wrote: > Simon Gray wrote: > >> Hi guys, >> >> I'm fairly new to apcupsd but have trawled through the mailing list >> and manual with no joy. I'm using a APC Smart-UPS 3000 with a AP9619 >> management card. I'm looking to have apcupsd communicate with the >> management card and shutdown itself, and eventually about half a dozen >> other servers. I also have 2x APC Smart-UPS 1500s which I'll connect >> up via serial or usb once I have the pcnet integration working - but >> this is separate for the moment. >> > > What firmware version does your AP9619 have? > v3.5.5 (c) Copyright 2007 All Rights Reserved Smart-UPS & Matrix-UPS APP v3.5.5 http://www.apc.com/resource/include/techspec_index.cfm?base_sku=AP9619&tab=Software afaik the latest ^^ > >> I've tried the debian package (3.12.4-2) and I've tested 3.14.3 and >> 3.14.4 from the source (./configure --enable-pcnet). I've set the >> powerchute shutdown auth phrase to 'fred' for testing (yes, I've added >> the client ip to the powerchute client list) and my apcupsd.conf file >> contains the following: >> >> ## apcupsd.conf v1.1 ## >> UPSCABLE ether >> UPSTYPE pcnet >> DEVICE 192.168.0.26:admin:fred >> LOCKFILE /var/lock >> UPSCLASS standalone >> #UPSCLASS netmaster >> UPSMODE disable >> #UPSMODE sharenet >> NETSERVER on >> NISPORT 3551 >> > > That all looks good. The IP address of the UPS in the DEVICE line is > critical, so be sure to double-check that. > > >> I've tried various options including running: apcupsd -d1000 -T >> >> Within the trace file I keep getting: >> >> 42.004 apcupsd: pcnet.c:426 process_packet: >> line='SH=5154E6DD55549B789AA9AB67F34DA431' >> 42.004 apcupsd: pcnet.c:434 process_packet: key='SH' >> value='5154E6DD55549B789AA9AB67F34DA431' >> 42.004 apcupsd: pcnet.c:426 process_packet: >> line='MD=b2e9d6cd90359a732f20412e41cb305a' >> 42.004 apcupsd: pcnet.c:434 process_packet: key='MD' >> value='b2e9d6cd90359a732f20412e41cb305a' >> 42.004 apcupsd: pcnet.c:426 process_packet: line='</BODY>' >> 42.004 apcupsd: pcnet.c:444 process_packet: >> calculated=912be3b4e49581e6ac9b0552ec47c4d6 >> 42.004 apcupsd: pcnet.c:447 process_packet: message hash failed >> > > Ok, clearly an authentication failure. Could you send me (privately) a full > trace log? > > >> And I'm also receiving alerts for: >> >> Broadcast Message from root@dns2 >> (somewhere) at 14:50 ... >> >> Warning communications lost with UPS dns2 >> > > Expected because all the data from the UPS is being tossed on the floor due > to the authentication failure. > > --Adam SG ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Apcupsd-users mailing list Apcupsd-users@... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
|
|
Re: pcnet not working?Simon Gray wrote:
> Adam Kropelin wrote: >> Ok, clearly an authentication failure. Could you send me (privately) >> a full trace log? >> > Sent Thanks for the log. I believe I figured out what is going on. It's actually a configuration issue. I was able to reproduce the problem here essentially by accident. There are two issues: 1. The Apcupsd documentation is wrong about the username. The default username is 'apc' *not* 'admin'. I went back to my original notes when I figured out the authentication scheme the first time and I clearly wrote 'apc'. But I apparently wrote it incorrectly in the docs. 2. The Web/SNMP card requires that the PCNET password be a *minimum* of 15 characters. If you enter a shorter password, it silently ignores it and retains the existing password. No error message is given. (How's that for 'user friendly'?). I figured that one out by trial and error. It ignores a 14 character password but accepts a 15 character one. Anything from 15 - 32 characters seems to be ok. So, try fixing those two things and I will update the documentation. Please send an email to the list to let us know if this fixes it for you (or not)... --Adam ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Apcupsd-users mailing list Apcupsd-users@... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
|
|
Re: pcnet not working?Adam Kropelin wrote:
> Thanks for the log. I believe I figured out what is going on. It's > actually > a configuration issue. I was able to reproduce the problem here essentially > by accident. There are two issues: > > 1. The Apcupsd documentation is wrong about the username. The default > username is 'apc' *not* 'admin'. I went back to my original notes when I > figured out the authentication scheme the first time and I clearly wrote > 'apc'. But I apparently wrote it incorrectly in the docs. > > 2. The Web/SNMP card requires that the PCNET password be a *minimum* of 15 > characters. If you enter a shorter password, it silently ignores it and > retains the existing password. No error message is given. (How's that for > 'user friendly'?). I figured that one out by trial and error. It ignores a > 14 character password but accepts a 15 character one. Anything from 15 - 32 > characters seems to be ok. > > So, try fixing those two things and I will update the documentation. Please > send an email to the list to let us know if this fixes it for you (or > not)... > > --Adam > ## apcupsd.conf v1.1 ## UPSCABLE ether UPSTYPE pcnet DEVICE 192.168.0.26:apc:123456789012345 36.744 apcupsd: pcnet.c:444 process_packet: calculated=2298e4ac7eb80b89968351aa66887bd9 36.744 apcupsd: pcnet.c:450 process_packet: message hash passed 36.744 apcupsd: pcnet.c:458 process_packet: Expected IP=192.168.0.26 36.744 apcupsd: pcnet.c:459 process_packet: Received IP=192.168.0.26 36.744 apcupsd: pcnet.c:486 process_packet: Our reboots=8 36.744 apcupsd: pcnet.c:487 process_packet: UPS reboots=8 36.745 apcupsd: pcnet.c:488 process_packet: Our uptime=44436522 36.745 apcupsd: pcnet.c:489 process_packet: UPS uptime=44439119 SG ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Apcupsd-users mailing list Apcupsd-users@... https://lists.sourceforge.net/lists/listinfo/apcupsd-users |
| Free Forum Powered by Nabble | Forum Help |