1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: Smart UPS-communication setup failure against linux cluster

    From Charles Curley@21:1/5 to Tulika" on Mon Nov 18 23:50:01 2024
    On Mon, 18 Nov 2024 11:45:33 +0000
    "Gupta, Tulika" <t.gupta@ucl.ac.uk> wrote:

    The APC UPS Model: SURTD3000XLIM (APC model) has one serial com
    connector and one USB connector on the back of the UPS. Two cables
    were provided alongwith the UPS purchase- a) RJ-45 to DB-9
    communication cable (goes to the serial com connector of UPS) and
    also b) an USB-A to mini-USB cable connector. I used both the cables
    to connect to our two Linux clusters.

    That last sentence is your first mistake. You should use either the
    serial cable or the USB cable, not both. Connect it to one computer,
    then set the other one up as a slave to the first one. I suggest the
    USB. It is less troublesome than the serial even with apcupsd.

    Let's get the USB host working, then we'll work on the others.

    Once you connect it, you should see something like:

    root@issola:~# lsusb | grep Power
    Bus 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
    root@issola:~#

    For host b, the USB host, you have:

    UPSNAME LG27a
    UPSCABLE usb
    UPSTYPE usb
    DEVICE

    I have DEVICE comment out. I don't know if that will make a difference
    or not.

    NETSERVER on
    NISIP 0.0.0.0
    NISPORT 3551

    Everything else look good. You should see:

    root@issola:~# systemctl status apcupsd.service
    ● apcupsd.service - UPS power management daemon
    Loaded: loaded (/lib/systemd/system/apcupsd.service; enabled; preset: enabled)
    Active: active (running) since Mon 2024-11-18 06:07:25 MST; 9h ago
    Docs: man:apcupsd(8)
    Process: 2164 ExecStartPre=/lib/apcupsd/prestart (code=exited, status=0/SUCCESS)
    Process: 2177 ExecStart=/sbin/apcupsd (code=exited, status=0/SUCCESS)
    Main PID: 2183 (apcupsd)
    Tasks: 3 (limit: 9204)
    Memory: 1.0M
    CPU: 1.230s
    CGroup: /system.slice/apcupsd.service
    └─2183 /sbin/apcupsd

    Nov 18 06:07:25 issola systemd[1]: Starting apcupsd.service - UPS power management daemon...
    Nov 18 06:07:25 issola systemd[1]: apcupsd.service: Can't open PID file /run/apcupsd.pid (yet?) after start: No such file or directory
    Nov 18 06:07:25 issola apcupsd[2183]: apcupsd 3.14.14 (31 May 2016) debian startup succeeded
    Nov 18 06:07:25 issola apcupsd[2183]: NIS server startup succeeded
    Nov 18 06:07:25 issola systemd[1]: Started apcupsd.service - UPS power management daemon.
    root@issola:~# apcaccess | grep -i status
    STATUS : ONLINE
    root@issola:~#

    Note that the "Can't open PID file /run/apcupsd.pid (yet?)" bit is nominal.

    If the daemon is running, you should see the web server at http://<hostname>/cgi-bin/apcupsd/multimon.cgi


    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john doe@21:1/5 to Tulika on Tue Nov 19 08:10:02 2024
    On 11/18/24 12:45, Gupta, Tulika wrote:
    Dear support team

    I have purchased a new APC UPS which I want to connect with four Linux Debian clusters.

    The APC UPS Model: SURTD3000XLIM (APC model) has one serial com connector and one USB connector on the back of the UPS. Two cables were provided alongwith the UPS purchase- a) RJ-45 to DB-9 communication cable (goes to the serial com connector of UPS)
    and also b) an USB-A to mini-USB cable connector. I used both the cables to connect to our two Linux clusters.


    Are the clusters on separated machines, if yes, you can only use one
    UPS per HW!

    --
    John Doe

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)