[Bug 891707] Re: java webstart creates infinite open windows, desktop DoS
Can fix by downloading jnlp file Right click on file and change properties such that it is opened with Sun Java Webstart rather than a Browser (not sure whether I set that at some stage or whether it was set automatically) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891707 Title: java webstart creates infinite open windows, desktop DoS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/891707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891707] Re: java webstart creates infinite open windows, desktop DoS
Experiencing same problem on Ubuntu 11.10 running Firefox 10.0.2 with sun java6 plugin installed Connecting to a supermicro kvm Tabs keep opening firefox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891707 Title: java webstart creates infinite open windows, desktop DoS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/891707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527401] Re: grub-installer fails to install on a raid1 array
Just to re-iterate, I succesfully installed ubuntu 10.04 lts beta2 to a RAID1 config without any problems after the initial bug identified here was fixed. The grub installer also seemed to install copies of itself to both drives which is a plus (I've been manually doing that in the past). Keep up the good work. -stephen -- Stephen Mulcahy Atlantic Linux http://www.atlanticlinux.ie Registered in Ireland, no. 376591 (144 Ros Caoin, Roscam, Galway) -- grub-installer fails to install on a raid1 array https://bugs.launchpad.net/bugs/527401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 527401] Re: grub-installer fails to install on a raid1 array
Wow - great work! Verified that grub now installs on RAID1 system without errors. Have not yet verified that it boots correctly as I'm running into some graphics issues at boot-time but I suspect this is unrelated. Thanks, -stephen -- Stephen Mulcahy Atlantic Linux http://www.atlanticlinux.ie Registered in Ireland, no. 376591 (144 Ros Caoin, Roscam, Galway) -- grub-installer fails to install on a raid1 array https://bugs.launchpad.net/bugs/527401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484343] Re: openldap section of ubuntu server guide should document simple replication
Thanks for your work on this. I'm afraid I'm currently running a suitable Karmic/Lucid server. It'll be a while before I can migrate to Lucid and test this. I'll log a further bug if I run into any problems at that stage. -- openldap section of ubuntu server guide should document simple replication https://bugs.launchpad.net/bugs/484343 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527401] Re: grub-installer fails to install on a raid1 array
Just ran into this this morning when test installing a server with beta1 - would be very nice to have this fixed for this release -- grub-installer fails to install on a raid1 array https://bugs.launchpad.net/bugs/527401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484343] [NEW] openldap section of ubuntu server guide should document simple replication
Public bug reported: Binary package hint: ubuntu-docs The section on openldap in the ubuntu server guide (e.g. https://help.ubuntu.com/9.10/serverguide/C/openldap-server.html but also previous versions) addresses openldap replication - BUT only Multi- Master mode - which is arguably not the best approach to replication (in terms of complexity). It also uses the ldap admin account for replication. Consider also documenting a simpler master-slave replication configuration using a read-only account on the master for replication purposes. I tried configuring such an environment using the server guide and the openldap admin guide but failed - hence my request to provide such a config. ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New -- openldap section of ubuntu server guide should document simple replication https://bugs.launchpad.net/bugs/484343 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311637] Re: dmraid enabled on install target even if disabled during installation
I also got bitten by this (long-winded description of problem and solution at http://atlanticlinux.ie/blog/?p=137) - you can recover from this by booting from the install cd in rescue mode after installation and purging the dmraid package from your installation -- but I'm +1 for *not* installing the dmraid package if you decline SATA/fake raid during installation. A nodmraid kernel flag might also work. -- dmraid enabled on install target even if disabled during installation https://bugs.launchpad.net/bugs/311637 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338157] Re: FAI is out of date
I'd suggest removing it entirely until such time as it works. Or at least add a big readme clarifying the known, non-working status of it in Ubuntu. -- FAI is out of date https://bugs.launchpad.net/bugs/338157 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409344] [NEW] pipe pdsh output through dshbak -c by default
Public bug reported: Binary package hint: pdsh It would be more useful if pdsh piped its output through dshbak -c by default ** Affects: pdsh (Ubuntu) Importance: Undecided Status: New -- pipe pdsh output through dshbak -c by default https://bugs.launchpad.net/bugs/409344 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409340] Re: pdsh documentation is incorrect about where default rcmd is set
Of course cat'ing /usr/bin/pdsh would also have revealed the magic that is /etc/pdsh/rcmd_default :) -- pdsh documentation is incorrect about where default rcmd is set https://bugs.launchpad.net/bugs/409340 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409340] [NEW] pdsh documentation is incorrect about where default rcmd is set
Public bug reported: Binary package hint: pdsh /usr/share/doc/pdsh/README.Debian suggests the default rcmd can be changed by creating /etc/genders/pdsh with a single line such as ssh This doesn't seem to work. Running strace on pdsh suggests that creating /etc/pdsh/rcmd_default with the single line ssh does seem to work I could see no reference to this in the man page either. I suggest a) documenting it and maybe b) setting the default to ssh (which is going to be far more useful on a typical modern day cluster) Tested this on the intrepid and jaunty packages - same problem seems to exist on both ** Affects: pdsh (Ubuntu) Importance: Undecided Status: New -- pdsh documentation is incorrect about where default rcmd is set https://bugs.launchpad.net/bugs/409340 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352446] Re: libtomcat6-java depends on libecj-java
*** This bug is a duplicate of bug 347393 *** https://bugs.launchpad.net/bugs/347393 So it is, apologies for not checking all the dependencies before opening this. Feel free to close. -- libtomcat6-java depends on libecj-java https://bugs.launchpad.net/bugs/352446 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352446] [NEW] libtomcat6-java depends on libecj-java
Public bug reported: Binary package hint: tomcat6 libtomcat6-java depends on libecj-java which in turn installs gcj. In practice, if I have sun-java6-jdk installed and then install tomcat6 with sudo aptitude -R install tomcat6 which doesn't pull ecj-gcj libecj-java-gcj as dependencies, everything works fine and my environment continues using sun java6 (which I need for my project). Can we rectify the dependencies here to avoid this implicit dependency on gcj? ** Affects: tomcat6 (Ubuntu) Importance: Undecided Status: New -- libtomcat6-java depends on libecj-java https://bugs.launchpad.net/bugs/352446 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347837] [NEW] Allow partitioning of more than one disk
Public bug reported: I know this is a limitation of the partman tool used by kickseed and that it may take some time to fix but nonetheless, I think it would be a nice addition to kickstart. I can work-around this at the moment by adding the following to my ks.cfg so I guess this is low priority. (suggestions on how to do what I'm doing in a better way welcome, please add a comment to this bug - its a good source of info for workarounds for now). Note, since parted claims to not support ext3 directly, I'm creating an ext2 filesystem and then converting to ext3 with tune2fs afterwards. %post --interpreter=/bin/bash parted -s /dev/sdb mklabel msdos sudo parted -s /dev/sdb mkpartfs primary ext2 0 1000GB tune2fs -j /dev/sdb1 mkdir /webstar2 echo "/dev/sdb1 /webstar2 ext3 noatime 0 0" >> /etc/fstab ** Affects: kickseed (Ubuntu) Importance: Undecided Status: New -- Allow partitioning of more than one disk https://bugs.launchpad.net/bugs/347837 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48311] Re: kickstart partitioning fails with --recommended or --asprimary
Hi, I just got bitten by this bug also. The following does not work (on reboot, the I get a kernel panic on being unable to mount root), part swap --size 4096 --asprimary --ondisk sda part / --fstype ext3 --size 10240 --asprimary --ondisk sda part /webstar1 --fstype ext3 --size 1 --grow --asprimary --ondisk sda The following works as expected (giving me logical partitions) part swap --size 4096 --ondisk sda part / --fstype ext3 --size 10240 --ondisk sda part /webstar1 --fstype ext3 --size 1 --grow --ondisk sda Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0004b696 Device Boot Start End Blocks Id System /dev/sda1 * 1 498 4000153+ 82 Linux swap / Solaris /dev/sda2 499 121601 972759847+ 5 Extended /dev/sda5 49917431431 83 Linux /dev/sda61744 121601 962759353+ 83 Linux -- kickstart partitioning fails with --recommended or --asprimary https://bugs.launchpad.net/bugs/48311 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338157] [NEW] FAI is out of date
Public bug reported: Latest FAI at http://www.informatik.uni-koeln.de/fai/ is 3.2.16 Latest stable Debian package is also at 3.2.16 http://packages.debian.org/lenny/fai-server This release contains significant improvements including a better partitioning tool. I've been testing FAI on ubuntu and running into lots of small problems even completing the quickstart process - I can document these but may make more sense to start from a newer baseline. Can we get the newest version for Jaunty? ** Affects: fai (Ubuntu) Importance: Undecided Status: New -- FAI is out of date https://bugs.launchpad.net/bugs/338157 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329067] Re: Cannot change password on ldap client unless libpam-cracklib also installed
This is my /etc/pam.d/common-password after recently running another "aptitude upgrade", restoring the problematic line to /etc/pam.d/common- password In this format, if I login as an LDAP user and type passwd, I get the following interaction ste...@apps:~$ passwd Enter login(LDAP) password: passwd: password updated successfully If I now change the line below password[success=1 user_unknown=ignore default=die] pam_ldap.so use_authtok try_first_pass to password[success=1 user_unknown=ignore default=die] pam_ldap.so try_first_pass and then try changing my password again ... ste...@apps:~$ passwd Enter login(LDAP) password: New password: Re-enter new password: LDAP password information changed for stemul passwd: password updated successfully ste...@apps:~$ # # /etc/pam.d/common-password - password-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define the services to be # used to change user passwords. The default is pam_unix. # Explanation of pam_unix options: # # The "sha512" option enables salted SHA512 passwords. Without this option, # the default is Unix crypt. Prior releases used the option "md5". # # The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in # login.defs. # # See the pam_unix manpage for other options. # As of pam 1.0.1-5, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # here are the per-package modules (the "Primary" block) password[success=2 default=ignore] pam_unix.so obscure sha512 password[success=1 user_unknown=ignore default=die] pam_ldap.so use_authtok try_first_pass # here's the fallback if no module succeeds passwordrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around passwordrequiredpam_permit.so # and here are more per-package modules (the "Additional" block) # end of pam-auth-update config ** Changed in: libpam-ldap (Ubuntu) Status: Incomplete => Confirmed -- Cannot change password on ldap client unless libpam-cracklib also installed https://bugs.launchpad.net/bugs/329067 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
We're still seeing occasional machine check events but nothing logged in /var/log/mcelog Feb 25 00:10:46 dev kernel: [110217.794081] Machine check events logged Feb 25 01:13:16 dev kernel: [113958.998576] Machine check events logged and no further soft lockups. -- RAID array causing "BUG: soft lockup" errors/system freeze https://bugs.launchpad.net/bugs/312163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312163] Re: RAID array causing "BUG: soft lockup" errors/system freeze
Hi, I'm seeing a similar problem on my system with frequent soft lockup messages and machine check events logged. Distributor ID: Ubuntu Description:Ubuntu 8.10 Release:8.10 Codename: intrepid Errors with linux-image-2.6.27-11-server (64-bit). It's not clear if there are specific activities triggering the bug. Rolling back to Hardy kernel (linux-image-2.6.24-23-server) seems to have addressed the problem - no error messages in last 12 hours of heavy system activity. System has 2 x Western Digital WDC WD10EADS-00L5B1 drives (1TB) in RAID1 config (for both root partition and swap partition). smulc...@dev:/var/log$ sudo mdadm --misc -D /dev/md1 /dev/md1: Version : 00.90 Creation Time : Mon Feb 9 11:59:43 2009 Raid Level : raid1 Array Size : 974808064 (929.65 GiB 998.20 GB) Used Dev Size : 974808064 (929.65 GiB 998.20 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Tue Feb 24 12:18:54 2009 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : c8cf85b7:a96d5ddf:b32eea70:c5f0704e Events : 0.25 Number Major Minor RaidDevice State 0 820 active sync /dev/sda2 1 8 181 active sync /dev/sdb2 smulc...@dev:/var/log$ sudo mdadm --misc -D /dev/md2 /dev/md2: Version : 00.90 Creation Time : Mon Feb 9 12:29:38 2009 Raid Level : raid1 Array Size : 1951744 (1906.32 MiB 1998.59 MB) Used Dev Size : 1951744 (1906.32 MiB 1998.59 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Tue Feb 24 12:08:02 2009 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 8957636b:79f79a80:9069ef6b:43c30843 Events : 0.8 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 Log file excerpt, Feb 20 10:07:20 dev kernel: [933002.012531] Machine check events logged Feb 20 11:23:39 dev kernel: [937580.632507] BUG: soft lockup - CPU#1 stuck for 61s! [kswapd1:185] Feb 20 11:23:39 dev kernel: [937580.632507] Modules linked in: af_packet ipv6 iptable_filter ip_tables x_tables parport_pc lp parport loop joydev evdev pcspkr container isp1760 amd_rng button i2c_amd756 k8temp shpchp i2c_amd8111 pci_hotplug i2c_core ext3 jbd mbcache sr_mod cdrom pata_acpi sd_mod crc_t10dif sg usbhid hid ata_generic tg3 libphy sata_sil ohci_hcd usbcore pata_amd libata scsi_mod dock raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse Feb 20 11:23:39 dev kernel: [937580.632507] CPU 1: Feb 20 11:23:39 dev kernel: [937580.632507] Modules linked in: af_packet ipv6 iptable_filter ip_tables x_tables parport_pc lp parport loop joydev evdev pcspkr container isp1760 amd_rng button i2c_amd756 k8temp shpchp i2c_amd8111 pci_hotplug i2c_core ext3 jbd mbcache sr_mod cdrom pata_acpi sd_mod crc_t10dif sg usbhid hid ata_generic tg3 libphy sata_sil ohci_hcd usbcore pata_amd libata scsi_mod dock raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse Feb 20 11:23:39 dev kernel: [937580.632507] Pid: 185, comm: kswapd1 Tainted: G M 2.6.27-11-server #1 Feb 20 11:23:39 dev kernel: [937580.632507] RIP: 0010:[] [] find_get_pages+0x77/0x110 Feb 20 11:23:39 dev kernel: [937580.632507] RSP: 0018:88007d5b1bc0 EFLAGS: 0293 Feb 20 11:23:39 dev kernel: [937580.632507] RAX: 880070fd4ae8 RBX: 88007d5b1c00 RCX: 880070fd4ae8 Feb 20 11:23:39 dev kernel: [937580.632507] RDX: RSI: RDI: e261b300 Feb 20 11:23:39 dev kernel: [937580.632507] RBP: 00018031371c R08: R09: 0001 Feb 20 11:23:39 dev kernel: [937580.632507] R10: R11: 0040 R12: 0001 Feb 20 11:23:39 dev kernel: [937580.632507] R13: 802b6ba9 R14: e261b2c0 R15: 0246 Feb 20 11:23:39 dev kernel: [937580.632507] FS: 4020a950() GS:88013f40b300() knlGS:f7bb56b0 Feb 20 11:23:39 dev kernel: [937580.632507] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Feb 20 11:23:39 dev kernel: [937580.632507] CR2: 7fa35c00b000 CR3: 00201000 CR4: 06e0 Feb 20 11:23:39 dev kernel: [937580.632507] DR0: DR1: DR2: Feb 20 11:23:39 dev kernel: [937580.632507] DR3: DR6: 0ff0 DR7: 0400 Feb 20 11:23:39 dev kernel: [937580.632507] Feb 20 11:23:39 dev kernel: [937580.632507] Call Trac
[Bug 329067] [NEW] Cannot change password on ldap client unless libpam-cracklib also installed
Public bug reported: Binary package hint: libpam-ldap I have a working LDAP client config using libnss-ldapd and libpam-ldap. I can login to the system using any valid LDAP user. However, when I attempt to change the password using 'passwd', the following occurs ste...@dev:~$ passwd Enter login(LDAP) password: passwd: password updated successfully ste...@dev:~$ The command returns without ever giving me the chance to change the password (although it does require the correct password to even get this far). Some Googling suggested removing use_authtok from vi /etc/pam.d/common- password changing the line password[success=1 user_unknown=ignore default=die] pam_ldap.so use_authtok try_first_pass to password[success=1 user_unknown=ignore default=die] pam_ldap.so try_first_pass After doing this, I can now change my password using passwd. It looks like use_authtok only makes sense in common-password if you have installed libpam-cracklib or similar - is that correct? Thanks ** Affects: libpam-ldap (Ubuntu) Importance: Undecided Status: New -- Cannot change password on ldap client unless libpam-cracklib also installed https://bugs.launchpad.net/bugs/329067 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319685] Re: Using gosa-encrypt-passwords on a working GOsa install breaks it
If I change step 4. above to sudo vi /etc/apache2/conf.d/gosa.conf and make the change there, the procedure seems to work. However, at least in my case, logins to GOsa now seem to take forever. This may be a quirk of my setup though (in which case this bug should still be resolved by updating the README as per this comment). It would be good if someone else could test this to see if they also get very slow logins to GOsa. -- Using gosa-encrypt-passwords on a working GOsa install breaks it https://bugs.launchpad.net/bugs/319685 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319685] [NEW] Using gosa-encrypt-passwords on a working GOsa install breaks it
Public bug reported: Binary package hint: gosa Description:Ubuntu 8.10 Release:8.10 If I follow this procedure (modified from /usr/share/doc/gosa/README.Debian to include the php5 library required for encryption) on a GOsa installation that is working and allows me to login - it ceases to work afterwards. It looks like the LDAP admin password is corrupted or invalid afterwards. 1. sudo a2enmod headers 2. sudo aptitude install php5-mcrypt 3. sudo gosa-encrypt-passwords 4. Edit the file /etc/gosa/apache.conf and uncomment the following line #include /etc/gosa/gosa.secrets 5.Restart apache sudo /etc/init.d/apache2 restart Is there a bug in the procedure I used or gosa-encrypt-passwords? Error message from GOsa after following the above procedure FATAL: Error when connecting the LDAP. Server said 'Could not bind to cn=admin,dc=example,dc=net (while operating on LDAP server ldaps://ldap.example.net)'. gosa: Installed: 2.5.16.1-3ubuntu1 Candidate: 2.5.16.1-3ubuntu1 Version table: *** 2.5.16.1-3ubuntu1 0 500 http://gb.archive.ubuntu.com intrepid/universe Packages 100 /var/lib/dpkg/status slapd: Installed: 2.4.11-0ubuntu6 Candidate: 2.4.11-0ubuntu6 Version table: *** 2.4.11-0ubuntu6 0 500 http://gb.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status apache2-mpm-prefork: Installed: 2.2.9-7ubuntu3 Candidate: 2.2.9-7ubuntu3 Version table: *** 2.2.9-7ubuntu3 0 500 http://gb.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status ** Affects: gosa (Ubuntu) Importance: Undecided Status: New -- Using gosa-encrypt-passwords on a working GOsa install breaks it https://bugs.launchpad.net/bugs/319685 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319544] [NEW] gosa-schema contains schema with bad char in filename
Public bug reported: Binary package hint: gosa-schema In order to use gosa with OpenLDAP 2.4 which uses an in memory directory information tree (cn=config) for storing configuration information and schema, the schema from the gosa schema package need to be converted to ldif format using the following procedure (for example, adapted from https://help.ubuntu.com/8.10/serverguide/C/openldap-server.html), 1. Put the filenames of schema to be converted into a file (schema_convert.conf) include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/inetorgperson.schema include /etc/ldap/schema/nis.schema include /etc/ldap/schema/samba3.schema include /etc/ldap/schema/trust.schema include /etc/ldap/schema/gosystem.schema include /etc/ldap/schema/gofon.schema include /etc/ldap/schema/goto.schema include /etc/ldap/schema/gofax.schema include /etc/ldap/schema/goserver.schema include /etc/ldap/schema/goto-mime.schema include /etc/ldap/schema/gosa+samba3.schema 2. Create a temporary directory for the output mkdir /tmp/ldif_output 3. Use slaptest to convert the schema to ldif slaptest -f schema_convert.conf -F /tmp/ldif_output If you follow steps 1-3 using the files from gosa-schema as is, you get the following error after running slaptest. backend_startup_one: bi_db_open failed! (-1) slap_startup failed (test would succeed using the -u switch) Some testing and googling reveals that the problem comes from the filename gosa+samba3.schema Renaming this to /etc/ldap/schema/gosa-samba3.schema allows the LDIF conversion to proceed without issue. Can this file be renamed in future releases of the package? thanks, ** Affects: gosa (Ubuntu) Importance: Undecided Status: New -- gosa-schema contains schema with bad char in filename https://bugs.launchpad.net/bugs/319544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
