Wolfgang,
I'm closing the bug since you have a fix.
If you feel you are still facing an issue, don't hesitate to reopen this bug,
or open a new one.
cheers,
--- Arnaud
** Changed in: nut (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a
Wolfgang,
I'm closing the bug since you have a fix.
If you feel you are still facing an issue, don't hesitate to reopen this bug,
or open a new one.
cheers,
--- Arnaud
** Changed in: nut (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a
@Arnaud, I'm confused as to the current status of this bug. Is there
anything that needs to be done?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/608182
Title:
problems
2011/7/18 Dave Walker davewal...@ubuntu.com
@Arnaud, I'm confused as to the current status of this bug. Is there
anything that needs to be done?
@Dave: I'm not completely sure. the user has found a workaround.
IMHO, we are probably facing some race condition between upstart native
script Vs
@Arnaud, I'm confused as to the current status of this bug. Is there
anything that needs to be done?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608182
Title:
problems with ups (mge
2011/7/18 Dave Walker davewal...@ubuntu.com
@Arnaud, I'm confused as to the current status of this bug. Is there
anything that needs to be done?
@Dave: I'm not completely sure. the user has found a workaround.
IMHO, we are probably facing some race condition between upstart native
script Vs
** Changed in: nut (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/608182
Title:
problems with ups (mge pulsar es 8+)
--
Ubuntu-server-bugs
** Changed in: nut (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608182
Title:
problems with ups (mge pulsar es 8+)
--
ubuntu-bugs mailing list
I'm running now manually a script after reboot to start nut, because
scripts run during boot can't start nut, don't know why
--
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
Server Team, which is
I'm running now manually a script after reboot to start nut, because
scripts run during boot can't start nut, don't know why
--
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
/var/log/boot.log says nothing about failed drivers or so
after changing /etc/init.d/nut and rebooting there is no /tmp/mge-utalk.log,
I've tried it several times
regards wolfgang
--
problems with ups (mge pulsar es 8+)
https://bugs.launchpad.net/bugs/608182
You received this bug notification
/var/log/boot.log says nothing about failed drivers or so
after changing /etc/init.d/nut and rebooting there is no /tmp/mge-utalk.log,
I've tried it several times
regards wolfgang
--
problems with ups (mge pulsar es 8+)
https://bugs.launchpad.net/bugs/608182
You received this bug notification
there are no results for mge-utalk in /var/log/messages
if I don't start nut manually with /etc/init.d/nut start, I always get the
following message:
Broadcast Message from n...@l4
(somewhere) at 10:40 ...
** Attachment added: replacement /etc/init.d/nut for debug / investigation
purpose
http://launchpadlibrarian.net/52657944/nut
--
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
Server Team,
2010/7/28 Wolfgang Lubowski
there are no results for mge-utalk in /var/log/messages
any (driver(s) failed) message during the boot?
if I don't start nut manually with /etc/init.d/nut start, I always get the
following message:
Broadcast Message from n...@l4
(somewhere) at 10:40 ...
there are no results for mge-utalk in /var/log/messages
if I don't start nut manually with /etc/init.d/nut start, I always get the
following message:
Broadcast Message from n...@l4
(somewhere) at 10:40 ...
** Attachment added: replacement /etc/init.d/nut for debug / investigation
purpose
http://launchpadlibrarian.net/52657944/nut
--
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
2010/7/28 Wolfgang Lubowski
there are no results for mge-utalk in /var/log/messages
any (driver(s) failed) message during the boot?
if I don't start nut manually with /etc/init.d/nut start, I always get the
following message:
Broadcast Message from n...@l4
(somewhere) at 10:40 ...
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/000:00:00
grep --color=auto mge-utalk
upsc mgeups:
** Changed in: nut (Ubuntu)
Importance: Undecided = Low
--
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
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs mailing list
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/000:00:00
grep --color=auto mge-utalk
upsc mgeups:
** Changed in: nut (Ubuntu)
Importance: Undecided = Low
--
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
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/000:00:00 grep
--color=auto mge-utalk
upsc mgeups:
Error: Driver not connected
ls -la /var/run/nut:
I think I've detected another problem:
If I start NUT-Monitor immediately after running /etc/init.d/nut start it
starts not correctly, I can't do anything, so I have to reboot the system
--
problems with ups (mge pulsar es 8+)
https://bugs.launchpad.net/bugs/608182
You received this bug
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/000:00:00 grep
--color=auto mge-utalk
upsc mgeups:
Error: Driver not connected
ls -la /var/run/nut:
nut monitor works now, I forgot to reboot
thank you very much!
--
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
I think I've detected another problem:
If I start NUT-Monitor immediately after running /etc/init.d/nut start it
starts not correctly, I can't do anything, so I have to reboot the system
--
problems with ups (mge pulsar es 8+)
https://bugs.launchpad.net/bugs/608182
You received this bug
this is the output for upsc mgeups:
device.mfr: MGE UPS SYSTEMS
device.model: Pulsar ES8+
device.type: ups
driver.name: mge-utalk
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal: 0.89
ups.firmware: 0
ups.id: Pulsar ES8+ 0
ups.mfr:
2010/7/23 Wolfgang Lubowski w@gmx.at
this is the output for upsc mgeups:
device.mfr: MGE UPS SYSTEMS
device.model: Pulsar ES8+
device.type: ups
driver.name: mge-utalk
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal:
this is the output for upsc mgeups:
device.mfr: MGE UPS SYSTEMS
device.model: Pulsar ES8+
device.type: ups
driver.name: mge-utalk
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal: 0.89
ups.firmware: 0
ups.id: Pulsar ES8+ 0
ups.mfr:
2010/7/23 Wolfgang Lubowski w@gmx.at
this is the output for upsc mgeups:
device.mfr: MGE UPS SYSTEMS
device.model: Pulsar ES8+
device.type: ups
driver.name: mge-utalk
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0
driver.version: 2.4.3
driver.version.internal:
sorry for bothering you again
autoshutdown works fine, thank you :)
but a graphical tool would be nice too, and nut-monitor doesn't work up to now:
if I start it from terminal, I get the following:
Traceback (most recent call last):
File /usr/bin/NUT-Monitor, line 883, in module
gui =
and there is another thing I don't really understand:
these ups-things aren't started completely, after reboot I get UPS
mge...@localhost is unavailable, so I have to run /etc/init.d/nut start and
then it works.
This is my /etc/default/nut:
# start upsd
START_UPSD=yes
# start upsmon
Hi Wolfgang,
I'm cc'ing NUT-Monitor author, for info
2010/7/22 Wolfgang Lubowski
sorry for bothering you again
autoshutdown works fine, thank you :)
but a graphical tool would be nice too, and nut-monitor doesn't work up to
now:
if I start it from terminal, I get the following:
Traceback
2010/7/22 Wolfgang Lubowski 608...@bugs.launchpad.net
and there is another thing I don't really understand:
these ups-things aren't started completely, after reboot I get UPS
mge...@localhost is unavailable, so I have to run /etc/init.d/nut start
and then it works.
there can be several
** Tags added: patch
--
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
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
sorry for bothering you again
autoshutdown works fine, thank you :)
but a graphical tool would be nice too, and nut-monitor doesn't work up to now:
if I start it from terminal, I get the following:
Traceback (most recent call last):
File /usr/bin/NUT-Monitor, line 883, in module
gui =
and there is another thing I don't really understand:
these ups-things aren't started completely, after reboot I get UPS
mge...@localhost is unavailable, so I have to run /etc/init.d/nut start and
then it works.
This is my /etc/default/nut:
# start upsd
START_UPSD=yes
# start upsmon
Hi Wolfgang,
I'm cc'ing NUT-Monitor author, for info
2010/7/22 Wolfgang Lubowski
sorry for bothering you again
autoshutdown works fine, thank you :)
but a graphical tool would be nice too, and nut-monitor doesn't work up to
now:
if I start it from terminal, I get the following:
Traceback
2010/7/22 Wolfgang Lubowski 608...@bugs.launchpad.net
and there is another thing I don't really understand:
these ups-things aren't started completely, after reboot I get UPS
mge...@localhost is unavailable, so I have to run /etc/init.d/nut start
and then it works.
there can be several
** Tags added: patch
--
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
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52254514/Dependencies.txt
--
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
Server Team, which is subscribed to nut in
these are my conf-files:
** Attachment added: nut.conf
http://launchpadlibrarian.net/52259768/nut.conf
--
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
Server Team, which is subscribed to nut
** Attachment added: nut.conf
http://launchpadlibrarian.net/52259831/nut.conf
--
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
Server Team, which is subscribed to nut in ubuntu.
--
oops, doesn't work like I expected :)
nut.conf:
MODE=none
ups.conf:
[mgeups]
driver = mge-utalk
port = /dev/ttyS0
desc = MGE Pulsar ES 8+
pollinterval=20
upsd.conf:
LISTEN 127.0.0.1 3493
MAXAGE 25
upsd.users:
[admin]
password = mgepass
allowfrom
Hi Wolfgang,
a first and quick comment: this is not a NUT bug, but rather a PSP one!
2010/7/21 Wolfgang Lubowski
oops, doesn't work like I expected :)
nut.conf:
MODE=none
apart from some binary issues with PSP, this one is still sitting on NUT 2.2
compatibility.
On Debian, I've recently
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52254514/Dependencies.txt
--
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.
--
these are my conf-files:
** Attachment added: nut.conf
http://launchpadlibrarian.net/52259768/nut.conf
--
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.
--
** Attachment added: nut.conf
http://launchpadlibrarian.net/52259831/nut.conf
--
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
oops, doesn't work like I expected :)
nut.conf:
MODE=none
ups.conf:
[mgeups]
driver = mge-utalk
port = /dev/ttyS0
desc = MGE Pulsar ES 8+
pollinterval=20
upsd.conf:
LISTEN 127.0.0.1 3493
MAXAGE 25
upsd.users:
[admin]
password = mgepass
allowfrom
Hi Wolfgang,
a first and quick comment: this is not a NUT bug, but rather a PSP one!
2010/7/21 Wolfgang Lubowski
oops, doesn't work like I expected :)
nut.conf:
MODE=none
apart from some binary issues with PSP, this one is still sitting on NUT 2.2
compatibility.
On Debian, I've recently
51 matches
Mail list logo
