Two wireshark traces were uploaded. The system crystal3 is the Windows
server. The system fs1 is the Ubuntu server.
--
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/526464
Title:
@Surbhi, unfortunately increasing the log level to 10 caused a
production outage. The high amount of logging overloaded the system and
made it unresponsive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
@Peter, we made all the suggested changes to the multipath.conf file,
but still have the same issue. The root filesystem goes read-only as
soon as multipathd starts. For the sake if time, the OS will now be
installed on an internal drive instead of boot from SAN. I'll post the
results from this
Output from multipath -v4
** Attachment added: multipath_v4_output.txt
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/716659/+attachment/1877247/+files/multipath_v4_output.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
Binary package hint: multipath-tools
Installing either multipath-tools-boot or multipath-tools causes the
- root partition to go 'Read onlyl'. System is then unable to reboot.
- The only way to recover system is to boot in rescue mode and un-install
+ root
@Surbhi, We have logs with the log level set to 5. Will setting the
log level to 10 provide additional valuable data? We would like to
prevent any changes, since this is a production environment, and
changing the log level requires a maintenance window.
--
You received this bug notification
@ Surbhi, thanks for the feedback. I don't see debuglevel in the
smb.conf file. Is the parameter log level = N the same option? In
the previous logs we had this set to 5. I can see if we can increase
it to 10. If debuglevel and log level are different, I can see if
we can add that
We performed a full Wireshark trace when the authentication failure
happens.
It looks like all successful authentications send packets to the domain
controller and perform an LDAP searchRequest. However, when the failures
happen, we don't see any data being sent to the Windows domain
controllers.
@Peter
Thanks for the suggestion. I will report back.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
https://bugs.launchpad.net/bugs/716659
Title:
Root filesystem goes Read only after installing
Public bug reported:
Binary package hint: multipath-tools
Installing either multipath-tools-boot or multipath-tools causes the
root partition to go 'Read onlyl'. System is then unable to reboot.
The only way to recover system is to boot in rescue mode and un-install
multipath-tools.
The
** Attachment added: multipath.conf
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/716659/+attachment/1842127/+files/multipath.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
Logs from system that had this failure.
** Attachment added: Ubuntu-Multipating.Sys-Message-Syslog-log.rar
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/716659/+attachment/1842153/+files/Ubuntu-Multipating.Sys-Message-Syslog-log.rar
--
You received this bug notification
We disabled the AppArmor profile, but there was no effect on this error.
We reviewed the domain controller logs when one of these authentication
failures happened. There was not entry in the domain controller logs
stating that the authentication was attempted. For all successful
This has happened again. Since this is Hardy, there is no apport-
collect. The following information has been added to the bug:
1) uname -a uname-a.log
2) dmesg dmesg.log
3) sudo lspci -vvnn lspci-vvnn.log
4) cat /proc/version_signature version.log
Please let us know if any additional data
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791464/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791465/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791466/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791467/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
One additional detail. The following error was reported on the
application side:
destination file error: CrystalEnterprise.DiskUnmanaged: Access is
denied.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
It looks like the problem has not happened again in a while. I've had
an instance running for almost a month now, and the IP Address has not
been lost:
$ euca-describe-instances
RESERVATION r-44510791 admin default
INSTANCEi-4A870825 emi-230B11AE172.23.46.78
Thank you, Thierry. I will edit the whiteboard to reflect the missing
package.
--
Package sysstat with Ubuntu Server
https://bugs.launchpad.net/bugs/480151
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sysstat in ubuntu.
--
Public bug reported:
Binary package hint: sysstat
Ubuntu Server does not have the sysstat package installed by default.
This package is very important for performance work related to the
Ubuntu Server.
I'd like to add request to the wish list to have the sysstat package
shipped with Ubuntu
I re-ran all of the tests using the latest in karmic-proposed. All
tests passed:
$ dpkg -l | grep qemu
ii qemu-kvm 0.11.0-0ubuntu6.3 Full
virtualization on i386 and amd64 hardwa
Test 1: VT Enabled in BIOS(On a machine that supports VT):
$ kvm-ok
I can give this a test today. I will post feedback shortly.
--
kvm disabled in bios (was: Unable to start EUC instances - no supported
architecture for os type 'hvm')
https://bugs.launchpad.net/bugs/452323
You received this bug notification because you are a member of Ubuntu
Server Team, which
Here are the results from my testing:
Test 1: VT Enabled in BIOS(On a machine that supports VT):
$ kvm-ok
INFO: Your CPU supports KVM extensions
INFO: /dev/kvm exists
KVM acceleration can be used
Test 2a: (run this on a system that does not support VT)
j...@jts-ubuntu:/etc/apt$ kvm-ok
INFO:
One other thing to note. The following is the output of euca-describe-
instances from this morning. Before the issue was reproduced:
$ euca-describe-instances
RESERVATION r-39C7074C admin default
INSTANCEi-46910829 emi-230B11AE172.23.46.78172.19.1.2
running
Looks like I just reproduced it after seven days:
$ euca-describe-instances
RESERVATION r-39C7074C admin default
INSTANCEi-46910829 emi-230B11AE172.19.1.2 172.19.1.2
running mykey 0 c1.medium 1970-01-01T00:00:00.813Z
ubuntucluster1
I restarted my instance on Monday after the public IP address changed.
The initial issue happened after three days. However, it's now been
four days, and I have not been able to reproduce it again. It now seems
there is not a pre-determined amount of time before the IP address
expires.
I'll
I'm reviewing the logs now to see if there are additional details.
I think the max-lease-time is running out which is defined in
/etc/dhcp3/dhcpd.conf. The two configurable settings are:
default-lease-time 600;
max-lease-time 7200;
7200 is three days, which is the right about when my public IP
Public bug reported:
I started an instance, which was assigned an IP Address from the cluster
DHCP. However, after a couple of days, the instance was no longer using
the IP address from DHCP, and would only respond to the private IP
Address.
This is what euca-describe-instance reported
I checked the bios and found that VT extensions were not enabled. I
enabled them and was able to start my instance :-)
However, I ran into an issuing the ssh command listed in the test case:
$ ssh -i mykey.priv ubu...@$ipaddr
Permission denied (publickey).
I'll investigate this further.
I
Public bug reported:
I'm having an issue starting an instance. I see errors stating disk
not found and no domain with matching name found. I'm also seeing an
error saying no supported architecture for os type 'hvm':
Snippet from nc.log:
[Wed Oct 14 14:57:00 2009][001691][EUCAINFO ] currently
Restarting libvirt and eucalyptus-nc did not seem to work around the
issue. Just to make sure I restarted things properly here is what I did
on the Node Controller:
eqlu...@granada:~$ sudo /etc/init.d/libvirt-bin restart
* Restarting libvirt management daemon /usr/sbin/libvirtd [
Contents of /var/log/eucalyptus/euca_test_nc.log:
This is perl, v5.10.0 built for i486-linux-gnu-thread-multi
Copyright 1987-2007, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Hmm. I wonder if this could be related to the bios. I'll check it to
ensure the correct settings are enabled for KVM. Could an error like
this occur if the bios was not setup correctly?
--
Unable to start EUC instances - no supported architecture for os type 'hvm'
I think I found the issue:
kern.log:Oct 13 15:53:45 granada kernel: [7.832803] kvm: disabled by
bios
I will correct the bios and re-test.
--
Unable to start EUC instances - no supported architecture for os type 'hvm'
https://bugs.launchpad.net/bugs/452323
You received this bug notification
I like your option. If a test case was automated, a check could be
performed first :-) As long as that error is always reported by dmesg
when the bios is not enabled :-)
--
kvm disable in bios (was: Unable to start EUC instances - no supported
architecture for os type 'hvm')
I opened a duplicate bug: 451291
--
euca-describe-images reports all UEC images as x86_64
https://bugs.launchpad.net/bugs/451358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
UEC Installer Only Configures One Network Interface
https://bugs.launchpad.net/bugs/448036
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Attaching a modified /etc/network/interfaces that allowed the network to
start.
** Attachment added: interfaces.working.txt
http://launchpadlibrarian.net/33521281/interfaces.working.txt
--
uec node cd install doesn't handle static network configuration
https://bugs.launchpad.net/bugs/446023
Attaching the broken /etc/network/interfaces from my configuration.
** Attachment added: interfaces.bad
http://launchpadlibrarian.net/33521225/interfaces.bad
--
uec node cd install doesn't handle static network configuration
https://bugs.launchpad.net/bugs/446023
You received this bug
101 - 141 of 141 matches
Mail list logo
