Apcupsd starts up twice



  • Dear List,

    We have apcupsd running on two pfSense boxes connection to a ups. Sometimes the boxes slow down to a grinding halt because of a double start. Why? Everything is the newest version. We see this all the time:

    Jul 13 15:34:08 fw2 apcupsd[58559]: apcupsd 3.14.12 (29 March 2014) freebsd startup succeeded
    Jul 13 15:34:08 fw2 apcupsd[58559]: NIS server startup succeeded
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd 3.14.12 (29 March 2014) freebsd startup succeeded
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcserver: cannot bind port 3551. ERR=Address already in use
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in pcnet.c at line 663 Cannot bind socket (48)
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
    Jul 13 15:34:08 fw2 apcupsd[62688]: apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided

    • thousands more of this….

    Please help,

    Thanks,

    Alfredo


Log in to reply