Re: [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
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.net>wrote: > i'll try that, > but, > i have never putted trailing slashes in the mointpoints, > and the double moutings only occus for the cifs ro mounts > > mvg, > G > > On Mon, 2011-10-24 at 12:50 +, Steve Sutton wrote: > > Off topic, but the multiple mount can be caused if you miss trailing > > slashes off the mountpoint in fstab > > > > /media/myfs < bad > > /media/myfs/ < good > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (768506). > https://bugs.launchpad.net/bugs/211631 > > Title: > Network is brought down before network filesystems are unmounted (CIFS > timeout at shutdown) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions > -- 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/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/211631/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 305454] [NEW] 'mount error 13 = Permission denied' when user mounts cifs (sudo works!)
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 /home//media cifs noauto,users,exec,uid=1000,gid=1000,password=,iocharset=utf80 0 With this command line, a user can mount it (if Windows shares the directory!). Yesterday I booted again to Ubuntu on my home computer and there were a lot of updates, I also think Samba got updated. I noticed that all my shares were unshared, so I had to share my folders again. I did so, using the 'Share' tab of the folder and I gave access to guests. Now, on my laptop I can only mount the share as super user (sudo mount ~/media). If I mount the share as normal user, I get the following message: mount error 13 = Permission denied Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) This used to work, but now it doesn't. So, I think this justifies a bug report. Hopefully, this makes Ubuntu better :-). (Again: If I share a map on Windows (Desktop) and access this map with Ubuntu (Laptop), a user can mount it. If I share a map on Ubuntu (Desktop) and access this map with Ubuntu (Laptop), a user cannot mount the share.) Some more info: Both computers are running the following version of Samba: >apt-cache policy samba samba: Installed: 2:3.2.3-1ubuntu3.3 Candidate: 2:3.2.3-1ubuntu3.3 Version table: *** 2:3.2.3-1ubuntu3.3 0 500 http://nl.archive.ubuntu.com intrepid-updates/main Packages 500 http://security.ubuntu.com intrepid-security/main Packages 100 /var/lib/dpkg/status 2:3.2.3-1ubuntu3 0 500 http://nl.archive.ubuntu.com intrepid/main Packages The laptop has proposed enabled. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 'mount error 13 = Permission denied' when user mounts cifs (sudo works!) https://bugs.launchpad.net/bugs/305454 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 305454] Re: 'mount error 13 = Permission denied' when user mounts cifs (sudo works!)
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. -- 'mount error 13 = Permission denied' when user mounts cifs (sudo works!) https://bugs.launchpad.net/bugs/305454 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 768506] [NEW] CIFS VFS Server is slowing down shutdown
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): CIFS VFS: Server xxx.xxx.xxx.xxx has not responded in 300 seconds. Reconnecting... So, I guess the CIFS server does not quit and therefore the computer is not turned off. Can I do anything to stop CIFS server? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: samba 2:3.5.8~dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CIFSMounts: Error: command ['mount', '|', 'grep', 'cifs'] failed with exit code 1: mount: only root can do that Date: Thu Apr 21 20:17:04 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100122) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: Upgraded to natty on 2011-03-26 (26 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty ubuntu-une unity-2d -- 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 settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 768506] Re: CIFS VFS Server is slowing down shutdown
-- 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 settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 768506] Re: CIFS VFS Server is slowing down shutdown
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 is slowing down shutdown -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 491288] [NEW] File corruption after copying files via samba from Karmic to Karmic
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 desktop on my latop and started the copy process on the laptop. After this, I tried to play the files on my desktop. However, I got errors from Exaile: the stream was not correct. So, I used foobar to test the File integrity of the files, and in almost all files, it found errors. I checked on my laptop, and those errors did not exist on the files on the laptop. So, I tried to copy them again using samba, but with the same result. foobar's File Integrity test even give exactly the same errors for the files (see the attached error log). Then, I copied the files using a USB stick and this time, foobar reported al was ok. So, I think this is a bug in the samba package, as copying over samba did not work and an USB stick worked fine. I think I should give more info, but I don't know what to report. $ apt-cache policy samba samba: Installed: 2:3.4.0-3ubuntu5.1 Candidate: 2:3.4.0-3ubuntu5.2 Version table: 2:3.4.0-3ubuntu5.2 0 500 http://nl.archive.ubuntu.com karmic-proposed/main Packages *** 2:3.4.0-3ubuntu5.1 0 500 http://nl.archive.ubuntu.com karmic-updates/main Packages 100 /var/lib/dpkg/status 2:3.4.0-3ubuntu5 0 500 http://nl.archive.ubuntu.com karmic/main Packages $ apt-cache policy ntfs-3g ntfs-3g: Installed: 1:2009.4.4-1ubuntu4 Candidate: 1:2009.4.4-1ubuntu4 Version table: *** 1:2009.4.4-1ubuntu4 0 500 http://nl.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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 member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 491288] Re: File corruption after copying files via samba from Karmic to Karmic
** 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 member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 491288] Re: File corruption after copying files via samba from Karmic to Karmic
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 server), the corruption does not happen. (It doesn't matter if I run Win7 or Linux) I mount the share with the following entry in /etc/fstab: //172.19.3.4/Media/home/ernstblaauw/mediacifs comment=sshfs,username=user,password=pass,noauto,nounix,users,exec,uid=1000,gid=1000,domain=domain,iocharset=utf8 00 The comment is used to unmount the share if the network goes down and remount it if the network comes up. Do I have weird options in my fstab entry? I think this bug is quite severe, I hope it attracts some attention. -- 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 member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 491288] Re: File corruption after copying files via samba from Karmic to Karmic
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 samba from Karmic to Karmic https://bugs.launchpad.net/bugs/491288 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 491288] Re: File corruption after copying files via samba from Karmic to Karmic
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, bug #453579 which also involves data loss has status critical! So this bug deserves such priority too. -- 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 member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 491288] Re: File corruption after copying files via samba from Karmic to Karmic
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 100 /var/lib/dpkg/status On Tue, Jan 12, 2010 at 23:25, Raptor 2101 wrote: > Since "smbfs (2:3.4.0-3ubuntu5)" i experience same problems. I've > mounted my homedirs via CIFS. All works fine (servernio to get KDE-apps > working). After this update i noticed some "extrem" file errors while > using Opera (HD-Cache enabled) and Firefox. Trying to download something > always causes a damaged file. Every large file (> 500kb) results in a > damaged file. > > If i switch from servernio to directio. Firefox and Opera works fine, > now javaws, skype and some other apps craches cause of file corruption. > > But copying files from or to some "normal" mounts works perfectly. > > smb.conf > >>[homes] > >> comment = Home Directories > >> browseable = yes > >> writeable = yes > >> available = yes > >> guest ok = no > >> > >> [Media] > >> path = /storage/Media > >> comment = Mediensammlung > >> nt acl support = yes > >> browsable = yes > >> writeable = yes > >> available = yes > >> guest ok = no > >> inherit permissions = yes > >> hide dot files = yes > > mounting via pam_mount > > >> mountpoint="/home/%(USER)" options="rw,hard,iocharset=utf8,serverino"/> > >> mountpoint="/mnt/Media" options="rw,hard,iocharset=utf8"/> > > /proc/fs/cifs/DebugData > >>Display Internal CIFS Data Structures for Debugging > >>--- > >>CIFS Version 1.60 > >>Active VFS Requests: 790 > >>Servers: > >>1) Name: 192.168.99.2 Domain: WORKGROUP Uses: 5 OS: Unix > >>NOS: Samba 3.4.0Capability: 0x80f3fd > >> SMB session status: 1 TCP status: 1 > >>Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0 > >>Shares: > >>1) Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x1002f > PathComponentMax: 255 Status: 0x1 type: 0 > >>2) Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x1002f > PathComponentMax: 255 Status: 0x1 type: 0 > >>3) Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x1002f > PathComponentMax: 255 Status: 0x1 type: 0 > >>4) Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x1002f > PathComponentMax: 255 Status: 0x1 type: 0 > >>5) Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x1002f > PathComponentMax: 255 Status: 0x1 type: 0 > >> > >>MIDs: > > dmesg and /var/log/syslog shows nothing interesting even with “echo 3 > > /proc/fs/cifs/cifsFYI” > > -- > 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 direct subscriber > of the bug. > -- 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 member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
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 noticed that there isn't any log output, neither in the console messages at boot time nor in the syslog. I injected an error by misspecifying the nis domain. This also did not produce any output anywhere that might help to debug. I think (but I am no sure) that you would see more output with the current stock nis package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
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) Thanks Clint for finally fixing this bug. -- 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/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
now I have tested squid 2.7.STABLE7-1ubuntu12.3 on lucid (on a copy of the system where this bug report originated) -> squid starts with network not yet available -> invocation of /etc/resolvconf/update-libc.d/squid does no longer kill it -> everything else is normal Thus verified. There is one thing I do not understand yet: I thought 'restart' was changed to 'reload' in /etc/resolvconf/update-libc.d/squid (see comment #16 above). But it isn't. Still it works, the bug is fixed. -- 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/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
the new maverick package 2.7.STABLE9-2ubuntu5.1 still has the problem that squid is killed when the resolvconf script is called, exactly as described in comment #7 above. The maverick packages still has 'reload squid' in /etc/resolvconf/update- libc.d/squid. This kills squid, so that it is not running after the interface comes up. It should contain 'restart squid' which works fine. -> it seems to me that restart and reload was mixed up in some of the discussion following comment #7 -> sorry I was not careful enough when I tested the proposed-package, this is very embarassing :-( -> it seems the bug needs to be reopened -- 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/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 809526] [NEW] squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in /etc/resolvconf/update-libc.d/squid
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 This kills squid. The syslog shows "squid main process (nnn) killed by HUP signal" I freshly installed squid and squid-common after purging them, nothing was changed after installation, system was rebooted before test ** Affects: squid (Ubuntu) Importance: Undecided Status: 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 /etc/resolvconf/update-libc.d/squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
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 bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 809526] Re: squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in /etc/resolvconf/update-libc.d/squid
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 hand months ago and it was used daily. -- 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 /etc/resolvconf/update-libc.d/squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 809526] Re: squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in /etc/resolvconf/update-libc.d/squid
** 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 /etc/resolvconf/update-libc.d/squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 782890] Re: no ping response on all hosts after upgrade
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/782890/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 835829] Re: package bind9 1:9.7.3.dfsg-1ubuntu2.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
-- 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 den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/835829/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 835829] [NEW] package bind9 1:9.7.3.dfsg-1ubuntu2.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
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 Architecture: i386 Date: Sun Aug 28 06:43:33 2011 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) RelatedPackageVersions: bind9utils 1:9.7.3.dfsg-1ubuntu2.2 apparmor 2.6.1-0ubuntu3 SourcePackage: bind9 SyslogBind9: Title: package bind9 1:9.7.3.dfsg-1ubuntu2.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to natty on 2011-05-15 (104 days ago) mtime.conffile..etc.bind.db.0: 2011-02-28T06:23:36.422062 mtime.conffile..etc.bind.db.127: 2011-02-28T06:24:36.530061 mtime.conffile..etc.bind.db.255: 2011-02-28T06:24:16.998062 mtime.conffile..etc.bind.db.local: 2011-02-28T06:24:09.258062 mtime.conffile..etc.bind.named.conf: 2011-03-27T14:42:18.054062 mtime.conffile..etc.bind.named.conf.default.zones: 2011-02-28T06:16:07.818062 mtime.conffile..etc.bind.named.conf.local: 2011-03-28T20:43:22.810062 mtime.conffile..etc.bind.named.conf.options: 2011-03-28T06:58:34.222062 ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- 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 den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/835829/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 -> 2
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 -> works -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561779/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 -> 2
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561779/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 365259] [NEW] on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde
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 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde https://bugs.launchpad.net/bugs/365259 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 365259] Re: on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde
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 correctly in a kde debconf window, the questions also appear in the term.log but in a different format. As an example I show the output for dnsmasq at the bottom === [...] Vorbereiten zum Ersetzen von samba-common 2:3.2.3-1ubuntu3.5 (durch .../samba-common_2%3a3.3.2-1ubuntu3_i386.deb) ... b) ... Entpacke Ersatz für samba-common ... [...] Richte samba-common ein (2:3.3.2-1ubuntu3) ... momentanen Version. Installiere neue Version der Konfigurationsdatei /etc/dhcp3/dhclient-enter-hooks.d/samba ... Paket-Konfiguration ┌──┤ Samba Server ├──┐ ││ │ Eine neue Version der │ │ Konfigurationsdatei│ │ /etc/samba/smb.conf ist│ │ verfügbar, aber die installierte │ │ Version wurde verändert. │ ││ ││ ││ └┘ ─┤ Samba Server ├ mit smb.conf Version des Paket-Betreuers ins ↑ aktuell installierte Version be ▮ ─ Richte samba-common ein (2:3.3.2-1ubuntu3) ... Installiere neue Version der Konfigurationsdatei /etc/dhcp3/dhclient-enter-hooks.d/samba ... Replacing config file /etc/samba/smb.conf with new version === [...] Richte dnsmasq ein (2.47-3) ... Installiere neue Version der Konfigurationsdatei /etc/init.d/dnsmasq ... Installiere neue Version der Konfigurationsdatei /etc/default/dnsmasq ... e Version herausgegeben. Was möchten Sie damit machen? Ihre Wahlmöglichkeiten sind: Y oder I : Die Version des Paket-Betreuers installieren N oder O : Die momentan installierte Version beibehalten D : Die Unterschiede zwischen den Versionen anzeigen Z : Prozess in den Hintergrund, um die Situation zu begutachten Der Standardweg ist das Beibehalten der momentanen Version. *** dnsmasq.conf (Y/I/N/O/D/Z) [Vorgabe=N] ? *** dnsmasq.conf (Y/I/N/O/D/Z) [Vorgabe=N] ? y Installiere neue Version der Konfigurationsdatei /etc/dnsmasq.conf ... [...] === -- on update to jaunty, configuration questions are asked in curses dialog but debconf is configured to use kde https://bugs.launchpad.net/bugs/365259 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] [NEW] openvpn doesn't start automatically at boot time
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 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20091009) Package: openvpn 2.1~rc19-1ubuntu1 [modified: usr/sbin/openvpn] ProcEnviron: LANG=de_CH.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: openvpn Uname: Linux 2.6.31-12-generic i686 XsessionErrors: (gnome-settings-daemon:2721): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:3744): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:3769): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] Re: openvpn doesn't start automatically at boot time
** 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 openvpn in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449323] [NEW] openssh-server doesn't start automatically at boot time
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: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20091009) Package: openssh-server 1:5.1p1-6ubuntu1 ProcEnviron: LANG=de_CH.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: openssh Uname: Linux 2.6.31-12-generic i686 XsessionErrors: (gnome-settings-daemon:2721): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:3744): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:3769): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449323] Re: openssh-server doesn't start automatically at boot time
** 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 subscribed to openssh in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449323] Re: openssh-server doesn't start automatically at boot time
** 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] Re: openvpn doesn't start automatically at boot time
** 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] Re: openvpn doesn't start automatically at boot time
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 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] Re: openvpn doesn't start automatically at boot time
@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 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] Re: 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 fact that the network is brought up later fine. I'll be able to send the requested files tomorrow I think -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449326] Re: openvpn doesn't start automatically at boot time
@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 because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 449323] Re: openssh-server doesn't start automatically at boot time
*** 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 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 369682] Re: AutoFS direct maps not working with NFSv4 exports
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 because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 369682] Re: AutoFS direct maps not working with NFSv4 exports
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 unclear to me after having looked at the last 4 package versions. This bug should be closed as invalid. -- AutoFS direct maps not working with NFSv4 exports https://bugs.launchpad.net/bugs/369682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] [NEW] squid starts and stops immediately (after upgrade from karmic to lucid)
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 DistroRelease: Ubuntu 10.04 Package: squid 2.7.STABLE7-1ubuntu11 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Apr 12 21:12:34 2010 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: squid ** Affects: squid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
** 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) https://bugs.launchpad.net/bugs/561750 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] [NEW] squid is not started on runlevel transition 1 -> 2
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 would stop on entering runlevel 1 and be started again on entering runlevel 2 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: squid 2.7.STABLE7-1ubuntu11 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Mon Apr 12 21:48:49 2010 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: squid ** Affects: squid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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 squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 -> 2
** 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 squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
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 prevent squid from doing the DNS tests during start (there are no error messages in /var/log/squid attached earlier). ** Attachment added: "/etc/network/interfaces" http://launchpadlibrarian.net/44118835/interfaces -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
** 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
$ 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 Apr 14 07:38:35 rechner6 init: anacron main process (1296) killed by TERM signal Apr 14 07:38:35 rechner6 init: plymouth-stop pre-start process (2288) terminated with status 1 -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
- 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 package) /etc/resolvconf/update-libc.d/squid which contains the command 'invoke-rc.d squid reload' This command does the wrong thing, it stops squid: r...@rechner6:~# start squid squid start/running, process 3328 (now squid is usable) r...@rechner6:~# /etc/resolvconf/update-libc.d/squid Rather than invoking init scripts through /etc/init.d, use the service(8) [...] r...@rechner6:~# status squid squid stop/waiting (the squid/cache.log shows the normal shutdown sequence) ** Attachment added: "/var/log/squid/cache.log" http://launchpadlibrarian.net/44224116/cache.log -- 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 subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561779] Re: squid is not started on runlevel transition 1 -> 2
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 received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
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 ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
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 management of the dependency of nis on a working network interface is not correctly done ** Changed in: nis (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1068036] [NEW] postfix (precise) has lost the ability to lookup aliases in NIS
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 - and mail is not forwarded Obviously some build switch was changed between 10.04 and 12.04. In 10.04: $ postconf -m | grep nis nis In 12.04 the output is empty. But still in 12.04 the postfix.postinst skript looks for nis and creates an appropriate mail.cf entry for lookup in nis:mail.aliases $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 $ apt-cache policy postfix postfix: Installiert: 2.9.3-2~12.04.3 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1068036 Title: postfix (precise) has lost the ability to lookup aliases in NIS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1068036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1068036] Re: postfix (precise) has lost the ability to lookup aliases in NIS
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: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1068036 Title: postfix (precise) has lost the ability to lookup aliases in NIS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1068036/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1007273] Re: autofs does not start automatically after reboot
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. https://bugs.launchpad.net/bugs/1007273 Title: autofs does not start automatically after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1007273/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs