[Bug 175806] Re: dhclient tries to chmod /etc/resolv.conf only before it creates it
Fixing bug #251632 would fix this one also. -- dhclient tries to chmod /etc/resolv.conf only before it creates it https://bugs.launchpad.net/bugs/175806 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 250459] Re: Example in snmpcmd man page shows wrong parameter
I'm working for this ** Changed in: net-snmp (Ubuntu) Assignee: (unassigned) => Salvatore Palma (palma-salvatore) ** Changed in: net-snmp (Ubuntu) Status: New => In Progress -- Example in snmpcmd man page shows wrong parameter https://bugs.launchpad.net/bugs/250459 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp 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 250459] Re: Example in snmpcmd man page shows wrong parameter
This is the bugfix ** Attachment added: "net-snmp_5.4.1~dfsg-7.1ubuntu3.debdiff" http://launchpadlibrarian.net/16321424/net-snmp_5.4.1%7Edfsg-7.1ubuntu3.debdiff ** Changed in: net-snmp (Ubuntu) Assignee: Salvatore Palma (palma-salvatore) => (unassigned) Status: In Progress => Confirmed -- Example in snmpcmd man page shows wrong parameter https://bugs.launchpad.net/bugs/250459 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp 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 118523] Re: mysql server fails to start, claims /var/lib/mysql full
I'm closing this report because this is not reproducible and probably caused by a teporary lack of disk space. Feel free to re-open if you're able to reproduce it and provide more informations. Thanks for your time. ** Changed in: mysql-dfsg-5.0 (Ubuntu) Status: Incomplete => Invalid -- mysql server fails to start, claims /var/lib/mysql full https://bugs.launchpad.net/bugs/118523 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 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 252113] [NEW] Cannot reinstall or uninstall samba
Public bug reported: Binary package hint: samba [EMAIL PROTECTED]:~$ sudo apt-get install samba Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: openbsd-inetd inet-superserver smbldap-tools The following NEW packages will be installed: samba 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. 4 not fully installed or removed. Need to get 3840kB of archives. After this operation, 9429kB of additional disk space will be used. Get:1 ftp://ftp.otenet.gr hardy-proposed/main samba 3.0.28a-1ubuntu4.5 [3840kB] Fetched 3840kB in 18s (209kB/s) Preconfiguring packages ... Selecting previously deselected package samba. (Reading database ... 139229 files and directories currently installed.) Unpacking samba (from .../samba_3.0.28a-1ubuntu4.5_i386.deb) ... Setting up samba-common (3.0.28a-1ubuntu4.5) ... Not replacing deleted config file /etc/samba/smb.conf chmod: cannot access `/etc/samba/smb.conf': No such file or directory dpkg: error processing samba-common (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of smbclient: smbclient depends on samba-common (= 3.0.28a-1ubuntu4.5); however: Package samba-common is not configured yet. dpkg: error processing smbclient (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of smbfs: smbfs depends on samba-common (= 3.0.28a-1ubuntu4.5); however: Package samba-common is not configured yet. dpkg: error processing smbfs (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of winbind: winbind depends on samba-common (= 3.0.28a-1ubuntu4.5); however: Package samba-common is not configured yet. dpkg: error processing winbind (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of samba: samba depends on samba-common (= 3.0.28a-1ubuntu4.5); however: Package samba-common is not configured yet. dpkg: error processing samba (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: samba-common smbclient smbfs winbind samba E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package Architecture: i386 Date: Sat Jul 26 16:07:11 2008 DistroRelease: Ubuntu 8.04 ErrorMessage: dependency problems - leaving unconfigured Package: samba 3.0.28a-1ubuntu4.5 PackageArchitecture: i386 SourcePackage: samba Title: package samba 3.0.28a-1ubuntu4.5 failed to install/upgrade: dependency problems - leaving unconfigured Uname: Linux 2.6.24-20-generic i686 ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- Cannot reinstall or uninstall samba https://bugs.launchpad.net/bugs/252113 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 252113] Re: Cannot reinstall or uninstall samba
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/16321629/Dependencies.txt ** Attachment added: "DpkgTerminalLog.gz" http://launchpadlibrarian.net/16321630/DpkgTerminalLog.gz -- Cannot reinstall or uninstall samba https://bugs.launchpad.net/bugs/252113 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 252113] Re: Cannot reinstall or uninstall samba
OK, I resolved it by typing in terminal: sudo touch /etc/samba/smb.conf sudo dpkg-reconfigure samba-common sudo dpkg-reconfigure windbind sudo apt-get -f install thanks -- Cannot reinstall or uninstall samba https://bugs.launchpad.net/bugs/252113 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 199124] Re: amavisd-release uses wrong socket
** Changed in: amavisd-new (Debian) Status: New => Fix Released -- amavisd-release uses wrong socket https://bugs.launchpad.net/bugs/199124 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new 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 235560] Re: Connect to smb server by name doesn't work, but by IP address does
Thanks Steve, That's fixed it for me (Setting /etc/samba/smb.conf to: name resolve order = lmhosts wins bcast host). I had previously thought that adding the value "wins" in the line in /etc/nsswitch.conf as suggested by va9rant had fixed it, and it had, but it also stopped the network drives mounted in /etc/fstab from mounting, as they stopped being able to be resolved (despite being on the same server as the one I was having trouble manualy mounting). Anyway, thanks Steve Andy -- Connect to smb server by name doesn't work, but by IP address does https://bugs.launchpad.net/bugs/235560 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 251469] Re: samba nightmare
short answer: Because after installing some packages, my system was malfunctioning with substantial breakage of the printing system, I used the synaptic package manager to uninstall both Samba and CUPS, then I manually deleted/moved the /etc/samba folder to ensure that the configs would be recreated when I reinstalled. Long answer see below especially item #5. - as I see it, there are 5 bugs here 1) There is the design issue with Ubuntu itself. If you want to achieve mass adoption of Ubuntu (which it fully deserves) then it MUST be able to interoperate with MS Windows computers "out of the box". Currently it takes a computer expert in order to be able to install and configure Samba to be able to share printers and files. That has to change, it has to be possible for end users with a minimum of skill to be able to right click on a folder or printer and choose sharing and have it work; and to be able to do this without installing and configuring any additional software. 2) Samba is fundamentally broken. I have now spent *days* searching the web and reading the docs and trying the example configs and I still can't get it to work with Windows 98, I keep getting a password prompt and no matter what I enter it gets rejected. I did not yet find the solution to the problem, but I did find other people complaining about the same problem. I have tried what some people said should work and it does not work for me. Now for comparision, I also have installed Mephis Linux and pcLinuxOS and I was able to get Samba to work on both of those computers, Mephis basically worked out of the box, but Samba tended to crash a lot. pcLinuxOS took a but of fuss to get it working properly but once working it doesn't crash the way that Mephis did and it does work with Win 98. Those distros are old, Mephis is from about 3 or 4 years ago and pcLinuxOS is from about 2 years ago, Ubuntu on the other hand has all the latest and greatest versions of software and for the most part it really is much better than any other of the numerous distros I've tried. But this Samba is royally screwed up and does not work the way it is supposed to. Now quite possibly I missed installing some package or other that Samba needs because after all, with the lack of Ubuntu specific docs on the subject I have had to guess at which packages I need to install. 3) Installing certain packages causes breakage. After I installed and used gsambad and a couple of other packages I could no longer get the printer configuration dialog (system-config-printer) to run/open it would crash instead. This might be related to bug #135321 This is why I ended up uninstalling Samba and CUPS and starting over. Which is what caused bug 5 to occur. 4) (Fit and Finish) The package called "system-config-printer" and the package called "gnome-cups-manager" both create an identical menu entry called system/administration/Printer. These two packages both provide overlapping but not identical functionality, I found it useful to have both installed, they should use different names for their menu entries. 5) This is the crash that caused this bug entry to be created, but this is the least of the problems. In fact this problem is not likely to ever occur if the first 3 bugs above are fixed. The crash is caused because I uninstalled Samba and then I removed the /etc/samba/smb.conf. When I reinstalled Samba I expected it to create a pristine new copy of smb.conf. Instead what it does is crash during the install -- which by the way renders Synaptic Package unusable. Even more strangely is that when I restored smb.conf from a backup and then reinstalled Samba, it prompted me and said smb.conf already exists do you want to replace it with the one from the package maintainer. I told it yes to replace it, but after the install was complete I looked at the smb.conf and found that it was the one I had put there, the file was not replaced despite asking me if I wanted it to do so. Happily, reinstalling did fix the breakage which occurred in bug 3 above. But I still don't have a working Samba, although with certain configs I did manage to get XP to be able to have way tooo much access... major security issues there, but I still never got Win 98 to be able to talk to it. By the way, I can access shared folders just fine from another Linux computer. This broken folder sharing functionality is specific to Windows 98. But none of them will print via Samba, I did ultimately get printing to work using IPP which is a bypass of Samba. --- Okay, so that is what this bug is about. As far as I am concerned the actual crash #5 -- which generated this bug -- is mostly a non-issue, fix the other bugs and the circumstances that caused the crash is unlikely to occur. I am not familiar with your bug tracking system, but many would split this into 5 separate entires in order to track each issue separately, on the other hand I've also encountered some ve
[Bug 252200] [NEW] ssh-agent does not expire key
Public bug reported: When I add an SSH key to ssh-agent the lifetime (-t) parameter seems to be ignored: $ ssh-add -t 1 /home/pieter/.ssh/id_work $ ssh-add -l 1024 76:a9:b1:c4:af:ef:b5:b9:6e:39:05:91:c9:a2:b7:89 (DSA) $ ssh [work] -->OK Now I wait, and after 1 second, 1 minute, 1 hour I can still login. However, deleting the key manually: $ ssh-add -D All identities removed. does expire the key correctly: $ ssh [work] Permission denied (publickey). This is risky when you lose a laptop, since the thief has infinite time to login to your hosts. The key should expire after the set expiry time... Environment: $ lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:4.7p1-8ubuntu1.2 Candidate: 1:4.7p1-8ubuntu1.2 Version table: *** 1:4.7p1-8ubuntu1.2 0 500 http://nl.archive.ubuntu.com hardy-updates/main Packages 500 http://security.ubuntu.com hardy-security/main Packages 100 /var/lib/dpkg/status 1:4.7p1-8ubuntu1 0 500 http://nl.archive.ubuntu.com hardy/main Packages ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- ssh-agent does not expire key https://bugs.launchpad.net/bugs/252200 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 120375] Re: cannot boot raid1 with only one disk
Thank you for your comments and I'm sorry me slowly commenting overlapped with
your updated patches. (Of course you just worked to fast ;-), and fixed things
beforehand, perfect. :)
It's good to see that happen, and I've seen the merrit of the while loop
in intrepid now. It looks much better than in hardy.
Yes, lets fix things avoiding immeadiate pittfalls.
Lets think crucial things like initramfs through while we are at it. I'll try
to shake the ends over here that together we'll get those bugs thoroughly out
of our puppy.
>> This means of course we need to know the required array in initramfs.
>Well, that part is doable for the root filesystem at least. It's
${ROOT} within the initramfs scripts.
${ROOT} may be the md device that needs to be run degraded in the corner
case of a non-partitionable, non-crypted, non-lvm, md device.
>What you're talking about is going to be more complicated, and can be handled
>at a later time, by subsequent patches.
Yes, initramfs setup doesn't seem to be easy to me. I'd like to make
much later work unneccesary.
> How about opening a separate bug for independently
allowing/disallowing each array to be started in degraded mode?
It's more than that. For example the --incremental option is neccessary,
because there is this nasty Bug #244792 waiting, (For that reason I have
gathered all that in the BootDegradedRaid comments.)
---
I tested the changes and a crypted root does not yet come up degraded.
The init-premount/mdadm script is responsible to set up arrays. (the
local script depends on it) With udev+mdadm init-premount/mdadm doesn't
have to do more then register its mountfail hook and degrade arrays if
they are not available after a while, if requested.
init-premount/mdadm needs to degrade the array before local-
top/cryptroot.
I see two changes for package mdadm.
-> in init-premount/mdadm:mountroot_fail() run the array degraded imediately
(implemented by ppa9). This will start degraded arrays that are made of several
_crypt devices, after the rootdelay.
-> Regular degraded arrays should be run degraded directly in
init-premount/mdadm, if a "while array not active" slumber loop timed out. (not
yet implemented in ppa9)
Here is why:
With the second change local-top/cryptroot can find its source device.
Cryptsetup is not triggered by udev (and can not be, because non-luks
partitions can not trigger events), its run by local-top/cryptroot. It
doesn't make much sence to enter local-top/cryptroot with an inactive
array, only to let it fail and then wait rootdelay to see that mounting
the rootfs also fails and then try to recover with another rootdelay.
The rootdelay is there to wait for removable root devices. But encrypted
root devices won't show up.
(Its another bug 251164, but serves the understanding:
local-top/cryptroot fails even with full array present when the disk has not
triggerd an udev event. This is because cryptroot does not have its own
checking loop, just as mdadm does not have its own checking loop yet. Only
mounting root has its checking loop. Mixing one into another is not such a good
idea because dependencies get lost and no while condition is adequate for all
waiting involved.)
If a missing encrypted array member shows up 1 second into the rootdelay,
cryptroot can't set up the root device before the failure hooks kick in, the
root device won't show up for sure.
(And maybe we don't want the cryptsetup to be part of a loop with unlimited
trys.)
When instad mdadm waits for the raid device to become active,
local-top/cryptroot will start to set the root device up a second later and
rootdelay would exit immediately.
On my testing system (8.04) local-top/cryptroot is not run at all after
the array is degraded, and the root mounting fails. (cryptroot has no
failure hooks) Ok, cryptsetup is a different package producing the issue
at hand, but we are not yet done with package mdadm.
With manual cryptsetup and mounting of the rootfilesystem, the system
still did not come up degraded. The /home raid isn't set up. Of course
this part of "cannot boot raid1 with only one disk" can be dealt with
in /etc/init.d/mdadm-raid with a "while array inactive" delay loop.
---
When the confusion sets in, orchestred or not, recall.
Do stay on top. Fix the system, not the numberd bugs.
Orientation is your mastership.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
--
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 120375] Re: cannot boot raid1 with only one disk
>From my perspective, what needs to happen is that the issue of booting from a >degraded root on kernel software raid needs a simple, easy to implement fix >for those who run fixed configuration machines, I.E. servers and the like. The provided patches seem to accomplish this goal with a boot parameter that an individual that administers/manages servers would be able to apply. Furthermore, it would be reasonable to me that the server distribution have that boot parameter set as a default to minimize the number of surprises. Someone running a server system is unlikely to be using external storage that is not for backup of some sort or some type of more reliable hardware configuration (SAS, SCSI etc...) and can be considered on their own recognizance for doing weird things like making a raid stripe of firewire drives or something bizarre like that. The issue of a desktop system booting with missing raid elements is another issue. The same workaround should be available for those who choose to run their root on software raid disks with the aforementioned caveats. It would of course be quite nice to have some sort of iterative y/n/r prompt sort of setup for filesystems listed in /etc/fstab so that a marginally technical user could interactively make a decision about continuing to bring the system up with degraded disks or a more technical user could set the kernel parameter, again at their own risk. This discussion, while absolutely necessary, is somewhat political and outside the scope of this bug and belongs in another bug if for no other reason than to close the bug and stabilize the distro for those who are running business functions on it. I am using Alexanders patch and will switch over to Dustin's as I have time. Thank you both for your contributions. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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 252113] Re: Cannot reinstall or uninstall samba
Closing this bug report, thank you for following up. ** Changed in: samba (Ubuntu) Status: New => Invalid -- Cannot reinstall or uninstall samba https://bugs.launchpad.net/bugs/252113 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
