NUT 2.2.0 - pfSense 1.2b2 - not working
-
Did you handled a proloblem with new ver. of NUT? It is not working for me too
-
I decided to wait until 1.2 goes final (as the box is stable). The loss of the NUT package isn't a real problem as it was a client.
-
Looking this topic
http://forum.pfsense.org/index.php/topic,7017.msg41154.html#msg41154NUT problem with perl scripts?
have 'bug' on perl-5.8.8_1 port
In top url simple temporary decision -
Hi,
same problem here with 1.2-RC4… i've tried also to overwrite the libperl.so downloaded from the other topic in the /usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so, uninstalled and reinstallet the nut package... still no works.
Any ideas? tnx -
Manually replace libperl.so
Use this URL for download:
http://diskatel.narod.ru/libperl.so -
Hi thanks for the quick answer…
I've already tried to overwrite libperl.so but I've always the same error message.
So I've tried to reinstall an all new 1.2-rc4 and restored my setting, copied again the but still doesn't work.there is sone other test i can do?
tnx
-
I'll look into this when I have some free time. I need to get a UPS setup again with my virtual machine so I can test.
-
ok,
i've found these two links maybe could be useful :
http://lists.freebsd.org/pipermail/cvs-src/2007-November/084046.html
http://groups.google.com/group/lucky.freebsd.questions/msg/1fa8564a3a000390tnx bye
-
I got nowhere with the perl lib, so I ended up finding a copy of nut 2.0.4 on a FreeBSD package mirror and loading that from the shell. This was after I had installed the 2.2.0 pfSense package. It's an ugly hack, but it works and the status page in the webgui looks fine.
-
Trying to install on 1.2rc3 it keeps hanging at
"nut-2.2.0 (extracting)"
Any help appreciated.
Thanks,
Craig -
I had some time to test this out on 1.2 RC4. I experienced no problems with the package install or deinstall. The extracting nut-2.2.0 step does take 30 seconds or so to complete so give it a minute. However I did find an error when trying to start the daemon
/usr/local/etc/rc.d/nut.sh start
starting genericups
Network UPS Tools - UPS driver controller 2.2.0
/libexec/ld-elf.so.1: /usr/local/libexec/nut/upsdrvctl: Undefined symbol
"__sbmaskrune"
genericups failed to startI'm looking at how to resolve this and will update this thread when I figure it out.
-
Looking to the perl-5.8.8_1 port libperl.so
May be this can help you? -
Alright I've come to the bottom of this. The 6-stable folder nut-2.2.0 version is broken with the above error. The 6.3-release folder nut-2.2.0 version works. The 6.2-release folder nut-2.0.4 works as well. I'm not sure if we should just roll back to nut-2.0.4 or if there will be issues from using the 6.3 release version of nut-2.2.0.
If we roll back to 2.0.4 I know nut-2.2.0 version replaces the newhidups driver with usbhid-ups. I'm not sure if this was just a name change or if it added support for more UPS's.
-
The changelog can be found at: http://www.networkupstools.org/source/2.2/testing/ChangeLog. It looks like newhidups and usbhid-ups are different drivers, so not a name change. I'd expect that the newer one supported more UPSs.
I'd say that if pfSense 1.2 is based on 6.3 then go with the 6.3 version, otherwise stick with the (working) 6.2 version.
-
@Cry:
The changelog can be found at: http://www.networkupstools.org/source/2.2/testing/ChangeLog. It looks like newhidups and usbhid-ups are different drivers, so not a name change. I'd expect that the newer one supported more UPSs.
I'd say that if pfSense 1.2 is based on 6.3 then go with the 6.3 version, otherwise stick with the (working) 6.2 version.
I was just going by what was stated on the post months ago when 2.0.5 was updated to 2.2.0 in the 6-stable directory. pfSense is based on 6.2. I'll move the package back to 2.04 in the 6.2-release today.
-
To switch to the working 2.0.4 version you need to uninstall the package via the package manager and then install it again.
-
That works - thanks.
-
tnx now it work again ;D
z
