APC Back-UPS650_CS [solved]

[AussieJohn]

Thanks Ian, for keeping a watch on me. Greatly appreciated.

Does the following result mean anything to you ???.

 

[john@localhost ~]$ netstat -tunlip
Kernel Interface table
Iface	   MTU Met	RX-OK RX-ERR RX-DRP RX-OVR	TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0	   1500   0  1076430	  0	  0	  0   712495	  0	  0	  0 BMRU
eth1	   1500   0		0	  0	  0	  0		0	  0	  0	  0 BMU
lo		16436   0	   28	  0	  0	  0	   28	  0	  0	  0 LRU
[john@localhost ~]$

 

I don't know what it all means other than etho is my internet connection.

 

Cheers. John.

[spinynorman]

John - I don't know what it means either, but I've put your output in a code box to make it easier to read. :)

[ianw1974]

Does the following result mean anything to you ???.

...

 

You put an i in the command, so it didn't give what I was quite after :). It is tunlp (TUNLP in uppercase for easier identification). You should get something like this:

 

ian@europa:~$ su
Password: 
root@europa:/home/ian# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address		   Foreign Address		 State	   PID/Program name   
tcp		0	  0 127.0.0.1:2208		  0.0.0.0:*			   LISTEN	 5175/hpiod		  
tcp		0	  0 0.0.0.0:6000			0.0.0.0:*			   LISTEN	 5107/X			  
tcp		0	  0 0.0.0.0:22			  0.0.0.0:*			   LISTEN	 5301/sshd		   
tcp		0	  0 127.0.0.1:631		   0.0.0.0:*			   LISTEN	 5151/cupsd		  
tcp		0	  0 127.0.0.1:2207		  0.0.0.0:*			   LISTEN	 5178/python		 
udp		0	  0 0.0.0.0:32768		   0.0.0.0:*						  5040/avahi-daemon:  
udp		0	  0 0.0.0.0:5353			0.0.0.0:*						  5040/avahi-daemon:  
udp		0	  0 172.20.12.17:123		0.0.0.0:*						  5389/ntpd		   
udp		0	  0 127.0.0.1:123		   0.0.0.0:*						  5389/ntpd		   
udp		0	  0 0.0.0.0:123			 0.0.0.0:*						  5389/ntpd

 

this is an example from my machine, of course ignore what I've got running, but you can at least see the correct format and what should be listed when you run the command.

[AussieJohn]

Sorry Ian for the dopey booboo. Thanks Spinynorman for making that change. I only know the old copy and paste method.

I ran it again but this time as root so I hope I got it right this time for you.

 

 

[john@localhost ~]$ su
Password:
[root@localhost john]# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address			   Foreign Address			 State	   PID/Progr
am name
tcp		0	  0 0.0.0.0:35586			   0.0.0.0:*				   LISTEN	  3199/ekpd

tcp		0	  0 0.0.0.0:3493				0.0.0.0:*				   LISTEN	  3542/upsd

tcp		0	  0 0.0.0.0:199				 0.0.0.0:*				   LISTEN	  4290/snmp
d
tcp		0	  0 0.0.0.0:631				 0.0.0.0:*				   LISTEN	  4380/cups
d
tcp		0	  0 :::631					  :::*						LISTEN	  4380/cups
d
udp		0	  0 0.0.0.0:161				 0.0.0.0:*							   4290/snmp
d
udp		0	  0 0.0.0.0:68				  0.0.0.0:*							   4120/dhcl
ient
udp		0	  0 10.0.0.1:123				0.0.0.0:*							   5425/ntpd

udp		0	  0 127.0.0.1:123			   0.0.0.0:*							   5425/ntpd					   
udp		0	  0 0.0.0.0:123				 0.0.0.0:*							   5425/ntpd					   
udp		0	  0 fe80::211:d8ff:fef9:123	 :::*									5425/ntpd					   
udp		0	  0 ::1:123					 :::*									5425/ntpd					   
udp		0	  0 :::123					  :::*									5425/ntpd					   
[root@localhost john]#

 

 

Cheers. John

[ianw1974]

OK, what I see here is that not a lot is listening on 127.0.0.1. But I do see the ups listening on 0.0.0.0 which should have been able to pick up both the ethernet card as well as the localhost for connecting to it.

 

What I'd be tempted to do is reconfigure the app you had configured for localhost to look at the IP of your ethernet card instead (hope it's static ip!), and then see if it makes a difference. You'll see in the end column the upsd, which shows you which port and what it's listening on.

 

There's no nis services running though, I would look in services for netfs, portmap and see if these are enabled or disabled as these normally provide nis services. Although, I wouldn't have expected these to be enabled for simple monitoring of a UPS device! These are normally for file sharing, unless I'm mistaken.

 

EDIT:

 

I fixed your little copy/paste bit. It's nice and simple, all you do for putting it in the little code box is to type [ code ] but without the spaces between the code and the square brackets. At the end of the paste, finish it off with [ /code ] again without the spaces. Then it appears nice and neatly formatted :)

 

I think there is even a button there when editing (in full mode) for putting the code stuff in place.

[AussieJohn]

Thanks Ian.

 

I had a bit of a fiddle but couldn't make any sense of it. Had a number of weird things happening and with a fair bit of cooker in there I decided to try something very different.

 

I reformatted..... /....... and..... /home...... and did a clean install with the absolutely barest minimum possible to just get the OS up and running (was about 850mbs). I even went through every rpm shown in the packages selection process and unticked everything that was not related to anything that I normally use. You would be astounded at the amount of packages that are unecessarily installed.......about 450mbs worth. Then I installed everything I wanted from online rather than from the dvd. This way I only had about 8 updates and every application was fresh rather than updated.

 

This of course included apcupsd (backend) and apcupsd-gapcmon (frontend gui). Imagine my shock when I had ups monitoring running in just 30secs. Yes just 30sec and no tweaking required.

 

See the enclosed snapshots of how it all looks. It is everything I had hoped it would be.

 

My problem is now gone but I still don't know how it was resolved. As you pointed to the localhost aspect it is interesting that it says localhost@localhost.

 

I have PCLinuxOS2007 on my 2nd drive so I will fiddle there and compare settings with my New Mandriva2007-Spring and see if I can work it all out.

 

Cheers. John

[ianw1974]

Glad you got it working. It always amazes me when you clean install and it works. I sometimes have this too, and I try to figure out what went wrong, and haven't quite managed it yet. I suppose comparing what was installed last time versus this time might help, or even the config files since they might have had some bizarre entry causing all the issues. I swear an LDAP problem I had not so long ago was because of this, as it worked after a clean install.