New package Apcupsd is available.
-
Could you collect all the log?
On Diagnostics –> Command Prompt
cat /var/log/apcupsd.events
Use a pastebin like pastebin.ca
Thank you.
Config was as attached (of course service was enabled; I disabled it for now since I am using NUT). All other settings are left at default.
When you have a chance, on UPSType / Device put just "usb" and try again.
Unfortunately that did not help :\ still have the same problem:
2014-04-11 13:58:04 -0700 Lock file data error: X���� 2014-04-11 13:58:04 -0700 apcupsd FATAL ERROR in apcupsd.c at line 285 Failed to acquire device lock file 2014-04-11 13:58:04 -0700 Lock file data error: ؋B 2014-04-11 13:58:04 -0700 apcupsd error shutdown completed
-
Could you collect the log?
On Diagnostics –> Command Prompt
cat /var/log/apcupsd.events
Use a pastebin like pastebin.ca
Thank you.
Config was as attached (of course service was enabled; I disabled it for now since I am using NUT). All other settings are left at default.
When you have a chance, on UPSType / Device put just "usb" and try again.
Unfortunately that did not help :\ still have the same problem:
2014-04-11 13:58:04 -0700 Lock file data error: X���� 2014-04-11 13:58:04 -0700 apcupsd FATAL ERROR in apcupsd.c at line 285 Failed to acquire device lock file 2014-04-11 13:58:04 -0700 Lock file data error: ؋B 2014-04-11 13:58:04 -0700 apcupsd error shutdown completed
Log here:
http://pastebin.com/9e347baC
The log is as-of yesterday.
-
Thanks for the log.
Could you check what is on this directory?
ls -lha /var/spool/lock/
Log here:
http://pastebin.com/9e347baC
The log is as-of yesterday.
-
Also, this file exists?
/var/run/apcupsd.pid
Thanks for the log.
Could you check what is on this directory?
ls -lha /var/spool/lock/
Log here:
http://pastebin.com/9e347baC
The log is as-of yesterday.
-
Also, this file exists?
/var/run/apcupsd.pid
Thanks for the log.
Could you check what is on this directory?
ls -lha /var/spool/lock/
Log here:
http://pastebin.com/9e347baC
The log is as-of yesterday.
I enabled the service and checked /var/spool/lock - nothing there except LCK..:
[2.1.2-RELEASE][root@pfsense]/var/spool/lock(8): ls -la total 4 drwxrwxr-x 2 uucp dialer 512 Apr 10 21:37 . drwxr-xr-x 8 root wheel 512 Apr 10 23:37 .. -rw-r--r-- 1 root dialer 0 Apr 10 19:46 LCK..
In /var/run - apcupsd.pid does not exist :\
-
remove this LCK and restart the service, please
I enabled the service and checked /var/spool/lock - nothing there except LCK..:
[2.1.2-RELEASE][root@pfsense]/var/spool/lock(8): ls -la total 4 drwxrwxr-x 2 uucp dialer 512 Apr 10 21:37 . drwxr-xr-x 8 root wheel 512 Apr 10 23:37 .. -rw-r--r-- 1 root dialer 0 Apr 10 19:46 LCK..
In /var/run - apcupsd.pid does not exist :\
-
remove this LCK and restart the service, please
I enabled the service and checked /var/spool/lock - nothing there except LCK..:
[2.1.2-RELEASE][root@pfsense]/var/spool/lock(8): ls -la total 4 drwxrwxr-x 2 uucp dialer 512 Apr 10 21:37 . drwxr-xr-x 8 root wheel 512 Apr 10 23:37 .. -rw-r--r-- 1 root dialer 0 Apr 10 19:46 LCK..
In /var/run - apcupsd.pid does not exist :\
Yup! That did it!
Thanks!!!
Now - the email functionality; I presume there's nothing to modify or change, right? Once it goes on battery power - an email is automatically dispatched?
-
Yup! That did it!
Thanks!!!
Now - the email functionality; I presume there's nothing to modify or change, right? Once it goes on battery power - an email is automatically dispatched?
Thank you McFuzz.
I will update the package for fix this problem.
About notifications.
Config:
System -> Advanced -> Notifications –> SMTP E-MailInstall:
mailgraph packageAnd then, you can test apcupsd e-mail notifications:
/usr/pbi/apcupsd-i386/etc/apcupsd/onbattery
/usr/pbi/apcupsd-i386/etc/apcupsd/offbatteryor
/usr/pbi/apcupsd-amd64/etc/apcupsd/onbattery
/usr/pbi/apcupsd-amd64/etc/apcupsd/offbatteryBest Regards.
-
https://forum.pfsense.org/index.php?topic=91783
Sent you a PM about this. I am having the same issue now where multiple instances of it get ran.
-
https://forum.pfsense.org/index.php?topic=91783
Sent you a PM about this. I am having the same issue now where multiple instances of it get ran.
Ok thanks.
I've sent a PR for adding apcupsd on pfSense 2.3.
https://github.com/pfsense/FreeBSD-ports/pull/128
On pfSense 2.3 the problem with emails won't happening. ;D
-
Rockin…I am thinking I will have to install it.
-
Are there plans to make Apcupsd available for PfSense 2.3.x ?
Sorry, forget my question above. I overlooked that you are already working on that. Great!
Greetings
flu -
Just posting to show interest.. Used this on a older install, immediately went to look for it on this new install and was sad when I didn't see it..
Appreciate your work on this.
-
How to install apcupsd on pfSense 2.3.2 ???
This package is not available in the "Package Manager" :-[ -
How to install apcupsd on pfSense 2.3.2 ???
This package is not available in the "Package Manager" :-[
[/quote]I think it will be available soon.
A developer was assigned to the PR:
https://github.com/pfsense/FreeBSD-ports/pull/128 -
But… should be "merged it only for 2.3.3-snapshots"? (https://github.com/pfsense/FreeBSD-ports/pull/128)
I'm on 2.3.3 but apcupsd isn't listed on packages page.
There is a way to get the pkg…? -
But… should be "merged it only for 2.3.3-snapshots"? (https://github.com/pfsense/FreeBSD-ports/pull/128)
I'm on 2.3.3 but apcupsd isn't listed on packages page.
There is a way to get the pkg…?I've sent a message to the devs about this.
I think it will be available very soon. -
apcupsd is now published! :)
Service starts and on "Status information" I can see UPS parameters.
But in system logs:Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
My system:
pfsense 2.3.3-DEVELOPMENT (amd64) built on Tue Aug 09 21:57:46 CDT 2016
ups APC sua1000i controlled via network card AP9630 -
But… should be "merged it only for 2.3.3-snapshots"? (https://github.com/pfsense/FreeBSD-ports/pull/128)
I'm on 2.3.3 but apcupsd isn't listed on packages page.
There is a way to get the pkg…?I've sent a message to the devs about this.
I think it will be available very soon.And it is available now. ;D
-
[snip]
Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided [snip] Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided Aug 10 09:35:18 apcupsd 58288 apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
My system:
pfsense 2.3.3-DEVELOPMENT (amd64) built on Tue Aug 09 21:57:46 CDT 2016
ups APC sua1000i controlled via network card AP9630On the Status Information page, are you seeing the information through apcaccess -h 0.0.0.0:3551 ? or did you used the ip address of your network card ?
Could you show it ?Are you using "pcnet" or "net" on UPS Type ?
See this information about pcnet:
https://forum.pfsense.org/index.php?topic=85083.msg497267#msg497267Also, if you have another apcupsd running on your network, try to use "net" and the ip address of that machine for testing.
Best Regards.