[arch-general] nut UPS driver (upsdrvctl) fails to start for usbhid devices due to node perms - howto fix?
Guys, As a follow-on to the thread "package: network-ups-tools what happened to it?" I have discussed the fail-to-start issue with the nut developers and the reason why nut used to just "work" in the past for usb devices, but now no longer does without additional configuration. This apparently has to do with hotplug/udev permissions on newer Linux systems. I guess this went into Arch about 12-18 months ago, because that is when nut stopped working without further configuration. After working through errors starting the latest nut from git with systemd, the problem was that /dev/bus/usb/004/002 is owned by root:root forcing nut-driver.server to fail to start. Essentially upsdrvctl could not find/connect with /dev/bus/usb/004/002 and could not find the ups usb connection. Modifying the Execstart=/usr/bin/upsdrvctl start to: /usr/bin/upsdrvctl -u root start <upsname> allowed upsdrvctl to connect, but then created the state files in /var/state/ups with root:root permission which in turn caused nut-server.service (upsd) to fail on startup. upsd could not read the device files created in the state directory and could not create the upsd.pid as it was running gid "nut". Changing gid ownership of /dev/bus/usb/004/002 to root:nut solves all problem and allows upsdrvctl, upsd and upsmon to all start and connect fine. However, there is no way for the packager to know what bus a device with install or or whether it will be plugged back into the same port each time. I would like to investigate how Arch could be changed/configured so that nut simply runs out of the box as it used to before what ever changed changed. Is there a way the packager can do this? There are articles about rolling custom udev files -- that essentially accomplish linking the device to systemd and the ups name through /etc/ups/ups.conf: http://www.kepstin.ca/blog/networkupstoolsnutandsystemd/ That too is something impossible for the packager to take into account when building the package. How do we package something like nut just works after it is installed like it used to? Essentially, what is broken is nut's ability to probe and connect to the ups device on startup due to the default device permissions. Did the usb devices used to have 0666 permissions in the past? That's the only way I can see upsdrvctl being able to probe/connect to the device right out of the box. What are the security consideration of having a usb device world writable? Could we modify the default Arch udev setup to recognize UPS devices and make these world writable by default? I don't know much about the new udev/usb logic, so I'm asking, what say the experts? -- David C. Rankin, J.D.,P.E.
On 12/14/2013 03:16 PM, David C. Rankin wrote: Disregard the previous information in this thread. Here is the new information: After upgrade to kernel 3.12.5-1 and glic 2.18-11, network-ups-tools (upsd) fails to start giving the error: getaddrinfo: Servname not supported for I had spent the last couple of days working with nut, so I was very familiar with how it was starting on this box. Literally, nothing else changed, it looks the update killed it. Here is the journalctl log per/post reboot for kernel update when glibc was updated: Dec 14 14:02:00 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 14 14:02:00 phoinix upsd[32616]: fopen /var/state/ups/upsd.pid: No such file or directory Dec 14 14:02:00 phoinix upsd[32616]: listening on 192.168.7.16 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on ::1 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on 127.0.0.1 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on 192.168.7.16 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on ::1 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on 127.0.0.1 port 3493 Dec 14 14:02:00 phoinix upsd[32617]: Startup successful Dec 14 14:02:00 phoinix systemd[1]: Started Network UPS Tools - power devices information server. Dec 16 14:05:26 phoinix systemd[1]: Stopping Network UPS Tools - power devices information server... Dec 16 14:05:26 phoinix upsd[21265]: Network UPS Tools upsd 2.7.1-signed-9-g6fb35b3 Dec 16 14:05:26 phoinix systemd[1]: Stopped Network UPS Tools - power devices information server. -- Reboot -- Dec 16 14:05:16 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 16 14:05:16 phoinix upsd[369]: fopen /var/state/ups/upsd.pid: No such file or directory Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for ai_socktype Dec 16 14:05:16 phoinix upsd[369]: Network UPS Tools upsd 2.7.1-signed-9-g6fb35b3 Dec 16 14:05:16 phoinix systemd[1]: nut-server.service: control process exited, code=exited status=1 Dec 16 14:05:16 phoinix systemd[1]: Failed to start Network UPS Tools - power devices information server. Dec 16 14:05:16 phoinix systemd[1]: Unit nut-server.service entered failed state. Is this a glibc issue or a nut issue? Sorry for continuing this in the same thread, but I could not create a new thread because: Posting of your message titled "nut UPS (upsd) fails to start after kernel upgrade (3.12.5-1) error: getaddinfo" has been rejected by the list moderator. The moderator gave the following reason for rejecting your request: "Stop creating brand new threads for discussing related issues. Cheers. --Gaetan" So if you think this should be in a new thread and not here -- talk to Gaetan. -- David C. Rankin, J.D.,P.E.
[2013-12-16 21:33:33 -0600] David C. Rankin:
So if you think this should be in a new thread and not here -- talk to Gaetan.
I'm quite confident no-one is going to care: it's now the third message you've send to this list about network-ups-tools. The first two haven't attracted much attention, so it's likely few people here care about that piece of software - nor should they, since it's unsupported. Obviously, we're happy to help with the occasional issue, but you have the annoying habit of sending every single one of your support requests to this list. So when you *really* have to post, please concentrate the noise in just one thread.
Is this a glibc issue or a nut issue?
How about asking a network-ups-tools support list? Or its developers? This mailing list is for Arch-related discussions. This isn't one. -- Gaetan
On 12/17/2013 01:35 AM, Gaetan Bisson wrote:
Is this a glibc issue or a nut issue? How about asking a network-ups-tools support list? Or its developers? This mailing list is for Arch-related discussions. This isn't one.
I already did, and a review of the getaddrinfo code seemed to follow all of the recommendations on how to use that function. They were also caught by the fact that this was a 2.18-10 to 2.18-11 updated and not a 2.17-x to 2.18-x update. There recommendation was to check and confirm that Arch wasn't mixing 32bit and 64bit libraries somewhere. Bottom line, something in the update yesterday broke upsd causing it to throw the error: upsd[369]: getaddrinfo: Servname not supported for ai_socktype I tried downgrading glibc 2.18-11 => 2.18-10, but didn't reboot the remote box. After downgrade, the same error was generated on upsd start. Looking at the upgrades, I'm not sure what other package could have broken upsd. I even rebuilt network-ups-tools and reinstalled. Same error. $ ldd /usr/bin/upsd linux-vdso.so.1 (0x00007fff77374000) libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0x00007f292b13d000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007f292ad35000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f292ab18000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f292a76e000) libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f292a56a000) libz.so.1 => /usr/lib/libz.so.1 (0x00007f292a354000) /lib64/ld-linux-x86-64.so.2 (0x00007f292b3aa000) I can't see what else could have impacted this except maybe the linux-api-headers, but I've rebuilt/reinstalled since and have the same issue. Does anybody else have any suggestions as to what changed? The list of packages updated were: [2013-12-16 14:02] [PACMAN] Running 'pacman -Syu' [2013-12-16 14:02] [PACMAN] synchronizing package lists [2013-12-16 14:03] [PACMAN] starting full system upgrade [2013-12-16 14:03] [PACMAN] removed foomatic-filters (1:4.0.17_20130518-1) [2013-12-16 14:03] [PACMAN] removed sysvinit-tools (2.88-12) [2013-12-16 14:03] [PACMAN] upgraded linux-api-headers (3.10.6-1 -> 3.12.4-1) [2013-12-16 14:03] [PACMAN] upgraded glibc (2.18-10 -> 2.18-11) [2013-12-16 14:03] [PACMAN] upgraded util-linux (2.24-1 -> 2.24-2) [2013-12-16 14:03] [PACMAN] upgraded apr (1.4.8-2 -> 1.5.0-1) [2013-12-16 14:03] [PACMAN] upgraded libldap (2.4.37-1 -> 2.4.38-1) [2013-12-16 14:03] [PACMAN] upgraded apr-util (1.5.2-3 -> 1.5.3-1) [2013-12-16 14:03] [PACMAN] upgraded binutils (2.23.2-3 -> 2.24-1) [2013-12-16 14:03] [PACMAN] upgraded bison (3.0.1-1 -> 3.0.2-1) [2013-12-16 14:04] [PACMAN] upgraded cmake (2.8.12.1-1 -> 2.8.12.1-3) [2013-12-16 14:04] [PACMAN] upgraded cronie (1.4.9-5 -> 1.4.11-1) [2013-12-16 14:04] [PACMAN] upgraded libjpeg-turbo (1.3.0-3 -> 1.3.0-4) [2013-12-16 14:04] [PACMAN] upgraded gcc-libs (4.8.2-4 -> 4.8.2-6) [2013-12-16 14:04] [PACMAN] upgraded poppler (0.24.3-1 -> 0.24.4-1) [2013-12-16 14:04] [PACMAN] upgraded cups-filters (1.0.41-1 -> 1.0.42-2) [2013-12-16 14:04] [PACMAN] upgraded libvpx (1.2.0-2 -> 1.3.0-1) [2013-12-16 14:04] [PACMAN] upgraded opus (1.0.3-2 -> 1.1-1) [2013-12-16 14:04] [PACMAN] upgraded x264 (20131030-1 -> 20131030-2) [2013-12-16 14:04] [PACMAN] upgraded ffmpeg (1:2.1.1-1 -> 1:2.1.1-2) [2013-12-16 14:04] [PACMAN] upgraded file (5.15-1 -> 5.16-1) [2013-12-16 14:04] [PACMAN] upgraded foomatic-db (1:4.0.17_20130518-1 -> 2:4.0.9_20131201-1) [2013-12-16 14:04] [PACMAN] upgraded foomatic-db-engine (1:4.0.17_20130518-1 -> 2:4.0.9_20131201-1) [2013-12-16 14:04] [PACMAN] upgraded foomatic-db-nonfree (1:4.0.17_20130518-1 -> 2:4.0.9_20131201-1) [2013-12-16 14:04] [PACMAN] upgraded freetype2 (2.5.0.1-2 -> 2.5.2-1) [2013-12-16 14:04] [PACMAN] upgraded gcc (4.8.2-4 -> 4.8.2-6) [2013-12-16 14:04] [PACMAN] upgraded gdb (7.6.1-1 -> 7.6.2-1) [2013-12-16 14:04] [PACMAN] upgraded git (1.8.4.2-1 -> 1.8.5.1-1) [2013-12-16 14:04] [PACMAN] upgraded grub (2.00.5086-1 -> 1:2.00.1282.g5ae5c54-1) [2013-12-16 14:04] [PACMAN] upgraded gstreamer0.10 (0.10.36-2 -> 0.10.36-3) [2013-12-16 14:04] [PACMAN] upgraded gstreamer0.10-base (0.10.36-1 -> 0.10.36-2) [2013-12-16 14:04] [PACMAN] upgraded harfbuzz (0.9.23-1 -> 0.9.24-1) [2013-12-16 14:04] [PACMAN] upgraded imagemagick (6.8.7.8-1 -> 6.8.7.9-1) [2013-12-16 14:04] [PACMAN] upgraded inetutils (1.9.1.341-1 -> 1.9.1.341-2) [2013-12-16 14:04] [PACMAN] upgraded jasper (1.900.1-9 -> 1.900.1-10) [2013-12-16 14:04] [PACMAN] upgraded libdrm (2.4.49-1 -> 2.4.50-1) [2013-12-16 14:04] [PACMAN] upgraded libmariadbclient (5.5.34-1 -> 5.5.34-3) [2013-12-16 14:04] [PACMAN] upgraded libnl (3.2.22-1 -> 3.2.23-1) [2013-12-16 14:04] [PACMAN] upgraded libpipeline (1.2.4-1 -> 1.2.5-1) [2013-12-16 14:04] [PACMAN] upgraded libwbclient (4.1.2-1 -> 4.1.3-1) [2013-12-16 14:04] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ... [2013-12-16 14:04] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait... <snip> [2013-12-16 14:04] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img [2013-12-16 14:04] [ALPM-SCRIPTLET] ==> Image generation successful [2013-12-16 14:04] [PACMAN] upgraded linux (3.12.1-3 -> 3.12.5-1) [2013-12-16 14:04] [PACMAN] upgraded lua (5.2.2-1 -> 5.2.3-1) [2013-12-16 14:04] [PACMAN] upgraded make (4.0-1 -> 4.0-2) [2013-12-16 14:04] [PACMAN] upgraded man-pages (3.54-1 -> 3.55-1) [2013-12-16 14:04] [PACMAN] upgraded mariadb-clients (5.5.34-1 -> 5.5.34-3) [2013-12-16 14:04] [PACMAN] upgraded mariadb (5.5.34-1 -> 5.5.34-3) [2013-12-16 14:04] [PACMAN] upgraded mc (4.8.10-2 -> 4.8.11-1) [2013-12-16 14:04] [PACMAN] upgraded mesa (9.2.4-1 -> 9.2.5-1) [2013-12-16 14:04] [PACMAN] upgraded minicom (2.6.2-1 -> 2.6.2-2) [2013-12-16 14:04] [PACMAN] upgraded mpfr (3.1.2.p4-1 -> 3.1.2.p5-1) [2013-12-16 14:04] [PACMAN] upgraded perl-io-socket-ssl (1.960-1 -> 1.962-1) [2013-12-16 14:04] [PACMAN] upgraded perl-net-dns (0.72-2 -> 0.73-1) [2013-12-16 14:04] [PACMAN] upgraded php (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-apache (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-cgi (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-enchant (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-gd (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-intl (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-ldap (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-mcrypt (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-odbc (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-pear (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded postgresql-libs (9.3.1-4 -> 9.3.2-4) [2013-12-16 14:04] [PACMAN] upgraded php-pgsql (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-pspell (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-snmp (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded sqlite (3.8.1-2 -> 3.8.2-1) [2013-12-16 14:04] [PACMAN] upgraded php-sqlite (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-tidy (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded php-xsl (5.5.6-1 -> 5.5.7-1) [2013-12-16 14:04] [PACMAN] upgraded procps-ng (3.3.8-3 -> 3.3.9-1) [2013-12-16 14:04] [PACMAN] installed libmng (2.0.2-3) [2013-12-16 14:04] [PACMAN] upgraded qt4 (4.8.5-6 -> 4.8.5-7) [2013-12-16 14:04] [PACMAN] upgraded smbclient (4.1.2-1 -> 4.1.3-1) [2013-12-16 14:04] [PACMAN] upgraded samba (4.1.2-1 -> 4.1.3-1) [2013-12-16 14:04] [PACMAN] upgraded sqlite-doc (3.8.1-2 -> 3.8.2-1) [2013-12-16 14:04] [PACMAN] upgraded sqlite-tcl (3.8.1-2 -> 3.8.2-1) [2013-12-16 14:04] [PACMAN] upgraded unrar (1:5.0.13-1 -> 1:5.0.14-1) [2013-12-16 14:04] [PACMAN] upgraded xorg-server-common (1.14.4-1 -> 1.14.5-1) [2013-12-16 14:04] [PACMAN] upgraded xorg-server (1.14.4-1 -> 1.14.5-1) [2013-12-16 14:04] [PACMAN] Running 'pacman -Sy --needed linux-lts' [2013-12-16 14:04] [PACMAN] synchronizing package lists [2013-12-16 14:05] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ... <snip> [2013-12-16 14:05] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img [2013-12-16 14:05] [ALPM-SCRIPTLET] ==> Image generation successful [2013-12-16 14:05] [PACMAN] installed linux-lts (3.10.24-1) [2013-12-16 17:52] [PACMAN] Running 'pacman -U network-ups-tools-git-v2.7.1.signed.r10.g6fb35b3-1-x86_64.pkg.tar.xz' [2013-12-16 17:52] [PACMAN] upgraded network-ups-tools-git (v2.7.1.signed.r9.g6fb35b3-1 -> v2.7.1.signed.r10.g6fb35b3-1) [2013-12-16 21:34] [PACMAN] Running 'pacman -U glibc-2.18-10-x86_64.pkg.tar.xz' [2013-12-16 21:35] [PACMAN] downgraded glibc (2.18-11 -> 2.18-10) [2013-12-16 21:49] [PACMAN] Running 'pacman -U glibc-2.18-11-x86_64.pkg.tar.xz' [2013-12-16 21:49] [PACMAN] upgraded glibc (2.18-10 -> 2.18-11) -- David C. Rankin, J.D.,P.E.
Hello, ** David C. Rankin [2013-12-16 21:33:33 -0600]:
On 12/14/2013 03:16 PM, David C. Rankin wrote:
Disregard the previous information in this thread. Here is the new information:
After upgrade to kernel 3.12.5-1 and glic 2.18-11, network-ups-tools (upsd) fails to start giving the error:
getaddrinfo: Servname not supported for
I had spent the last couple of days working with nut, so I was very familiar with how it was starting on this box. Literally, nothing else changed, it looks the update killed it. Here is the journalctl log per/post reboot for kernel update when glibc was updated:
Dec 14 14:02:00 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 14 14:02:00 phoinix upsd[32616]: fopen /var/state/ups/upsd.pid: No such file or directory Dec 14 14:02:00 phoinix upsd[32616]: listening on 192.168.7.16 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on ::1 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on 127.0.0.1 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on 192.168.7.16 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on ::1 port 3493 Dec 14 14:02:00 phoinix upsd[32616]: listening on 127.0.0.1 port 3493 Dec 14 14:02:00 phoinix upsd[32617]: Startup successful Dec 14 14:02:00 phoinix systemd[1]: Started Network UPS Tools - power devices information server. Dec 16 14:05:26 phoinix systemd[1]: Stopping Network UPS Tools - power devices information server... Dec 16 14:05:26 phoinix upsd[21265]: Network UPS Tools upsd 2.7.1-signed-9-g6fb35b3 Dec 16 14:05:26 phoinix systemd[1]: Stopped Network UPS Tools - power devices information server. -- Reboot -- Dec 16 14:05:16 phoinix systemd[1]: Starting Network UPS Tools - power devices information server... Dec 16 14:05:16 phoinix upsd[369]: fopen /var/state/ups/upsd.pid: No such file or directory Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for ai_socktype Dec 16 14:05:16 phoinix upsd[369]: Network UPS Tools upsd 2.7.1-signed-9-g6fb35b3 Dec 16 14:05:16 phoinix systemd[1]: nut-server.service: control process exited, code=exited status=1 Dec 16 14:05:16 phoinix systemd[1]: Failed to start Network UPS Tools - power devices information server. Dec 16 14:05:16 phoinix systemd[1]: Unit nut-server.service entered failed state.
Is this a glibc issue or a nut issue?
No, it seems that is your issue (a body between monitor and a chair). I wouldn't do such brilliant suggestions without deep investigation with doubtless facts. And about facts, network-ups-tools works fine on my system: ---------------------- 8< ---------------------- Linux smoon 3.12.5-1-ARCH #1 SMP PREEMPT Thu Dec 12 12:57:31 CET 2013 x86_64 GNU/Linux local/glibc 2.18-11 (base) GNU C Library ---------------------- 8< ---------------------- though it took time to build correctly the package. Just for record, my custom PKGBUILD for the package: https://github.com/vp1981/pkgbuild/tree/master/network-ups-tools and some configuration files for the program: https://github.com/vp1981/scripts/tree/master/network-ups-tools Current status: nut-server.service - Network UPS Tools - power devices information server Loaded: loaded (/usr/lib/systemd/system/nut-server.service; enabled) Active: active (running) since Пн 2013-12-16 20:03:24 IRKT; 23h ago Process: 616 ExecStart=/usr/bin/upsd (code=exited, status=0/SUCCESS) Main PID: 624 (upsd) CGroup: /system.slice/nut-server.service └─624 /usr/bin/upsd nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static) Active: active (running) since Пн 2013-12-16 20:03:24 IRKT; 23h ago Process: 530 ExecStart=/usr/bin/upsdrvctl start (code=exited, status=0/SUCCESS) Main PID: 615 (blazer_usb) CGroup: /system.slice/nut-driver.service └─615 /usr/bin/blazer_usb -a ippon nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/usr/lib/systemd/system/nut-monitor.service; enabled) Active: active (running) since Пн 2013-12-16 20:03:25 IRKT; 23h ago Process: 625 ExecStart=/usr/bin/upsmon (code=exited, status=0/SUCCESS) Main PID: 643 (upsmon) CGroup: /system.slice/nut-monitor.service ├─642 /usr/bin/upsmon └─643 /usr/bin/upsmon So, try harder.
Sorry for continuing this in the same thread, but I could not create a new thread because:
Posting of your message titled "nut UPS (upsd) fails to start after kernel upgrade (3.12.5-1) error: getaddinfo"
has been rejected by the list moderator. The moderator gave the following reason for rejecting your request:
"Stop creating brand new threads for discussing related issues. Cheers. --Gaetan"
So if you think this should be in a new thread and not here -- talk to Gaetan.
W/o comments. --- WBR, Vladimir Lomov -- Any man who hates dogs and babies can't be all bad. -- Leo Rosten, on W.C. Fields
On 12/17/2013 04:29 AM, Vladimir Lomov wrote:
No, it seems that is your issue (a body between monitor and a chair). I wouldn't do such brilliant suggestions without deep investigation with doubtless facts. And about facts, network-ups-tools works fine on my system:
GRRR! I hate it when you are right... Dec 17 10:21:01 phoinix upsd[27151]: =========== Error Block Hit ============ Dec 17 10:21:01 phoinix upsd[27151]: getaddrinfo : Servname not supported for ai_socktype Dec 17 10:21:01 phoinix upsd[27151]: Server addr (Nodename) : 192.168.7.16 Dec 17 10:21:01 phoinix upsd[27151]: Server port (Servname) : :3493 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_flags : 1 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_family : 0 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_socktype : 1 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_protocol : 6 Huh? :3493? Seems I've been hit by the vi bug... Sorry for the noise... -- David C. Rankin, J.D.,P.E.
On Tue, Dec 17, 2013 at 7:07 PM, David C. Rankin
On 12/17/2013 04:29 AM, Vladimir Lomov wrote:
No, it seems that is your issue (a body between monitor and a chair). I wouldn't do such brilliant suggestions without deep investigation with doubtless facts. And about facts, network-ups-tools works fine on my system:
GRRR! I hate it when you are right...
Dec 17 10:21:01 phoinix upsd[27151]: =========== Error Block Hit ============ Dec 17 10:21:01 phoinix upsd[27151]: getaddrinfo : Servname not supported for ai_socktype Dec 17 10:21:01 phoinix upsd[27151]: Server addr (Nodename) : 192.168.7.16 Dec 17 10:21:01 phoinix upsd[27151]: Server port (Servname) : :3493 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_flags : 1 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_family : 0 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_socktype : 1 Dec 17 10:21:01 phoinix upsd[27151]: hints.ai_protocol : 6
Huh? :3493?
Seems I've been hit by the vi bug...
Sorry for the noise...
Good rubberducking! +1 cheers! mar77i
participants (4)
-
David C. Rankin
-
Gaetan Bisson
-
Martti Kühne
-
Vladimir Lomov