Apcupsd fatal error in smart setup.c at line 58

Code: Select all [ 6. I have done some more playing with this, and it seems that the problem is that the daemon is not starting. I will have to keep digging into this as I get time Encountered something similar. I just installed the package. I have not tried compiling from sources yet. I will give that a shot when I get time. Any tips on configuration? Search forums. Log in. Install the app. For a better experience, please enable JavaScript in your browser before proceeding.

You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser. Thread starter fullauto Start date Oct 31, Installed FreeBSD Broadcast Message from tim. Communications with UPS lost. If apcupsd or apctest is already running, please stop it and run this program again.

Click to expand None of the initial UPS data runtime, battery status, voltages etc have been initialized. I can see all of the info pertaining to the UPS for which pfSense is configured.

So, network connectivity is good: it's just that for some reason, the package isn't picking up the information for the configured UPS. I tested this further by spinning up a second apcupsd service on my computer at home.

With the exact same config settings, it picked up all the UPS info from the netops server and off it went. Note that the version of apcupsd running on the netops server and my home computer is 3.

I'm just wondering if anyone has any suggestions as to what else I could try here? In the past, apcupsd on pfSense has depended on perl and snmp packages, and older verisons yet also needed the snmp and trap services running in order to function: I tried toggling these on in my pfSense installation, but it didn't make any difference. For those interested, here is the output of acpaccess for the local and remote services.

I've been starting and stopping the daemon from the command line. Whether or not it's started or stopped, that command doesn't produce any output, nor does it drop anything into the log:. Thanks dbaio… this hadn't occurred to me. Sadly, after restart, the service still isn't able to consume the UPS data over the network.

I've tried here and "net" doesn't have the simular bug like "pcnet", thanks for trying. Thanks for the suggestion. I gave this a try as well, but sadly those changes didn't work either. If I can find a similar version of apcupsd I'm going to try installing it on a linux machine behind pfSense to see if this is an issue with this specific version of apcupsd and the net connectivity I'm using. PARC :. They are separate settings.

The default username on a new card is "apc" and the default passphrase is "admin user phrase". This assumes firmware v3. Other versions may place the setting elsewhere. The password must be a minimum of 15 characters long. The web UI will silently ignore shorter passwords and does not give an error message. There is no apparent way to change the username. Using the ipaddr, user, and passphrase will prevent this behavior.

Also, you can add the IP of pfSense box to the powerchute clients in the web interface like mk96 saied. Just wanted to mention that I noticed a new version of the apcupsd package was available; I uninstalled the previous package and installed the new one.

That resolved this issue. Register Login. Apcupsd 3. Reply Reply as topic. This topic has been deleted.