Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    After Upgrade to pfsense 2.0, NUT will not start

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 1 Posters 2.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • knight-of-niK
      knight-of-ni
      last edited by

      I have an MGE Pulsar Evolution UPS attached to COM1.
      NUT worked fine when running pfsense 1.2.3.

      This morning I upgraded to pfsense 2.0, and it seems I can no longer select a port other than "Auto (USB Only)" from the gui. The odd thing is that, no matter what local ups model I select from the list, the only local ups port option available is "Auto (USB Only)".

      Because of this, I get the following when I try to start NUT:

      # /usr/local/etc/rc.d/nut.sh start
      starting mge-shut
      Network UPS Tools - UPS driver controller 2.2.2
      Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.66 (2.2.2)
      
      Unable to open auto: No such file or directory
      
      Things to try:
      
       - Check 'port=' in ups.conf
      
       - Check owner/permissions of all parts of path
      
      Fatal error: unusable configuration
      Driver failed to start (exit status=1)
      mge-shut failed to start
      
      

      Completely uninstalling and then reinstalling NUT did not help.

      Suggestions?

      1 Reply Last reply Reply Quote 0
      • knight-of-niK
        knight-of-ni
        last edited by

        Update: I seem to no longer have a COM1, /dev/ttyd0

        Dmesg detects it:

        uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
        uart0: [FILTER]
        
        

        However the device /dev/ttyd0 does not get created.
        I've noticed the device.hints files appear to be different between version of pfsense.
        Continuing to investigate…

        1 Reply Last reply Reply Quote 0
        • knight-of-niK
          knight-of-ni
          last edited by

          Looks like FreeBSD decided to change /dev/ttyd0 to /dev/ttyu0.

          Changing the port in /usr/local/etc/nut/ups.conf to /dev/ttyu0, as described in the link below, "fixes" the problem.

          http://forum.pfsense.org/index.php/topic,37471.0.html

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.