Nut upsuser - Mar 2013 - Automatic start fails in boot

Hi,

I have problems starting NUT 2.6.5-7.fc18 in Fedora 18 (now running kernel
3.8.3-201.fc18.x86_64), some details here:
http://forums.fedoraforum.org/showthread.php?t=289724

The problem is, nut-driver.service automatic startup in boot fails with this:

Mar 17 11:48:19 mybox upsdrvctl[1054]: Fatal error: unusable configuration
Mar 17 11:48:19 mybox upsdrvctl[1054]: Network UPS Tools - BCMXCP UPS
driver 0.26 (2.6.5)
Mar 17 11:48:19 mybox upsdrvctl[1054]: RS-232 communication subdriver 0.19
Mar 17 11:48:19 mybox upsdrvctl[1054]: Unable to open /dev/ttyS6: Device
or resource busy
Mar 17 11:48:19 mybox upsdrvctl[1054]: Current user id: nut (57)
Mar 17 11:48:19 mybox upsdrvctl[1054]: Serial port owner: root (0)
Mar 17 11:48:19 mybox upsdrvctl[1054]: Serial port group: dialout (18)
Mar 17 11:48:19 mybox upsdrvctl[1054]: Mode of port: 0660
Mar 17 11:48:19 mybox upsdrvctl[1054]: Things to try:
Mar 17 11:48:19 mybox upsdrvctl[1054]: - Use another port (with the right
permissions)
Mar 17 11:48:19 mybox upsdrvctl[1054]: - Fix the port owner/group or
permissions on this port
Mar 17 11:48:19 mybox upsdrvctl[1054]: - Run this driver as another user
(upsdrvctl -u or 'user=...' in ups.conf).
Mar 17 11:48:19 mybox upsdrvctl[1054]: See upsdrvctl(8) and ups.conf(5).
Mar 17 11:48:19 mybox upsdrvctl[1054]: Driver failed to start (exit status=1)
Mar 17 11:48:19 mybox upsdrvctl[1054]: Network UPS Tools - UPS driver
controller 2.6.5

And  nut-server.service also fails because it depends on
nut-driver.service. The nut-monitor.service starts OK, but stats walling
error messages.

After the boot everythign starts OK:

$ sudo systemctl stop nut-monitor.service
$ sudo systemctl start nut-server.service
$ sudo systemctl start nut-monitor.service

And everything is running nicely. Serial ports belong to dialout group and
nut user is a member.

What is taking the /dev/ttyS6 serial port during the boot? Could this me
some timing problem?

Installed nut and nut-client from standard Fedora repositories (I have not
yet defined any 3rd party repos).

UPS is PowerWare/Eaton PW5115 1000i, connected with a serial cable to
/dev/ttyS6, which is Titan Electronics Inc VScom 400H 8-port serial
controller sitting in PCI bus. Everything has been rock solid reliable for
years, I have been running Fedora and nut for a long time.

Output of 'bcmxcp -DD -a PowerWare_5115' in attached log file if it is
needed.

Any help is appreciated a lot!

-Paavo
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bcmxcp_log.txt
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130319/8d26fef8/attachment.txt>

Hi,

this was the answer. This cured the problem:

    systemctl stop NetworkManager.service
    systemctl disable NetworkManager.service
    systemctl enable network.service
    systemctl start network.service

Big thanks to Charles Lepple! And the authors
of nut, I'm again a happy nut user/sysadmin.

-Paavo

-----Original Message-----
From: Charles Lepple [mailto:clepple at gmail.com] 
Sent: 21. maaliskuuta 2013 13:02
To: Paavo Leinonen
Subject: Re: [Nut-upsuser] Automatic start fails in boot

On Mar 19, 2013, at 3:22 AM, Paavo Leinonen wrote:
> What is taking the /dev/ttyS6 serial port during the boot? Could this me
> some timing problem?
Is it possible that something like NetworkManager is scanning for modem
serial ports?

-- 
Charles Lepple
clepple at gmail