Public bug reported:
$ swift stat -- container 'åbject'
Traceback (most recent call last):
File "/usr/bin/swift", line 1479, in
globals()['st_%s' % args[0]](parser, argv[1:], thread_manager)
File "/usr/bin/swift", line 671, in st_stat
command_helpers.stat_object(conn, options, args, t
Another similar-looking crash file (3.3.8-1ubuntu6.2 as well) in case it
could be useful.
** Attachment added: "_usr_lib_squid3_pinger.0.crash"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4306990/+files/_usr_lib_squid3_pinger.0.crash
--
You received this bug not
Merged the changes into 0006-ups-conf-maxretry.patch as requested.
** Patch added:
"http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/4/2";
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+attachment/4295435/+files/4_2.diff
** Changed in: nut (Ubuntu)
Sta
** Branch linked: lp:~iheino+ub/+junk/nut-upsconf-docfix
--
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/1405822
Title:
Default ups.conf should have maxretry setting above examples secti
Public bug reported:
Default/sample ups.conf has maxretry setting at end. Above that are
examples and an empty line.
Uncommenting any of the examples or merging with older configs are
likely to end up with a broken config file, since the parser will
interpret existing maxretries to be inside driv
Trusty issue seems to be different from original one, to actually get
the error message printed I had to use:
$ sudo -g nut -u nut upsdrvctl start
... which revealed an unrelated documentation bug in newer ups.conf.
Might file another bug for that unless one is already filed.
** Tags removed: t
Reinstalled nut on 14.04.1 with identical changes in config files, got
same issue again.
udevadm trigger does not seem to get activated, not even by replugging ups.
(command used to start it right after install + editing config files: sudo
service nut-server restart)
Bus 003 Device 003: ID 06da:
Correction to above: Udevadm-trigger does seem to get fired. Symptoms
looked indentical but might be a different issue this time.
crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
FYI neel, current version in 14.04.1 LTS (1.5.4+bzr2294-0ubuntu1.1) does
not seem include a fix for this. A backport (or SRU?) would be nice to
have for this. Or a ReleaseNotes entry at least.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
--
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/920844
Title:
nut-client is missing /etc/init.d/ups-monitor for MODE=netclient (is
in nut-server)
To manage notifications about this bug
Public bug reported:
Installed only nut-client in order to use nut with MODE=netclient -
/etc/init.d/nut seems to exist only in nut-server, which is otherwise
unnecessary for MODE=netclient.
As both nut-server and nut-client need /etc/init.d/nut, either it should
be moved to libupsclient1 or bo
After changing port back to auto it seems to work. System has not been rebooted
since installing nut.
Could this be some form of a race condition as speculated in other bug reports?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut i
--
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/850672
Title:
"port = auto" does not work with bcmxcp_usb (powerware 5115)
To manage notifications about this bug go to:
https://bugs.laun
Public bug reported:
With the following ups.conf (using the only documented (bcmxcp_usb(8))
value of "auto" for port) nut fails to connect to the ups:
[powerware]
driver = bcmxcp_usb
port = auto
Sep 14 08:59:37 ub3 upsd[31413]: listening on 127.0.0.1 port 3493
Sep 14 08:59:37 ub3 upsd[31413]: li
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/783193
Title:
package openssh-server 1:5.8p1-1ubuntu3 failed to install/upgrade:
subprocess new pre-installation script returned erro
Public bug reported:
Natty installation with text mode installer, openssh-server task
selected. May be an issue with the (default, most likely .fi) mirror
used.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: openssh-server 1:5.8p1-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-gener
16 matches
Mail list logo
