2010/7/26 Wolfgang Lubowski <w....@gmx.at> > I still get the same outputs with NUT-Monitor. > my nut.conf looks now the following: > MODE=standalone > > ps -efl | grep mge-utalk: > 0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/0 00:00:00 > grep --color=auto mge-utalk > > upsc mgeups: > Error: Driver not connected > > ls -la /var/run/nut: > insgesamt 8 > drwxrwx--- 2 root nut 80 2010-07-26 08:32 . > drwxr-xr-x 22 root root 760 2010-07-26 08:32 .. > -rw-r--r-- 1 nut nut 5 2010-07-26 08:32 upsd.pid > -rw-r--r-- 1 root root 5 2010-07-26 08:32 upsmon.pid >
all this confirms that the driver failed to start. can you try grep'ing your /var/log/messages for "mge-utalk" the NUT-Monitor problem are related to that. If you have any other info (or a screenshot) to give more details on the "it starts not correctly". Ie does it crash, is there a trace, ...? Arnaud -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
