several people have commented that they have the same or similar
problems
** Changed in: autofs5 (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
on the system where I had the problem I did this to verify the fix
- removed workarounds in main.cf
- sent emails and verified that they trigger the error and remain in the queue
- installed 2.9.3-2~12.04.4
- bug is gone, mail works normally
** Tags removed: verification-needed
** Tags added:
Public bug reported:
on a (freshly installed) system with nis authentication, postfix is no longer
able to read aliases from the nis table mail.aliases.
in 10.04 it worked
symptoms are:
- errors in /var/log/mail.log:
warning: nis:mail.aliases is unavailable. unsupported dictionary type: nis
-
it is an error for ypbind to not start correctly when the network
interface is managed by network-manager and thus comes up a bit slowly
of course, changing the configuration to not rely on network-manager, as
explained in comment #3 is a workaround
still i would consider this a bug: the
just to add a data point: starting 2012-04-19 my lucid machine is
working with 3.17-31ubuntu0.10.04.3 from proposed with. A few nis
accounts are being used regularly. There have been a large number of
suspend resume cycles and various reboots without any nis related
problems.
--
You received
I have installed 3.17-31ubuntu0.10.04.3 on lucid after purging the previous
version including our hand crafted upstart configuration.
- Installation went fine
- I have tested the function as a NIS client successfully
- starting after reboot works, it also survives a suspend/resume cycle
But I
This bug is disappeared for me (it started reapppearing a week ago), with
the changes in /etc/init/dbus.conf still in effect.
Maybe this has to do with my reinstall of grub2; after that, my computer
shuts again. This possinly indicates it has to do with certain boot options?
--
You received
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
On Mon, Oct 24, 2011 at 16:03, Gonzals, S.
211...@bugs.launchpad.netwrote:
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
tested with lucid 10.04.3 - OK
procedure:
with old package
- access the web through squid
- init 1
- init 2
- ps aux | grep squid # - squid not running
with proposed package
- access the web through squid
- init 1
- init 2
- ps aux | grep squid # - squid IS running
- access the web through squid
tested with an up-to-date maverick system
same procedure as above - OK
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561779
Title:
squid is not started on runlevel transition 1 - 2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/835829
Title:
package bind9 1:9.7.3.dfsg-1ubuntu2.2 failed to install/upgrade:
Unterprozess installiertes post-installation-Skript gab
Public bug reported:
This behavior faced up during normal Patch-Update. I can't give you
closer informations.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: bind9 1:9.7.3.dfsg-1ubuntu2.2
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
** Changed in: backuppc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
https://bugs.launchpad.net/bugs/782890
Title:
no ping response on all hosts after upgrade
To
** Changed in: squid (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/809526
Title:
squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in
this is an issue in maverick only
- lucid already uses 'restart squid' - ok
- natty uses 'reload squid' and this works fine due to some other changes - ok
- I do not know about oneiric but I guess it works like natty
yes, the fix is indeed as you describe it in comment #1.
I applied that fix by
Public bug reported:
this is a leftover issue from bug
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750
I am creating a new bug report to leave complicated history behind.
The maverick squid package 2.7.STABLE9-2ubuntu5.1 calls 'reload squid' in
/etc/resolvconf/update-libc.d/squid
well, i guess originally this bug had been about 'reload' not working
correctly (#7), but focus has shifted over time.
To keeps things simple I have created a new bug report for the remaining
maverick problem at
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526
--
You received this
I tested the package from maverick-proposed against the current package
from maverick: both of the problems that were discussed in this bug
report are now gone (squid starts sucessfully with network not being
available yet, resolvconf script reloads the squid configuration and
does not kill squid)
The CIFS share is mounted in fstab. If I do sudo umount /mnt/share,
the computer will turn off normally.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/768506
Title:
CIFS VFS Server
Public bug reported:
Binary package hint: samba
Since I upgraded to Natty, the computer takes a very long time to shut
down (approximately 5 minutes). I made a movie from the shutdown
messages and I think the CIFS server is not stopped correctly. I see the
following message (for a split second):
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/768506
Title:
CIFS VFS Server is slowing down shutdown
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
In my setup this bug causes excessive boot delays. I want to question
the wishlist importance.
--
NIS upstart dependancy broken for lucid
https://bugs.launchpad.net/bugs/569757
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in
Runlevel changes have been an essential functionality of unix / linux
for a long time. You could use them for regular administration tasks.
Now this stopped to work. This bug is a regression.
--
squid is not started on runlevel transition 1 - 2
https://bugs.launchpad.net/bugs/561779
You
I have an ethernet interface with a static IP address, there is no
traffic routed to the internet over this interface.
Secondly there is a dsl-connection (pppoe) that provides the route to
the internet.
See also attached file /etc/network/interfaces
But I also have changed /etc/default/squid to
** Attachment added: /etc/default/squid
http://launchpadlibrarian.net/44118845/squid
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is
$ grep squid /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
$ grep init: /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
Apr 14 07:38:33 rechner6 init: ssh main process (1095) terminated with status
255
- there is no respawn option in /etc/init/squid.conf (but I think this
wouldn't normally be a problem, except when squid crashed by itself)
- there is exactly one thing that does something to squid when the dsl-
interface is brought up (I have resolvconf installed which is suggested
by the squid
Public bug reported:
Binary package hint: squid
after booting, squid starts normally, and then stops again immediately.
There is no error (see logfile).
After that i can start squid with 'sudo start squid' and it works
flawlessly (this bug report is made through it).
ProblemType: Bug
** Attachment added: squid log file
http://launchpadlibrarian.net/43955964/cache.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43955337/Dependencies.txt
--
squid starts and stops immediately (after upgrade from karmic to lucid)
Public bug reported:
Binary package hint: squid
when you go to runlevel 1 for maintenance with 'telinit 1', squid is
stopped correctly
when you go back to runlevel 2 with 'telinit 2' squid is not started
because /etc/init/squid.conf does not contain a condition for that.
in karmic, squid
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43958720/Dependencies.txt
--
squid is not started on runlevel transition 1 - 2
https://bugs.launchpad.net/bugs/561779
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Indeed, a default install of karmic-autofs has
DISABLE_DIRECT=1
in /etc/default/autofs
This is also documented in /usr/share/doc/autofs/README.direct
A workaround might be to use autofs5.
According to the original poster the behaviour changed at some point in
time. The reason remains
On Lucid Alpha 2, it looks like the bug is fixed: I cannot reproduce it like
I did it before.
$ apt-cache policy samba
samba:
Installed: 2:3.4.3-2ubuntu2
Candidate: 2:3.4.3-2ubuntu2
Version table:
*** 2:3.4.3-2ubuntu2 0
500 http://nl.archive.ubuntu.com lucid/main Packages
I think this bug deserves a higher priority, because it seems the copy
process finishes successfully, but people end up in having corrupted
files. I think this behavior is easily repeated by other people and
could do a lot of harm.
So please, set the priority to 'critical' (or high). For example,
Does 'Fix Released' means this is fixed in an Ubuntu package (I would like to
test!) or does it mean the bug is fixed upstream?
I don't know how to apply the patch of the upstream bug report, so with only
that patch, I will not be able to test this.
--
File corruption after copying files via
I have some more information:
- this does not happen if the desktop computer is running Windows 7 (So I'm
copying from my latop with Karmic 2.6.31.15 to the Windows computer).
- Currently, the share is mounted via /etc/fstab. If I mount the share
using the Gnome interface (Places Connect to
Public bug reported:
Binary package hint: samba
Yesterday, I tried to copy flac files from my laptop (Ubuntu Karmic,
32-bit, running ext4 but source files are on ntfs) to my desktop (Ubuntu
Karmic, 32-bit, running ext4 but destination was on ntfs) via samba. I
mounted the samba share of my
** Attachment added: foobar File Integrity Check.txt
http://launchpadlibrarian.net/36328212/foobar%20File%20Integrity%20Check.txt
--
File corruption after copying files via samba from Karmic to Karmic
https://bugs.launchpad.net/bugs/491288
You received this bug notification because you are a
this bug is still present in karmic
lines in auto.master starting with /- seem to be just ignored
** Changed in: autofs (Ubuntu)
Status: Won't Fix = Confirmed
--
AutoFS direct maps not working with NFSv4 exports
https://bugs.launchpad.net/bugs/369682
You received this bug notification
*** This bug is a duplicate of bug 449326 ***
https://bugs.launchpad.net/bugs/449326
@Kamus
Yes, this bug has been fixed with latest updates, thanks (the other
duplicate-marked bug I opened about openvpn has thus been marked fixed).
--
openssh-server doesn't start automatically at boot
@small_frenchy,
I found out that openssh, openvpn and cups don't start automatically on this
machine, do cups start on your system (or ssh if you have it installed) ?
--
openvpn doesn't start automatically at boot time
https://bugs.launchpad.net/bugs/449326
You received this bug notification
@Mathias Gug
Yes that's on the same system. I will post the requested informations as soon
as I get a hand on this machine again. Networking works (after login as it's
using wireless/Network Manager to connect).
--
openvpn doesn't start automatically at boot time
@Thierry Carrez
Nope this is not checked. But I can tell you that I have more than 50 jaunty
users where I only apt-get install openssh-server and openvpn where most of
those users are using laptops and Network Manager in its default configuration
and both ssh server and vpn client handle the
Public bug reported:
Binary package hint: openvpn
On a fresh Karmic beta installation I installed openvpn but it doesn't
autostart at boot. Machines upgraded from jaunty to karmic don't exhibit
this issue.
ProblemType: Bug
Architecture: i386
Date: Mon Oct 12 10:06:03 2009
DistroRelease: Ubuntu
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33483354/Dependencies.txt
--
openvpn doesn't start automatically at boot time
https://bugs.launchpad.net/bugs/449326
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
On a fresh Karmic beta installation I installed openssh-server but it
doesn't autostart at boot. Machines upgraded from jaunty to karmic don't
exhibit this issue.
ProblemType: Bug
Architecture: i386
Date: Mon Oct 12 10:01:43 2009
DistroRelease: Ubuntu 9.10
InstallationMedia:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33483304/Dependencies.txt
--
openssh-server doesn't start automatically at boot time
https://bugs.launchpad.net/bugs/449323
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags added: regression-potential
--
openssh-server doesn't start automatically at boot time
https://bugs.launchpad.net/bugs/449323
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
** Tags added: regression-potential
--
openvpn doesn't start automatically at boot time
https://bugs.launchpad.net/bugs/449326
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in ubuntu.
--
Ubuntu-server-bugs mailing list
I'm using the same configuration and the vpn is started successfully if
I start it using /etc/init.d/openvpn start in both cases.
I guess something is up with the init.d-upstart transition but I'm not
sure.
--
openvpn doesn't start automatically at boot time
the question asked in the terminal window was do you want to keep your
smb.conf or install the one provided in the package
below are some excerpts from /var/log/dist-upgrade/term.log (which is in
German, but you will identify what happens)
for other packages where the questions were asked
Public bug reported:
Binary package hint: samba-common
on update to jaunty, configuration questions are asked in curses dialog
inside the terminal-window of the update manager.
But debconf is configured to use kde, and questions for other packages
actually have been asked with kde dialogs
**
In this bug report, I used anonymous (guest) access to the share. I
changed the login policy and now I have to specify a username and
password. In contrary to the above bug report, a user is able to mount
the new configuration without problems. It seems the bug is related to
guest access.
--
Public bug reported:
Binary package hint: samba
I'm using samba to share files between my home computer (dual boot
Windows/Ubuntu 8.10) and my laptop (Ubuntu 8.10). Most of the time,
Windows is running at the home computer. Sharing goes fine with the
following fstab entry:
//172.19.3.4/Media
Do people who were experiencing this bug with a wired connexion still
have this issue in Intrepid fully up to date ? I had this issue on my
desktop computer but it seems fixed now ?
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received
55 matches
Mail list logo
